Re: python/python2.3 circularity in unstable?
On November 25, 2003 12:54 pm, Norman Walsh wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> In a recent apt-get update/upgrade cycle on a machine running
> unstable, I seem to have stumbled over an inconsistency.
>
> # apt-get upgrade
> Reading Package Lists... Done
> Building Dependency Tree... Done
> The following packages will be upgraded
> python python2.3
> 2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> Need to get 2897kB of archives.
> After unpacking 16.4kB of additional disk space will be used.
> Do you want to continue? [Y/n] y
> Get:1 http://http.us.debian.org unstable/main python 2.3.2-6 [153kB]
> Get:2 http://http.us.debian.org unstable/main python2.3 2.3.2-6 [2744kB]
> Fetched 2635kB in 3m16s (13.4kB/s)
> Reading changelogs... Done
> (Reading database ... 73727 files and directories currently installed.)
> Preparing to replace python 2.3.2-2 (using .../python_2.3.2-6_all.deb) ...
> Document `python-policy' is not installed, cannot remove.
> Unpacking replacement python ...
> dpkg: error processing /var/cache/apt/archives/python_2.3.2-6_all.deb
> (--unpack): trying to overwrite
> `/usr/share/doc/python2.3/python-policy.html', which is also in package
> python2.3 dpkg: considering removing python in favour of python2.3 ...
> dpkg: no, cannot remove python (--auto-deconfigure will help):
> python-gdk-imlib-1.2 depends on python (<< 2.4)
> python is to be removed.
> dpkg: regarding .../python2.3_2.3.2-6_i386.deb containing python2.3:
> python2.3 conflicts with python (<= 2.3.2-5)
> python (version 2.3.2-2) is installed.
> dpkg: error processing /var/cache/apt/archives/python2.3_2.3.2-6_i386.deb
> (--unpack): conflicting packages - not installing python2.3
> Errors were encountered while processing:
> /var/cache/apt/archives/python_2.3.2-6_all.deb
> /var/cache/apt/archives/python2.3_2.3.2-6_i386.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> Is this a known inconsistency, or have I mangled something on my machine?
>
> Be seeing you,
> norm
>
I also noticed this problem. You have not mangled anything on your machine.
Reply to: