Ian Murdock writes ("Bug#1496: dpkg returns to dselect on SIGSTOP"):
>    Date: Thu, 28 Sep 95 20:28 BST
>    From: Ian Jackson <[EMAIL PROTECTED]>
>
>    > I was using dselect for the first time (for real), and it is very,
>    > very nice.  However, while it was upgrading my bash.deb, it stopped to
>    > query about the confile '/etc/profile'.  Fair enough, it was
>    > different.  I chose the 'Z' (?) option to suspend and investigate for
>    > myself.  dpkg was then stopped, but instead of starting a shell, it
>    > returned to the dselect menu, after which I couldn't do anything, as
>    > dpkg was locked.
>
>    I had a bug report like this before.  Can you reproduce it ?  If you
>    have two .deb files which have different versions of a conffile in it
>    you can keep getting dpkg to prompt by editing the conffile once and
>    then never answering `y' as you install them alternately.
>
> Were you doing this in the dselect automatically started after
> installing the base system?  In this case, dselect is started from a
> shell script (namely, /root/.bash_profile).  Could this be the
> problem?

Aaah, the light dawns.  Ooops.

Ian M.: please arrange for the environment variable "DPKG_NO_TSTP" to
be set to some non-empty value (like "yes") when dselect is invoked in
this way.  This will cause dpkg to invoke "$SHELL -i" instead (or "sh
-i" if SHELL isn't set).

This feature will be in 0.93.79.

Of course, any conffiles prompts at this stage reflect bugs in the
base disks.

Ian.

Reply via email to