From: Stefan Kangas <stefankangas@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Guillaume MULLER <guillaume.muller@univ-st-etienne.fr>,
51205-done@debbugs.gnu.org
Subject: bug#51205: 26.3; useful packages auto-removed
Date: Sun, 3 Sep 2023 01:43:52 -0700 [thread overview]
Message-ID: <CADwFkmk_H5oN5yrOiwz+pnOKwpdDzzwEQB-3MdtujzeozurtMA@mail.gmail.com> (raw)
In-Reply-To: <874jxc7oti.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 12 Sep 2022 14:35:37 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Guillaume MULLER <guillaume.muller@univ-st-etienne.fr> writes:
>
>> - When I hit "M-x package-autoremove" , some of the packages I use on an
>> every day basis got removed automatically.
>
> (I'm going through old bug reports that unfortunately weren't resolved
> at the time.)
>
> That command removes packages that were not installed explicitly, but
> were installed as a dependency for package(s) that you've later removed.
>
>> I don't know what are the criteria used to detect a package is not used
>> anymore, but clearly some of my packages got removed abusively.
>
> "Not used" is not the criterion.
>
> Did that command remove anything that you hadn't installed explicitly?
> I tested the command here, but it seems like it's working as designed
> for me.
>
> If you see a bug here, do you have a recipe to reproduce it, starting
> from "emacs -Q"?
More information was requested, but none was given within 12 months, so
I'm closing this bug. If this is still an issue, please reply to this
email (use "Reply to all" in your email client) and we can reopen the
bug report.
prev parent reply other threads:[~2023-09-03 8:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 14:52 bug#51205: 26.3; useful packages auto-removed Guillaume MULLER
2022-09-12 12:35 ` Lars Ingebrigtsen
2023-09-03 8:43 ` Stefan Kangas [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmk_H5oN5yrOiwz+pnOKwpdDzzwEQB-3MdtujzeozurtMA@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=51205-done@debbugs.gnu.org \
--cc=guillaume.muller@univ-st-etienne.fr \
--cc=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.