Subject: debconf: Debconf's frontend fail to detect finish of maintainer scripts on a perl 5.8.0 envirovment
Date: Sat, 12 Oct 2002 02:18:29 +0200
Package: debconf
Version: 1.2.10
Severity: important
It seems that when on a system with perl 5.8.0/unstable, frontend do
not detect that a maintainer script has been finished, and so the
debconf/dpkg process remain running in memory, preventing the user to
return to normal bash prompt until he issues two CRTL-C
Debconf seems to work correctly when the same installation action is
performed on a system with perl 5.6
For systems with perl 5.8.0 the maintainer needs to include a final
'db_stop' in any script calling debconf module for the installation to
work properly.
This behaviour has been found trying to install at least the following
packages
* phpnuke_5.6-4 (note that the actual unstable version 5.6-5 has
already been patched with the final 'db_stop'
* postnuke_0.714-1
* phpgroupware_0.9.14-0.RC3.2 (just on the postrm script)
This behaviour has been found by two maintainers on different computers
(see bug #164148 discussion)
I suspect this behaviour could be found on more packages compiled on
perl 5.6 envirovment and using debconf.
Regards
Hugo Espuny [email protected]
Debian maintainer for phpnuke and postnuke
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux RA 2.4.18-586tsc #1 Sun Apr 14 10:57:57 EST 2002 i586
Locale: LANG=C, LC_CTYPE=C
Versions of packages debconf depends on:
ii perl-base 5.8.0-13 The Pathologically Eclectic Rubbis
[email protected] wrote:
> It seems that when on a system with perl 5.8.0/unstable, frontend do
> not detect that a maintainer script has been finished, and so the
> debconf/dpkg process remain running in memory, preventing the user to
> return to normal bash prompt until he issues two CRTL-C
>
> Debconf seems to work correctly when the same installation action is
> performed on a system with perl 5.6
>
> For systems with perl 5.8.0 the maintainer needs to include a final
> 'db_stop' in any script calling debconf module for the installation to
> work properly.
>
> This behaviour has been found trying to install at least the following
> packages
>
> * phpnuke_5.6-4 (note that the actual unstable version 5.6-5 has
> already been patched with the final 'db_stop'
>
> * postnuke_0.714-1
>
> * phpgroupware_0.9.14-0.RC3.2 (just on the postrm script)
Do these start daemons? Can you find some examples of packages that I can
install to reproduce your problem without waiting an hour on the download
and dragging in tons of random libraries and installing a sql server? If
this is some general problem with perl 5.8 SIGPIPE propigation as you
seem to imply I'd expect that it would break every package; why is it
seemingly limited to php packages? Is there any chance that these
packages' postinsts echo random stuff at stdout and thus confuse
debconf? Where is the DEBCONF_DEBUG transcript that all the debconf
documentation says you should submit with bug reports of this sort?
> I suspect this behaviour could be found on more packages compiled on
> perl 5.6 envirovment and using debconf.
What do you mean by "compiled on perl 5.6 environment"? None of the
packages you named are compiled against perl at all.
--
see shy jo
On Sat, Oct 12, 2002 at 01:54:19PM -0400, Joey Hess wrote:
> Do these start daemons?
They could restart the webserver throught the wwwconfig-common
interface.
> Can you find some examples of packages that I can
> install to reproduce your problem without waiting an hour on the download
> and dragging in tons of random libraries and installing a sql server?
Sorry about that. The SQL server you don't have to be installed. Just the
mysql-client, and then ask debconf not to generate the database.
>If
> this is some general problem with perl 5.8 SIGPIPE propigation as you
> seem to imply I'd expect that it would break every package; why is it
> seemingly limited to php packages?
I have isolate a little bit the problem. It seems to occur only when you
ask debconf to restart the webserver (tested with apache). If you ask
not to configure any webserver, it seems to die properly.
> Is there any chance that these
> packages' postinsts echo random stuff at stdout and thus confuse
> debconf? Where is the DEBCONF_DEBUG transcript that all the debconf
> documentation says you should submit with bug reports of this sort?
I did not sent you before because it was completly normal till the point
where it dies. Here it goes:
RA:/home/hec# apt-get install phpnuke
Reading Package Lists... Done
Building Dependency Tree... Done
The following NEW packages will be installed:
phpnuke
0 packages upgraded, 1 newly installed, 0 to remove and 0 not
upgraded.
Need to get 0B/1906kB of archives. After unpacking 11.0MB will be
used.
Preconfiguring packages ...
debconf (developer): starting /tmp/config.87531 configure
debconf (developer): <-- INPUT medium phpnuke/webserver
debconf (developer): --> 0 question will be asked
debconf (developer): <-- INPUT medium phpnuke/dbgeneration
debconf (developer): --> 0 question will be asked
debconf (developer): <-- GO
debconf (developer): --> 0 ok
debconf (developer): <-- GET phpnuke/dbgeneration
debconf (developer): --> 0 false
debconf (developer): <-- INPUT low phpnuke/dbgeneration_negation
debconf (developer): --> 30 question skipped
debconf (developer): <-- GO
debconf (developer): --> 0 ok
Selecting previously deselected package phpnuke.
(Reading database ... 38239 files and directories currently
installed.)
Unpacking phpnuke (from .../archives/phpnuke_5.6-4_all.deb) ...
Setting up phpnuke (5.6-4) ...
debconf (developer): frontend started
debconf (developer): frontend running, package name is phpnuke
debconf (developer): starting /var/lib/dpkg/info/phpnuke.config
configure
debconf (developer): <-- INPUT medium phpnuke/webserver
debconf (developer): --> 30 question skipped
debconf (developer): <-- INPUT medium phpnuke/dbgeneration
debconf (developer): --> 30 question skipped
debconf (developer): <-- GO
debconf (developer): --> 0 ok
debconf (developer): <-- GET phpnuke/dbgeneration
debconf (developer): --> 0 false
debconf (developer): <-- INPUT low phpnuke/dbgeneration_negation
debconf (developer): --> 30 question skipped
debconf (developer): <-- GO
debconf (developer): --> 0 ok
debconf (developer): starting /var/lib/dpkg/info/phpnuke.postinst
configure
debconf (developer): <-- GET phpnuke/webserver
debconf (developer): --> 0 Apache
debconf (developer): <-- GET phpnuke/dbadmin
debconf (developer): --> 0 root
debconf (developer): <-- GET phpnuke/dbadmpass
debconf (developer): --> 0
debconf (developer): <-- RESET phpnuke/dbadmpass
debconf (developer): --> 0
debconf (developer): <-- GET phpnuke/dbserver
debconf (developer): --> 0 localhost
debconf (developer): <-- GET phpnuke/dbgeneration
debconf (developer): --> 0 false
And then it dies. If you ask a "ps ax", you'll find
8738 pts/2 S 0:07 apt-get install phpnuke
8794 pts/2 S 0:10 /usr/bin/dpkg --configure phpnuke
8795 pts/2 S 0:09 /usr/bin/perl -w \
/usr/share/debconf/frontend /var/lib/dpkg/info/phpnuke.postinst \
configure
8801 pts/2 Z 0:00 [phpnuke.postins <defunct>]
> What do you mean by "compiled on perl 5.6 environment"? None of the
> packages you named are compiled against perl at all.
I just meant 'built and tested on a machine with perl 5.6'. Improper use
of words, i know.
So, as far as i discover by now, it happens only when you say debconf to
restart apache (maybe other webservers) through wwwconfig-common.
I will try to look for same behaviour on other packages restarting
apache by wwwconfig-common and without it.
Regards.
Hugo Espuny
--
"I've seen things you people wouldn't believe, huh!
Attack ships on fire off the shoulder of Orion.
I've watched C-beams glittering in the dark near the Tannhauser Gate.
All those moments will be lost in time, like tears ... in the rain.
Time to die."
-- Roy Batty, nexus 6 Tyrrel Corp. replicant, 2019 AC, L.A. --
pub 1024D/E8074ECF 2002-06-28 Hugo Espuny <[email protected]>
Key fingerprint = D324 3DC4 1F2A 0936 DEB9 A4D9 D24A 8237 E807 4ECF
sub 2048g/5FE11467 2002-09-29
[email protected] wrote:
> On Sat, Oct 12, 2002 at 01:54:19PM -0400, Joey Hess wrote:
>
> > Do these start daemons?
>
> They could restart the webserver throught the wwwconfig-common
> interface.
> I have isolate a little bit the problem. It seems to occur only when you
> ask debconf to restart the webserver (tested with apache). If you ask
> not to configure any webserver, it seems to die properly.
Then they probably need to tell debconf when to stop. I suppose I'll
merge this with #50595 and unmerge #164354 and reassign that back to
phpgroupware.
--
see shy jo
Subject: Re: Bug#164396: debconf: Debconf's frontend fail to detect finish
of maintainer scripts on a perl 5.8.0 envirovment
Date: Sat, 12 Oct 2002 21:01:09 +0200
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Joey Hess wrote:
|
|Then they probably need to tell debconf when to stop. I suppose I'll
|merge this with #50595 and unmerge #164354 and reassign that back to
|phpgroupware.
OK.
I filled the bug against debconf because it seems to weird that this
behaviour just appears when upgraded to perl 5.8.0, but not when
installing on a machine with the previous version of perl.
If you feel that's the way, it's OK with me.
Regards.
Hugo Espuny
- --
"I've seen things you people wouldn't believe, huh!
~ Attack ships on fire off the shoulder of Orion.
~ I've watched C-beams glittering in the dark near the Tannhauser Gate.
~ All those moments will be lost in time, like tears ... in the rain.
~ Time to die."
~ -- Roy Batty, nexus 6 Tyrrel Corp. replicant, 2019 AC, L.A. --
pub 1024D/E8074ECF 2002-06-28 Hugo Espuny <[email protected]>
~ Key fingerprint = D324 3DC4 1F2A 0936 DEB9 A4D9 D24A 8237 E807 4ECF
sub 2048g/5FE11467 2002-09-29
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org
iD8DBQE9qHF10kqCN+gHTs8RAtchAKCRh/C7xWrbwE7pGl4oCTCfnnAtBwCcDPPR
7GPsS5Vy+9F66lSWcmh4JRQ=
=BcaX
-----END PGP SIGNATURE-----
Debbugs is free software and licensed under the terms of the GNU General
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.