package upgrade failed python2.7.9-2+deb8u1

[seahorse41]

When attempting to upgrade upgradable packages, I get errors:
E: /var/cache/apt/archives/python2.7-dev_2.7.9-2+deb8u1_i386.deb: trying to overwrite '/usr/share/doc/python2.7', which is also in package python 2.7.9-1
E: /var/cache/apt/archives/python2.7_2.7.9-2+deb8u1_i386.deb: trying to overwrite '/usr/share/doc/python2.7', which is also in package python 2.7.9-1

Then it wouldn't let me upgrade any of the other packages until I first fixed the 2 broken packages.
python2.7
python2.7-dev
Both show installed version to be 2.7.9-2

I tried package-force-version to 2.7.9-2 but that failed:
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: Unable to correct dependencies
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: Unable to correct dependencies
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: Unable to correct dependencies
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: Unable to correct dependencies
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: Unable to correct dependencies
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: Unable to correct dependencies
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: Unable to correct dependencies
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: Unable to correct dependencies
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: Unable to correct dependencies
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: Unable to correct dependencies


Next I tried unmark all, and only upgrade these 2 packages to newest mentioned in title,
Here is the output:

(synaptic:21636): GLib-CRITICAL **: g_child_watch_add_full: assertion 'pid > 0' failed
(Reading database ... 210286 files and directories currently installed.)
Preparing to unpack .../python2.7-dev_2.7.9-2+deb8u1_i386.deb ...
Unpacking python2.7-dev (2.7.9-2+deb8u1) over (2.7.9-2) ...
dpkg: error processing archive /var/cache/apt/archives/python2.7-dev_2.7.9-2+deb8u1_i386.deb (--unpack):
trying to overwrite '/usr/share/doc/python2.7', which is also in package python 2.7.9-1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Preparing to unpack .../python2.7_2.7.9-2+deb8u1_i386.deb ...
Unpacking python2.7 (2.7.9-2+deb8u1) over (2.7.9-2) ...
dpkg: error processing archive /var/cache/apt/archives/python2.7_2.7.9-2+deb8u1_i386.deb (--unpack):
trying to overwrite '/usr/share/doc/python2.7', which is also in package python 2.7.9-1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for desktop-file-utils (0.22-1) ...
Processing triggers for gnome-menus (3.13.3-6) ...
Processing triggers for mime-support (3.58) ...
Errors were encountered while processing:
/var/cache/apt/archives/python2.7-dev_2.7.9-2+deb8u1_i386.deb
/var/cache/apt/archives/python2.7_2.7.9-2+deb8u1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:

Help!

[stevepusser]

The -2 doesn't seem to be in Jessie yet. Are you getting that from the proposed-updates repository?

[seahorse41]

The -2 doesn't seem to be in Jessie yet. Are you getting that from the proposed-updates repository?

$ cat /etc/apt/sources.list
deb cdrom:[Debian GNU/Linux 8.1.0 _Jessie_ - Official i386 DVD Binary-1 20150606-13:00]/ jessie contrib main
deb http://ftp.us.debian.org/debian/ jessie main non-free contrib
deb-src http://ftp.us.debian.org/debian/ jessie main non-free contrib
deb http://security.debian.org/ jessie/updates main contrib non-free
deb-src http://security.debian.org/ jessie/updates main contrib non-free
# jessie-updates, previously known as 'volatile'
deb http://ftp.us.debian.org/debian/ jessie-updates main contrib non-free
deb-src http://ftp.us.debian.org/debian/ jessie-updates main contrib non-free
# pipelight
deb http://repos.fds-team.de/stable/debian/ jessie main


How can I tell which repository it pulled the package from?

[seahorse41]

Trying things on my own, I restarted Synaptic Package Manager, selected the 2 broken packages,
Again clicked on Package . Force version 2.7.9-2
There are only 2 choices, and 2.7.9-1 is not on the list.

It then requires changes to 5 packages, but the ones installed are not changed, and should be fine with the installed version.
Clicking Accept gives an error:
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: Unable to correct dependencies

So I instead try to remove the offending python2.7-dev package,
Accept it will remove 4 additional -dev packages, mostly libboost, and click accept, expecting I can reinstall the same working versions again later..., but I get another error:

Could not apply changes! Fix broken packages first.

So I can't remove the broken package without fixing it, and I can't fix it without ... It's not a perfect loop yet, I see something about dependencies...
The dependency list for libpython2.7-dev Is not a long list, and I don't see anything that was in the batch of upgrades I allowed.

[Head_on_a_Stick]

How can I tell which repository it pulled the package from?

Code: Select all

apt-cache policy python2.7 python2.7-dev

[seahorse41]

Code: Select all

apt-cache policy python2.7 python2.7-dev

python2.7:
Installed: 2.7.9-2
Candidate: 2.7.9-2+deb8u1
Version table:
2.7.9-2+deb8u1 0
500 http://ftp.us.debian.org/debian/ jessie/main i386 Packages
*** 2.7.9-2 0
500 cdrom://[Debian GNU/Linux 8.1.0 _Jessie_ - Official i386 DVD Binary-1 20150606-13:00]/ jessie/main i386 Packages
100 /var/lib/dpkg/status
python2.7-dev:
Installed: 2.7.9-2
Candidate: 2.7.9-2+deb8u1
Version table:
2.7.9-2+deb8u1 0
500 http://ftp.us.debian.org/debian/ jessie/main i386 Packages
*** 2.7.9-2 0
500 cdrom://[Debian GNU/Linux 8.1.0 _Jessie_ - Official i386 DVD Binary-1 20150606-13:00]/ jessie/main i386 Packages
100 /var/lib/dpkg/status

[Head_on_a_Stick]

How about:

Code: Select all

apt-cache policy python

[seahorse41]

How about:

Code: Select all

apt-cache policy python

python:
Installed: 2.7.9-1
Candidate: 2.7.9-1
Version table:
*** 2.7.9-1 0
500 cdrom://[Debian GNU/Linux 8.1.0 _Jessie_ - Official i386 DVD Binary-1 20150606-13:00]/ jessie/main i386 Packages
500 http://ftp.us.debian.org/debian/ jessie/main i386 Packages
100 /var/lib/dpkg/status


Okay, I see finally the -1 that stevepusser referred to as most current in Jessie. Next move?
Surely I'm not the only person getting this problem?
This is the best place to get help for this, right?

[stevepusser]

I checked, and I have the updated -2 already installed, so I don't know why yours didn't update smoothly like mine did.

You count try manually installing the packages from your package cache, in /var/cache/apt/archives/ with the overwrite flag:

Code: Select all

dpkg -i --force-overwrite <name-of-deb-file>

as root or with sudo, whatever you use.

[seahorse41]

I checked, and I have the updated -2 already installed, so I don't know why yours didn't update smoothly like mine did.

You count try manually installing the packages from your package cache, in /var/cache/apt/archives/ with the overwrite flag:

Code: Select all

dpkg -i --force-overwrite <name-of-deb-file>

Right I have -2 installed as well, or did before this update.
So you're saying I should force overwrite of the newest update -2+deb8u1 or the existing -2 ?

[seahorse41]

I thought about it and deduced your intent.
$ sudo dpkg -i --force-overwrite python2.7_2.7.9-2+deb8u1_i386.deb
(Reading database ... 210286 files and directories currently installed.)
Preparing to unpack python2.7_2.7.9-2+deb8u1_i386.deb ...
Unpacking python2.7 (2.7.9-2+deb8u1) over (2.7.9-2) ...
dpkg: warning: overriding problem because --force enabled:
dpkg: warning: trying to overwrite '/usr/share/doc/python2.7', which is also in package python 2.7.9-1
dpkg: warning: overriding problem because --force enabled:
dpkg: warning: trying to overwrite '/usr/share/doc/python2.7', which is also in package python2.7-dev 2.7.9-2
Setting up python2.7 (2.7.9-2+deb8u1) ...
Processing triggers for desktop-file-utils (0.22-1) ...
Processing triggers for gnome-menus (3.13.3-6) ...
Processing triggers for mime-support (3.58) ...
Processing triggers for man-db (2.7.0.2-5) ...

Problem solved. Thank you.

[stevepusser]

Great! (i resisted the impulse to tell you to "use the force") Could you edit the title of your first post in this thread and add "SOLVED"?*

*Until the sequel, when the phantom menace that created this very odd problem strikes again.