On Fri, Jun 1, 2012 at 4:48 PM, Peter Samuelson <pe...@p12n.org> wrote: > (Aside: half this NMU will be reverted or modified anyway. I explained > in #621460 why we have to be explicit about db versions, but Ondrej's > NMU says libdb-dev with no qualifications. And I'll probably revert > the libsvn-java split, as multiarch for java makes little sense.)
I did reply you: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621460#34 and you didn't respond from that time at all. There's really no reason to depend on specific libdbX.Y-dev version and dbX.Y-util, you would only break the ability to do binNMUs when needed to switch the default db version in the unstable archive. I would be happy to work with you on a viable solution to allow binNMUs and yet keep you reasonable asured that nothing will break - the procedure of upgrading Berkeley DB environment is well documented and works reasonably well. The approach taken by cyrus-imapd-2.4 (f.e.)[1] is to note the Berkeley DB database version used in previous version and do something (upgrade the database, print debconf message) if that differ from a newly installed version. Again I would be happy to help to write such logic into maintainer scripts. Links: 1. http://anonscm.debian.org/gitweb/?p=pkg-cyrus-imapd/cyrus-imapd-2.4.git;a=blob;f=debian/cyrus-upgrade-db Ondrej -- Ondřej Surý <ond...@sury.org> -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
