dapper -> edgy upgrade breaks on python-clearsilver and python-pythoncard packages

Bug #68764 reported by randomjunk
14
Affects Status Importance Assigned to Milestone
clearsilver (Ubuntu)
Confirmed
High
Unassigned

Bug Description

Binary package hint: python-clearsilver

The apt-get dist-upgrade command throws out the following. It seems to be conflicting with some other version of itself from somewhere:

Preparing to replace python-clearsilver 0.9.13-3.2ubuntu1 (using .../python-clearsilver_0.10.3-2_i386.deb) ...
Unpacking replacement python-clearsilver ...
dpkg: error processing /var/cache/apt/archives/python-clearsilver_0.10.3-2_i386.deb (--unpack):
 trying to overwrite `/usr/lib/python2.4/site-packages/neo_cgi.so', which is also in package python2.4-clearsilver
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Preparing to replace python-pythoncard 0.8.1-3ubuntu1 (using .../python-pythoncard_0.8.1-7_all.deb) ...
Unpacking replacement python-pythoncard ...
dpkg: error processing /var/cache/apt/archives/python-pythoncard_0.8.1-7_all.deb (--unpack):
 trying to overwrite `/usr/share/pythoncard/pythoncard_config.txt', which is also in package python2.4-pythoncard
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/python-clearsilver_0.10.3-2_i386.deb
 /var/cache/apt/archives/python-pythoncard_0.8.1-7_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Michael Vogt (mvo)
Changed in clearsilver:
importance: Undecided → High
Revision history for this message
Michael Hackett (at217) wrote :

I'm getting the same error for python-clearsilver when upgrading to edgy Xubuntu (using dist-upgrade).

Revision history for this message
Michael Hackett (at217) wrote :

My workaround was simply to remove python-clearsilver, as I suspect the python2.4-clearsilver package (which has the same version number) will do the trick for whatever is depending on it. I guess I'll find out if that's the case soon.

Is this maybe an old package that should be removed? It seems that usually packages named like this are empty packages that depend on the latest more-specific version of the package, to make upgrading easier. Does this one actually contain all the same files as the python2.4-clearsilver package?

Revision history for this message
John Vivirito (gnomefreak) wrote :

Is this still a problem for either of you?

Changed in clearsilver:
status: Unconfirmed → Needs Info
Revision history for this message
Taylor Mitchell (tmitchell) wrote :

Just ran into this bug today. Backing out python-clearsilver will require me to remove trac also so I'm not inclined to do that.

Revision history for this message
Michael Hackett (at217) wrote :

John,

As far as I can tell, nothing has changed. I did an update and try to install python-clearsilver again and got the same error.

Having never packaged anything, I'm not sure about this, but it seems from other packages are organized that the python-clearsilver package should be an empty archive with a dependency on python2.4-clearsilver (or whatever is the current version).

Instead, it contains the same set of files as the python2.4-clearsilver archive, but appears to contain a newer version of the package (0.10.3-2 vs. 0.9.13-3.2). I know nothing about this package itself (it was installed as a dependcy of something else), so I don't know if there's a reason to keep the old version, but if not, I'd suggest repackaging the current version as python2.4-clearsilver and making the package with no version number strictly a dependent on that real package. Please correct me if I've got this stuff wrong, as I'd like to get more involved once I understand the system a little better.

Revision history for this message
Kai Kasurinen (kai-kasurinen) wrote :

python-clearsilver need to conflicts/replaces python2.4-clearsilver. Now it only conflicts/replaces python2.3-clearsilver.

Changed in clearsilver:
status: Needs Info → Confirmed
Revision history for this message
Bobby (bobbymartin2) wrote :

I was two releases behind, so I did an upgrade from dapper to edgy, which appeared to go flawlessly. Then I did an upgrade from edgy to feisty, which broke as listed above, except that I only have python-pythoncard installed (not python-clearsilver) and the target version is 0.8.1-3ubuntu1, not 0.8.1-3ubuntu1.

I can provide my full logs upon request. Does anyone have a solution for this yet?

Revision history for this message
Bobby (bobbymartin2) wrote :

Er, forget the nonsensical comment about the target version.

I meant to say the installed version of python-pythoncard was python-pythoncard_0.8.1-8.1_all.deb, not python-pythoncard_0.8.1-7_all.deb.

Revision history for this message
Chris Wagner (chris-wagner) wrote :
Download full text (4.2 KiB)

I had such a similar issue when upgrading from Edgy to Feisty. After the upgrade, a "sudo apt-get dist-upgrade" would look like this:
-------------------------------------------------------------------------
chris@easyweaze:~$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  python-clearsilver
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/169kB of archives.
After unpacking 397kB of additional disk space will be used.
Do you want to continue [Y/n]? y
(Reading database ... 31042 files and directories currently installed.)
Preparing to replace python-clearsilver 0.9.13-3.2ubuntu1 (using .../python-clearsilver_0.10.3-4.1_i386.deb) ...
Unpacking replacement python-clearsilver ...
dpkg: error processing /var/cache/apt/archives/python-clearsilver_0.10.3-4.1_i386.deb (--unpack):
 trying to overwrite `/usr/lib/python2.4/site-packages/neo_cgi.so', which is also in package python2.4-clearsilver
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/python-clearsilver_0.10.3-4.1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
-------------------------------------------------------------------------

A simple "sudo apt-get remove python2.4-clearsilver" didn't fix the problem, as I'd expect. I had to remove both python2.4-clearsilver and python-clearsilver, which in turn removed trac, as well. So, I fixed the problem like this:
-------------------------------------------------------------------------
chris@easyweaze:~$ sudo apt-get remove python2.4-clearsilver python-clearsilver
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  python-clearsilver python2.4-clearsilver trac
0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
Need to get 0B of archives.
After unpacking 2367kB disk space will be freed.
Do you want to continue [Y/n]? y
(Reading database ... 31041 files and directories currently installed.)
Removing trac ...
dpkg - warning: while removing trac, directory `/usr/share/trac/wiki-macros' not empty so not removed.
dpkg - warning: while removing trac, directory `/usr/share/trac' not empty so not removed.
Removing python-clearsilver ...
Removing python2.4-clearsilver ...
chris@easyweaze:~$ sudo apt-get install
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
chris@easyweaze:~$ sudo apt-get install trac
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  python-clearsilver
Suggested packages:
  python-docutils
Recommended packages:
  python-setuptools
The following NEW packages will be installed:
  python-clearsilver trac
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/554kB of archives.
After unpacking 2544kB of additional disk space will be used.
Do you want to...

Read more...

Revision history for this message
Artti (artti) wrote :

# apt-get remove python2.4-clearsilver python-clearsilver
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package python-clearsilver is not installed, so not removed
You might want to run `apt-get -f install' to correct these:
The following packages have unmet dependencies:
  trac: Depends: python-clearsilver (>= 0.9.3) but it is not going to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).

# apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following extra packages will be installed:
  python-clearsilver
The following NEW packages will be installed:
  python-clearsilver
0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded.
1 not fully installed or removed.
Need to get 0B/82.1kB of archives.
After unpacking 233kB of additional disk space will be used.
Do you want to continue [Y/n]? Y
(Reading database ... 26322 files and directories currently installed.)
Unpacking python-clearsilver (from .../python-clearsilver_0.10.3-2_i386.deb) ...
dpkg: error processing /var/cache/apt/archives/python-clearsilver_0.10.3-2_i386.deb (--unpack):
 trying to overwrite `/usr/lib/python2.4/site-packages/neo_cgi.so', which is also in package python2.4-clearsilver
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/python-clearsilver_0.10.3-2_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Argh!

Revision history for this message
Artti (artti) wrote :

Forget about last one. I missed the "trac" part.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.