Martin-Éric, even with APT::Immediate-Configure set to true, I'm unable to reproduce the failure you see:
$ apt-config dump | grep Immediate
APT::Immediate-Configure "true";
$ sudo sh -c 'LC_ALL=C apt-get install libsasl2-2'
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
libdb4.6
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
libsasl2-modules
Suggested packages:
libsasl2-modules-otp libsasl2-modules-ldap libsasl2-modules-sql libsasl2-modules-gssapi-mit libsasl2-modules-gssapi-heimdal
The following packages will be upgraded:
libsasl2-2 libsasl2-modules
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/286kB of archives.
After this operation, 32.8kB of additional disk space will be used.
Do you want to continue [Y/n]? y
(Reading database ... 116308 files and directories currently installed.)
Preparing to replace libsasl2-2 2.1.22.dfsg1-23ubuntu3.1 (using .../libsasl2-2_2.1.23.dfsg1-1ubuntu3_amd64.deb) ...
Unpacking replacement libsasl2-2 ...
Preparing to replace libsasl2-modules 2.1.22.dfsg1-23ubuntu3.1 (using .../libsasl2-modules_2.1.23.dfsg1-1ubuntu3_amd64.deb) ...
Unpacking replacement libsasl2-modules ...
Setting up libsasl2-modules (2.1.23.dfsg1-1ubuntu3) ...
Setting up libsasl2-2 (2.1.23.dfsg1-1ubuntu3) ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
$
Can you attach the output of 'apt-config dump'? What's the history of the system where this bug occurs; what was it originally installed as and how has it been upgraded?
Martin-Éric, even with APT::Immediate- Configure set to true, I'm unable to reproduce the failure you see:
$ apt-config dump | grep Immediate Immediate- Configure "true"; modules modules- otp libsasl2- modules- ldap libsasl2- modules- sql libsasl2- modules- gssapi- mit libsasl2- modules- gssapi- heimdal dfsg1-23ubuntu3 .1 (using .../libsasl2- 2_2.1.23. dfsg1-1ubuntu3_ amd64.deb) ... dfsg1-23ubuntu3 .1 (using .../libsasl2- modules_ 2.1.23. dfsg1-1ubuntu3_ amd64.deb) ... dfsg1-1ubuntu3) ... dfsg1-1ubuntu3) ...
APT::
$ sudo sh -c 'LC_ALL=C apt-get install libsasl2-2'
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
libdb4.6
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
libsasl2-
Suggested packages:
libsasl2-
The following packages will be upgraded:
libsasl2-2 libsasl2-modules
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/286kB of archives.
After this operation, 32.8kB of additional disk space will be used.
Do you want to continue [Y/n]? y
(Reading database ... 116308 files and directories currently installed.)
Preparing to replace libsasl2-2 2.1.22.
Unpacking replacement libsasl2-2 ...
Preparing to replace libsasl2-modules 2.1.22.
Unpacking replacement libsasl2-modules ...
Setting up libsasl2-modules (2.1.23.
Setting up libsasl2-2 (2.1.23.
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
$
Can you attach the output of 'apt-config dump'? What's the history of the system where this bug occurs; what was it originally installed as and how has it been upgraded?