Control: tags -1 moreinfo

On Fri, Nov 21, 2014 at 12:00:53PM +0100, Holger Levsen wrote:
> https://jenkins.debian.net/view/d-i_manual/job/chroot-installation_wheezy_install_education-thin-client-server_upgrade_to_jessie/5/console
> and 
> https://jenkins.debian.net/view/d-i_manual/job/chroot-installation_wheezy_install_education-workstation_upgrade_to_jessie/5/console
> (and several attempts before) hang "forever" at 

> Preparing to unpack .../libpam-modules-bin_1.1.8-3.1_amd64.deb ...
> Unpacking libpam-modules-bin (1.1.8-3.1) over (1.1.3-7.1) ...
> Replacing files in old package libpam-modules:amd64 (1.1.3-7.1) ...
> Setting up libpam-modules-bin (1.1.8-3.1) ...

> I don't see any useful hint whats happening when looking at the processes:

> 29258 ?        S      0:00      \_ /bin/sh -xe 
> /tmp/hudson8147454957601885791.sh
> 29272 ?        S      0:00      |   \_ /bin/bash 
> /srv/jenkins/bin/chroot-installation.sh wheezy education-thin-client-server 
> jessie
> 29308 ?        S      0:00      |       \_ /usr/bin/python 
> /srv/jenkins/bin/setsid.py /tmp/jenkins-script-ObHlitjD wheezy 
> education-thin-client-server jessie
> 29325 ?        Ss     0:00      |           \_ /bin/bash 
> /tmp/jenkins-script-ObHlitjD wheezy education-thin-client-server jessie
> 39022 ?        S      0:00      |               \_ sudo chroot 
> /chroots/chroot-installation-wheezy.yru9xUhsR /tmp/tmp.7L3G0jVHmA
> 39023 ?        S      0:00      |                   \_ /bin/sh 
> /tmp/tmp.7L3G0jVHmA
> 12963 ?        S      0:08      |                       \_ apt-get -yf 
> dist-upgrade
> 57306 ?        R    124:55      |                           \_ /usr/bin/dpkg 
> --status-fd 17 --unpack --auto-deconfigure 
> /var/cache/apt/archives/libpam-modules_1.1.8-3.1_amd64.deb

The libpam-modules-bin package ships no maintainer scripts.  Therefore there
is nothing at the "setting up" stage which is under control of this package.
Your ps output also shows that the package currently being installed is
libpam-modules, *not* libpam-modules-bin.  libpam-modules does have
maintainer scripts, but your output doesn't show the line that would be
expected, "Preparing to unpack", which should be emitted before the
(debconf-using) preinst script is called.

So this doesn't look to me like a bug in the pam package.  It would be
interesting to know what 'pidof xscreensaver xlockmore' returns on the
affected system, in case there is some interaction with the preinst script.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
[email protected]                                     [email protected]

Attachment: signature.asc
Description: Digital signature

Reply via email to