On Wed, Aug 28, 2024 at 12:56:32AM +0200, Guillem Jover wrote: > On Fri, 2024-06-21 at 10:53:20 +0300, Martin-Éric Racine wrote: > > Unpacking pci.ids (0.0~2024.05.31-1) over (0.0~2024.04.20-1) ... > > debconf: Unable to load Debconf::Element::Dialog. Failed because: Can't > > locate Debconf/Element/Dialog.pm in @INC (you may need to install the > > Debconf::Element::Dialog module) (@INC entries checked: /etc/perl > > /usr/local/lib/i386-linux-gnu/perl/5.38.2 /usr/local/share/perl/5.38.2 > > /usr/lib/i386-linux-gnu/perl5/5.38 /usr/share/perl5 > > /usr/lib/i386-linux-gnu/perl-base /usr/lib/i386-linux-gnu/perl/5.38 > > /usr/share/perl/5.38 /usr/local/lib/site_perl) at (eval 19) line 1, <GEN0> > > line 3. > > BEGIN failed--compilation aborted at (eval 19) line 1, <GEN0> line 3. > > > > Can't locate object method "new" via package "Debconf::Element::Dialog" > > (perhaps you forgot to load "Debconf::Element::Dialog"?) at > > /usr/share/perl5/Debconf/FrontEnd.pm line 69, <GEN0> line 3. > > Setting up pci.ids (0.0~2024.05.31-1) ... > > As mentioned on the report, this is not an issue with pci.ids, but > with something (apt) calling debconf (perhaps indirectly) between the > unpack and configure runs. I'd assume an apt hook is causing this. I'm > reassigning this to debconf as the actual thing apparently failing, but > if the actual hook (or caller) can be tracked down then perhaps that > can be reassigned there. (Sorry for passing along this hot potato. :) > > (The BTS contains mails with several log files, and some analysis.)
Martin-Éric, could you provide the output of "ls /etc/apt/apt.conf.d/" and "grep -E 'debconf|dpkg-' /etc/apt/apt.conf.d/*"? That would probably speed up the search here. Thanks, -- Colin Watson (he/him) [[email protected]]
