Yes, it happened - it was the result of an explicit autoremove on my part though after I had dist-upgraded to current focal-updates. I should have noticed that this was happening and stopped it, granted. :)
Attached is the snippet of apt's term.log corresponding to the autoremove run. It crapped out at the end as usual because I have a tiny /boot; not included but mentioning because it might mean the log is truncated a bit.
Now, this system has been through several Ubuntu development cycles. It's likely to be unclean. So I don't mind if the priority is low but making use of this feature of apt feels sensible to me, although admittedly there's a question about where we would stop if we started to do it.
Cheers Steve. Nope, -proposed is not enabled.
Yes, it happened - it was the result of an explicit autoremove on my part though after I had dist-upgraded to current focal-updates. I should have noticed that this was happening and stopped it, granted. :)
Attached is the snippet of apt's term.log corresponding to the autoremove run. It crapped out at the end as usual because I have a tiny /boot; not included but mentioning because it might mean the log is truncated a bit.
Now, this system has been through several Ubuntu development cycles. It's likely to be unclean. So I don't mind if the priority is low but making use of this feature of apt feels sensible to me, although admittedly there's a question about where we would stop if we started to do it.