Bernhard R. Link wrote on 13/05/2006 19:19: > * Sven Mueller <[EMAIL PROTECTED]> [060512 22:16]: > >>libdb3 is really outdated and is supposed to get removed from testing >>before etch is released. It would be a pity if reprepro would be removed >>as well because it depends on libdb3. >>If you need help getting reprepro to work with libdb4, I _might_ be able >>to help (if time permits). Note that I'm far from being a libdb guru >>though, I never used it in my own projects. > > It looks like it can relatively easily ported to newer libdb4.4 with > only some additional NULL arguments to some DB->open calls.
That's most of what needed to be done for cyrus-imapd, right. > The things that until now have hold me back are: > - there is no libdb-4.* in woody. A bit sad, but yes. But to be totally honest, I don't know why anyone would still want to use the 5 year old woody now that sarge has been out for wll more than half a year. > - database files modified with libdb-4.4 may be unreadable > with libdb3 s/may be/will/, at least as far as I can tell. > - I've worked around so many quirks in libdb3 that I am > afraid what new ones they implemented for the ones > they fixed. :-/ This would be a quite funny remark if it ain't so sad. > Especially the second point is important to me. I'll do some more > research if it at least fails gracefully in such cases. As far as I remember (though I'm not 100% sure), it will fail to open libdb4 files completely. It doesn't corrupt them. Unfortunately, the same seems to be true for the libdb4.2->libdb4.4 transition (they need to get updated by the associated upgrade tool shipped with libdb4.x-utils. I certainly hate it when some so-called-DB-library changes file formats in an incompatible way even with minor revisions. However, it is still true that libdb3 is supposed to get removed from etch. Reprepro is one of the few (about 5) last packages depending on it. Regards, Sven
signature.asc
Description: OpenPGP digital signature
