Well, I uploaded it to Debian on May 31st, and it was even accepted in Buster (which was testing at the time) five days later, on June 6th; but I see on my Debian Maintainer dashboard that it never reached eoan. I didn't investigate further about why it was not automatically synced as usually.
I also see in my dashboard, for eoan, "prop: 1.1.0-5". I don't know what this means; "proposed updates" maybe ? But I thought proposed updates was a testing ground for updates to **stable** ? I wouldn't mind an explanation... Also, if kernel 5.2 is ever backported to disco, acpi-call would also need a backport. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830040 Title: acpi-call 1.1.0-4 ADT test failure with linux 5.2.0-0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1830040/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
