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

Bug#193566: marked as done (Uninstallable in testing)



Your message dated Fri, 17 Oct 2003 11:36:09 -0400
with message-id <20031017153609.GE6350@dijkstra.csh.rit.edu>
and subject line [cjwatson@debian.org: Bug#198658: Why doesn't remove packages?]
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; 16 May 2003 16:47:44 +0000
>From randy@orrison.com Fri May 16 11:47:43 2003
Return-path: <randy@orrison.com>
Received: from cmailg1.svr.pol.co.uk [195.92.195.171] 
	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
	id 19GiMx-00014Z-00; Fri, 16 May 2003 11:47:43 -0500
Received: from modem-1665.rhino.dialup.pol.co.uk ([62.137.102.129] helo=evo.orrison.com)
	by cmailg1.svr.pol.co.uk with esmtp (Exim 4.14)
	id 19GiMv-0001fC-4j
	for submit@bugs.debian.org; Fri, 16 May 2003 17:47:41 +0100
Received: from randy by evo.orrison.com with local (Exim 3.36 #1 (Debian))
	id 19GiMp-0002pk-00; Fri, 16 May 2003 17:47:13 +0100
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Randy Orrison <randy@orrison.com>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: python-apt: depends on python  (>= 2.1), python (<< 2.2), should
	depend on python2.1
X-Mailer: reportbug 2.10.1
Date: Fri, 16 May 2003 17:47:13 +0100
Message-Id: <E19GiMp-0002pk-00@evo.orrison.com>
Delivered-To: submit@bugs.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0
	tests=BAYES_10,HAS_PACKAGE
	version=2.53-bugs.debian.org_2003_05_09
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_05_09 (1.174.2.15-2003-03-30-exp)

Package: python-apt
Version: 0.5.4.3 (not installed)
Severity: normal



-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux evo 2.4.19-k7 #1 Tue Nov 19 03:01:13 EST 2002 i686
Locale: LANG=en_GB, LC_CTYPE=en_GB


I just did apt-get dist-upgrade on a mostly testing (slightly unstable)
system, and apt-listchanges and python-apt were removed.  Trying to
reinstall, I've found that python-apt won't install:


$ sudo apt-get install python-apt
Reading Package Lists... Done
Building Dependency Tree... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:

Sorry, but the following packages have unmet dependencies:
  python-apt: Depends: python (< 2.2) but 2.2.2-6 is to be installed
E: Sorry, broken packages
$

So, it says it requires a version of python less than 2.2 to be
installed.  However:

$ dpkg -l | grep python2\\..\
ii  python2.1      2.1.3-18       An interactive object-oriented scripting lan
ii  python2.2      2.2.2-6        An interactive object-oriented scripting lan

I have both python2.1 and python2.2 installed.  Shouldn't python-apt be
able to work with my installed python2.1?  Checking the dependancies for
python-apt I see:

$ apt-cache show python-apt
Package: python-apt	[ unstable ]
Priority: optional
Section: python
Installed-Size: 164
Maintainer: APT Development Team <deity@lists.debian.org>
Architecture: i386
Version: 0.5.5
Depends: python (>= 2.2), python (<< 2.3), libapt-inst-libc6.3-5-1.0, libapt-pkg-libc6.3-5-3.3, libc6 (>= 2.3.1-1)
Filename: pool/main/p/python-apt/python-apt_0.5.5_i386.deb
Size: 41226
MD5sum: 4d0b5890d1a88633d448feeb5622cd23
Description: Python interface to libapt-pkg
 The apt-pkg Python interface will provide full access to the internal
 libapt-pkg structures allowing Python programs to easily perform a
 variety of functions, such as:
 .
  - Access to the APT configuration system
  - Access to the APT package information database
  - Parsing of Debian package control files, and other files with a
    similar structure

Package: python-apt	[ testing ]
Priority: optional
Section: python
Installed-Size: 256
Maintainer: APT Development Team <deity@lists.debian.org>
Architecture: i386
Version: 0.5.4.3
Depends: python (>= 2.1), python (<< 2.2), libapt-inst-libc6.2-3-2-1.0, libapt-pkg-libc6.2-3-2-3.2, libc6 (>= 2.2.4-4)
Filename: pool/main/p/python-apt/python-apt_0.5.4.3_i386.deb
Size: 69510
MD5sum: 84de01b39bbe2ef0106121cf152f40d2
Description: Python interface to libapt-pkg
 The apt-pkg Python interface will provide full access to the internal
 libapt-pkg structures allowing Python programs to easily perform a
 variety of functions, such as:
 .
  - Access to the APT configuration system
  - Access to the APT package information database
  - Parsing of Debian package control files, and other files with a
    similar structure
$

So, both the unstable and testing versions of python-apt depend on
"python", but on different versions.  Since "python2.1" and "python2.2"
exist as packages, shouldn't python-apt depend on the appropriate
package?

Since I do have unstable sources, I can fix this by installing the
unstable python-apt, but shouldn't it work with the testing version?

Thanks,

Randy Orrison


---------------------------------------
Received: (at 193566-done) by bugs.debian.org; 17 Oct 2003 15:36:12 +0000
>From mdz@csh.rit.edu Fri Oct 17 10:36:11 2003
Return-path: <mdz@csh.rit.edu>
Received: from blacksheep.csh.rit.edu [129.21.60.6] 
	by master.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1AAWeA-0000cs-00; Fri, 17 Oct 2003 10:36:10 -0500
Received: from dijkstra (dijkstra.csh.rit.edu [129.21.60.152])
	by blacksheep.csh.rit.edu (Postfix) with ESMTP id 2382A2C8
	for <193566-done@bugs.debian.org>; Fri, 17 Oct 2003 11:36:10 -0400 (EDT)
Received: from mdz by dijkstra with local (Exim 3.35 #1 (Debian))
	id 1AAWe9-0001hH-00
	for <193566-done@bugs.debian.org>; Fri, 17 Oct 2003 11:36:09 -0400
Date: Fri, 17 Oct 2003 11:36:09 -0400
From: Matt Zimmerman <mdz@debian.org>
To: 193566-done@bugs.debian.org
Subject: [cjwatson@debian.org: Bug#198658: Why doesn't remove packages?]
Message-ID: <20031017153609.GE6350@dijkstra.csh.rit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.28i
Sender: Matt Zimmerman <mdz@csh.rit.edu>
Delivered-To: 193566-done@bugs.debian.org
X-Spam-Status: No, hits=-8.8 required=4.0
	tests=EMAIL_ATTRIBUTION,QUOTED_EMAIL_TEXT,SIGNATURE_LONG_SPARSE
	autolearn=ham version=2.53-bugs.debian.org_2003_10_17
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_10_17 (1.174.2.15-2003-03-30-exp)

python-apt (and therefore apt-listchanges) are now now installable in
testing again.

----- Forwarded message from Colin Watson <cjwatson@debian.org> -----

Date: Fri, 17 Oct 2003 06:00:55 -0500
From: Colin Watson <cjwatson@debian.org>
Resent-From: Colin Watson <cjwatson@debian.org>
To: Uwe Storbeck <uwe@ibr.ch>, 198658@bugs.debian.org
Subject: Bug#198658: Why doesn't remove packages?

On Tue, Oct 07, 2003 at 11:41:13PM +0200, Uwe Storbeck wrote:
> BTW, how can a package get into testing with such basically unmet
> dependencies? This state keeps on for months ...
> 
> # apt-get install apt-listchanges
> ...
> Sorry, but the following packages have unmet dependencies:
>   apt-listchanges: Depends: python (>= 2.3) but 2.1.3-4 is to be installed

Actually, that state has changed over the last few months: it used to be
something else that caused apt-listchanges to be uninstallable. The
problem is that once a package is uninstallable in testing, which
apt-listchanges was due to a complicated "greatest good for the greatest
number" situation a while back, the scripts that manage testing are
completely willing to break more of its dependencies and make it worse,
so it can be quite difficult to get it back.

apt-listchanges is now installable in sarge, and whichever bugs are open
about that alone (not this one) can be closed now.

Cheers,

-- 
Colin Watson                                  [cjwatson@flatline.org.uk]


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

----- End forwarded message -----

-- 
 - mdz



Reply to: