Chris DiVirgilio <divirg@umich.edu> writes:
I'm having a bit of a problem with apt-get upgrade.
Every night cron runs
apt-get update && apt-get -s upgrade | mail divirg@umich.edu
I would use apt-get -d dist-upgrade here. Download the debs already
for near instant installs the next morning.
which emails the day's new patches to me. The next day I look at the
patches and install them with an apt-get upgrade.
One morning I get an email with:
Reading Package Lists... Done
Building Dependency Tree... Done
The following packages will be upgraded:
apache2-utils libapr0 lynx
3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Inst libapr0 [2.0.54-5] (2.0.54-5 Debian-Security:3.1/stable)
Inst apache2-utils [2.0.54-5] (2.0.54-5 Debian-Security:3.1/stable)
Inst lynx [2.8.5-2sarge1] (2.8.5-2sarge1 Debian-Security:3.1/stable)
Conf libapr0 (2.0.54-5 Debian-Security:3.1/stable)
Conf apache2-utils (2.0.54-5 Debian-Security:3.1/stable)
Conf lynx (2.8.5-2sarge1 Debian-Security:3.1/stable)
The amd64 archive did recompile some security fixes because it didn't
copy them from security.debian.org. This results in two different
packages with the same version to be available, one from security.d.o
and one from amd64.d.n.
Now apt-get want to install the package from the first source in your
sources.list while you already have the package from the second source
installed. You also (and here I guess) still have the package from the
second source in your apt cache. Now apt has a little bug that it
won't fetch the file if the cache already has it so it reinstalls the
one from the cache (second source) again and again.
If I'm guessing right a simple "apt-get clean" will solve the problem.