2.3/Sid release engineering (was Re: Missing autoconf build-dependancy in cyrus-imapd-2.3 branch ?)

[Benjamin Seidenberg]

I'd like to see a bit more research on the issue to be comfortable, to
make sure this is true in all cases, not just the case on your server.

Sven Mueller wrote:
> For the record:
> Upgrading Berkeley DB files from 4.2 to 4.7 doesn't change the DB file
> (or any other file in the directory, including subdirectories, for that
> matter). So we could simply s/BerkeleyDB4.2/BerkeleyDB4.7/ on
> /usr/lib/cyrus/cyrus-db-types.active on upgrades.
>
> Nice thing, removes the biggest obstacle I saw in upgrading...
>
> Now the remaining question is wether a package upgrade from 2.2 to 2.3
> simply works or not (possibly due to some additional features that need
> to be configured). But I don't think we would have any problem there...
>
> Regards,
> Sven
>
> Sven Mueller schrieb:
>   
>> Duncan Gibb schrieb:
>>     
>>> Sven Mueller wrote:
>>>
>>> DG> a bit more release engineering will be required before we
>>> DG> upload to Sid, I think...
>>>
>>> SM> I took some time today to start developing a script which
>>> SM> would upgrade all BerkeleyDB-Files as needed. Point is: At
>>> SM> least from the currently used 4.2 to 4.6 (which seems to be
>>> SM> the most recent version in unstable), a db4.6_upgrade on a
>>> SM> 4.2 db file reports a successful upgrade without changing a
>>> SM> single byte of the db file. So in this special case, we
>>> SM> wouldn't need to do anything at all, it seems, except
>>> SM> perhaps to automatically change the cyrus-db-types.active
>>> SM> file to reflect the now-used BerkeleyDB engine.
>>>
>>> That's great - thank you.
>>>
>>> Sid and Squeeze are both carrying libdb4.7 for a reasonable spread of
>>> architectures.
>>>
>>> We (Sirius) had some issues with 4.6 on in-house builds, which looked
>>> similar to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510270
>>> Under pressure of time we decided to backport 4.7 to Lenny rather than
>>> figure out what the real problem was...
>>>
>>> Will make time to look at this properly RSN, honest ;-)
>>>       
>> I will now build a 4.7 backport, too (didn't find the db4.7 stuff
>> because it is in pool/main/d/db, not in directories carrying the version
>> number like with the 4.* versions up to 4.6). Will try what the upgrade
>> does from 4.7 later today and report back.
>>
>> If an actual upgrade is needed, I will try to write a sufficient script
>> to automatically update all DB files used, even by non-standard
>> installations (like mine ;-)).
>>
>> Regards,
>> Sven
>>
>>
>> PS: No need to Cc: me.
>>
>> _______________________________________________
>> Pkg-Cyrus-imapd-Debian-devel mailing list
>> Pkg-Cyrus-imapd-Debian-devel at lists.alioth.debian.org
>> http://lists.alioth.debian.org/mailman/listinfo/pkg-cyrus-imapd-debian-devel
>>     
>
> _______________________________________________
> Pkg-Cyrus-imapd-Debian-devel mailing list
> Pkg-Cyrus-imapd-Debian-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/pkg-cyrus-imapd-debian-devel
>   


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-cyrus-imapd-debian-devel/attachments/20090629/b93faa2d/attachment.pgp>