Bug#574199: ltsp-client-core: installation fails
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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#574199: ltsp-client-core: installation fails
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 | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#574199: ltsp-client-core: installation fails
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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#574199: ltsp-client-core: installation fails
Package: ltsp-client-core Version: 5.2-1 Severity: serious User: debian...@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 | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
