Debian Bug report logs - #574199
ltsp-client-core: does not display reason for failed install

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Lucas Nussbaum <lucas@lucas-nussbaum.net>

To: submit@bugs.debian.org

Subject: ltsp-client-core: installation fails

Date: Wed, 17 Mar 2010 00:01:24 +0100

Package: ltsp-client-core
Version: 5.2-1
Severity: serious
User: debian-qa@lists.debian.org
Usertags: instest-20100316 instest

Hi,

While testing the installation of all packages in unstable, I ran
into the following problem:

> Reading package lists...
> Building dependency tree...
> Reading state information...
> Suggested packages:
> ldm pulseaudio-esound-compat ltspfsd mdetect alsa-utils cryptsetup
> libasound2-plugins netcat-traditional netcat rdesktop inputattach joystick
> sshfs python-serial ntpdate numlockx sdm-terminal x-display-manager
> pulseaudio esound nas sane-utils cups-bsd
> The following NEW packages will be installed:
> ltsp-client-core
> 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> Need to get 117kB of archives.
> After this operation, 639kB of additional disk space will be used.
> WARNING: The following packages cannot be authenticated!
> ltsp-client-core
> Authentication warning overridden.
> Get:1 http://localhost sid/main ltsp-client-core 5.2-1 [117kB]
> Preconfiguring packages ...
> Fetched 117kB in 2s (47.9kB/s)
> Selecting previously deselected package ltsp-client-core.
> (Reading database ... 13494 files and directories currently installed.)
> Unpacking ltsp-client-core (from .../ltsp-client-core_5.2-1_amd64.deb) ...
> dpkg: error processing /var/cache/apt/archives/ltsp-client-core_5.2-1_amd64.deb (--unpack):
> subprocess new pre-installation script returned error exit status 1
> Errors were encountered while processing:
> /var/cache/apt/archives/ltsp-client-core_5.2-1_amd64.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)

The full build log is available from:
 http://people.debian.org/~lucas/logs/2010/03/16/ltsp-client-core.log

It is reproducible by installing your package in a clean chroot, using
the debconf Noninteractive frontend, and priority: critical.

This test was carried out using about 50 AMD64 nodes of the Grid'5000
platform.  Internet was not accessible from the nodes.

-- 
| Lucas Nussbaum
| lucas@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lucas@nussbaum.fr             GPG: 1024D/023B3F4F |

Message #10 received at 574199@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@freegeek.org>

To: Lucas Nussbaum <lucas@lucas-nussbaum.net>, 574199@bugs.debian.org

Subject: Re: Bug#574199: ltsp-client-core: installation fails

Date: Mon, 22 Mar 2010 16:37:20 -0700

severity 574199 normal
retitle 574199 ltsp-client-core: does not display reason for failed install
block 574199 by 367497
block 574199 by 398707
thanks

On Wed, Mar 17, 2010 at 12:01:24AM +0100, Lucas Nussbaum wrote:
> > Selecting previously deselected package ltsp-client-core.
> > (Reading database ... 13494 files and directories currently installed.)
> > Unpacking ltsp-client-core (from .../ltsp-client-core_5.2-1_amd64.deb) ...
> > dpkg: error processing /var/cache/apt/archives/ltsp-client-core_5.2-1_amd64.deb (--unpack):
> > subprocess new pre-installation script returned error exit status 1
> > Errors were encountered while processing:
> > /var/cache/apt/archives/ltsp-client-core_5.2-1_amd64.deb
> > E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> The full build log is available from:
>  http://people.debian.org/~lucas/logs/2010/03/16/ltsp-client-core.log
> 
> It is reproducible by installing your package in a clean chroot, using
> the debconf Noninteractive frontend, and priority: critical.

thanks for the report... we've been here before. :)

this seems to be a repeat of:

  http://bugs.debian.org/398630

essentially, ltsp-client-core shouldn't be installed on a normal system, and
checks for the presence of /etc/ltsp_chroot, and errors out if it doesn't find
it (which is created by ltsp-build-client).

it does issue an error through debconf at priority critical, though the
noninteractive debconf frontend still seems to silently discard error messages
(or email when possible, but in this case, a chroot, it's often not possible):

  http://bugs.debian.org/367497
  http://bugs.debian.org/398707

i guess i can manually output an error message using echo (with mangled file
descriptors due to the running debconf interface) in the next ltsp upload, but
it seems a little redundant to duplicate the message in two places.  i'd almost
rather not work around it that way...

live well,
  vagrant

Message #23 received at 574199@bugs.debian.org (full text, mbox, reply):

From: Lucas Nussbaum <lucas@lucas-nussbaum.net>

To: Vagrant Cascadian <vagrant@freegeek.org>

Cc: 574199@bugs.debian.org

Subject: Re: Bug#574199: ltsp-client-core: installation fails

Date: Tue, 23 Mar 2010 07:10:03 +0100

On 22/03/10 at 16:37 -0700, Vagrant Cascadian wrote:
> severity 574199 normal
> retitle 574199 ltsp-client-core: does not display reason for failed install
> block 574199 by 367497
> block 574199 by 398707
> thanks
> 
> On Wed, Mar 17, 2010 at 12:01:24AM +0100, Lucas Nussbaum wrote:
> > > Selecting previously deselected package ltsp-client-core.
> > > (Reading database ... 13494 files and directories currently installed.)
> > > Unpacking ltsp-client-core (from .../ltsp-client-core_5.2-1_amd64.deb) ...
> > > dpkg: error processing /var/cache/apt/archives/ltsp-client-core_5.2-1_amd64.deb (--unpack):
> > > subprocess new pre-installation script returned error exit status 1
> > > Errors were encountered while processing:
> > > /var/cache/apt/archives/ltsp-client-core_5.2-1_amd64.deb
> > > E: Sub-process /usr/bin/dpkg returned an error code (1)
> > 
> > The full build log is available from:
> >  http://people.debian.org/~lucas/logs/2010/03/16/ltsp-client-core.log
> > 
> > It is reproducible by installing your package in a clean chroot, using
> > the debconf Noninteractive frontend, and priority: critical.
> 
> thanks for the report... we've been here before. :)
> 
> this seems to be a repeat of:
> 
>   http://bugs.debian.org/398630
> 
> essentially, ltsp-client-core shouldn't be installed on a normal system, and
> checks for the presence of /etc/ltsp_chroot, and errors out if it doesn't find
> it (which is created by ltsp-build-client).
> 
> it does issue an error through debconf at priority critical, though the
> noninteractive debconf frontend still seems to silently discard error messages
> (or email when possible, but in this case, a chroot, it's often not possible):
> 
>   http://bugs.debian.org/367497
>   http://bugs.debian.org/398707
> 
> i guess i can manually output an error message using echo (with mangled file
> descriptors due to the running debconf interface) in the next ltsp upload, but
> it seems a little redundant to duplicate the message in two places.  i'd almost
> rather not work around it that way...

Hi,

Well, an error message echoed on the console would be great, but if you
don't mind me filing bugs from time to time... ;)
-- 
| Lucas Nussbaum
| lucas@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lucas@nussbaum.fr             GPG: 1024D/023B3F4F |

Message #28 received at 574199@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@freegeek.org>

To: Lucas Nussbaum <lucas@lucas-nussbaum.net>, 574199@bugs.debian.org

Subject: Re: Bug#574199: ltsp-client-core: installation fails

Date: Wed, 24 Mar 2010 13:27:08 -0700

tags 574199 pending
thanks

On Tue, Mar 23, 2010 at 07:10:03AM +0100, Lucas Nussbaum wrote:
> On 22/03/10 at 16:37 -0700, Vagrant Cascadian wrote:
> > i guess i can manually output an error message using echo (with mangled file
> > descriptors due to the running debconf interface) in the next ltsp upload, but
> > it seems a little redundant to duplicate the message in two places.  i'd almost
> > rather not work around it that way...

> Well, an error message echoed on the console would be great, but if you
> don't mind me filing bugs from time to time... ;)

should be in next upload. committed to bzr:

  http://bzr.debian.org/loggerhead/pkg-ltsp/ltsp-debian-packaging/revision/996

live well,
  vagrant

Message #35 received at 574199-close@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@debian.org>

To: 574199-close@bugs.debian.org

Subject: Bug#574199: fixed in ltsp 5.2.1-1

Date: Mon, 05 Apr 2010 00:39:25 +0000

Source: ltsp
Source-Version: 5.2.1-1

We believe that the bug you reported is fixed in the latest version of
ltsp, which is due to be installed in the Debian FTP archive:

ltsp-client-builder_5.2.1-1_all.udeb
  to main/l/ltsp/ltsp-client-builder_5.2.1-1_all.udeb
ltsp-client-core_5.2.1-1_i386.deb
  to main/l/ltsp/ltsp-client-core_5.2.1-1_i386.deb
ltsp-client_5.2.1-1_i386.deb
  to main/l/ltsp/ltsp-client_5.2.1-1_i386.deb
ltsp-server-standalone_5.2.1-1_all.deb
  to main/l/ltsp/ltsp-server-standalone_5.2.1-1_all.deb
ltsp-server_5.2.1-1_all.deb
  to main/l/ltsp/ltsp-server_5.2.1-1_all.deb
ltsp_5.2.1-1.diff.gz
  to main/l/ltsp/ltsp_5.2.1-1.diff.gz
ltsp_5.2.1-1.dsc
  to main/l/ltsp/ltsp_5.2.1-1.dsc
ltsp_5.2.1.orig.tar.gz
  to main/l/ltsp/ltsp_5.2.1.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 574199@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Vagrant Cascadian <vagrant@debian.org> (supplier of updated ltsp package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sun, 04 Apr 2010 16:06:07 -0700
Source: ltsp
Binary: ltsp-server ltsp-server-standalone ltsp-client-core ltsp-client ltsp-client-builder
Architecture: source all i386
Version: 5.2.1-1
Distribution: unstable
Urgency: low
Maintainer: LTSP Debian/Ubuntu Maintainers <pkg-ltsp-devel@lists.alioth.debian.org>
Changed-By: Vagrant Cascadian <vagrant@debian.org>
Description: 
 ltsp-client - complete LTSP client environment
 ltsp-client-builder - build an LTSP environment in the installer target (udeb)
 ltsp-client-core - basic LTSP client environment
 ltsp-server - basic LTSP server environment
 ltsp-server-standalone - complete LTSP server environment
Closes: 574199
Changes: 
 ltsp (5.2.1-1) unstable; urgency=low
 .
   * New upstream version:
     - Add SCREEN_DEFAULT parameter to select which screen script will be
       displayed at boot.
     - Improved sound support with rdesktop screen script.
     - Set default microphone volume to 40% if unspecified to avoid problems
       with sound feedback.
     - New "NBD_SWAP_THRESHOLD" lts.conf parameter, to automatically
       enable NBD_SWAP for clients with less RAM than that threshold.
     - Consistantly change NBD_PORT to NBD_SWAP_PORT and NBD_ROOT_PORT, and
       SWAP_SERVER to NBD_SWAP_SERVER where appropriate.
     - nbdswapd: Increase the default size to 64 MB.
 .
     - Fat clients:
       + Option to enable NFS mounted home directories for fat clients.
       + Disable local devices when configured as a fat client.
 .
     - Localapps:
       + Do not follow symlinks with sshfs mounted home directory by default.
 .
     - ltsp-build-client:
       + Simplified unmounting of filesystems by splitting into a separate
         plugin.
       + New plugin to install custom .deb files from specified directory.
 .
     - ltsp-update-sshkeys:
       + Add an ssh key entry for "server" referring to the LTSP server itself.
       + Clean up usage info in ltsp-update-sshkeys.
 .
     - initramfs-tools hooks:
       + When using an aufs mounted root filesystem, set permissions on
         writeable tmpfs so that it is not world-writeable (LP: #516608).
       + Properly separate tftppath when downloading lts.conf (LP: #238010).
       + Allow clientid to be passed as a kernel parameter when using udhcpc
         (LP: #505916).
 .
   * Install dpkg triggers so that initramfs-tools will regenerate the
     initramfs on upgrade.
   * Add patch from upstream to initialize tty using openvt before starting a
     screen script on that tty.
   * Work around bugs in debconf which prevent error messages from getting
     displayed by also displaying text directly (Closes: #574199).
   * Include nbd-proxy manpage.
   * Drop revert-fgconsole patch, applied upstream.
   * Remove un-used lintian overrides for ltsp-client. lintian no longer
     complains about architecture-specific metapackages.
   * debian/rules: Clean the nbd-proxy dir in the clean target.
   * Add debian/source/format and set to 1.0.
Checksums-Sha1: 
 22163b75c5ddad29caa2dd5963e1b18d0a2b32ef 2177 ltsp_5.2.1-1.dsc
 ff53a8222614cf6a9fa8ac2879df75604d99cbe5 584926 ltsp_5.2.1.orig.tar.gz
 bcba429371745673e3e1e48d5a8fd84c23158775 74629 ltsp_5.2.1-1.diff.gz
 1cdab5f127bae46a1a6365a20dbc23c8aa25c204 137506 ltsp-server_5.2.1-1_all.deb
 f5a265bee4d6e6b0ce07a1c1b172515ab11c8156 50270 ltsp-server-standalone_5.2.1-1_all.deb
 ed73ad252536e6843be3d02d17f824890ea954cd 9334 ltsp-client-builder_5.2.1-1_all.udeb
 1ae7d25f5fa587085dc611c87d5cac9638731975 117546 ltsp-client-core_5.2.1-1_i386.deb
 0e3aa247da48d8edbc5a03e99e13817894f2f073 49338 ltsp-client_5.2.1-1_i386.deb
Checksums-Sha256: 
 5e1fc77dc23fb2b32720d6ff9e21024e35ca0cbee7aa210c33c35b5ba21bb0d4 2177 ltsp_5.2.1-1.dsc
 1b7cb95972a591cc9077e8a94067728a51eb46b683e1acfe9c932520db46abd5 584926 ltsp_5.2.1.orig.tar.gz
 0b48f9ce3a483df4b2823c34ebccd08a0a53c5532269935e98fc3617c18c047a 74629 ltsp_5.2.1-1.diff.gz
 fa3eefe0e63da29fc9bb00fc2f77b5e311e19868a6469966887bb2550266dc5d 137506 ltsp-server_5.2.1-1_all.deb
 96c47976715515c65fdccdd9f47eb7f2de67a517750c009b0b92174e86955b83 50270 ltsp-server-standalone_5.2.1-1_all.deb
 beea1d8bd3914876c196ac5a9891b630db1f05122f0949f5d13192886383c581 9334 ltsp-client-builder_5.2.1-1_all.udeb
 f10b388dc08d346f9027eb085d19cd8dbb3e8638cb2f1555ac546008d30065e7 117546 ltsp-client-core_5.2.1-1_i386.deb
 e3dfdcdee0c1bae02d1d54adb672a4a5551484078b63ab78b29cf4aa4f9b56fb 49338 ltsp-client_5.2.1-1_i386.deb
Files: 
 d0a72455043aa4c5be6a49daf0d63af5 2177 misc extra ltsp_5.2.1-1.dsc
 8dca5449b21858d8c87cc0a7cf461cb0 584926 misc extra ltsp_5.2.1.orig.tar.gz
 ca3f47b959df6af954f3c772744a1454 74629 misc extra ltsp_5.2.1-1.diff.gz
 f92eb324ac7f75e4f3d19302ca122330 137506 misc extra ltsp-server_5.2.1-1_all.deb
 fc3a82c824c5106083418ff38c4d1de8 50270 misc extra ltsp-server-standalone_5.2.1-1_all.deb
 2a6582fca7e7647fe2811ecbdd7389fb 9334 debian-installer extra ltsp-client-builder_5.2.1-1_all.udeb
 3386c3bc3a830fbbb4d02c655564f8fc 117546 misc extra ltsp-client-core_5.2.1-1_i386.deb
 78f90eebed9496d7847aa59c386d0f62 49338 misc extra ltsp-client_5.2.1-1_i386.deb
Package-Type: udeb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iQIcBAEBCAAGBQJLuR71AAoJEAMEK/Djv2x4SAQP/RBhHcX8RzB14J41C6cCOWnL
9rvuuUxi3EuyZ5n2VgNOBIQg3JnB5edEykcdzO1k4n8H6D/rqJXzJwVqauM0qMwg
lH+Arf8VczA+uzYxY4RXa+9OQreuEDZoOneLzoaGELxbeqaLAUYq0LFDfrShx7w0
1qbqVq/FRJ58Zk8EGlHETSFb84CxVurBTPZDZY90UAxCde9yZ62sth1+9uUXNIcI
8srfyK1lkoRO9JbDUHSVCzBia9wEJ/jm7NycoIMBanFMNsCgH5kLnbGyq+KJLerE
9HplY42H24HvUgo3cFW+00HLKwSdNJlxf/qB1oOnkMlxLlgLVzqLULxsgXqThIm9
zb27JdtxHeAeIX95vKX8qNrB+lG1AcLncSMrq8iR1ycs80geJeAau/KHuCfnUsCY
W063Kfb7R8YL7/OXGo4xIYCBBT15VhCWA28m9YUfrI92Jc8Ubj+C5dnKSV6B/k4L
3NfqpWmHfktgn2j4J7gbSWHAeFwWGCoEtVbaWCMRED8fYMUTKhwF28CXiKMdiRU+
4zxw7oF9qJ2rDXRdKgSv8Sosoz84rgR95m76bm8YjKe4M3eo712T0Wsov5L8klfm
4Lyv0wVPrHiPuqtIjoEgo3GuCNstBI97nqLkF94wt4+8U4VU/RWEJ4k59SVm158R
PjFP8J0XGjVr2lK4ksD7
=fT0s
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.