Changes between Version 10 and Version 11 of MostFrequentDuplicates

Timestamp:

Jun 3, 2011, 9:43:00 PM (13 years ago)

Author:

Christian Boos

Comment:

New entry for the "upgrade to 0.12 / reuse 0.11" problem with timestamps

MostFrequentDuplicates

@@ -4 +4 @@
 
 Here's a short list of the issues with a pathologically high duplicate rate:
+ - #9403: '''!ValueError: timestamp out of range for platform time_t''' ([search:'"ValueError: timestamp out of range for platform time_t"' see all])
+     ''This is not even a bug, rather an installation issue. This is typically seen when upgrading a Trac installation to 0.12 then downgrading to 0.11 again. During the upgrade, the timestamps previously stored as number of seconds since Unix epoch were converted to microseconds. If the Trac 0.11 code sees that database again, it won't be able to deal with these larger values correctly and will throw this error. Solution: make sure you're using 0.12 (or at worst, revert to the backup database generated during the upgrade) ''
 
  - #5028: '''!TracError: Unsupported version control system "svn"''' 
    ([search:'!TracError: Unsupported version control system "svn"' see all])
-     ''This is not even a bug, rather an installation issue. The error means that for some reason, the Python bindings to the Subversion libraries couldn't be found or loaded. The TracSubversion page provides detailed [TracSubversion#Troubleshooting troubleshooting] information. In Trac [milestone:0.11], if this problem happens, it will only be reported as a warning for non-repository related pages. It's planned to improve the error message even further (#6796)''
+     ''Also an installation issue. The error means that for some reason, the Python bindings to the Subversion libraries couldn't be found or loaded. The TracSubversion page provides detailed [TracSubversion#Troubleshooting troubleshooting] information. In Trac [milestone:0.11], if this problem happens, it will only be reported as a warning for non-repository related pages.''
+     The error message has been improved, so this issue is less frequently reported now (#6796)''
 
  - #3839: '''Authentication information not available.'''