Control: reassign -1 libapt-pkg4.12 1.0.9.3 Hi!
Including all of Andreas message to give context to the apt maintainers (CCed). Please see the bug log for further details. Andreas, thanks for the investigation! On Wed, 2014-10-29 at 21:54:53 +0100, Andreas Beckmann wrote: > Control: retitle -1 apt-get sometimes does not output "Setting up $p ($v) > ..." messages from dpkg > Control reassign -1 libapt-pkg4.12 1.0.9.3 > > On 2014-10-28 21:47, Guillem Jover wrote: > > Ok, could you try few things to try to discard possible problems. > > Could you enter the chroot w/o using pbuilder, and check with that > > directly, if you have not alrady tried that? After that, try installing > > whiptail so that debconf can use the Dialog interface. Otherwise, I > > don't know, would be nice to check possible differences with a normal > > system. > > I'm connecting to the machine via ssh and usually run stuff inside screen. So > I tried > * ssh, screen, pbuilder > * ssh, screen, chroot > * ssh, pbuilder > * ssh, chroot > all with whiptail installed and all with the same result: no "Setting up". > I'll test locally on the machine later ... > I also tested putting the chroot on a real file system instead of tmpfs - no > change. > > > In any case I don't think this is a problem with dpkg, maybe in the > > chroot, the setup or whoever is invoking it, in this case apt, but > > let's see. > > I also tried > strace -o foo -ff apt-get install libpfm4-dev > and grepping in the foo.* I find the "Setting up" from dpkg, but this seems > to be eaten by apt, as I didn't see it on screen. /var/log/apt/term.log also > misses these bits: > > Log started: 2014-10-29 19:55:25 > Selecting previously unselected package libpfm4:amd64. > (Reading database ... ^M(Reading database ... 5%^M(Reading database ... > 10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading database > ... 25%^M(Reading database ... 30%^M(Reading database ... 35%^M(Reading > database ... 40%^M(Reading database ... 45%^M(Reading database ... > 50%^M(Reading database ... 55%^M(Reading database ... 60%^M(Reading database > ... 65%^M(Reading database ... 70%^M(Reading database ... 75%^M^M(Reading > database ... 80%^M(Reading database ... 85%^M(Reading database ... > 90%^M(Reading database ... 95%^M(Reading database ... 100%^M(Reading database > ... 13951 files and directories currently installed.) > Preparing to unpack .../libpfm4_4.5.0+git38-g1ca1338-2_amd64.deb ... > Unpacking libpfm4:amd64 (4.5.0+git38-g1ca1338-2) ... > Selecting previously unselected package libpfm4-dev:amd64. > Preparing to unpack .../libpfm4-dev_4.5.0+git38-g1ca1338-2_amd64.deb ... > Unpacking libpfm4-dev:amd64 (4.5.0+git38-g1ca1338-2) ... > Log ended: 2014-10-29 19:55:27 > > Hmm, now I have even seen this on the "host" system with wheezy's aptitude > (and libapt* and dpkg from jessie). > > Seems to be apt's fault: > > wheezy-pbuilder-chroot > * works fine > > wheezy-pbuilder-chroot, upgrade libapt-pkg4.12 to jessie (requires updating > libc6, libstdc++6, libapt-inst1.5, too) apt, dpkg are from wheezy > * messages are missing > > wheezy-pbuilder-chroot, upgrade libc6, libstdc++6, libapt-inst1.5, to jessie, > but keep libapt-pkg4.12 at wheezy's version > * works fine > > (pbuild5842)# dpkg -i > /var/cache/apt/archives/libapt-pkg4.12_1.0.9.3_amd64.deb > (Reading database ... 13787 files and directories currently installed.) > Preparing to replace libapt-pkg4.12:amd64 0.9.7.9+deb7u6 (using > .../libapt-pkg4.12_1.0.9.3_amd64.deb) ... > Unpacking replacement libapt-pkg4.12:amd64 ... > Setting up libapt-pkg4.12:amd64 (1.0.9.3) ... > (pbuild5842)# apt-get install libjpeg8-dev > Reading package lists... Done > Building dependency tree > Reading state information... Done > The following extra packages will be installed: > libjpeg8 > The following NEW packages will be installed: > libjpeg8 libjpeg8-dev > 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. > Need to get 0 B/383 kB of archives. > After this operation, 837 kB of additional disk space will be used. > Do you want to continue [Y/n]? > Selecting previously unselected package libjpeg8:amd64. > (Reading database ... 13788 files and directories currently installed.) > Unpacking libjpeg8:amd64 (from .../libjpeg8_8d-1+deb7u1_amd64.deb) ... > Selecting previously unselected package libjpeg8-dev:amd64. > Unpacking libjpeg8-dev:amd64 (from .../libjpeg8-dev_8d-1+deb7u1_amd64.deb) ... > ***** here the messages are missing ***** > (pbuild5842)# dpkg --purge libjpeg8-dev libjpeg8 > (Reading database ... 13811 files and directories currently installed.) > Removing libjpeg8-dev:amd64 ... > Removing libjpeg8:amd64 ... > (pbuild5842)# dpkg -i > /var/cache/apt/archives/libapt-pkg4.12_0.9.7.9+deb7u6_amd64.deb > dpkg: warning: downgrading libapt-pkg4.12:amd64 from 1.0.9.3 to 0.9.7.9+deb7u6 > (Reading database ... 13788 files and directories currently installed.) > Preparing to replace libapt-pkg4.12:amd64 1.0.9.3 (using > .../libapt-pkg4.12_0.9.7.9+deb7u6_amd64.deb) ... > Unpacking replacement libapt-pkg4.12:amd64 ... > Setting up libapt-pkg4.12:amd64 (0.9.7.9+deb7u6) ... > (pbuild5842)# apt-get install libjpeg8-dev > Reading package lists... Done > Building dependency tree > Reading state information... Done > The following extra packages will be installed: > libjpeg8 > The following NEW packages will be installed: > libjpeg8 libjpeg8-dev > 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. > Need to get 0 B/383 kB of archives. > After this operation, 837 kB of additional disk space will be used. > Do you want to continue [Y/n]? > Selecting previously unselected package libjpeg8:amd64. > (Reading database ... 13787 files and directories currently installed.) > Unpacking libjpeg8:amd64 (from .../libjpeg8_8d-1+deb7u1_amd64.deb) ... > Selecting previously unselected package libjpeg8-dev:amd64. > Unpacking libjpeg8-dev:amd64 (from .../libjpeg8-dev_8d-1+deb7u1_amd64.deb) ... > ***** this is fine: ***** > Setting up libjpeg8:amd64 (8d-1+deb7u1) ... > Setting up libjpeg8-dev:amd64 (8d-1+deb7u1) ... > (pbuild5842)# > > The same problem with missing messages occurs in a clean jessie or sid > pbuilder chroot. > In addition to the "Setting up" messages, also the "Processing triggers" > messages seem to be missing sometimes (no testcase). > If I install something larger (e.g. libreoffice) I do get (some? all?) > "Setting up" messages. Thanks, Guillem -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
