Am Sa, 25. Sep 2004, 18:57:59 +0200 schrieb Jö Fahlke:
> I'll try to prepare a patch doing just that.
Here it is. It is a simple s,debconf/frontend,DEBIAN_FRONTEND, on
installer/doc/manual/en/boot-installer/parameters.xml. All other
occurences either turn out to be something like
/usr/lib/debcon
Am Do, 23. Sep 2004, 17:28:34 +0200 schrieb Joey Hess:
> I don't feel comfortable applying this because it breaks anything that
> currently uses DEBIAN_FRONTEND. I thought about adding
> || [ -z "$DEBIAN_FRONTEND" ]
> but there are apparently some scripts in rootskel for s390 that export
A quick g
Jö Fahlke wrote:
> Am Mi, 22. Sep 2004, 21:49:30 +0100 schrieb Colin Watson:
> > debconf/frontend doesn't have a default, so I'd be inclined to just
> > debconf-get it and see if it's non-empty. Testing the 'seen' flag seems
> > a bit weird since it hasn't in fact been shown to the user.
>
> Ok, h
On Wed, Sep 22, 2004 at 11:02:59PM +0200, Jö Fahlke wrote:
> Am Mi, 22. Sep 2004, 21:49:30 +0100 schrieb Colin Watson:
> > debconf/frontend doesn't have a default, so I'd be inclined to just
> > debconf-get it and see if it's non-empty. Testing the 'seen' flag seems
> > a bit weird since it hasn't
Am Mi, 22. Sep 2004, 21:49:30 +0100 schrieb Colin Watson:
> debconf/frontend doesn't have a default, so I'd be inclined to just
> debconf-get it and see if it's non-empty. Testing the 'seen' flag seems
> a bit weird since it hasn't in fact been shown to the user.
Ok, here is a patch doing just tha
Am Mi, 22. Sep 2004, 21:49:30 +0100 schrieb Colin Watson:
> debconf/frontend doesn't have a default, so I'd be inclined to just
> debconf-get it and see if it's non-empty. Testing the 'seen' flag seems
> a bit weird since it hasn't in fact been shown to the user.
packages/rootskel/src/sbin/env2deb
On Wed, Sep 22, 2004 at 09:20:14PM +0200, Jö Fahlke wrote:
> Am Mi, 22. Sep 2004, 18:59:02 +0200 schrieb Jö Fahlke:
> > My plan is to not automagically set any variables if the corresponding
> > debconf option is set in the database. Since these variables are set
> > from scripts in run-parts-styl
Am Mi, 22. Sep 2004, 18:59:02 +0200 schrieb Jö Fahlke:
> My plan is to not automagically set any variables if the corresponding
> debconf option is set in the database. Since these variables are set
> from scripts in run-parts-style directories it's probably easiest to
> use a seperate skript whic
Am Di, 21. Sep 2004, 22:18:51 +0200 schrieb Geert Stappers:
> + - debconf/frontend as documented, DEBIAN_FRONTEND is a workaround
If nobody opposes I will start to work on this.
My plan is to not automagically set any variables if the corresponding
debconf option is set in the database. Si
On Tue, Sep 21, 2004 at 12:30:49PM -0400, Joey Hess wrote:
> Petter Reinholdtsen wrote:
> > [Geert Stappers]
> > > The manual writes about bootparameter debconf/frontend=
> > > but that didn't make sense with cdebconf_udeb 0.70
> > >
> > > Adding DEBIAN_FRONTEND= did do what I wanted.
> >
> >
Petter Reinholdtsen wrote:
> [Geert Stappers]
> > The manual writes about bootparameter debconf/frontend=
> > but that didn't make sense with cdebconf_udeb 0.70
> >
> > Adding DEBIAN_FRONTEND= did do what I wanted.
>
> I prefer DEBIAN_FRONTEND because it is the same as the parameter used
> on
[Geert Stappers]
> The manual writes about bootparameter debconf/frontend=
> but that didn't make sense with cdebconf_udeb 0.70
>
> Adding DEBIAN_FRONTEND= did do what I wanted.
I prefer DEBIAN_FRONTEND because it is the same as the parameter used
on the shell command line, and the traditional
Hello Dist,
The manual writes about bootparameter debconf/frontend=
but that didn't make sense with cdebconf_udeb 0.70
Adding DEBIAN_FRONTEND= did do what I wanted.
Was there a transistion from one to the other bootparameter?
(and had I the bad luck to encounter it? ;-)
What should be done
13 matches
Mail list logo
