On Tue, Nov 08, 2005 at 09:06:39AM -0500, Todd Charron <[EMAIL PROTECTED]> was heard to say: > The real problem is that aptitude didn't report the error and then > whenever I ran aptitude update && aptitude upgrade I was informed there were > no new packages to install or fix, etc. which lead to security updates > not getting installed! Now in my case I only missed a few since when > the openssl security update came out I knew for a fact that I had that > installed and that it would need to be updated so I was puzzled when it > didn't. After aptitude insisted there was nothing to install I did an > apt-get update && apt-get upgrade which gave me the error about things > being in an inconsistent state and to run apt-get -f install (which > installed makepasswd). After this was done aptitude updated properly > and detected the security packages that needed to be installed.
I can't reproduce this in 0.4: "aptitude upgrade" prints an error
message for me. For instance,
[EMAIL PROTECTED]:~$ aptitude -s upgrade
Reading package lists... Done
Building dependency tree... Done
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
Building tag database... Done
The following packages have unmet dependencies:
console-tools: Depends: libconsole (= 1:0.2.3dbs-58) but 1:0.2.3dbs-57 is
installed and it is kept back.
I fixed one bug like this in 0.4, and I suppose it's possible that there
are more skulking around. Could you send me (in private mail) the contents
of /var/lists/apt, /var/lib/dpkg/status, and /var/lib/aptitude/pkgstates?
Thanks,
Daniel
signature.asc
Description: Digital signature
