[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#712232: marked as done (LIVE_NOCONFIGS in /etc/live/config/* broken)



Your message dated Sun, 16 Jun 2013 10:04:05 +0200
with message-id <51BD7175.9020708@progress-technologies.net>
and subject line Re: Bug#712232: LIVE_NOCONFIGS in /etc/live/config/* broken
has caused the Debian Bug report #712232,
regarding LIVE_NOCONFIGS in /etc/live/config/* broken
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
712232: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712232
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: live-config
Version: 3.0.23-1
Severity: normal

In Tails [1] we set:

    LIVE_NOCONFIGS="${LIVE_NOCONFIGS},sudo,policykit"

in /etc/live/config/noroot.conf, but with live-config 3.0.23-1 these
exceptions are *not* honoured (e.g. /etc/sudoers.d/live is created).
They worked fine until (and including) version 3.0.12-1.

For the record, appending `live-noconfig=sudo,policykit` to the kernel
command line works as expected even in version 3.0.23-1, so the issue
must have something to do with the /etc/live/config/* files.

Cheers!

[1] https://tails.boum.org



-- 

Attachment: pgp4K7kTIys5B.pgp
Description: PGP signature


--- End Message ---
--- Begin Message ---
On 06/16/13 09:40, tails@boum.org wrote:
> If I remove `config' from the kernel command-line, no live-config 
> script is run at all, despite LIVE_NOCONFIGS is set in 
> /etc/live/config/*. This looks like a bug

no, not a bug.

if you use cmdline, then the *complete* set of required variables are
set according to your specification.

if you use config files, only those variables are set that you put
into the config file since we cannot guess the intention (like we can
when you use cmdline).

if you want to have all scripts run except a few, and doing that with
variables, then you need to specify both LIVE_NOCONFIGS and
LIVE_CONFIG_SCRIPTS in your config file, see the
'live-noconfig=*|noconfig=*)' case in /lib/live/config.sh.

oiow: you forgot to specify LIVE_CONFIG_SCRIPTS, closing.

-- 
Address:        Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email:          daniel.baumann@progress-technologies.net
Internet:       http://people.progress-technologies.net/~daniel.baumann/

--- End Message ---

Reply to: