apt-get wants to upgrade package to same version?
Hello,
I have just being playing around with apt-proxy, and noticed something
weird. Every time I run apt-get, it wants to upgrade the packages it
just upgraded 5 seconds ago (it only happens on this computer, too):
(note: se_apt-get is the same thing as apt-get, but sets
the selinux domain up correctly).
scrooge:/tmp# se_apt-get upgrade
Authenticating bam.
Password:
Reading Package Lists... Done
Building Dependency Tree... Done
The following packages have been kept back
stat
12 packages upgraded, 0 newly installed, 0 to remove and 1 not
upgraded.
Need to get 0B/1052kB of archives. After unpacking 0B will be used.
Do you want to continue? [Y/n]
Reading changelogs... Done
(Reading database ... 104220 files and directories currently installed.)
Preparing to replace libkrb-1-kerberos4kth 1.1-11-2 (using
.../libkrb-1-kerberos4kth_1.1-11-2_i386.deb) ...
Unpacking replacement libkrb-1-kerberos4kth ...
Preparing to replace libacl1-kerberos4kth 1.1-11-2 (using
.../libacl1-kerberos4kth_1.1-11-2_i386.deb) ...
Unpacking replacement libacl1-kerberos4kth ...
Preparing to replace libcomerr1-kerberos4kth 1.1-11-2 (using
.../libcomerr1-kerberos4kth_1.1-11-2_i386.deb) ...
Unpacking replacement libcomerr1-kerberos4kth ...
Preparing to replace libkadm1-kerberos4kth 1.1-11-2 (using
.../libkadm1-kerberos4kth_1.1-11-2_i386.deb) ...
Unpacking replacement libkadm1-kerberos4kth ...
Preparing to replace libkdb-1-kerberos4kth 1.1-11-2 (using
.../libkdb-1-kerberos4kth_1.1-11-2_i386.deb) ...
Unpacking replacement libkdb-1-kerberos4kth ...
Preparing to replace libroken9-kerberos4kth 1.1-11-2 (using
.../libroken9-kerberos4kth_1.1-11-2_i386.deb) ...
Unpacking replacement libroken9-kerberos4kth ...
Preparing to replace libotp0-kerberos4kth 1.1-11-2 (using
.../libotp0-kerberos4kth_1.1-11-2_i386.deb) ...
Unpacking replacement libotp0-kerberos4kth ...
Preparing to replace libsl0-kerberos4kth 1.1-11-2 (using
.../libsl0-kerberos4kth_1.1-11-2_i386.deb) ...
Unpacking replacement libsl0-kerberos4kth ...
Preparing to replace libss0-kerberos4kth 1.1-11-2 (using
.../libss0-kerberos4kth_1.1-11-2_i386.deb) ...
Unpacking replacement libss0-kerberos4kth ...
Preparing to replace libkafs0-kerberos4kth 1.1-11-2 (using
.../libkafs0-kerberos4kth_1.1-11-2_i386.deb) ...
Unpacking replacement libkafs0-kerberos4kth ...
Preparing to replace kerberos4kth-dev 1.1-11-2 (using
.../kerberos4kth-dev_1.1-11-2_i386.deb) ...
Unpacking replacement kerberos4kth-dev ...
Preparing to replace kerberos4kth1 1.1-11-2 (using
.../kerberos4kth1_1.1-11-2_all.deb) ...
Unpacking replacement kerberos4kth1 ...
Setting up libkrb-1-kerberos4kth (1.1-11-2) ...
Setting up libacl1-kerberos4kth (1.1-11-2) ...
Setting up libcomerr1-kerberos4kth (1.1-11-2) ...
Setting up libkadm1-kerberos4kth (1.1-11-2) ...
Setting up libkdb-1-kerberos4kth (1.1-11-2) ...
Setting up libroken9-kerberos4kth (1.1-11-2) ...
Setting up libotp0-kerberos4kth (1.1-11-2) ...
Setting up libsl0-kerberos4kth (1.1-11-2) ...
Setting up libss0-kerberos4kth (1.1-11-2) ...
Setting up libkafs0-kerberos4kth (1.1-11-2) ...
Setting up kerberos4kth-dev (1.1-11-2) ...
Setting up kerberos4kth1 (1.1-11-2) ...
What is going on here? Why does it not realize the package it just
installed is the package it just downloaded?
scrooge:/tmp# apt-cache policy kerberos4kth1
kerberos4kth1:
Installed: 1.1-11-2
Candidate: 1.1-11-2
Version Table:
1.1-11-2 0
-1 http://snoopy.apana.org.au unstable/main Packages
1.1-11-2 0
700 http://snoopy.apana.org.au woody/main Packages
*** 1.1-11-2 0
100 /var/lib/dpkg/status
1.1-8-2 0
700 http://snoopy.apana.org.au woody/updates/main Packages
700 http://snoopy.apana.org.au woody/non-US/main Packages
scrooge:/tmp# md5sum /var/cache/apt/archives/kerberos4kth1_1.1-11-2_all.deb
330d49310a3264f037875e06a1328458 /var/cache/apt/archives/kerberos4kth1_1.1-11-2_all.deb
This is the same MD5SUM in the packages file:
Package: kerberos4kth1
Version: 1.1-11-2
Priority: optional
Section: net
Maintainer: Mikael Andersson <mikan@debian.org>
Architecture: all
Filename: ./pool/krb4/kerberos4kth1_1.1-11-2_all.deb
Size: 57786
MD5sum: 330d49310a3264f037875e06a1328458
Description: Dummy library package for Kerberos4 From KTH.
This is a dummy package. It should be safe to remove it.
installed-size: 76
source: krb4
All I can think of is that apt-get is getting confused
for some reason between that entry and this unstable entry
(this version of kerberos4kth is not installable on my system
due to a dependancy on the new version of libc6, not shown
in this package):
Package: kerberos4kth1
Priority: optional
Section: net
Installed-Size: 68
Maintainer: Mikael Andersson <mikan@debian.org>
Architecture: all
Source: krb4
Version: 1.1-11-2
Filename: pool/main/k/krb4/kerberos4kth1_1.1-11-2_all.deb
Size: 57584
MD5sum: d2578663139242eb543153aad6e46597
Description: Dummy library package for Kerberos4 From KTH.
This is a dummy package. It should be safe to remove it.
Which is from the unused source (pin priority = -1).
Comments?
Can't apt realize that if it is going to install a package from source
X, it should use the Packages entry from source X too?
--
Brian May <bam@snoopy.apana.org.au>
Reply to: