Update dpkg to 1.18.18
Bug #1654905 reported by
Julian Andres Klode
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| dpkg (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
Our dpkg is 1.18.10 from summer 2016. apt might want to start (build-)depending on 1.18.11 soon, we should really get this up a bit. Background is of course architecture patterns/wildcards:
dpkg < 1.18.11 uses triplets, dpkg >= 1.18.11 uses 4-tuplets.
And supporting both variants would be a bit annoying.
Revision history for this message
| Julian Andres Klode (juliank) wrote | #1 |
| Changed in dpkg (Ubuntu): | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
Revision history for this message
| Unit 193 (unit193) wrote | #2 |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in dpkg (Ubuntu): | |
| status: | Triaged → Fix Released |
To post a comment you must log in.
Marking this as triaged and medium, as it really makes sense to have the 4-tuple dpkg instead of the triplet based dpkg.
It's not entirely clear if the apt thing happens in the 1.4 series scheduled for zesty (and Debian stretch), or if it will move to zesty+1 (or +2 -- depending on how long stretch is frozen, zesty and zesty+1 might share an apt release series).