Bug#165921: acknowledged by developer (Re: Bug#165921: libc6: Please use debconf to warn of likely breakage on major upgrade)
At Tue, 19 Oct 2004 17:24:47 +0200,
Adrian Bunk wrote:
> On Tue, Oct 12, 2004 at 09:00:45AM +0900, GOTO Masanori wrote:
> > At Mon, 11 Oct 2004 22:47:33 +0200,
> > Adrian Bunk wrote:
> > > > Nowadays "restarting services" question is ready for noninteractive
> > > > upgrade. We assume "Yes" at that mode. So if you want to use debconf
> > > > for noninteractive upgrade, it's already fixed. If you have no
> > > > objection, I'll close it.
> > >
> > > You might not like my answer, but to be honest, I still don't like
> > > questions being asked during postinst even for interactive upgrades.
> >
> > Then how about Ben's comment; ie. debconf may not be available. If
> > you don't have any proposed ways, then the answer is: unfortunatelly
> > no.
>
> Shouldn't it be possible to use debconf if it is available?
>
> debconf should work both at configuration prior to installation and at
> the time postinst runs.
Then how to detect whether it's available or not?
Note that it seems the time is over - I put -18, and at least I don't
have plan to modify it until sarge release.
Regards,
-- gotom
Reply to: