Debian Bug report logs - #398630
ltsp-client: preinst fails

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: preinst fails

Date: Tue, 14 Nov 2006 17:59:00 +0100

Package: ltsp-client
Version: 0.99debian7
Severity: serious
Usertags: grid5000

Hi,

During a piuparts run over all the packages in etch, I ran into a
problem with your package:
  Selecting previously deselected package ltsp-client.
  Unpacking ltsp-client (from .../ltsp-client_0.99debian7_i386.deb) ...
  dpkg: error processing
/var/cache/apt/archives/ltsp-client_0.99debian7_i386.deb (--unpack):
   subprocess pre-installation script returned error exit status 1

The full log is available from 
http://ox.blop.info/bazaar/buildlogs/20061114/

The piuparts run was done on about 40 AMD64 nodes of the Grid'5000
platform, using a clean chroot containing an etch i386 environment
(not unstable).  Internet was not accessible from the build systems.

About Grid'5000:
Grid'5000 is an highly reconfigurable experimental Grid platform
gathering 9 sites and featuring a total of 5000 CPUs. It serves as a
testbed for research in Grid Computing. See https://www.grid5000.fr/
-- 
| Lucas Nussbaum
| lucas@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lucas@nussbaum.fr             GPG: 1024D/023B3F4F |

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

From: Vagrant Cascadian <vagrant@freegeek.org>

To: 398630-submitter@bugs.debian.org, 398630@bugs.debian.org

Subject: Re: [Pkg-ltsp-devel] Bug#398630: ltsp-client: preinst fails

Date: Tue, 14 Nov 2006 10:21:17 -0800

On Tue, Nov 14, 2006 at 05:59:00PM +0100, Lucas Nussbaum wrote:
> Package: ltsp-client
> Version: 0.99debian7
> Severity: serious
> Usertags: grid5000
> 
> Hi,
> 
> During a piuparts run over all the packages in etch, I ran into a
> problem with your package:
>   Selecting previously deselected package ltsp-client.
>   Unpacking ltsp-client (from .../ltsp-client_0.99debian7_i386.deb) ...
>   dpkg: error processing
> /var/cache/apt/archives/ltsp-client_0.99debian7_i386.deb (--unpack):
>    subprocess pre-installation script returned error exit status 1

this is intentional. from the description:

Description: LTSP client environment
 The scripts needed to configure and boot an LTSP client.
 .
 DO NOT install this package on a regular machine, it is intended only
 for installation inside a LTSP client filesystem.

it requires the presence of an /etc/ltsp_chroot file in order to
install. this is a safety precaution to ensure that ltsp-client is being
in an LTSP environment and not on the regular system, as the ltsp-client
init scripts do things that most users would not want on a regular
system.

though, now that you've brought it up, it might be better for the init
scripts to check for the presence of /etc/ltsp_chroot rather than
preinst.

live well,
  vagrant

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

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

To: Vagrant Cascadian <vagrant@freegeek.org>

Cc: 398630@bugs.debian.org

Subject: Re: Bug#398630: [Pkg-ltsp-devel] Bug#398630: ltsp-client: preinst fails

Date: Tue, 14 Nov 2006 19:47:20 +0100

On 14/11/06 at 10:21 -0800, Vagrant Cascadian wrote:
> On Tue, Nov 14, 2006 at 05:59:00PM +0100, Lucas Nussbaum wrote:
> > Package: ltsp-client
> > Version: 0.99debian7
> > Severity: serious
> > Usertags: grid5000
> > 
> > Hi,
> > 
> > During a piuparts run over all the packages in etch, I ran into a
> > problem with your package:
> >   Selecting previously deselected package ltsp-client.
> >   Unpacking ltsp-client (from .../ltsp-client_0.99debian7_i386.deb) ...
> >   dpkg: error processing
> > /var/cache/apt/archives/ltsp-client_0.99debian7_i386.deb (--unpack):
> >    subprocess pre-installation script returned error exit status 1
> 
> this is intentional. from the description:
> 
> Description: LTSP client environment
>  The scripts needed to configure and boot an LTSP client.
>  .
>  DO NOT install this package on a regular machine, it is intended only
>  for installation inside a LTSP client filesystem.
> 
> it requires the presence of an /etc/ltsp_chroot file in order to
> install. this is a safety precaution to ensure that ltsp-client is being
> in an LTSP environment and not on the regular system, as the ltsp-client
> init scripts do things that most users would not want on a regular
> system.
> 
> though, now that you've brought it up, it might be better for the init
> scripts to check for the presence of /etc/ltsp_chroot rather than
> preinst.

preinst or postinst looks fine, but please output an error message
explaining exactly what you explained in that mail, instead of just
dying silently :-)
-- 
| Lucas Nussbaum
| lucas@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lucas@nussbaum.fr             GPG: 1024D/023B3F4F |

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

From: Oliver Grawert <ogra@ubuntu.com>

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

Subject: Re: Bug#398630: [Pkg-ltsp-devel] Bug#398630: ltsp-client: preinst fails

Date: Tue, 14 Nov 2006 20:34:27 +0100

[Message part 1 (text/plain, inline)]

hi,
Am Dienstag, den 14.11.2006, 19:47 +0100 schrieb Lucas Nussbaum:
> > it requires the presence of an /etc/ltsp_chroot file in order to
> > install. this is a safety precaution to ensure that ltsp-client is being
> > in an LTSP environment and not on the regular system, as the ltsp-client
> > init scripts do things that most users would not want on a regular
> > system.
> > 
> > though, now that you've brought it up, it might be better for the init
> > scripts to check for the presence of /etc/ltsp_chroot rather than
> > preinst.
> 
> preinst or postinst looks fine, but please output an error message
> explaining exactly what you explained in that mail, instead of just
> dying silently :-)

erm, in ubuntu it presents you a debconf warning with the text vagrant
pointed out from the package description and fails gracefully, i dont
know why it doesnt do that in debian, did you by chance play with the
debconf priorities ?

ciao
	oli

[signature.asc (application/pgp-signature, inline)]

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

From: Vagrant Cascadian <vagrant@freegeek.org>

To: 398630-submitter@bugs.debian.org, 398630@bugs.debian.org

Subject: Re: Bug#398630: [Pkg-ltsp-devel] Bug#398630: ltsp-client: preinst fails

Date: Tue, 14 Nov 2006 12:47:38 -0800

On Tue, Nov 14, 2006 at 08:34:27PM +0100, Oliver Grawert wrote:
> hi,
> Am Dienstag, den 14.11.2006, 19:47 +0100 schrieb Lucas Nussbaum:
> > > it requires the presence of an /etc/ltsp_chroot file in order to
> > > install. this is a safety precaution to ensure that ltsp-client is being
> > > in an LTSP environment and not on the regular system, as the ltsp-client
> > > init scripts do things that most users would not want on a regular
> > > system.
> > > 
> > > though, now that you've brought it up, it might be better for the init
> > > scripts to check for the presence of /etc/ltsp_chroot rather than
> > > preinst.
> > 
> > preinst or postinst looks fine, but please output an error message
> > explaining exactly what you explained in that mail, instead of just
> > dying silently :-)
> 
> erm, in ubuntu it presents you a debconf warning with the text vagrant
> pointed out from the package description and fails gracefully, i dont
> know why it doesnt do that in debian, did you by chance play with the
> debconf priorities ?

i suspect piuparts is running with the noninteractive mode and priority
critical.

looking at the preinst, we only ask with priority high. we also use a
"note" type debconf question, when really i think an "error" type is
more appropriate.

i still think the best bet is to drop the preinst, and make the package
harmless to install on a normal system by default. i'll look more into
this.

if that turns out to be non-trivial, changing it to an "error" type with
priority "critical" will hopefully be sufficient.

live well,
  vagrant

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

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

To: Oliver Grawert <ogra@ubuntu.com>

Cc: 398630@bugs.debian.org, control@bugs.debian.org

Subject: Re: Bug#398630: [Pkg-ltsp-devel] Bug#398630: ltsp-client: preinst fails

Date: Wed, 15 Nov 2006 08:51:30 +0100

severity 398630 wishlist
thanks
On 14/11/06 at 20:34 +0100, Oliver Grawert wrote:
> hi,
> Am Dienstag, den 14.11.2006, 19:47 +0100 schrieb Lucas Nussbaum:
> > > it requires the presence of an /etc/ltsp_chroot file in order to
> > > install. this is a safety precaution to ensure that ltsp-client is being
> > > in an LTSP environment and not on the regular system, as the ltsp-client
> > > init scripts do things that most users would not want on a regular
> > > system.
> > > 
> > > though, now that you've brought it up, it might be better for the init
> > > scripts to check for the presence of /etc/ltsp_chroot rather than
> > > preinst.
> > 
> > preinst or postinst looks fine, but please output an error message
> > explaining exactly what you explained in that mail, instead of just
> > dying silently :-)
> 
> erm, in ubuntu it presents you a debconf warning with the text vagrant
> pointed out from the package description and fails gracefully, i dont
> know why it doesnt do that in debian, did you by chance play with the
> debconf priorities ?

I did, yes, since piuparts requires this. The debconf warning is
priority high. critical might be more suitable.

It would also be a good idea to just display something to stdout (using
echo), so this would be displayed even with the noninteractive frontend.

Additionnally, it would be great if there was a noninteractive-like
debconf frontend that would display what is being answered
automatically. I'll file a wishlist bug.

Thank you for your time, and sorry for the noise :)
-- 
| Lucas Nussbaum
| lucas@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lucas@nussbaum.fr             GPG: 1024D/023B3F4F |

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

From: Vagrant Cascadian <vagrant@freegeek.org>

To: 398630-close@bugs.debian.org

Subject: Bug#398630: fixed in ltsp 0.99debian8

Date: Fri, 17 Nov 2006 14:19:58 -0800

Source: ltsp
Source-Version: 0.99debian8

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:

ldm_0.99debian8_all.deb
  to pool/main/l/ltsp/ldm_0.99debian8_all.deb
ltsp-client-builder_0.99debian8_all.udeb
  to pool/main/l/ltsp/ltsp-client-builder_0.99debian8_all.udeb
ltsp-client_0.99debian8_i386.deb
  to pool/main/l/ltsp/ltsp-client_0.99debian8_i386.deb
ltsp-server-standalone_0.99debian8_all.deb
  to pool/main/l/ltsp/ltsp-server-standalone_0.99debian8_all.deb
ltsp-server_0.99debian8_all.deb
  to pool/main/l/ltsp/ltsp-server_0.99debian8_all.deb
ltsp_0.99debian8.dsc
  to pool/main/l/ltsp/ltsp_0.99debian8.dsc
ltsp_0.99debian8.tar.gz
  to pool/main/l/ltsp/ltsp_0.99debian8.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 398630@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Vagrant Cascadian <vagrant@freegeek.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: SHA1

Format: 1.7
Date: Tue, 14 Nov 2006 18:50:02 -0700
Source: ltsp
Binary: ltsp-server ltsp-server-standalone ltsp-client ltsp-client-builder ldm
Architecture: source all i386
Version: 0.99debian8
Distribution: unstable
Urgency: low
Maintainer: LTSP Debian/Ubuntu Maintainers <pkg-ltsp-devel@lists.alioth.debian.org>
Changed-By: Vagrant Cascadian <vagrant@freegeek.org>
Description: 
 ldm        - LTSP display manager
 ltsp-client - LTSP client environment
 ltsp-client-builder - Build an LTSP environment in the installer target (udeb)
 ltsp-server - Basic LTSP server environment
 ltsp-server-standalone - Complete LTSP server environment
Closes: 396684 398630
Changes: 
 ltsp (0.99debian8) unstable; urgency=low
 .
   [Vagrant Cascadian]
   * drop recommends on inputattach (Closes: #396684)
   * change dependency on joystick to suggests
   * optimize check if inputattach should be used
   * change ltsp-client abort-installation debconf question to type "error" and
     priority "critical" (Closes: #398630)
   * only run ltsp-client init scripts if /etc/ltsp_chroot is present.
   * ltsp-build-client: simplified --arch handling (should work on all
     architectures now)
Files: 
 d3dcb5d5dd277fbe22a3e898ff624eef 937 misc extra ltsp_0.99debian8.dsc
 bd933920159ac9055a1e0e3d9e04752e 169093 misc extra ltsp_0.99debian8.tar.gz
 e319c0b7e6ca462d60046fc3bc226c18 47794 misc extra ltsp-server_0.99debian8_all.deb
 f2f3cc40e835b7b59784d09304c8717b 21784 misc extra ltsp-server-standalone_0.99debian8_all.deb
 877f17ca30c43dc3a9640158fbc2da0d 115100 misc extra ldm_0.99debian8_all.deb
 2ad4abca52531eb8d29fbc31f420a312 2078 debian-installer extra ltsp-client-builder_0.99debian8_all.udeb
 3f960aacd15b103e2b7af61f1c1fedb9 48044 misc extra ltsp-client_0.99debian8_i386.deb
Package-Type: udeb

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

iD8DBQFFXipd20zMSyow1ykRAiUAAJ4s97gS9AQ35C4r7bc1WEFw/Hkf6gCeNaVZ
8uzeqk+HrJVKGv2qaENGdxA=
=S0UT
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.