Hi, I'm checking bugs dormant too long to update their tracking. On this one I highly appreciate the report and the fixing we did in zesty (and later is done due to it being upstream) - it is ok to change that on a new release which zesty was.
But as outlined in comment #4 SRU'ing it would be as much chance for a regression to some users as it would fix others. Those affected (Like the reporter) already likely have workarounds in place, but others could be impacted by the reverse order. I asked to make it a more compelling case to drive the SRU in comment #7, but nothing happened. Thereby "timing out" the Xenial task and setting incomplete->invalid to clear the view for the issues currently actionable. If that still is a concern please provide the arguments needed for the SRU [1] and set it back to new or confirmed. [1]: https://wiki.ubuntu.com/StableReleaseUpdates P.S. Yakkety is EOL, so I set won't fix for that one ** Changed in: qemu (Ubuntu Yakkety) Status: Incomplete => Won't Fix ** Changed in: qemu (Ubuntu Xenial) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1670481 Title: Backport "populate PCI DT in reverse order" patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1670481/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
