dselect: no access methods are available
Bug #1504761 reported by
Martin-Éric Racine
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| dpkg (Debian) |
Fix Released
|
Unknown
|
|||
| dpkg (Ubuntu) |
Fix Released
|
High
|
Adam Conrad | ||
| Wily |
Fix Released
|
High
|
Adam Conrad | ||
Bug Description
dselect in Wily is broken due to a mishandled multiarch issue upstream at Debian.
Debian fixed the issue in dpkg 1.18.3. while Wily currently has 1.18.2ubuntu4 in its repository.
| Changed in dpkg (Debian): | |
| status: | Unknown → Fix Released |
| Changed in dpkg (Ubuntu Wily): | |
| status: | New → Triaged |
| importance: | Undecided → High |
| Changed in dpkg (Ubuntu Wily): | |
| assignee: | nobody → Adam Conrad (adconrad) |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in dpkg (Ubuntu Wily): | |
| status: | Triaged → Fix Released |
To post a comment you must log in.
This bug was fixed in the package dpkg - 1.18.2ubuntu5
---------------
dpkg (1.18.2ubuntu5) wily; urgency=medium
* Pull packaging changes from 1.18.3 to fix libdir issues (LP: #1504761)
* Fix an off-by-one write access in dpkg-deb when parsing the deb magic.
* Fix a segfault when using «dpkg --no-act» with a synthetic --admindir.
-- Adam Conrad <email address hidden> Sat, 17 Oct 2015 12:47:12 -0600