Package: release.debian.org Severity: normal User: release.debian....@packages.debian.org Usertags: transition
(sorry for double email, I just found the release.debian.org transition bugtracker) Hi, I would like to coordinate reduction of BDB packages since I took the unhappy job (as I could expect) to maintain BDB in Debian after Clint have orphaned them. The main issue which I have encountered (in cyrus-imapd) is that the change from 4.x to 5.x introduces code changes, because the packages check for 4 + something version number. The fix is easy (I can help with that if needed), but it still some work which needs to be done. My suggestion is (going one at the time starting with db4.6): 1) Fill bugreports against all packages linking to db4.Y to upgrade build depends to libdb-dev (>= 5.1) or at least to libdb5.1-dev (which makes later transitions harded). 1a) Optionally link with just -ldb and not -ldbX.Y (linking to specific BDB versions generate a lot of problems, since f.e. cyrus-imapd will happily include 5.1 headers and link to libdb4.7) 2. After some time rebuild the db4.Y to not generate -dev packages, but to keep db4.Y-util package available and increase severity 3. After some time rebuild the db4.Y to not generate libdb4.Y packages, but keep db4.Y-util package available and increase severity of the bug reports to RC Release next stable with just one libdbX.Y-dev (and libdb-dev) and all dbM.N-util which were included in current stable. For stable+2 reduce the number to just two version - current -dev and dbX.Y-util for stable+1 upgrades. I know this could cause a lot of pain, but I think the keeping of X > 2 versions of BDB is not sustainable from a long term PoV. Also any help would be much appreciated, I am already too overloaded, and I took BDB maintainership just because of cyrus-imapd sake, so if there are any other heavy BDB users, please come and join the packaging team (especially if you use BDB transactional mode). Affected packages: db4.6 (first in row): ----- bind9 (binNMU with small patch needed) dsniff (binNMU OK) guile-db (no upload since 2008) hpsockd (no upload since 2008) isync (nmued, no upload since 2008) libnss-db (nmued, no upload since 2009) mmorph (removed from testing, no upload since 2008) pkspxy (no upload since 2007) qtstalker (no upload since 2008) db4,7: ----- batv-milter claws-mail dkim-milter dnshistory drac etpan-ng hotkeys httest jabberd2 kolab-cyrus-imapd libetpan memcachedb nmh nvi perl radiusd-livingston skktools sks squidguard db4,8: ----- apr-util bmf bogofilter cairo-dock-plugins chise-base citadel clisp cyrus-sasl2 dovecot evolution-exchange exim4 ggz-server gridengine heimdal iproute jigdo kdesvn libapache2-mod-perl2 libapache2-mod-qos libdb-ruby libpam-ccreds librcc log4cxx mailavenger moc netatalk nss-updatedb onak opendkim openldap pam perdition php5 poedit python-bsddb3 python2.5 python2.6 python2.7 python3.1 rapidsvn redland rpm sendmail skksearch spamprobe squid3 subversion tcpstat webalizer webdruid xastir xemacs21 O. -- System Information: Debian Release: squeeze/sid APT prefers maverick-updates APT policy: (500, 'maverick-updates'), (500, 'maverick-security'), (500, 'maverick-proposed'), (500, 'maverick-backports'), (500, 'maverick') Architecture: amd64 (x86_64) Kernel: Linux 2.6.35-28-generic (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110406144301.1382.36343.reportbug@localhost6.localdomain6
