Lucid -> Precise upgrade does not clean up files

Bug #1031530 reported by Scott Kitterman
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-support (Ubuntu)
New
Undecided
Unassigned
Precise
Won't Fix
High
Unassigned

Bug Description

Upgraded today from Lucid to Precise. These packages need to clean up after themselves.

Processing triggers for python-support ...^M
WARNING: WARNING: /usr/share/pyshared/GnuPGInterface.py is linked but does not belong to any package.^M
WARNING: WARNING: /usr/share/pyshared/configobj.py is linked but does not belong to any package.^M
WARNING: WARNING: /usr/share/pyshared/pycurl-7.19.0.egg-info is linked but does not belong to any package.^M
WARNING: WARNING: /usr/share/pyshared/validate.py is linked but does not belong to any package.^M
WARNING: WARNING: /usr/share/pyshared/curl/__init__.py is linked but does not belong to any package.^M
WARNING: WARNING: /usr/share/pyshared/simplejson/__init__.py is linked but does not belong to any package.^M
WARNING: WARNING: /usr/share/pyshared/simplejson/decoder.py is linked but does not belong to any package.^M
WARNING: WARNING: /usr/share/pyshared/simplejson/encoder.py is linked but does not belong to any package.^M
WARNING: WARNING: /usr/share/pyshared/simplejson/scanner.py is linked but does not belong to any package.^M
WARNING: WARNING: /usr/share/pyshared/simplejson/tool.py is linked but does not belong to any package.^M
WARNING: WARNING: /usr/share/pyshared/simplejson/tests/__init__.py is linked but does not belong to any package.^M
WARNING: WARNING: /usr/share/pyshared/simplejson/tests/test_check_circular.py is linked but does not belong to any package.^M
WARNING: WARNING: /usr/share/pyshared/simplejson/tests/test_decode.py is linked but does not belong to any package.^M
WARNING: WARNING: /usr/share/pyshared/simplejson/tests/test_default.py is linked but does not belong to any package.^M
WARNING: WARNING: /usr/share/pyshared/simplejson/tests/test_dump.py is linked but does not belong to any package.^M
WARNING: WARNING: /usr/share/pyshared/simplejson/tests/test_encode_basestring_ascii.py is linked but does not belong to any package.^M
WARNING: WARNING: /usr/share/pyshared/simplejson/tests/test_fail.py is linked but does not belong to any package.^M
WARNING: WARNING: /usr/share/pyshared/simplejson/tests/test_float.py is linked but does not belong to any package.^M
WARNING: WARNING: /usr/share/pyshared/simplejson/tests/test_indent.py is linked but does not belong to any package.^M
WARNING: WARNING: /usr/share/pyshared/simplejson/tests/test_pass1.py is linked but does not belong to any package.^M
WARNING: WARNING: /usr/share/pyshared/simplejson/tests/test_pass2.py is linked but does not belong to any package.^M
WARNING: WARNING: /usr/share/pyshared/simplejson/tests/test_pass3.py is linked but does not belong to any package.^M
WARNING: WARNING: /usr/share/pyshared/simplejson/tests/test_recursion.py is linked but does not belong to any package.^M
WARNING: WARNING: /usr/share/pyshared/simplejson/tests/test_scanstring.py is linked but does not belong to any package.^M
WARNING: WARNING: /usr/share/pyshared/simplejson/tests/test_separators.py is linked but does not belong to any package.^M
WARNING: WARNING: /usr/share/pyshared/simplejson/tests/test_unicode.py is linked but does not belong to any package.^M

Changed in pycurl (Ubuntu Precise):
importance: Undecided → High
Changed in simplejson (Ubuntu Precise):
importance: Undecided → High
description: updated
Changed in gnupginterface (Ubuntu Precise):
importance: Undecided → High
Changed in configobj (Ubuntu Precise):
importance: Undecided → High
Revision history for this message
Piotr Ożarowski (piotr) wrote :

is that simplejson <= 2.1.2-1?

Changed in simplejson (Ubuntu):
status: New → Incomplete
Revision history for this message
Piotr Ożarowski (piotr) wrote :
Revision history for this message
Scott Kitterman (kitterman) wrote :

Simpljson 2.3.2-1

Changed in simplejson (Ubuntu):
status: Incomplete → New
Revision history for this message
Scott Kitterman (kitterman) wrote :

I agree it looks like that, but precise has python-support | 1.0.14ubuntu2 | precise/universe | source, all. Perhaps the old python-support was still used somehow?

Revision history for this message
Scott Kitterman (kitterman) wrote :

It does seem more likely a python-support issue (somehow).

affects: simplejson (Ubuntu) → python-support (Ubuntu)
no longer affects: configobj (Ubuntu)
no longer affects: configobj (Ubuntu Precise)
no longer affects: gnupginterface (Ubuntu Precise)
no longer affects: gnupginterface (Ubuntu)
no longer affects: pycurl (Ubuntu Precise)
no longer affects: pycurl (Ubuntu)
Revision history for this message
Stefano Rivera (stefanor) wrote :

I'd be interested to see the upgrade logs.

It really does look like the old python-support is still installed, but that shouldn't happen

The new python-minimal Breaks python-support (< 1.0.10ubuntu2). And the dhp2 modules depend on the new python.

So, I think it's only possible if the new modules are configured before the new python-support.

Revision history for this message
Scott Kitterman (kitterman) wrote : Re: [Bug 1031530] Re: Lucid -> Precise upgrade does not clean up files
  • apt-term.log Edit (236.9 KiB, text/x-log; charset="UTF-8"; name="apt-term.log")

On Wednesday, August 01, 2012 08:54:57 PM you wrote:
> I'd be interested to see the upgrade logs.

Here's the apt-term.log. Let me know if you need more.

Scott K

Revision history for this message
Stefano Rivera (stefanor) wrote :

Hi Scott (2012.08.02_00:49:18_+0200)
> > I'd be interested to see the upgrade logs.
> Here's the apt-term.log. Let me know if you need more.

The python-support trigger is firing before the new python-support is
unpacked, even though it's going to be unpacked in the same dpkg run.

$ egrep '(python-support|configobj)' apt-term.log
Processing triggers for python-support ...
Preparing to replace python-configobj 4.7.1-1 (using .../python-configobj_4.7.2+ds-3build1_all.deb) ...
Unpacking replacement python-configobj ...
Processing triggers for python-support ...
WARNING: WARNING: /usr/share/pyshared/configobj.py is linked but does not belong to any package.
Preparing to replace python-support 1.0.4ubuntu1 (using .../python-support_1.0.14ubuntu2_all.deb) ...
Unpacking replacement python-support ...
Setting up python-configobj (4.7.2+ds-3build1) ...
Setting up python-support (1.0.14ubuntu2) ...
Processing triggers for python-support ...

This is vaguely similar to these dpkg bugs
http://bugs.debian.org/671711
http://bugs.debian.org/484669

I don't know how best to handle this. An update-manager quirk?

Revision history for this message
Scott Kitterman (kitterman) wrote :
Download full text (4.7 KiB)

Sounds reasonable.

Stefano Rivera <email address hidden> wrote:

>Hi Scott (2012.08.02_00:49:18_+0200)
>> > I'd be interested to see the upgrade logs.
>> Here's the apt-term.log. Let me know if you need more.
>
>The python-support trigger is firing before the new python-support is
>unpacked, even though it's going to be unpacked in the same dpkg run.
>
>$ egrep '(python-support|configobj)' apt-term.log
>Processing triggers for python-support ...
>Preparing to replace python-configobj 4.7.1-1 (using
>.../python-configobj_4.7.2+ds-3build1_all.deb) ...
>Unpacking replacement python-configobj ...
>Processing triggers for python-support ...
>WARNING: WARNING: /usr/share/pyshared/configobj.py is linked but does
>not belong to any package.
>Preparing to replace python-support 1.0.4ubuntu1 (using
>.../python-support_1.0.14ubuntu2_all.deb) ...
>Unpacking replacement python-support ...
>Setting up python-configobj (4.7.2+ds-3build1) ...
>Setting up python-support (1.0.14ubuntu2) ...
>Processing triggers for python-support ...
>
>This is vaguely similar to these dpkg bugs
>http://bugs.debian.org/671711
>http://bugs.debian.org/484669
>
>I don't know how best to handle this. An update-manager quirk?
>
>--
>You received this bug notification because you are subscribed to the
>bug
>report.
>https://bugs.launchpad.net/bugs/1031530
>
>Title:
> Lucid -> Precise upgrade does not clean up files
>
>Status in “python-support” package in Ubuntu:
> New
>Status in “python-support” source package in Precise:
> New
>
>Bug description:
> Upgraded today from Lucid to Precise. These packages need to clean up
> after themselves.
>
> Processing triggers for python-support ...^M
>WARNING: WARNING: /usr/share/pyshared/GnuPGInterface.py is linked but
>does not belong to any package.^M
>WARNING: WARNING: /usr/share/pyshared/configobj.py is linked but does
>not belong to any package.^M
>WARNING: WARNING: /usr/share/pyshared/pycurl-7.19.0.egg-info is linked
>but does not belong to any package.^M
>WARNING: WARNING: /usr/share/pyshared/validate.py is linked but does
>not belong to any package.^M
>WARNING: WARNING: /usr/share/pyshared/curl/__init__.py is linked but
>does not belong to any package.^M
>WARNING: WARNING: /usr/share/pyshared/simplejson/__init__.py is linked
>but does not belong to any package.^M
>WARNING: WARNING: /usr/share/pyshared/simplejson/decoder.py is linked
>but does not belong to any package.^M
>WARNING: WARNING: /usr/share/pyshared/simplejson/encoder.py is linked
>but does not belong to any package.^M
>WARNING: WARNING: /usr/share/pyshared/simplejson/scanner.py is linked
>but does not belong to any package.^M
>WARNING: WARNING: /usr/share/pyshared/simplejson/tool.py is linked but
>does not belong to any package.^M
>WARNING: WARNING: /usr/share/pyshared/simplejson/tests/__init__.py is
>linked but does not belong to any package.^M
>WARNING: WARNING:
>/usr/share/pyshared/simplejson/tests/test_check_circular.py is linked
>but does not belong to any package.^M
>WARNING: WARNING: /usr/share/pyshared/simplejson/tests/test_decode.py
>is linked but does not belong to any package.^M
>WARNING: WARNING: /usr/share/pyshared/simplejson/tests/test_default.py
>is...

Read more...

Revision history for this message
Steve Langasek (vorlon) wrote :

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release

Changed in python-support (Ubuntu Precise):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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