Activity log for bug #1829860

Date Who What changed Old value New value Message
2019-05-21 12:45:18 Julian Andres Klode bug added bug
2019-05-29 18:58:20 Launchpad Janitor apt (Ubuntu): status New Fix Released
2019-08-05 15:41:25 Julian Andres Klode nominated for series Ubuntu Xenial
2019-08-05 15:41:25 Julian Andres Klode bug task added apt (Ubuntu Xenial)
2019-08-05 15:41:25 Julian Andres Klode nominated for series Ubuntu Disco
2019-08-05 15:41:25 Julian Andres Klode bug task added apt (Ubuntu Disco)
2019-08-05 15:41:25 Julian Andres Klode nominated for series Ubuntu Bionic
2019-08-05 15:41:25 Julian Andres Klode bug task added apt (Ubuntu Bionic)
2019-08-09 09:33:09 Julian Andres Klode description [Impact] APT releases the locks in the same order it acquires them, rather than reverse order. Given that we have no waiting for locks, this is not _super_ problematic, but it might be wrong: You'd get a lock failure on dpkg's lock, rather than lock-frontend. [Test case] ... [Regression potential] ... [Impact] APT releases the locks in the same order it acquires them, rather than reverse order. Given that we have no waiting for locks, this is not _super_ problematic, but it might be wrong: You'd get a lock failure on dpkg's lock, rather than lock-frontend. [Test case] Watch lock release with strace and see that it unlocks the right way. [Regression potential] ...
2019-08-09 09:36:41 Julian Andres Klode apt (Ubuntu Disco): status New In Progress
2019-08-09 09:49:27 Julian Andres Klode description [Impact] APT releases the locks in the same order it acquires them, rather than reverse order. Given that we have no waiting for locks, this is not _super_ problematic, but it might be wrong: You'd get a lock failure on dpkg's lock, rather than lock-frontend. [Test case] Watch lock release with strace and see that it unlocks the right way. [Regression potential] ... [Impact] APT releases the locks in the same order it acquires them, rather than reverse order. Given that we have no waiting for locks, this is not _super_ problematic, but it might be wrong: You'd get a lock failure on dpkg's lock, rather than lock-frontend. [Test case] Watch lock release with strace and see that it unlocks the right way. [Regression potential] Some other locking races or something?
2019-09-02 15:57:32 Łukasz Zemczak apt (Ubuntu Disco): status In Progress Fix Committed
2019-09-02 15:57:35 Łukasz Zemczak bug added subscriber Ubuntu Stable Release Updates Team
2019-09-02 15:57:38 Łukasz Zemczak bug added subscriber SRU Verification
2019-09-02 15:57:41 Łukasz Zemczak tags verification-needed verification-needed-disco
2019-09-03 10:49:47 Julian Andres Klode apt (Ubuntu Bionic): status New In Progress
2019-09-05 11:58:42 Łukasz Zemczak apt (Ubuntu Bionic): status In Progress Fix Committed
2019-09-05 11:58:46 Łukasz Zemczak tags verification-needed verification-needed-disco verification-needed verification-needed-bionic verification-needed-disco
2019-09-11 09:03:18 Julian Andres Klode tags verification-needed verification-needed-bionic verification-needed-disco verification-done-disco verification-needed verification-needed-bionic
2019-09-11 09:08:38 Julian Andres Klode tags verification-done-disco verification-needed verification-needed-bionic verification-done verification-done-bionic verification-done-disco
2019-09-12 12:13:46 Launchpad Janitor apt (Ubuntu Disco): status Fix Committed Fix Released
2019-09-12 12:14:04 Łukasz Zemczak removed subscriber Ubuntu Stable Release Updates Team
2019-09-12 12:14:19 Launchpad Janitor apt (Ubuntu Bionic): status Fix Committed Fix Released