fails to remove in maverick

Bug #716473 reported by Michael Vogt
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
jinja2 (Ubuntu)
Fix Released
Undecided
Unassigned
Maverick
Fix Released
High
Unassigned

Bug Description

TEST CASE:
1. install python3-jinja2 in maverick
2. uninstall python3-jinja2
3. verify that it fails
4. install python3-jinja2 from maverick-proposed
5. uninstall python3-jinja2
6. verify that it works now

During a automatic maverick->natty upgrade the auto-upgrade tester found the following problem:
...
Removing python3-jinja2 ...^M^M
+ find /usr/lib/python3.1/dist-packages/jinja2/ -name *\.pyc -delete^M
find: `/usr/lib/python3.1/dist-packages/jinja2/': No such file or directory^M
find: `/usr/lib/python3.1/dist-packages/jinja2/': No such file or directory^M^M
dpkg: error processing python3-jinja2 (--remove):^M^M
 subprocess installed pre-removal script returned error exit status 1^M^M
...

Revision history for this message
Michael Vogt (mvo) wrote :

The reason for the failure is that the path in the prerm scrip is incorrect:
-find /usr/lib/python3.1/dist-packages/jinja2/ -name '*\.pyc' -delete >/dev/null
+find /usr/lib/python3/dist-packages/jinja2/ -name '*\.pyc' -delete >/dev/null

Changed in jinja2 (Ubuntu):
status: New → Fix Released
Changed in jinja2 (Ubuntu Maverick):
importance: Undecided → High
status: New → In Progress
description: updated
Revision history for this message
Piotr Ożarowski (piotr) wrote : Re: [Bug 716473] [NEW] fails to remove in maverick

[Michael Vogt, 2011-02-10]
> Removing python3-jinja2 ...^M^M
> + find /usr/lib/python3.1/dist-packages/jinja2/ -name *\.pyc -delete^M
> find: `/usr/lib/python3.1/dist-packages/jinja2/': No such file or directory^M
> find: `/usr/lib/python3.1/dist-packages/jinja2/': No such file or directory^M^M
> dpkg: error processing python3-jinja2 (--remove):^M^M
>  subprocess installed pre-removal script returned error exit status 1^M^M

this was changed in 2.5.2-3 (after a change in python3.1 package in Debian)

PS you REALLY should consider adding package version numbers to bug
reports.

Revision history for this message
Martin Pitt (pitti) wrote : Please test proposed package

Accepted jinja2 into maverick-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Changed in jinja2 (Ubuntu Maverick):
status: In Progress → Fix Committed
tags: added: verification-needed
Revision history for this message
Pedro Villavicencio (pedro) wrote :

I've followed the test case and can confirm that the bug is fixed with the proposed package (package gets removed), marking this as verification-done, thanks all.

tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package jinja2 - 2.5.2-2ubuntu1

---------------
jinja2 (2.5.2-2ubuntu1) maverick-proposed; urgency=low

  * python3-jinja2.prerm:
    - fix find path to make the pacakge actually removable (LP: #716473)
 -- Michael Vogt <email address hidden> Thu, 10 Feb 2011 16:16:44 +0100

Changed in jinja2 (Ubuntu Maverick):
status: Fix Committed → Fix Released
tags: added: testcase
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.