Colin Watson wrote:
> OK, let's try this, moving the common show() code into
> Debconf::Element::Noninteractive:
>
> http://patches.ubuntulinux.org/patches/debconf.238301.v2.diff
>
> Tested with debootstrap, same changes. I'll probably put this version
> into Ubuntu for now at least.
Feel free
On Wed, Sep 29, 2004 at 07:13:56PM -0400, Joey Hess wrote:
> Colin Watson wrote:
> > That's possible ... suggestions for naming of the common class? I'd been
> > thinking the new classes were small enough not to matter too much.
> >
> > Maybe some magic could go into Debconf::Element::Noninteracti
Colin Watson wrote:
> That's possible ... suggestions for naming of the common class? I'd been
> thinking the new classes were small enough not to matter too much.
>
> Maybe some magic could go into Debconf::Element::Noninteractive.
Yes, it seems to me most noninteractive elemenets could just der
On Wed, Sep 29, 2004 at 06:25:06PM -0400, Joey Hess wrote:
> Colin Watson wrote:
> > This patch implements a DEBCONF_NONINTERACTIVE_SEEN environment variable
> > that debootstrap can set to make the noninteractive frontend behave a
> > little differently, without risking breaking other uses of the
Colin Watson wrote:
> This patch implements a DEBCONF_NONINTERACTIVE_SEEN environment variable
> that debootstrap can set to make the noninteractive frontend behave a
> little differently, without risking breaking other uses of the
> noninteractive frontend. What do you think?
This looks reasonabl
On Thu, Jul 29, 2004 at 02:32:58PM -0400, Joey Hess wrote:
> Mark Brown wrote:
> > I've found some more instances of this problem. I managed to catch a
> > diff of the config files before and after the upgrade, though I didn't
> > remember to rerun the upgrade or cache the entire database:
>
> No
On Thu, Jul 29, 2004 at 02:32:58PM -0400, Joey Hess wrote:
> I don't know of a good way to avoid this at this time; debconf's
> handling of the seen flag for the noninteractive frontend is basically
> correct; debootstrap's use of the noninteractive frontend is correct,
> and there's no way d-i ca
Mark Brown wrote:
> I've found some more instances of this problem. I managed to catch a
> diff of the config files before and after the upgrade, though I didn't
> remember to rerun the upgrade or cache the entire database:
Now I understand. This is because debootstrap installs packages using
the
On Tue, Mar 16, 2004 at 10:56:22PM -0500, Joey Hess wrote:
> Mark Brown wrote:
> > It seems to be happening an awful lot - I'd suggest including some kind
> > of automated reinstall of all the packages in the testing of the
> > installer (next time I do an install I'll probably give this a whirl).
On Tue, Mar 16, 2004 at 10:56:22PM -0500, Joey Hess wrote:
> I can't imagine how it could happen at all without some great care being
> taken to make debconf behave in a way it truely does not want to, or a
> debconf behavior I am not anticipating. Can you provide an example of a
> debconf databas
Mark Brown wrote:
> On Tue, Mar 16, 2004 at 01:14:19PM -0500, Joey Hess wrote:
> > Mark Brown wrote:
>
> > > During the installer run many packages (for example, setserial) appear
> > > to get installed without their debconf configuration scripts being run.
> > > This means that when the packages
Processing commands for [EMAIL PROTECTED]:
> clone 238301 -1
Bug#238301: After installer has run many debconf questions are not seeded
Bug 238301 cloned as bug 238390.
> reassign -1 setserial
Bug#238390: After installer has run many debconf questions are not seeded
Bug reassigned from p
clone 238301 -1
reassign -1 setserial
thanks
On Tue, Mar 16, 2004 at 01:14:19PM -0500, Joey Hess wrote:
> Mark Brown wrote:
> > During the installer run many packages (for example, setserial) appear
> > to get installed without their debconf configuration scripts being run.
> > This means that whe
On Tue, Mar 16, 2004 at 01:14:19PM -0500, Joey Hess wrote:
> Mark Brown wrote:
> > During the installer run many packages (for example, setserial) appear
> > to get installed without their debconf configuration scripts being run.
> > This means that when the packages get upgraded they prompt for
>
Mark Brown wrote:
> During the installer run many packages (for example, setserial) appear
> to get installed without their debconf configuration scripts being run.
> This means that when the packages get upgraded they prompt for
> configuration.
Incorrect, they are installed in the normal way but
Package: debian-installer
Version: As of 20040412
Severity: normal
During the installer run many packages (for example, setserial) appear
to get installed without their debconf configuration scripts being run.
This means that when the packages get upgraded they prompt for
configuration.
While thi
16 matches
Mail list logo
