Comment 29 for bug 1611010
Revision history for this message
| Julian Andres Klode (juliank) wrote | #29 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Likely. See, the whole thing happens when the call stack is unwound in response to the first error here. In the other cases, the status update happens elsewhere.
So, what happened here is that we fixed the first error on the apt side, and used this bug to track that (and marked it as such in the SRU). The other bug reports are about ubiquity only.
So what really happened it seems is that:
- the apt side of this bug is closed
- the real bug in ubiquity is not closed, which is a
bug in the debconf status reporting parsing thing
- the "fix" just added code to work around the apt issue.
So, let's keep the apt task to track the apt side (thus Fix Released and In Progress), and keep the ubiquity task open to fix that properly there. This way we can still sanely track the bug fixes and SRUs, even if it is a bit weird.