Bug#245253: apt-get: claims it will upgrade a packages that should/will not be
On Thu, Apr 22, 2004 at 08:10:29PM +0200, Yann Dirson wrote:
> On Thu, Apr 22, 2004 at 09:40:47AM -0700, Matt Zimmerman wrote:
> > > If I remove the w.o line or the unstable one from my sources.list that
> > > behaviour goes away. It comes back when I re-add those 2 lines.
> >
> > You probably already have the package in your cache (so it won't be listed
> > in --print-uris). The reason for the package being reinstalled is likely
> > that two packages have the same version number but are actually different.
> > This is a bug in the unofficial packages.
>
> You're right, it unpacked the version from the cache. But then there is
> still a bug in apt, since unless I clean the cache, it will continuously
> unpack it, thinking it is the right deb.
apt has no way to accomodate having two distinct packages in the cache with
the same version number, and I don't see any reason why it should.
(package,version) should refer unambiguously to a package, and that
assumption is deep in the packaging toolchain.
> What makes it think the one installed is not the available one ? Why
> wouldn't it be possible to detect the same problem wrt the cache ?
>
> And above all, why if I comment out any one of the 2 source lines, would it
> think that the installed package is good ?
apt is trying to deal sanely with a broken situation. This sort of thing
happens, for example, if the metadata in the Packages file doesn't match the
package that is actually available. apt has no way to d
--
- mdz
Reply to: