re-merge python-crypto according to build system changes
Bug #664648 reported by
Scott Moser
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-crypto (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: python-crypto
bug 662883 was opened to get a merge of Merge python-crypto 2.1.0-2 to fix packages that depend on the newer version.
The bug there had some discussion about which was the correct way to merge or handle the build, but there is an interest in getting the bug fixed to resolve dependencies before the discussion occurs.
This bug is opened as a placeholder to "fix it right".
Revision history for this message
| Sebastian Ramacher (s-ramacher) wrote | #1 |
Revision history for this message
| Benjamin Drung (bdrung) wrote | #2 |
| Changed in python-crypto (Ubuntu): | |
| status: | New → Fix Released |
To post a comment you must log in.
I guess this bug can be closed now as python-crypto has been synced from Debian (see #792349 for details).