[Bug 503765] Re: aptitude pkgstates gets corrupted
Sergio Callegari
sergio.callegari at gmail.com
Mon Sep 3 16:47:40 UTC 2012
I guess that invalidation of the bug comes after the long time elapsed
since its initial reporting and the subsequent inactivity.
Since reporting, I have simply stopped using aptitude, moving to apt-
get, so I do not have any test case, nor I know if the bug is still
valid.
However, I wonder if before declaring the bug invalid, the logic in
aptitude has been evaluated with respect to the possibility of something
changing behind his back in the installed packages due to the usage of
another package manager.
If aptitude only relies on its own view of the installed packages (which
might not reflect the actual situation of the installed packages due to
the use of another package manager between two aptitude invocations)
then its usage can become dangerous and IMHO the users should at least
be warned about it.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to aptitude in Ubuntu.
https://bugs.launchpad.net/bugs/503765
Title:
aptitude pkgstates gets corrupted
Status in “aptitude” package in Ubuntu:
New
Bug description:
Binary package hint: aptitude
On four different machines (one 32 bit, two 64bit), I am recently
experiencing corruptions in the package status database private to
aptitude, namely /var/lib/aptitude/pkgstates.
This results in a crazy behavior of aptitude, that starts thinking
that many packages are broken when in fact they are not. For
instance.
aptitude install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
The following packages are BROKEN:
apturl gnome-app-install libgpod4 libgpod4-nogtk mysql-server-core-5.1 rsyslog wine1.2
The following NEW packages will be installed:
acl binutils-static emacs22 emacs22-bin-common emacs22-common firefox-3.0-branding gcj-4.3
gfortran-4.3 gij gnome-mount imagemagick-doc klogd libavutil-unstripped-49
libboost-regex1.34.1 libboost-serialization1.34.1 libfame-0.9 libgcj9-0-awt libgcj9-dev
libggi-target-x libggi2 libgii1 libgii1-target-x libgmyth0 liblrdf0 libpolkit-gnome0
libpvm3 libsmbios2 libsoprano-dev libwxbase2.6-0 libwxgtk2.6-0 mysql-server-core-5.0
nvidia-180-kernel-source nvidia-180-libvdpau policykit-gnome pvm python-gconf
python-gst0.10 python-launchpad-integration python-pyorbit python-sexy sysklogd
ttf-bengali-fonts ttf-kannada-fonts ttf-oriya-fonts ttf-telugu-fonts update-motd wine
wine-gecko
This is very very dangerous, because, following up with its crazy
diagnosis, aptitude starts suggesting actions that can completely
break a system.
And the crazyness of aptitude can be very easily seen by considering
that for apt-get, synaptic and all the other front-ends to dpkg
everything is just fine.
Interestingly, aptitude starts reporting as broken either packages
that are installed and packages that are not installed. If one tries
an
aptitude remove <package that is not installed but is reported as
broken>
then aptitude does nothing, but the behavior of aptitude after this
sanifies a bit.
removing /var/lib/aptitude/pkgstates completely fixes the issue.
In the "wrong" pkgstates, it looks like many entries are just weird.
For instance, installed packages are indicated as unseen, and after
pkgstates is removed and re-generated, for many packages the state is
then different.
I tend to think that bug reports 477468 and 39497 are in fact caused by this very problem, so I suggest marking those as duplicate of this one.
ProblemType: Bug
Architecture: amd64
Date: Wed Jan 6 12:47:37 2010
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: aptitude 0.4.11.11-1ubuntu6
ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
SourcePackage: aptitude
Uname: Linux 2.6.31-16-generic x86_64
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/503765/+subscriptions
More information about the foundations-bugs
mailing list