ufw crashes in trigger on intrepid->jaunty upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-defaults (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
ufw (Ubuntu) |
Fix Released
|
Undecided
|
Jamie Strandboge |
Bug Description
Binary package hint: ufw
While doing a upgrade from intrepid to jaunty with a stock ubuntu-desktop install ufw crashed in
the trigger processing. I attach the full logs, but it seems like the relveant lines are:
term.log:
-----------
Processing triggers for ufw ...
...
Traceback (most recent call last):
File "/usr/sbin/ufw", line 25, in <module>
import ufw.frontend
ImportError: No module named ufw.frontend
dpkg: subprocess post-installation script returned error exit status 1
_usr_sbin_
-------
Traceback:
Traceback (most recent call last):
File "/usr/sbin/ufw", line 25, in <module>
import ufw.frontend
ImportError: No module named ufw.frontend
Related branches
Changed in ufw: | |
assignee: | nobody → jdstrand |
status: | New → In Progress |
Changed in python-defaults: | |
status: | New → In Progress |
Changed in ufw: | |
status: | Triaged → Fix Committed |
It seem like the problem is that our default python packaging makes it difficult to have stuff available during upgrade.
The attached branch should fix this (its against lp:ufw, I also checked lp:ufw/ufw-0.27-jaunty but that seems to not have any a different debian/changelog than in lp:ufw). I also attach it as a patch file (just in case I picked the wrong tree).
I have not yet tested the upgrade with the fix, but it will do no harm to add it even if it is not sufficient (but I think it is).