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

[Vagrant Cascadian]

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