Bug#731527: apt-listbugs: no package can get installed

Francesco Poli

unread,

Dec 6, 2013, 2:00:02 PM12/6/13

to

Control: notfound -1 apt-listbugs/0.1.9
Control: found -1 apt-listbugs/0.1.11
Control: severity -1 important
Control: tags -1 + moreinfo

On Fri, 06 Dec 2013 10:56:37 +0100 Enrique Garcia wrote:

> Package: apt-listbugs
> Version: 0.1.9
> Severity: grave
> Tags: upstream
> Justification: renders package unusable
>
> Dear Maintainer,

Hello Enrique,
thanks for your bug report.

>
> No package can be installed using version 0.1.11.

If you are experiencing the issue with apt-listbugs/0.1.11, it would
have been better to report the bug while having that version installed,
not after downgrading it...
I am fixing the version info of this report.

> This error is shown when you
> try to install any package using synaptic or aptitude (and any other install
> manager I guess).
>
> > E: APT_HOOK_INFO_FD is not correctly defined.
> > E: Sub-process /usr/sbin/apt-listbugs apt || exit 10 returned an error code
> (10)
> > E: Failure running script /usr/sbin/apt-listbugs apt || exit 10
>
> Downgrading to version 0.1.9 solves the problem.

It seems to me that you are using an outdated version of the
configuration file.

Please paste the output of the following command in your reply:

$ cat /etc/apt/apt.conf.d/10apt-listbugs

Maybe you customized this configuration file in the past and you didn't
accept the new version shipped with apt-listbugs/0.1.11 when upgrading
from apt-listbugs/0.1.9 ?
If this is the case, then please upgrade again to apt-listbugs/0.1.11,
accept the new version of the configuration file and then (possibly)
re-adapt it to your needs.
Please don't hesitate to ask for help, if you are not sure how to
proceed.

Please let me know, in any case.

--
http://www.inventati.org/frx/frx-gpg-key-transition-2010.txt
New GnuPG key, see the transition document!
..................................................... Francesco Poli .
GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE

Enrique

unread,

Dec 6, 2013, 4:30:01 PM12/6/13

to

On 06/12/13 19:53, Francesco Poli wrote:
> Control: notfound -1 apt-listbugs/0.1.9
> Control: found -1 apt-listbugs/0.1.11
> Control: severity -1 important
> Control: tags -1 + moreinfo
>
>
> On Fri, 06 Dec 2013 10:56:37 +0100 Enrique Garcia wrote:
>
>> Package: apt-listbugs
>> Version: 0.1.9
>> Severity: grave
>> Tags: upstream
>> Justification: renders package unusable
>>
>> Dear Maintainer,
> Hello Enrique,
> thanks for your bug report.
>
>> No package can be installed using version 0.1.11.
> If you are experiencing the issue with apt-listbugs/0.1.11, it would
> have been better to report the bug while having that version installed,
> not after downgrading it...
> I am fixing the version info of this report.

My apologies about that.

>
>> This error is shown when you
>> try to install any package using synaptic or aptitude (and any other install
>> manager I guess).
>>
>>> E: APT_HOOK_INFO_FD is not correctly defined.
>>> E: Sub-process /usr/sbin/apt-listbugs apt || exit 10 returned an error code
>> (10)
>>> E: Failure running script /usr/sbin/apt-listbugs apt || exit 10
>> Downgrading to version 0.1.9 solves the problem.
> It seems to me that you are using an outdated version of the
> configuration file.
>
> Please paste the output of the following command in your reply:
>
> $ cat /etc/apt/apt.conf.d/10apt-listbugs

$ cat /etc/apt/apt.conf.d/10apt-listbugs
// Before installing packages, check whether they have release-critical bugs.
// If you don't like it, comment it out.
DPkg::Pre-Install-Pkgs {"/usr/sbin/apt-listbugs apt";};
DPkg::Tools::Options::/usr/sbin/apt-listbugs "";
DPkg::Tools::Options::/usr/sbin/apt-listbugs::Version "3";
DPkg::Tools::Options::/usr/sbin/apt-listbugs::InfoFD "20";
AptListbugs::Severities "critical,grave,serious";
// AptListbugs::IgnoreRegexp "FTBFS";

>
> Maybe you customized this configuration file in the past and you didn't
> accept the new version shipped with apt-listbugs/0.1.11 when upgrading
> from apt-listbugs/0.1.9 ?

I don't remember having done that.

> If this is the case, then please upgrade again to apt-listbugs/0.1.11,
> accept the new version of the configuration file and then (possibly)
> re-adapt it to your needs.
> Please don't hesitate to ask for help, if you are not sure how to
> proceed.
>
> Please let me know, in any case.
>
--

Enrique Garcia

--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Francesco Poli

unread,

Dec 6, 2013, 5:10:03 PM12/6/13

to

On Fri, 06 Dec 2013 22:21:33 +0100 Enrique wrote:

> On 06/12/13 19:53, Francesco Poli wrote:

[...]

> > On Fri, 06 Dec 2013 10:56:37 +0100 Enrique Garcia wrote:

[...]

> >> No package can be installed using version 0.1.11.
> > If you are experiencing the issue with apt-listbugs/0.1.11, it would
> > have been better to report the bug while having that version installed,
> > not after downgrading it...
> > I am fixing the version info of this report.
> My apologies about that.

No problems...

> >
> >> This error is shown when you
> >> try to install any package using synaptic or aptitude (and any other install
> >> manager I guess).
> >>
> >>> E: APT_HOOK_INFO_FD is not correctly defined.
> >>> E: Sub-process /usr/sbin/apt-listbugs apt || exit 10 returned an error code
> >> (10)
> >>> E: Failure running script /usr/sbin/apt-listbugs apt || exit 10
> >> Downgrading to version 0.1.9 solves the problem.
> > It seems to me that you are using an outdated version of the
> > configuration file.
> >
> > Please paste the output of the following command in your reply:
> >
> > $ cat /etc/apt/apt.conf.d/10apt-listbugs
> $ cat /etc/apt/apt.conf.d/10apt-listbugs
> // Before installing packages, check whether they have release-critical bugs.
> // If you don't like it, comment it out.
> DPkg::Pre-Install-Pkgs {"/usr/sbin/apt-listbugs apt";};
> DPkg::Tools::Options::/usr/sbin/apt-listbugs "";
> DPkg::Tools::Options::/usr/sbin/apt-listbugs::Version "3";
> DPkg::Tools::Options::/usr/sbin/apt-listbugs::InfoFD "20";
> AptListbugs::Severities "critical,grave,serious";
> // AptListbugs::IgnoreRegexp "FTBFS";

Are you experiencing the bug with *this* configuration file and with
apt-listbugs/0.1.11 installed?!?

The error message you quoted seems to indicate that you had a different
10apt-listbugs configuration file when you experienced the issue...

Please let me know.

>
> >
> > Maybe you customized this configuration file in the past and you didn't
> > accept the new version shipped with apt-listbugs/0.1.11 when upgrading
> > from apt-listbugs/0.1.9 ?
> I don't remember having done that.

The mystery deepens... :-/

Enrique

unread,

Dec 6, 2013, 5:20:05 PM12/6/13

to

Yes.

> The error message you quoted seems to indicate that you had a different
> 10apt-listbugs configuration file when you experienced the issue...
>
> Please let me know.

For some reason the env var APT_HOOK_INFO_FD is getting value 0. How is the env
var setted?

>>> Maybe you customized this configuration file in the past and you didn't
>>> accept the new version shipped with apt-listbugs/0.1.11 when upgrading
>>> from apt-listbugs/0.1.9 ?
>> I don't remember having done that.
> The mystery deepens... :-/
>
>
>
>

--

Francesco Poli

unread,

Dec 6, 2013, 5:40:04 PM12/6/13

to

On Fri, 06 Dec 2013 23:08:51 +0100 Enrique wrote:

> On 06/12/13 22:59, Francesco Poli wrote:
> > On Fri, 06 Dec 2013 22:21:33 +0100 Enrique wrote:
> >
> >> On 06/12/13 19:53, Francesco Poli wrote:
> > [...]
> >>> On Fri, 06 Dec 2013 10:56:37 +0100 Enrique Garcia wrote:
[...]

> >>>> This error is shown when you
> >>>> try to install any package using synaptic or aptitude (and any other install
> >>>> manager I guess).
> >>>>
> >>>>> E: APT_HOOK_INFO_FD is not correctly defined.
> >>>>> E: Sub-process /usr/sbin/apt-listbugs apt || exit 10 returned an error code
> >>>> (10)
> >>>>> E: Failure running script /usr/sbin/apt-listbugs apt || exit 10
> >>>> Downgrading to version 0.1.9 solves the problem.
> >>> It seems to me that you are using an outdated version of the
> >>> configuration file.
> >>>
> >>> Please paste the output of the following command in your reply:
> >>>
> >>> $ cat /etc/apt/apt.conf.d/10apt-listbugs
> >> $ cat /etc/apt/apt.conf.d/10apt-listbugs
> >> // Before installing packages, check whether they have release-critical bugs.
> >> // If you don't like it, comment it out.
> >> DPkg::Pre-Install-Pkgs {"/usr/sbin/apt-listbugs apt";};
> >> DPkg::Tools::Options::/usr/sbin/apt-listbugs "";
> >> DPkg::Tools::Options::/usr/sbin/apt-listbugs::Version "3";
> >> DPkg::Tools::Options::/usr/sbin/apt-listbugs::InfoFD "20";
> >> AptListbugs::Severities "critical,grave,serious";
> >> // AptListbugs::IgnoreRegexp "FTBFS";
> > Are you experiencing the bug with *this* configuration file and with
> > apt-listbugs/0.1.11 installed?!?
> Yes.

This is really awkward.

> > The error message you quoted seems to indicate that you had a different
> > 10apt-listbugs configuration file when you experienced the issue...

Let me elaborate a bit: the error message you quoted talks about
sub-process "/usr/sbin/apt-listbugs apt || exit 10". This is the
process that exits unsuccessfully.

If your /etc/apt/apt.conf.d/10apt-listbugs invokes
"/usr/sbin/apt-listbugs apt", it looks as if something else invoked
"/usr/sbin/apt-listbugs apt || exit 10" ...

Could you please run

$ grep -r exit /etc/apt/apt.conf.d/

and paste the output in your reply?

Also, do you have a /etc/apt/apt.conf file?
If so, please run

$ grep exit /etc/apt/apt.conf

and paste the output in your reply.

> >
> > Please let me know.
> For some reason the env var APT_HOOK_INFO_FD is getting value 0. How is the env
> var setted?

This environment variable is set by apt-get (or compatible package
managers, such as aptitude) before invoking apt-listbugs. The value is
set in the option:

DPkg::Tools::Options::/usr/sbin/apt-listbugs::InfoFD "20";

Hence, it should be 20 in your case.

Enrique

unread,

Dec 6, 2013, 6:00:02 PM12/6/13

to

Let me add something else more akward, after reinstalling 0.1.11 version again (this maybe the 4th), now the bug is not reproduced any more.
My only explanation is that, as you said, for some reason config file was not properly installed in some installations. After upgrading/downgrading cycles the config file was finally properly installed.

Anyway, thanks for your great and fast help.