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

Bug#449600: marked as done (packages that fail to configure prevent totally unrelated packages from installing.)

Your message dated Thu, 13 Aug 2015 17:38:40 +0200
with message-id <20150813153840.GA12257@crossbow>
and subject line Re: aptitude upgrades itself, then fails due to missing libapt-pkg-libc6.6-6.so.4.4
has caused the Debian Bug report #449600,
regarding packages that fail to configure prevent totally unrelated packages from installing.
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.)


-- 
449600: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=449600
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Subject: aptitude upgrades itself, then fails due to missing libapt-pkg-libc6.6-6.so.4.4
Package: aptitude
Version: 0.4.6.1-1.1
Severity: normal

*** Please type your report below this line ***

I just upgraded this relatively small, cleanbb debian etch amd64 system
to lenny by changing /etc/apt/source.list, and then doing:

aptitude update
aptitude dist-upgrade

and aptitude broke itself, because it upgraded itself without ensuring
the apt package was properly upgraded firstb.

In particular, there was a mailman installation which had an
outstanding message, which caused an error during the upgrade.  for
whatever reason, aptitude apparently thought that meant that it
shouldn't bother installing the new version of apt before quitting,
which left it broken.

Here's a snippet of the console during this process, followed by me
trying another dist-upgrade, showing the brokennes:

-------------------
dpkg: error processing /var/cache/apt/archives/mailman_1%3a2.1.9-8_amd64.deb (--unpack):
 subprocess pre-installation script returned error exit status 1
No updates are necessary.
Starting Mailman master qrunner: mailmanctl.
Preparing to replace apt-utils 0.6.46.4-0.1 (using .../apt-utils_0.7.6_amd64.deb) ...
Unpacking replacement apt-utils ...
Preparing to replace aptitude 0.4.4-4 (using .../aptitude_0.4.6.1-1.1_amd64.deb) ...
Unpacking replacement aptitude ...
Preparing to replace debian-archive-keyring 2007.07.31~etch1 (using .../debian-archive-keyring_2007.07.31_all.deb) ...
Unpacking replacement debian-archive-keyring ...
Errors were encountered while processing:
 /var/cache/apt/archives/mailman_1%3a2.1.9-8_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up debian-archive-keyring (2007.07.31) ...
gpg: key 2D230C5F: "Debian Archive Automatic Signing Key (2006) <ftpmaster@debian.org>" not changed
gpg: key 6070D3A1: "Debian Archive Automatic Signing Key (4.0/etch) <ftpmaster@debian.org>" not changed
gpg: key ADB11277: "Etch Stable Release Key <debian-release@lists.debian.org>" not changed
gpg: key BBE55AB3: "Debian-Volatile Archive Automatic Signing Key (4.0/etch)" not changed
gpg: Total number processed: 4
gpg:              unchanged: 4
dpkg: dependency problems prevent configuration of aptitude:
 aptitude depends on libapt-pkg-libc6.6-6-4.4; however:
  Package libapt-pkg-libc6.6-6-4.4 is not installed.
dpkg: error processing aptitude (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of apt-utils:
 apt-utils depends on libapt-pkg-libc6.6-6-4.4; however:
  Package libapt-pkg-libc6.6-6-4.4 is not installed.
dpkg: error processing apt-utils (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 aptitude
 apt-utils
255 mailmantest:~# aptitude dist-upgrade
aptitude: error while loading shared libraries: libapt-pkg-libc6.6-6.so.4.4: cannot open shared object file: No such file or directory
127 mailmantest:~# 
-----------------

i managed to fix this by falling back to apt-get instead of aptitude:

--------------------
0 mailmantest:~# apt-get install apt
Reading package lists... Done
Building dependency tree... Done
Suggested packages:
  dpkg-dev apt-doc bzip2 lzma
The following packages will be upgraded:
  apt
1 upgraded, 0 newly installed, 0 to remove and 55 not upgraded.
2 not fully installed or removed.
Need to get 0B/1469kB of archives.
After unpacking 77.8kB of additional disk space will be used.
apt-extracttemplates: error while loading shared libraries: libapt-pkg-libc6.6-6.so.4.4: cannot open shared object file: No such file or directory
debconf: apt-extracttemplates failed: Bad file descriptor(Reading database ... 15806 files and directories currently installed.)
Preparing to replace apt 0.6.46.4-0.1 (using .../archives/apt_0.7.6_amd64.deb) ...
Unpacking replacement apt ...
Setting up apt (0.7.6) ...
Installing new version of config file /etc/cron.daily/apt ...
gpg: key 2D230C5F: "Debian Archive Automatic Signing Key (2006) <ftpmaster@debian.org>" not changed
gpg: key 6070D3A1: "Debian Archive Automatic Signing Key (4.0/etch) <ftpmaster@debian.org>" not changed
gpg: key ADB11277: "Etch Stable Release Key <debian-release@lists.debian.org>" not changed
gpg: key BBE55AB3: "Debian-Volatile Archive Automatic Signing Key (4.0/etch)" not changed
gpg: Total number processed: 4
gpg:              unchanged: 4
Setting up apt-utils (0.7.6) ...
Setting up aptitude (0.4.6.1-1.1) ...
0 mailmantest:~# 
-----------------------

and then aptitude worked again.

Thanks for maintaining the one of the best package managment tools in
the universe!

	--dkg


-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.18-5-xen-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages aptitude depends on:
ii  apt [libapt-pkg-libc6.6-6 0.7.6          Advanced front-end for dpkg
ii  libc6                     2.6.1-1        GNU C Library: Shared libraries
ii  libgcc1                   1:4.2.2-3      GCC support library
ii  libncursesw5              5.6+20071013-1 Shared libraries for terminal hand
ii  libsigc++-2.0-0c2a        2.0.17-2       type-safe Signal Framework for C++
ii  libstdc++6                4.2.2-3        The GNU Standard C++ Library v3

Versions of packages aptitude recommends:
pn  aptitude-doc-en | aptitude-do <none>     (no description available)
pn  libparse-debianchangelog-perl <none>     (no description available)

-- no debconf information

Attachment: pgpXoWKK8HWFs.pgp
Description: PGP signature


--- End Message ---
--- Begin Message --- 
Hi,

On Tue, Nov 06, 2007 at 06:23:34PM -0500, Daniel Kahn Gillmor wrote:
> Subject: aptitude upgrades itself, then fails due to missing libapt-pkg-libc6.6-6.so.4.4
> and aptitude broke itself, because it upgraded itself without ensuring
> the apt package was properly upgraded firstb.
> 
> In particular, there was a mailman installation which had an
> outstanding message, which caused an error during the upgrade.  for
> whatever reason, aptitude apparently thought that meant that it
> shouldn't bother installing the new version of apt before quitting,
> which left it broken.

Failing maintainerscripts cause apt (and everything above like aptitude)
to eventually error out. This is so that the failure can be resolved
before we continue (with another apt call or whatever). So that is kinda
expected, you just happened to be unlucky to hit this while upgrading
apt which back then had its library bundled which aptitude used, too.
That is now better (the library is split out).


> Thanks for maintaining the one of the best package managment tools in
> the universe!

No problem – and we are still hiring bugtriagers to response sooner than
8 years later to bugreports, so if you are interest… ;)


More seriously, I don't see anything actionable we could do further to
fix this bugreport, so I am gonna close this report now before waiting
another 8 years… If you have an idea feel free to reopen this bug and/or
open a new bug, of course!


Best regards

David Kalnischkies

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: