Hi! I recompiled man-db as it was (no change) and reuploaded. As someone made me notice, the pure rebuild had few bytes of difference, so maybe we get a different result. Can people try the upgrade from 2.3.13 ?? And can that people that got the error try to downgrade to slink version and then upgrade to the new one? This is the real upgrade that bother me.
If nobody will report any problem, I'll close the bugs. fab ----- Forwarded message from Debian Installer <[EMAIL PROTECTED]> ----- Delivered-To: [EMAIL PROTECTED] Date: 23 Mar 2000 12:24:17 -0000 From: Debian Installer <[EMAIL PROTECTED]> To: Fabrizio Polacco <[EMAIL PROTECTED]> Subject: man-db_2.3.15_i386.changes INSTALLED Installing: man-db_2.3.15.tar.gz to dists/potato/main/source/doc/man-db_2.3.15.tar.gz replacing man-db_2.3.14.tar.gz man-db_2.3.15.tar.gz to dists/woody/main/source/doc/man-db_2.3.15.tar.gz replacing man-db_2.3.14.tar.gz man-db_2.3.15.dsc to dists/potato/main/source/doc/man-db_2.3.15.dsc replacing man-db_2.3.14.dsc man-db_2.3.15.dsc to dists/woody/main/source/doc/man-db_2.3.15.dsc replacing man-db_2.3.14.dsc man-db_2.3.15_i386.deb to dists/potato/main/binary-i386/doc/man-db_2.3.15.deb replacing man-db_2.3.14.deb man-db_2.3.15_i386.deb to dists/woody/main/binary-i386/doc/man-db_2.3.15.deb replacing man-db_2.3.14.deb Changes: man-db (2.3.15) frozen unstable; urgency=high . * Just recompiled, with an upgraded potato system. Let's see if this wipes away the grave installation problem listed in bugs #60339, #60399, #60411, #60515. In that case, I'll close these bugs by hand :-) Announcing to debian-devel-changes@lists.debian.org Closing bugs: If the override file requires editing, reply to this email. Thank you for your contribution to Debian GNU/Linux. ----- End forwarded message ----- -- | [EMAIL PROTECTED] [EMAIL PROTECTED] | pgp: 6F7267F5 57 16 C4 ED C9 86 40 7B 1A 69 A1 66 EC FB D2 5E | [EMAIL PROTECTED] gsm: +358 (0)40 707 2468