apt-0.5.15lorg3.1-rc2

[Panu Matilainen]

On Tue, 2006-05-16 at 18:38 +0200, Ralf Corsepius wrote:
> On Tue, 2006-05-16 at 18:32 +0200, Ralf Corsepius wrote:
> > On Tue, 2006-05-16 at 18:21 +0300, Panu Matilainen wrote:
> > > Ok, this is now with the filelists fix, no other changes from rc1.
> > > Tested to survive fc4 -> fc5 upgrade calculation which is just about as
> > > acid as a depsolver test gets :) 
> > > 
> > > http://apt-rpm.org/testing/apt-0.5.15lorg3.1-rc2.tar.bz2
> > > 
> > > Please try to give it a spin,
> > 
> > Works MUCH better ...
> > 
> > >  I'm planning on putting final lorg3.1 out
> > > this weekend unless something dramatic turns up.
> > 
> > Another observation[1]:
> > 
> > During a dist-upgrade from FC4->FC5 on a Fedora 4 system:
> > ...
> > The following packages will be REMOVED:
> >    freeglut-devel (0:1.6.2-3jpp_8fc)
> > ...
> > 
> > This is wrong twice:
> > * freeglut-devel is available for FC5, so there should not be any need
> > to remove it.

Can't reproduce this one. Maybe it'd require some specific combination
of packages or then it's just some cache-invalidity issue. Running with
-o debug::pkgproblemresolver=true might give some hints at what's going
on.

> > * The version number being issued doesn't correspond to freeglut-devel.
> > It seems to be FC4's "ant"'s version.
> 
> 
> And yet another observation from the same "apt-get dist-upgrade" run
> ...
> The following NEW packages will be installed:
> ...
>    kernel#2.6.16-1.2096_FC5 (2.6.16-1.2096_FC5)
>    kernel#2.6.16-1.2111_FC5 (2.6.16-1.2111_FC5)

This kernel-thing I can easily reproduce, happens with lorg3 as well and
it'd happen with older versions as well: if you disable the
kernel-update lua stuff, (-o rpm::upgrade-virtual=false in
fedora-packages) the other kernel will disappear from that list. What
happens is that as the original FC4 kernel gets removed due to conflict,
apt will blindly pick some other kernel package that satisfies the
dependencies. Afterwards kernel-upgrade magic runs and picks up the
latest which will show up as a new installation as well.

I suppose it'd be possible to tweak the lua-script to take such
happenings into account. The "real" fix is very much non-trivial: teach
libapt-pkg how to properly deal with packages that can have several
versions simultaneously installed instead of the current
allow-duplicated workaround (ditto for multilib packages).

	- Panu -