Bug#165921: libc6: Please use debconf to warn of likely breakage on major upgrade
Package: libc6
Version: 2.3.1-3
Followup-For: Bug #165921
As someone who blundered into the libc6 upgrade because it was a
dependency for something else I upgraded (vncserver as it happens), I
would have appreciated a slightly bigger warning that I was likely to
break things.
Of course I understand that when living on the testing branch things
like this happen from time to time. Like the half of mild, I'm not
bitter.
Such a debconf warning may also be a convenient place to warn of
breakage to commercial packages (eg. Sun JDK <= 1.4.0) and request
that bugs are filed where they belong, not with libc6.
Sorry, no patch. 8-/
Matthew #8-)
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux troop.granta.internal 2.4.5 #1 Wed Mar 6 19:11:51 GMT 2002 i686
Locale: LANG=en_GB.ISO-8859-1, LC_CTYPE=en_GB.ISO-8859-1
Versions of packages libc6 depends on:
ii libdb1-compat 2.1.3-6 The Berkeley database routines [gl
-- no debconf information
Reply to: