Bug#538051: jackd: configuration fails with status 30
Package: jackd Version: 0.116.2+svn3592-1 Severity: grave Justification: renders package unusable (uninstallable) jackd.config runs in -e mode, but fails to account that db_input will return status 30 rather than 0 for questions the user has already seen; this applies even on the first installation of (or upgrade to) 0.116.2+svn3592-1 on systems on which (thanks to apt-utils) preconfiguration is possible. Please allow db_input to fail by protecting it with || true or (if you want to be really strict) || [ $? = 30 ]. BTW, I also observe that you appear to be treating debconf as a registry rather than a cache, and would advise setting the current value of jackd/tweak_rt_limits based on the presence or absence of /etc/security/limits.d/audio.conf. Thanks! -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages jackd depends on: ii cdebconf [debconf-2.0] 0.145 Debian Configuration Management Sy ii coreutils 7.4-2 The GNU core utilities ii debconf [debconf-2.0] 1.5.27Debian configuration management sy ii libasound2 1.0.20-3 shared library for ALSA applicatio ii libc6 2.9-21GNU C Library: Shared libraries ii libjack0 0.116.2+svn3592-1 JACK Audio Connection Kit (librari ii libreadline5 5.2-5 GNU readline and history libraries ii libsamplerate0 0.1.7-2 audio rate conversion library ii libsndfile11.0.20-1 Library for reading/writing audio Versions of packages jackd recommends: ii libpam-modules1.0.1-9Pluggable Authentication Modules f ii qjackctl 0.3.4-1User interface for controlling the Versions of packages jackd suggests: ii jack-tools0.0.2-6various JACK tools: plumbing, play pn libjackasyn0 none (no description available) ii meterbridge 0.9.2-6+b1 A collection of Audio meters for t -- debconf information: * jackd/tweak_rt_limits: false -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538051: jackd: configuration fails with status 30
On Wed, Jul 22, 2009 at 01:50:49PM -0400, Aaron M. Ucko wrote: Hi! Please allow db_input to fail by protecting it with || true or (if you want to be really strict) || [ $? = 30 ]. Fixed. BTW, I also observe that you appear to be treating debconf as a registry rather than a cache, and would advise setting the current value of jackd/tweak_rt_limits based on the presence or absence of /etc/security/limits.d/audio.conf. In other words, if /etc/security/limits.d/audio.conf is present, the dialog should say Yes no matter what the user has answered the last time? (to be honest, I really treat debconf as a registry, or at least the central place for this configuration value, but this might very likely be a misunderstanding. I'd be happy to follow your suggestions) Cheerio -- mail: a...@thur.de http://adi.thur.de PGP/GPG: key via keyserver -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538051: jackd: configuration fails with status 30
a...@drcomp.erfurt.thur.de (Adrian Knoth) writes: Fixed. Thanks! In other words, if /etc/security/limits.d/audio.conf is present, the dialog should say Yes no matter what the user has answered the last time? Yes, that's my understanding; likewise, if the user previously answered yes but then removed the file manually, the dialog should say no. See also http://lintian.debian.org/tags/debconf-is-not-a-registry.html and debconf-devel(7), which mentions this matter in the context of using debconf outside maintainer scripts: You can also use debconf in other, standalone programs. The issue to watch out for here is that debconf is not intended to be, and must not be used as a registry. This is unix after all, and programs are config- ured by files in /etc, not by some nebulous debconf database (that is only a cache anyway and might get blown away). So think long and hard before using debconf in a standalone program. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?...@monk.mit.edu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
