[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#245253: marked as done (apt-get: claims it will upgrade a packages that should/will not be)



Your message dated Thu, 22 Apr 2004 09:40:47 -0700
with message-id <20040422164047.GO31523@alcor.net>
and subject line Bug#245253: apt-get: claims it will upgrade a packages that should/will not be
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 22 Apr 2004 07:24:27 +0000
>From ydirson@altern.org Thu Apr 22 00:24:26 2004
Return-path: <ydirson@altern.org>
Received: from smtp8.wanadoo.fr (mwinf0802.wanadoo.fr) [193.252.22.23] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1BGYZO-0003bf-00; Thu, 22 Apr 2004 00:24:26 -0700
Received: from bylbo.nowhere.earth (APuteaux-115-1-13-41.w81-51.abo.wanadoo.fr [81.51.28.41])
	by mwinf0802.wanadoo.fr (SMTP Server) with ESMTP
	id 02850180020D; Thu, 22 Apr 2004 09:23:55 +0200 (CEST)
Received: from dwitch by bylbo.nowhere.earth with local (Exim 3.36 #1 (Debian))
	id 1BGYc2-00019V-00; Thu, 22 Apr 2004 09:27:10 +0200
Date: Thu, 22 Apr 2004 09:27:10 +0200
From: Yann Dirson <dirson@debian.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: apt-get: claims it will upgrade a packages that should/will not be
Message-ID: <[🔎] 20040422072710.GA4288@bylbo.nowhere.earth>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Reportbug-Version: 2.56
User-Agent: Mutt/1.5.5.1+cvs20040105i
Sender: Yann Dirson <ydirson@altern.org>
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-5.6 required=4.0 tests=BAYES_00,HAS_PACKAGE,
	WEIRD_PORT autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 
X-CrossAssassin-Score: 1

Package: apt
Version: 0.5.24
Severity: normal

I'm using both wesnoth.org and unstable as a source for the wesnoth{,-data}
packages for my testing box.  The box is configured such that unstable
packages are only ever installed or upgraded on explicit request.  The
wesnoth.org line is a recent addition that does not completely fit in this
original policy, and that seems to be the source of this problem.

I've upgraded the packages to the w.o version yesterday, and then the same
version entered unstable.  Now apt-get and aptitude both claim they mush
upgrade the wesnoth-data package to the same version than that installed,
although it does not seem apt-get will really do it:

# apt-cache policy wesnoth-data
wesnoth-data:
  Installed: 0.7.3-1
  Candidate: 0.7.3-1
  Version Table:
     0.7.3-1 0
         90 http://aptproxy unstable/main Packages
     0.7.3-1 0
        500 http://debian.wesnoth.org ./ Packages
 *** 0.7.3-1 0
        100 /var/lib/dpkg/status
     0.7-1 0
        990 ftp://ftp.debian.org testing/main Packages


# apt-get --print-uris -y upgrade
Reading Package Lists... Done
Building Dependency Tree... Done
The following packages have been kept back:
  enigma
The following packages will be upgraded:
  debootstrap gav ifupdown latex-xcolor pgf ppp ufoai-data-lanas wesnoth-data
8 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 3819kB/23.1MB of archives.
After unpacking 28.7kB of additional disk space will be used.
'http://ydirson.free.fr/soft/debian/ufoai/ufoai-data-lanas_0.0.040420-0.1_all.deb' ufoai-data-lanas_0.0.040420-0.1_all.deb 2182902 805b631e239d0ec8b22869b7050ca761
'ftp://ftp.debian.org/debian/pool/main/i/ifupdown/ifupdown_0.6.4-4.8_i386.deb' ifupdown_0.6.4-4.8_i386.deb 42338 ca297e5224c6ec4714047dc406f6181c
'ftp://ftp.debian.org/debian/pool/main/l/latex-xcolor/latex-xcolor_1.10-1_all.deb' latex-xcolor_1.10-1_all.deb 789152 5e80c5aaba412407e4b0d0b3b907ab38
'ftp://ftp.debian.org/debian/pool/main/p/pgf/pgf_0.61-1_all.deb' pgf_0.61-1_all.deb 358356 788771b87a3f1dce75eaa5e4243b13f3
'ftp://ftp.debian.org/debian/pool/main/p/ppp/ppp_2.4.2+20040202-3_i386.deb' ppp_2.4.2+20040202-3_i386.deb 283170 0426645173ab5bc0004f9b2529703725
'ftp://ftp.debian.org/debian/pool/main/d/debootstrap/debootstrap_0.2.33_i386.deb' debootstrap_0.2.33_i386.deb 61634 43dfa7d1b4cca49c01493a0b73728766
'ftp://ftp.debian.org/debian/pool/main/g/gav/gav_0.8.0-1_i386.deb' gav_0.8.0-1_i386.deb 101166 6fafb63ccb89eac768e9010ec4720c84


As you see, wesnoth-data is not in the URIs, although it's listed in the
"will be upgraded".  Now I cannot understand why the wesnoth package is not
given the same handling...

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.


-- Package-specific info:
[information manually extracted from the correct machine]

-- apt-config dump --

APT "";
APT::Architecture "i386";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Get "";
APT::Get::Show-Upgraded "true";
APT::Get::List-Cleanup "false";
APT::Cache-Limit "10000000";
Dir "/";
Dir::State "var/lib/apt/";
Dir::State::lists "lists/";
Dir::State::cdroms "cdroms.list";
Dir::State::userstatus "status.user";
Dir::State::status "/var/lib/dpkg/status";
Dir::Cache "var/cache/apt/";
Dir::Cache::archives "archives/";
Dir::Cache::srcpkgcache "srcpkgcache.bin";
Dir::Cache::pkgcache "pkgcache.bin";
Dir::Etc "etc/apt/";
Dir::Etc::sourcelist "sources.list";
Dir::Etc::vendorlist "vendors.list";
Dir::Etc::vendorparts "vendors.list.d";
Dir::Etc::main "apt.conf";
Dir::Etc::parts "apt.conf.d";
Dir::Etc::preferences "preferences";
Dir::Bin "";
Dir::Bin::methods "/usr/lib/apt/methods";
Dir::Bin::dpkg "/usr/bin/dpkg";
DPkg "";
DPkg::Pre-Install-Pkgs "";
DPkg::Pre-Install-Pkgs:: "/usr/sbin/dpkg-preconfigure --apt || true";

-- /etc/apt/preferences --


Explanation: default release
Package: *
Pin: release a=testing
Pin-Priority: 990

Package: *
Pin: release a=unstable
Pin-Priority: 90

Package: *
Pin: release a=experimental
Pin-Priority: 90


-- /etc/apt/sources.list --

deb ftp://ftp.debian.org/debian testing main contrib non-free
deb ftp://non-us.debian.org/debian-non-US testing non-US/main non-US/contrib non-US/non-free
deb http://aptproxy:9999/debian unstable main contrib non-free
deb http://aptproxy:9999/non-US unstable non-US/main non-US/contrib non-US/non-free
deb-src ftp://ftp.debian.org/debian unstable main contrib non-free
deb ftp://ftp.debian.org/debian woody main contrib non-free
deb ftp://non-us.debian.org/debian-non-US woody non-US/main non-US/contrib non-US/non-free
deb file:/export/work/admin/radeon/X/debs ./
deb ftp://ftp.nerim.net/debian-marillat/ testing main
deb ftp://ftp.nerim.net/debian-marillat/ unstable main
deb ftp://ftp.debian.org/debian ../project/experimental main contrib non-free
deb http://ydirson.free.fr/soft/debian/ ufoai/
deb http://debian.wesnoth.org/sid/ ./


-- System Information:
Debian Release: testing/unstable
  APT prefers testing

-- 
Yann Dirson    <ydirson@altern.org> |    Why make M$-Bill richer & richer ?
Debian-related: <dirson@debian.org> |   Support Debian GNU/Linux:
Pro:    <yann.dirson@fr.alcove.com> |  Freedom, Power, Stability, Gratuity
     http://ydirson.free.fr/        | Check <http://www.debian.org/>

---------------------------------------
Received: (at 245253-done) by bugs.debian.org; 22 Apr 2004 16:41:18 +0000
>From mdz@alcor.net Thu Apr 22 09:41:18 2004
Return-path: <mdz@alcor.net>
Received: from mta9.adelphia.net [68.168.78.199] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1BGhGI-0005l8-00; Thu, 22 Apr 2004 09:41:18 -0700
Received: from mizar.alcor.net ([69.167.148.1]) by mta9.adelphia.net
          (InterMail vM.5.01.06.08 201-253-122-130-108-20031117) with ESMTP
          id <20040422164047.QFUC26615.mta9.adelphia.net@mizar.alcor.net>;
          Thu, 22 Apr 2004 12:40:47 -0400
Received: from mdz by mizar.alcor.net with local (Exim 4.32)
	id 1BGhFn-0006bW-7P; Thu, 22 Apr 2004 09:40:47 -0700
Date: Thu, 22 Apr 2004 09:40:47 -0700
From: Matt Zimmerman <mdz@debian.org>
To: Yann Dirson <dirson@debian.org>, 245253-done@bugs.debian.org
Subject: Re: Bug#245253: apt-get: claims it will upgrade a packages that should/will not be
Message-ID: <20040422164047.GO31523@alcor.net>
References: <[🔎] 20040422072710.GA4288@bylbo.nowhere.earth>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[🔎] 20040422072710.GA4288@bylbo.nowhere.earth>
User-Agent: Mutt/1.5.5.1+cvs20040105i
Sender: Matt Zimmerman <mdz@alcor.net>
Delivered-To: 245253-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-5.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
	autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 
X-CrossAssassin-Score: 1

On Thu, Apr 22, 2004 at 09:27:10AM +0200, Yann Dirson wrote:

> # apt-get --print-uris -y upgrade
> Reading Package Lists... Done
> Building Dependency Tree... Done
> The following packages have been kept back:
>   enigma
> The following packages will be upgraded:
>   debootstrap gav ifupdown latex-xcolor pgf ppp ufoai-data-lanas wesnoth-data
> 8 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
> Need to get 3819kB/23.1MB of archives.
> After unpacking 28.7kB of additional disk space will be used.
> 'http://ydirson.free.fr/soft/debian/ufoai/ufoai-data-lanas_0.0.040420-0.1_all.deb' ufoai-data-lanas_0.0.040420-0.1_all.deb 2182902 805b631e239d0ec8b22869b7050ca761
> 'ftp://ftp.debian.org/debian/pool/main/i/ifupdown/ifupdown_0.6.4-4.8_i386.deb' ifupdown_0.6.4-4.8_i386.deb 42338 ca297e5224c6ec4714047dc406f6181c
> 'ftp://ftp.debian.org/debian/pool/main/l/latex-xcolor/latex-xcolor_1.10-1_all.deb' latex-xcolor_1.10-1_all.deb 789152 5e80c5aaba412407e4b0d0b3b907ab38
> 'ftp://ftp.debian.org/debian/pool/main/p/pgf/pgf_0.61-1_all.deb' pgf_0.61-1_all.deb 358356 788771b87a3f1dce75eaa5e4243b13f3
> 'ftp://ftp.debian.org/debian/pool/main/p/ppp/ppp_2.4.2+20040202-3_i386.deb' ppp_2.4.2+20040202-3_i386.deb 283170 0426645173ab5bc0004f9b2529703725
> 'ftp://ftp.debian.org/debian/pool/main/d/debootstrap/debootstrap_0.2.33_i386.deb' debootstrap_0.2.33_i386.deb 61634 43dfa7d1b4cca49c01493a0b73728766
> 'ftp://ftp.debian.org/debian/pool/main/g/gav/gav_0.8.0-1_i386.deb' gav_0.8.0-1_i386.deb 101166 6fafb63ccb89eac768e9010ec4720c84
> 
> 
> As you see, wesnoth-data is not in the URIs, although it's listed in the
> "will be upgraded".  Now I cannot understand why the wesnoth package is not
> given the same handling...
> 
> 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.

-- 
 - mdz



Reply to: