[Bug 519654] [NEW] mailman archiving sorting broken
Richard Tew
richard.m.tew at gmail.com
Wed Feb 10 07:22:12 CET 2010
Public bug reported:
This bug is for Mailman 2.1.x. Checking the mailman/2.1 branch shows
that the problem still exists there. I am aware the focus is now on the
3.x branches. I am reporting this in case development is still being
done on this branch.
Pipermail has indexes by subject, author and date. It stores by a tuple
typed key.
When doing the default threading approach, HyperDatabase calls
getOldestArticle with the subject.
def getOldestArticle(self, archive, subject):
self.__openIndices(archive)
subject = subject.lower()
try:
key, tempid=self.subjectIndex.set_location(subject)
self.subjectIndex.next()
[subject2, date]= key.split('\0')
if subject!=subject2: return None
return tempid
except KeyError:
return None
Note the key used in the index operation is a string. This will always
fail, because it is not the specialised article specific tuple that was
actually used as a key by pipermail.
This bug was also reported here (but is attached to a milestone I cannot change):
https://bugs.launchpad.net/mailman/+bug/266572
** Affects: mailman
Importance: Undecided
Status: New
--
mailman archiving sorting broken
https://bugs.launchpad.net/bugs/519654
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
More information about the Mailman-coders
mailing list