[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#972552: Buster->Sid upgrades fail with 'Could not perform immediate configuration on 'libnss-nis:amd64''



Control: reassign -1 apt
Control: forcemerge 953260 -1
Control: affects 953260 libnss-nis

Hi Otto,

This is tracked in Ubuntu, too:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1871268

Cheers,
Balint

On Tue, Oct 20, 2020 at 10:12 AM Otto Kekäläinen <otto@debian.org> wrote:
>
> Package: libnss-nis
> Version: 3.1-4
>
> In my regular Buster to Sid upgrade testing I noticed that apt upgrade
> runs started failing one week ago with the error message:
>
> Processing triggers for libc-bin (2.31-4) ...
> E: Could not configure 'libc6:amd64'.
> E: Could not perform immediate configuration on 'libnss-nis:amd64'.
> Please see man 5 apt.conf under APT::Immediate-Configure for details.
> (2)
>
> Apt exit code is 100.
>
> The next apt run goes fine and the error is not permanent. I am filing
> this bug report anyway, as I suspect that having a apt-get exit code
> 100 in the middle of a standard upgrade is not the intended design for
> the overall user experience.
>
>
> Steps to reproduce:
>
> host$ docker run -it debian:buster bash
> docker$ echo 'deb http://deb.debian.org/debian sid main' > /etc/apt/sources.list
> docker$ apt-get update
> docker$ apt-get install -y libnss-nis
> ....
> Unpacking libc-bin (2.31-4) over (2.28-10) ...
> Setting up libc-bin (2.31-4) ...
> Selecting previously unselected package krb5-locales.
> (Reading database ... 6762 files and directories currently installed.)
> Preparing to unpack .../krb5-locales_1.17-10_all.deb ...
> Unpacking krb5-locales (1.17-10) ...
> Setting up krb5-locales (1.17-10) ...
> E: Could not configure 'libc6:amd64'.
> E: Could not perform immediate configuration on 'libnss-nis:amd64'.
> Please see man 5 apt.conf under APT::Immediate-Configure for details.
> (2)
> docker$ echo $?
> 100
>
>
> Running 'apt-get install -y -oApt::Immediate-Configure=true
> libnss-nis'  does not make the error go away.
>
>
> The issue https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953260 is
> potentially related.
>


-- 
Balint Reczey
Ubuntu & Debian Developer


Reply to: