[Zope] ZODB packaging behaviour: bug or feature?

[Tim Peters]

[Tim Peters]
>> If you're using a current ZODB (anything at or after 3.2.1c1;
>> 3.2.5 is the latest stable release in the 3.2 line), an attempt to
>> pack to a time earlier than the most recent time ever packed to
>> shouldn't do anything more than raise a FileStorageError with
>> this detail:
>>
>>     The database has already been packed to a later time
>>     or no changes have been made since the last pack

[Chris Withers]
> I'm sure I remember discussions where it was agreed that this
> annoying behaviour would be dropped?
> (or at least turned into a subclass that could be easily caught,
> rathe than having to catch FileStorageError and then do a string
> comparison o the exception arguments :-( )

It was changed (to log a message instead).  I see that it's in ZODB
3.3 (under svn), but not on the Zope-2_7-branch branch of ZODB3 (under
CVS).  Don't know what happened there.  Looks like we're missing
several changes that were checked in -- maybe they're only on ZODB3
HEAD?  Something's screwed up here indeed.

>> Manually packing the database to 0 is a novel meaning
>> for "never packed the database to 0 days" <wink>.

> Why not? (sorry for being slow)

No idea what you're asking here.