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

Bug#953260: marked as done (E: Could not perform immediate configuration on 'libgcc1:amd64'.)

Your message dated Fri, 06 Mar 2020 18:58:53 +0100
with message-id <158351753346.2089.4577223866365674492@hoothoot>
and subject line Re: Bug#953260: Acknowledgement (E: Could not perform immediate configuration on 'libgcc1:amd64'.)
has caused the Debian Bug report #953260,
regarding E: Could not perform immediate configuration on 'libgcc1:amd64'.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
953260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953260
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: apt
Version: 1.9.10
Severity: normal

Hi,

recently mmdebstrap gained a new feature called --simulate which will
call apt with -oAPT::Get::Simulate=true. While this works fine in Debian
stable, it fails in current testing and unstable. To reproduce the
problem consider the Packages file at the end of this mail and the
following mmdebstrap command:

./mmdebstrap --verbose --dry-run --variant=essential . debian.tar "deb [trusted=yes] copy://$(pwd)/repo/ main ."
[...]
Reading package lists...
Building dependency tree...
The following additional packages will be installed:
  gcc-10-base libc6 libcrypt1 libgcc-s1 libgcc1
The following NEW packages will be installed:
  gcc-10-base libc-bin libc6 libcrypt1 libgcc-s1 libgcc1
0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded.
Inst gcc-10-base (10-20200222-1 localhost [amd64])
Conf gcc-10-base (10-20200222-1 localhost [amd64])
Inst libgcc-s1 (10-20200222-1 localhost [amd64]) []
Inst libc6 (2.29-10 localhost [amd64]) []
Inst libgcc1 (1:10-20200222-1 localhost [amd64]) []
Inst libcrypt1 (1:4.4.15-1 localhost [amd64])
Conf libgcc1 (1:10-20200222-1 localhost [amd64])
Conf libcrypt1 (1:4.4.15-1 localhost [amd64])
Conf libc6 (2.29-10 localhost [amd64])
Conf libgcc-s1 (10-20200222-1 localhost [amd64])
Inst libc-bin (2.29-10 localhost [amd64])
Conf libc-bin (2.29-10 localhost [amd64])
E: Could not configure 'libc6:amd64'. 
E: Could not perform immediate configuration on 'libgcc1:amd64'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2)


The apt command executed by mmdebstrap is essentialy:

APT_CONFIG=foo apt-get --yes -oApt::Get::Download-Only=true -oAPT::Get::Simulate=true install libc-bin

And where foo contains stuff along the lines of:

Apt::Architecture "amd64";
Apt::Architectures "amd64";
Dir "/tmp/mmdebstrap.Dt_RUrBC0g";
Dir::State::Status "/tmp/mmdebstrap.Dt_RUrBC0g/var/lib/dpkg/status";
Dir::Etc::Trusted "/etc/apt/trusted.gpg";
Dir::Etc::TrustedParts "/etc/apt/trusted.gpg.d/";
pkgCacheGen::ForceEssential ",";

I don't even know whether you care about this but the dependency
situation seems trivial so maybe this is actually an important bug?

Thanks!

cheers, josch





Package: libc-bin
Version: 2.29-10
Architecture: amd64
Depends: libc6
Essential: yes
Filename: foo
MD5sum: bar

Package: libc6
Version: 2.29-10
Architecture: amd64
Depends: libgcc1, libcrypt1
Filename: foo
MD5sum: bar

Package: libcrypt1
Version: 1:4.4.15-1
Architecture: amd64
Depends: libc6
Filename: foo
MD5sum: bar

Package: libgcc1
Version: 1:10-20200222-1
Architecture: amd64
Depends: gcc-10-base, libgcc-s1, libc6
Filename: foo
MD5sum: bar

Package: gcc-10-base
Version: 10-20200222-1
Architecture: amd64
Filename: foo
MD5sum: bar

Package: libgcc-s1
Version: 10-20200222-1
Architecture: amd64
Depends: gcc-10-base, libc6
Filename: foo
MD5sum: bar

--- End Message ---
--- Begin Message --- 
Okay, this is embarrassing... The solution was even in the error message.
Setting APT::Immediate-Configure to false fixes this problem. Thanks! :)

Attachment: signature.asc
Description: signature


--- End Message ---
Reply to: