d-shlibs gets upset with the new armhf linker
Bug #994250 reported by
Adam Conrad
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
d-shlibs (Debian) |
Fix Released
|
Unknown
|
|||
d-shlibs (Ubuntu) |
Fix Released
|
Undecided
|
Adam Conrad | ||
Precise |
Fix Released
|
Undecided
|
Adam Conrad |
Bug Description
This was discovered in Debian after we switched the linker to the new location, but we didn't get a chance to see the issue in precise, due to nothing build-depending on d-shlibs having been built after we made the change.
Already fixed in quantal in 0.51ubuntu1, simple patch being applied and uploaded to precise-proposed as well (this may also need copying to -security, as security doesn't depend on updates, and we could have security releases FTBFS because of this).
Changed in d-shlibs (Ubuntu): | |
assignee: | nobody → Adam Conrad (adconrad) |
Changed in d-shlibs (Ubuntu Precise): | |
assignee: | nobody → Adam Conrad (adconrad) |
Changed in d-shlibs (Ubuntu): | |
status: | New → Fix Released |
Changed in d-shlibs (Ubuntu Precise): | |
status: | New → In Progress |
Changed in d-shlibs (Debian): | |
status: | Unknown → New |
Changed in d-shlibs (Debian): | |
status: | New → Fix Released |
To post a comment you must log in.
Uploaded to precise-proposed at 0.49ubuntu1, awaiting approval from an SRU member who isn't me.