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
