On Fri, 15 Sep 2023 14:35:08 +0200 "Farblos" <akfkqu.9df...@vodafonemail.de> wrote: > Not sure whether this is still relevant or just bad luck or whatever ... my > unattended-upgrade failed today because of this issue. Logs available > on request. Work-around was to remove version 3.20+dfsg-7, retrigger > the unattended upgrade, install version 3.20+dfsg-8.
So 3.20+dfsg-7 is broken by emacs29 such that it can only be uninstalled, and not upgraded. I'm confident that your logs will show that the -7 is unpacked but no longer configured. If you're curious about what the generated configuration scripts actually do, then check out this article on how to inspect debs: https://blog.packagecloud.io/inspect-extract-contents-debian-packages/ To be honest I'm not totally sure why this unconfigured (or not totally configured) package can't be upgraded, but it can be argued that an upgrade from an undefined state is an unsafe upgrade. I mean the "why", where your logs will show the "what" and the "how" ;) Also, as maintainers our responsibility is reliable oldstable -> stable upgrades, so this kind of transient breakage will sometimes occur in unstable/sid as well as testing. > Thanks for taking care of this package, BTW! Yes, thank you Manphiz! And Farblos, thank you for reaching out :) While it's unfortunate that it was for a bug, it's always nice to hear from real users of mature software. Kind regards, Nicholas
signature.asc
Description: PGP signature
