Subject: bug#44306: package-delete exiting on encountering system/dependency packages

From: Stefan Kangas <[email-masked]>
Date: Sat, 31 Oct 2020 19:50:33 -0700

Boruch Baum <[email-masked]> writes:

> As a follow-up, I'm now noticing an additional related bug, which is
> kind-of a resiliency issue. Let's say several versions of a package
> accumulate, then what has happened in my case is that package-autoremove
> only deletes the single most recent obsolete version. For example, in
> examining my *Messages* buffer, I see that one run of the function
> reported
>
>    Package ‘popup-20200610.317’ deleted.
>
> A next run of the function reported
>
>    Package ‘popup-20200531.742’ deleted.
>
> Finally, the most recent run of the function reported:
>
>    Package ‘popup-0.5.8’ is a system package, not deleting

Please submit this bug, including which version(s) you are seeing this
on, as a separate bug report.

Thanks in advance.