Bug#165921: acknowledged by developer (Re: Bug#165921: libc6: Please use debconf to warn of likely breakage on major upgrade)
On Sat, Nov 09, 2002 at 12:00:57PM +0100, Adrian Bunk wrote:
> On Fri, Nov 08, 2002 at 10:12:24AM -0500, Ben Collins wrote:
> > On Fri, Nov 08, 2002 at 01:51:47PM +0100, Adrian Bunk wrote:
> > >
> > > Technically the following solution should be possible (pseudocode):
> >
> > Not to mention that even if debconf is installed, nothing says that the
> > system (especially during a libc6 upgrade) is in any state to start
> > debconf up.
>
> At least in the case when apt-utils is installed on the system the
> debconf questions are asked at a time when tho libc upgrade hasn't even
> started.
>
> Besides my impression with many libc upgrades on Debian machines is that
> there's at any time a usable libc installed, or are you thinking of a
> specific problem I don't know of?
Just because there's a usable libc, doesn't mean everything else is
usable. Go back through the archives of what happens what people hit ^C
during a libc install (even after unpack).
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
Deqo - http://www.deqo.com/
Reply to: