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

[Lucas Nussbaum]

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