Bug#301587: apt: Odd recommendation on dist-upgrade (upgrade gets it right)
I had basically the same problem as before again tonight. I'm not sure if
this has been discussed before, but it looks like it apt-get tried first to
upgrade all the packages that were already on the system and out of date and
then worked from that to resolve any further dependency/conflicts/etc
problems, that might fix this problem.
----------------
Thanks
Jefferson Cowart
Jeff@cowart.net
> -----Original Message-----
> From: Vincent Lefevre [mailto:vincent@vinc17.org]
> Sent: Thursday, April 14, 2005 15:20
> To: Jefferson Cowart
> Cc: 301587@bugs.debian.org
> Subject: Re: Bug#301587: apt: Odd recommendation on
> dist-upgrade (upgrade gets it right)
>
> On 2005-03-27 21:59:42 -0800, Jefferson Cowart wrote:
> > Looking through those bugs a large number of them seem to
> refer to package
> > holds. I don't think I have any on my system. Running 'dpkg
> -l' shows all
> > the lines as starting with 'ii' which I think confirms
> that. Is there
> > anything else I can do to help here or is this just a known
> issue that
> > doesn't have a programmable solution at the moment.
>
> The problem isn't necessarily due to the fact that the packages are
> on hold, but due to the fact that the system is not up-to-date. In
> my case, the culprit packages aren't on hold either.
>
> BTW, the problem has just occurred again:
>
> dixsept:/home/vlefevre# apt-get dist-upgrade -s
> Reading Package Lists... Done
> Building Dependency Tree... Done
> Calculating Upgrade... Done
> The following NEW packages will be installed:
> apache-common libapache-mod-security
> The following packages have been kept back:
> xserver-xfree86
> The following packages will be upgraded:
> kernel-package libapache2-mod-security mod-security-common
> 3 upgraded, 2 newly installed, 0 to remove and 1 not upgraded.
> Inst apache-common (1.3.33-4 Debian:unstable)
> Inst kernel-package [8.130] (8.131 Debian:unstable)
> Inst mod-security-common [1.8.4-2] (1.8.7-1 Debian:unstable)
> [libapache2-mod-security ]
> Inst libapache2-mod-security [1.8.4-2] (1.8.7-1 Debian:unstable)
> Inst libapache-mod-security (1.8.7-1 Debian:unstable)
> Conf apache-common (1.3.33-4 Debian:unstable)
> Conf kernel-package (8.131 Debian:unstable)
> Conf libapache-mod-security (1.8.7-1 Debian:unstable)
> Conf libapache2-mod-security (1.8.7-1 Debian:unstable)
> Conf mod-security-common (1.8.7-1 Debian:unstable)
>
> And after upgrading libapache2-mod-security (and mod-security-common,
> due to the dependence):
>
> dixsept:/home/vlefevre# apt-get dist-upgrade -s
> Reading Package Lists... Done
> Building Dependency Tree... Done
> Calculating Upgrade... Done
> The following packages have been kept back:
> xserver-xfree86
> The following packages will be upgraded:
> kernel-package
> 1 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
> Inst kernel-package [8.130] (8.131 Debian:unstable)
> Conf kernel-package (8.131 Debian:unstable)
>
> I think that apt did the following things:
>
> 1. mod-security-common is installed, so it should be upgraded.
>
> 2. Its dependencies:
> libapache-mod-security (= 1.8.7-1) |
> libapache2-mod-security (= 1.8.7-1)
>
> 3. Neither of these packages (with the correct version) are currently
> installed, therefore apt wants to install the first one, i.e.
> libapache-mod-security/1.8.7-1.
>
> 4. Hence the proposed upgrades, due to the remaining dependencies.
>
> --
> Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
> 100% accessible validated (X)HTML - Blog:
> <http://www.vinc17.org/blog/>
> Work: CR INRIA - computer arithmetic / SPACES project at LORIA
>
>
Reply to: