Hi - (Would a/the Debian developer with responsibility for the problem causing package please respond to this? Thank you! :) )
Thanks everyone for the great work on Debian! (This isn't a demand - just a plea for help!) I believe a serious problem exists: My requests are: Immediately: 1. Would someone please provide a reply email with a workaround for this bug? 2. Would someone please get this bug fixed? In the longer term: 3. Would someone care to develop a system to prevent this kind of bug? TIA! (I am posting this to debian-user so P -> W upgraders see proposed solutions. I am posting this to debian-devel so a developer who might be able to fix this becomes aware of this issue. I am posting this to debian-kde since any persons new to Debian via interest in installing the new KDE 2.2 will need to get at least a W/testing system installed in order to be able to install KDE 2.2 for Debian.) ************************************************************************** ************************************************************************** The detaiils: I believe a serious problem exists: There is a problem preventing the upgrade from Potato to Woody, and this problem appears to have existed for almost 3 weeks at least. I would think that such a case would be considered a severe bug. It is very bad to have _all_ people trying to install a clean W/Testing system to encounter such a bug. This bug probably requires many hours for each user to search for and implement a fix. I think it really hurts Debian, since it prevents people from trying out Woody/testing, putting a bottleneck in the debugging effort. I am not a Debian developer, I am trying to do this dist-upgrade. I do not know where to submit this as a bug, I hope (and am depending on you, dear reader) someone will get this submitted to the proper authority. In a larger sense, though: Would it be possible for such a bug (the submission of a package that breaks the P -> W upgrade) to be automatically detected, and prevent any such breaking package from going from Unstable -> W? Could a script be run against each .deb package, before it is moved from unstable to testing, that tries to do the upgrade from P -> W, and flags the package as unacceptable if the upgrade is unsuvessful, and notifies the package maintainer of that fact? ************************************************************************** ************************************************************************** The details: Some History: From: http://lists.debian.org/debian-user/2001/debian-user-200108/threads.html potato to sid upgrade error 32 broken pipe http://lists.debian.org/debian-user/2001/debian-user-200108/msg00019.html error message with "libdb.so.3" http://lists.debian.org/debian-user/2001/debian-user-200108/msg00269.html From: http://lists.debian.org/debian-user/2001/debian-user-200108/thrd5.html libdb.so.3 http://lists.debian.org/debian-user/2001/debian-user-200108/msg01986.html In essence, the problem is: 1. Starting from a basic Potato system (no tasks selected from tasksel during the install, and merely ~5MB of packages installed automatically at the end of the P install process): 2. Change /etc/apt/sources.list stable -> testing 3. apt-get update 4. apt-get dist-upgrade (or, (the latest suggestion on this problem) apt-get upgrade libdb2 , as shown here, suggested by: http://lists.debian.org/debian-user/2001/debian-user-200108/msg03112.html ) fails. ************************************************************************** ************************************************************************** Here's what I last tried: debian:/lib# l libdb* -rw-r--r-- 1 root root 237944 Aug 19 06:30 libdb-2.1.3.so lrwxrwxrwx 1 root root 15 Aug 19 17:15 libdb.so.2 -> libdb1-2.1.3.so lrwxrwxrwx 1 root root 14 Aug 19 17:15 libdb.so.3 -> libdb-2.1.3.so -rw-r--r-- 1 root root 50848 Aug 19 06:30 libdb1-2.1.3.so lrwxrwxrwx 1 root root 15 Aug 19 17:15 libdb1.so.2 -> libdb1-2.1.3.so debian:/lib# apt-get upgrade libdb2 . . Preparing to replace libreadline4 4.1-1 (using .../libreadline4_4.2-5_i386.deb) ... perl: error while loading shared libraries: libdb.so.3: cannot open shared object file: No such file or directory . . debian:/lib# l libdb* lrwxrwxrwx 1 root root 15 Aug 19 18:31 libdb.so.2 -> libdb1-2.2.3.so lrwxrwxrwx 1 root root 14 Aug 19 18:31 libdb.so.3 -> libdb.so.3.old -rw-r--r-- 1 root root 50884 Jul 27 13:42 libdb1-2.2.3.so lrwxrwxrwx 1 root root 15 Aug 19 18:31 libdb1.so.2 -> libdb1-2.2.3.so >From my user (not develpoer) level perspective it appears that maybe: The upgrade of libdb2 is failing because libdb.so.3 points to a non existent file at the time when libdb.so.3 must point to a real file. ************************************************************************** ************************************************************************** Here's the complete details: debian:/lib# l libdb* -rw-r--r-- 1 root root 237944 Aug 19 06:30 libdb-2.1.3.so lrwxrwxrwx 1 root root 15 Aug 19 17:15 libdb.so.2 -> libdb1-2.1.3.so lrwxrwxrwx 1 root root 14 Aug 19 17:15 libdb.so.3 -> libdb-2.1.3.so -rw-r--r-- 1 root root 50848 Aug 19 06:30 libdb1-2.1.3.so lrwxrwxrwx 1 root root 15 Aug 19 17:15 libdb1.so.2 -> libdb1-2.1.3.so debian:/lib# date Sun Aug 19 17:46:52 PDT 2001 debian:/lib# l /var/cache/apt/ total 2492 drwxr-xr-x 3 root root 28672 Aug 19 13:39 archives -rw-r--r-- 1 root root 1254314 Aug 19 13:46 pkgcache.bin -rw-r--r-- 1 root root 1254246 Aug 19 13:44 srcpkgcache.bin debian:/lib# apt-get update Fetched 1476kB in 8m4s (3049B/s) Reading Package Lists... Done Building Dependency Tree... Done debian:/lib# apt-get upgrade libdb2 Reading Package Lists... Done Building Dependency Tree... Done The following packages have been kept back adduser apt base-config console-data console-tools console-tools-libs dpkg exim groff libpam-modules lilo man-db netbase perl-5.005 perl-5.005-base perl-base sysklogd util-linux 73 packages upgraded, 0 newly installed, 0 to remove and 18 not upgraded. Need to get 0B/15.8MB of archives. After unpacking 6108kB will be used. Do you want to continue? [Y/n] y [Scanning packages] Configuring packages ... Reading database ... 6645 files and directories currently installed.) . . . (Reading database ... 6576 files and directories currently installed.) Preparing to replace libreadline4 4.1-1 (using .../libreadline4_4.2-5_i386.deb) ... perl: error while loading shared libraries: libdb.so.3: cannot open shared object file: No such file or directory dpkg: warning - old pre-removal script returned error exit status 127 dpkg - trying script from the new package instead ... perl: error while loading shared libraries: libdb.so.3: cannot open shared object file: No such file or directory dpkg: error processing /var/cache/apt/archives/libreadline4_4.2-5_i386.deb (--unpack): subprocess new pre-removal script returned error exit status 127 perl: error while loading shared libraries: libdb.so.3: cannot open shared object file: No such file or directory dpkg: error while cleaning up: subprocess post-installation script returned error exit status 127 Errors were encountered while processing: /var/cache/apt/archives/libreadline4_4.2-5_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) debian:/lib# l libdb* lrwxrwxrwx 1 root root 15 Aug 19 18:31 libdb.so.2 -> libdb1-2.2.3.so lrwxrwxrwx 1 root root 14 Aug 19 18:31 libdb.so.3 -> libdb.so.3.old -rw-r--r-- 1 root root 50884 Jul 27 13:42 libdb1-2.2.3.so lrwxrwxrwx 1 root root 15 Aug 19 18:31 libdb1.so.2 -> libdb1-2.2.3.so debian:/lib# l t* -rw-r--r-- 1 root root 94208 Aug 19 18:31 typescript -rw-r--r-- 1 root root 6264 Aug 19 16:45 typescript.b00 Script done on Sun Aug 19 18:33:35 2001 ************************************************************************** ************************************************************************** Thanks for your great work, and help. :) __________________________________________________ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/