Plainbox tests are broken by PEP 440 incompatible Debian/Ubuntu packages
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
PlainBox (Toolkit) |
Won't Fix
|
Undecided
|
Unassigned | ||
apturl (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
ufw (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
When running unit tests on my vivid VM I've noticed that many tests fail because there are extra lines printed by pkg_resources:
- /usr/lib/
- PEP440Warning,
- /usr/lib/
- PEP440Warning,
- /usr/lib/
- PEP440Warning,
I've discussed this with Barry Warsaw and a few other people and the result is that yes, it's a bug in _each_ of those packages and those should be fixed.
I think there are two things we need to do:
- a long term plan should be based on fixing all of those one by one upstream in debian/ubuntu
- a short term plan should be to prevent those additional lines from break our tests
summary: |
- tests broken by PEP 440 incompatible Debian/Ubuntu packages + Plainbox tests are broken by PEP 440 incompatible Debian/Ubuntu packages |
affects: | ufw → ufw (Ubuntu) |
affects: | python-apt → python-apt (Ubuntu) |
affects: | apturl → apturl (Ubuntu) |
Changed in plainbox: | |
status: | New → Confirmed |
Changed in plainbox: | |
status: | Confirmed → Won't Fix |
For python-apt, that's a duplicate of bug 1445949. This has been fixed in the 1.0 beta in Debian unstable.
Here's the function I used to translate the Debian version to the PEP440 (in most cases it works, there are some corner cases like ~ubuntu that are not expressible):
http:// anonscm. debian. org/cgit/ apt/python- apt.git/ commit/ ?id=165c3e53471 6c7f300a6419e2f 0ccc331f63c0c9