Hi!

There is not enough context in the report to really see what's going
on here.

On Fri, 2024-06-21 at 10:53:20 +0300, Martin-Éric Racine wrote:
> Package: pci.ids
> Version: 0.0~2024.05.31-1
> Severity: normal

> 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) ...

I don't see pci.ids failing to configure, at least there's no error
message after «Setting up» which would indicate that step of the
process. The errors happen between Unpacking and Setting up, but then
pci.ids has no debconf support at all, so this should be something
else. I'd assume something (apt perhaps?) is invoking something
debconf related in-between. But then the modules being complained
about are all inside debconf, so if those are failing then this would
look like a debconf issue?

In any case:
  - this is definitely not a pci.ids issue,
  - it's not clear who is invoking debconf (checking logs might help),
  - this looks like a potential debconf issue (but could be something
    else, like damaged system or partially configured packages).

So I'd either close this, or reassign, but it's not clear where, and
given the unclear culprit I'm a bit reluctant to dump this as is into
someone else tracker. :/

Thanks,
Guillem

Reply via email to