Your message dated Wed, 12 Aug 2015 11:22:27 +0200 with message-id <20150812092227.GA9950@crossbow> and subject line Re: Bug#410695: zope2.7 causqe upgrade failure has caused the Debian Bug report #410695, regarding zope2.7 causqe upgrade failure 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 410695: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=410695 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: zope2.7 causqe upgrade failure
- From: Bill Allombert <Bill.Allombert@math.u-bordeaux1.fr>
- Date: Mon, 12 Feb 2007 18:53:53 +0100
- Message-id: <20070212175353.GL3151@yellowpig>
Package: upgrade-reports Severity: serious The piuparts run below: /usr/sbin/piuparts -a -d sarge -d etch gnupg xawtv k3d-dev libcnumx0-dev mozilla-opensc xmms-coverviewer makeself koffice-i18n-nn kview libmcardplugin gij-3.4 gimp-dimage-color libast2-dev libaal-dev caudium-dev libcvsservice0 tex-guy linuxdoc-tools-latex snort-common multipath-tools isic libpam-pwdfile libotr1-dev libglib2-ruby haskelldb-bin cyrus21-imapd bsign scalapack-lam-test pyching freeswan dict-freedict-spa-eng xfaces libtie-cache-perl zope2.7-mimetypesregistry libdmsocket-0.32.5-0-dev attal-themes-medieval kde-i18n-srlatin dircproxy pica glimmer kappfinder kde-i18n-eu 9menu selflinux-pdf libgtksourceview-doc fails with: dpkg: python2.3: dependency problems, but removing anyway as you request: python2.3-xml depends on python2.3. python depends on python2.3 (>= 2.3.4-18). zope2.7 depends on python2.3 (>= 2.3.2). (Reading database ... 47589 files and directories currently installed.) Removing python2.3 ... (Reading database ... 47080 files and directories currently installed.) Preparing to replace python 2.3.5-2 (using .../python_2.4.4-2_all.deb) ... Unpacking replacement python ... Selecting previously deselected package python-minimal. Unpacking python-minimal (from .../python-minimal_2.4.4-2_all.deb) ... (Reading database ... 47090 files and directories currently installed.) Removing zope2.7-mimetypesregistry ... Removing zope2.7 ... awk: warning: escape sequence `\.' treated as plain `.' /var/lib/dpkg/info/zope2.7.prerm: line 60: python2.3: command not found dpkg: error processing zope2.7 (--remove): subprocess pre-removal script returned error exit status 127 dpkg: python2.3-xml: dependency problems, but removing anyway as you request: zope2.7 depends on python2.3-xml; however: Package python2.3-xml is to be removed. Removing python2.3-xml ... Errors were encountered while processing: zope2.7 The package zope2.7 was removed from Etch, but we still need to provide an upgrade path. Cheers, -- Bill. <ballombe@debian.org> Imagine a large blue swirl here.
--- End Message ---
--- Begin Message ---
- To: 410695-done@bugs.debian.org
- Subject: Re: Bug#410695: zope2.7 causqe upgrade failure
- From: David Kalnischkies <david@kalnischkies.de>
- Date: Wed, 12 Aug 2015 11:22:27 +0200
- Message-id: <20150812092227.GA9950@crossbow>
- In-reply-to: <20070309171111.GA13985@alpaca>
- References: <1172861394.31613.10.camel@tomoyo> <20070304043337.GL12934@mauritius.dodds.net> <1172997093.3825.120.camel@tomoyo> <20070305090956.GT4912@mauritius.dodds.net> <20070308163203.GA30445@alpaca> <20070309055945.GD8177@borges.dodds.net> <20070309171111.GA13985@alpaca>
Hi, On Fri, Mar 09, 2007 at 09:11:11AM -0800, Daniel Burrows wrote: > download and install them. apt-get does the same thing. TBH, I don't > see why aptitude should work here where apt-get doesn't, unless they > actually install different sets of packages. Indeed. I guess it really was a different solution by the resolvers which let the installation ordering find a sensible solution for aptitude while it wasn't for apt. Reproducing this after 8 years is a bit hard through and so I assume that one of the million changes which happend since then has fixed this problem. This is at least more likely than anyone reproducing this exact problem. If libapt still has this bug we are better of dealing with a recent incarnation of such a bug… so closing as 'too hard to reproduce and probably fixed'. Best regards David KalnischkiesAttachment: signature.asc
Description: Digital signature
--- End Message ---