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

Bug#713957: marked as done (manpage: make conffile variable usage more detailed)

Your message dated Mon, 24 Jun 2013 13:52:55 +0200
with message-id <51C83317.2080905@progress-technologies.net>
and subject line Re: Bug#713957: live-config: manpage is wrong about LIVE_NOCONFIGS usage
has caused the Debian Bug report #713957,
regarding manpage: make conffile variable usage more detailed
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

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


TL;DR: live-config(7) pretends that LIVE_NOCONFIGS equals
live-noconfig=, which is not the case.

As explained in message #45 on #712232, live-config(7) gives these
directions about LIVE_NOCONFIGS usage:

   Everything but the shortcuts that can be configured with a boot
   parameter can be alternatively also be configured through one or
   more files.
       This variable equals the 'live-noconfig=SCRIPT1,SCRIPT2, ...
       SCRIPTn' parameter.
   Removing existing config scripts
       To avoid to always need specifing disabled scripts through
       the boot parameter, a configuration file should be used, see above.

These directions don't work, which is kind of expected (at least for
those who wrote the code) as it completely contradict the intended
behavior that Daniel was kind enough to explain in message #40 on that
same bug report:

  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.

Note that the manpage has no mention of _SCRIPTS (LIVE_CONFIG_SCRIPTS'
name in 3.0.x), so there's no way one can guess they should set it,
just by reading the manpage.

In earlier versions of live-config, the documentation previously used
to match the actual behavior of the program (I believe the
documentation update was forgotten when the behavior changed in commit
b018878). So, this is a regression in the documentation, which is why
I dare setting "normal" severity.

  | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
  | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc

--- End Message ---
--- Begin Message ---
close 713957 4.0~a23-1

On 06/24/2013 11:51 AM, Daniel Baumann wrote:
> please send some additional text to be added to the manpage.

not needed, above version initializes LIVE_CONFIG_SCRIPTS automatically.

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: