Control: tags -1 moreinfo Hi!
On Fri, 2014-10-17 at 18:03:22 +0200, Andreas Beckmann wrote: > On 2014-10-17 17:23, Guillem Jover wrote: > > … yes, please explain how to reproduce. :) > > Sorry for my brevity in the initial report, was in a hurry ... > and had first noticed this with my non-free packages. No problem. > This is in a pbuilder sid amd64 chroot (that nicely builds all my packages) > > There are many many "Setting up" lines missing, last example further down > does not need "local" packages. > (pbuild22618)root@zam904:/# apt-get install libpfm4-dev > Reading package lists... Done > Building dependency tree > Reading state information... Done > The following extra packages will be installed: > libpfm4 > The following NEW packages will be installed: > libpfm4 libpfm4-dev > 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. > Need to get 0 B/409 kB of archives. > After this operation, 3183 kB of additional disk space will be used. > Do you want to continue? [Y/n] > debconf: unable to initialize frontend: Dialog > debconf: (No usable dialog-like program is installed, so the dialog based > frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line > 76, <> line 2.) > debconf: falling back to frontend: Readline > Selecting previously unselected package libpfm4:amd64. > (Reading database ... 20075 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) ... > > # and again nothing ... 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. 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. Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
