[Pkg-ltsp-devel] Bug#574199: ltsp-client-core: installation fails

[Lucas Nussbaum]

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 at lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lucas at nussbaum.fr             GPG: 1024D/023B3F4F |