package: libpam-modules-bin version: 1.1.8-3.1 severity: important x-debbugs-cc: upgrade-repo...@bugs.debian.org User: debian...@lists.debian.org Usertags: jenkins
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 /proc is mounted inside the chroot but nothing else: root@jenkins:~# mount|grep chroot-installation-wheezy.yru9xUhsR /proc on /srv/workspace/chroots/chroot-installation-wheezy.yru9xUhsR/proc type proc (rw,relatime) binfmt_misc on /srv/workspace/chroots/chroot-installation-wheezy.yru9xUhsR/proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime) root@jenkins:~# (I'm using plain /usr/sbin/chroot here, not /usr/bin/schroot.) OTOH, https://piuparts.debian.org/wheezy2jessie/pass/libpam-modules-bin_1.1.8-3.1.log does the upgrade just fine, so maybe this bug should only be of severity "important", filing as such, please upgrade the severity if you think thats appropriate. Thanks for maintaining pam!
signature.asc
Description: This is a digitally signed message part.
