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

RE: apt-get will upgrade aptitude will not



To answer most questions asked:

>>> Did you first update the packages database?
>>> 
>>> apt-get update
>>> aptitude update
>> 
>> apt-get and aptitude both use the same package database. Running the 
>> 'udpate' for both of them is not required.
>
> I just run "apt-get upgrade" and said there was nothing to do while running "aptitude upgrade" wanted to do very 
> (I mean *very*) weird things, such as removing a bunch of packages. After updating aptitude database all went smooth...
>

1)
My systems are all Squeeze. 

2)
~# cat /etc/apt/sources.list
deb http://ftp.nl.debian.org/debian/ squeeze main contrib non-free
deb-src http://ftp.nl.debian.org/debian/ squeeze main contrib non-free

deb http://security.debian.org/ squeeze/updates main contrib non-free
deb-src http://security.debian.org/ squeeze/updates main contrib non-free

# Squeeze-updates, previously known as 'volatile'
deb http://ftp.nl.debian.org/debian/ squeeze-updates main contrib non-free
deb-src http://ftp.nl.debian.org/debian/ squeeze-updates main contrib non-free

3)
The last time I ran a full-upgrade was when I upgraded from Lenny. I think this system started out as an Etch system years ago.
I'd like to think the aptitude full-upgrade (or apt-get dist-upgrade) is only to be used when doing major upgrades. But....
~# aptitude full-upgrade
The following packages will be upgraded:
  mysql-common
1 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 69.6 kB of archives. After unpacking 57.3 kB will be freed.
Do you want to continue? [Y/n/?]n

4)
The command
~# aptitude search " ~ahold"
gave no output so there are no held packages in aptitude. I tested that the last time just before doing the dist-upgrade and I never hold packages unless there is a VERY good reason.

But.... remember the aptitude upgrade gave
  No packages will be installed, upgraded, or removed.
  0 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
So there is that
  ... and 1 not upgraded.
In that line. For some reason aptitude will not upgrade that 1 component.

5)
Aptitude upgrade with the -v (or -vv or -vvv) switch gives not much more info, just:
Current status: 0 broken [+0], 1 update [+0], 16431 new [+0].


6)
~# apt-cache showpkg mysql-common
Package: mysql-common
Versions:
5.1.61-0+squeeze1 (/var/lib/apt/lists/security.debian.org_dists_squeeze_updates_main_binary-i386_Packages)
 Description Language:
                 File: /var/lib/apt/lists/security.debian.org_dists_squeeze_updates_main_binary-i386_Packages
                  MD5: 562d254c602f89e4390e28f6362283c8

5.1.49-3 (/var/lib/apt/lists/ftp.nl.debian.org_debian_dists_squeeze_main_binary-i386_Packages) (/var/lib/dpkg/status)
 Description Language:
                 File: /var/lib/apt/lists/ftp.nl.debian.org_debian_dists_squeeze_main_binary-i386_Packages
                  MD5: 562d254c602f89e4390e28f6362283c8


Reverse Depends:
  libmysqlclient15off,mysql-common 5.0.51a-24+lenny5
  mysql-server-5.1,mysql-common 5.1.61-0+squeeze1
  mysql-client-5.1,mysql-common 5.1.61-0+squeeze1
  libmysqlclient16,mysql-common 5.1.61-0+squeeze1
  mysql-server-5.1,mysql-common 5.1.49-3
  mysql-client-5.1,mysql-common 5.1.49-3
  libmysqlclient16,mysql-common 5.1.49-3
Dependencies:
5.1.61-0+squeeze1 - mysql-common-4.1 (0 (null)) mysql-common-4.1 (0 (null))
5.1.49-3 - mysql-common-4.1 (0 (null)) mysql-common-4.1 (0 (null))
Provides:
5.1.61-0+squeeze1 - mysql-common-4.1
5.1.49-3 - mysql-common-4.1
Reverse Provides:

So it seems the update is present on my system and ready to be installed, just not by a normal aptitude upgrade.
It is either a normal apt-get upgrade or an aptitude full-upgrade. But why.....?

I will just do an apt-get upgrade now.

Bonno Bloksma


Reply to: