unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 59005@debbugs.gnu.org, Jonas Bernoulli <jonas@bernoul.li>,
	Stefan Kangas <stefankangas@gmail.com>,
	miha@kamnitnik.top
Subject: bug#59005: 29.0.50; Package transient installed as dependency despite it being built-in
Date: Sun, 12 Feb 2023 11:48:21 -0800	[thread overview]
Message-ID: <87pmaehdh6.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87v8k8lvmq.fsf@web.de> (Michael Heerdegen's message of "Sat, 11 Feb 2023 04:38:05 +0100")

Michael Heerdegen <michael_heerdegen@web.de> writes:

> Jonas Bernoulli <jonas@bernoul.li> writes:
>
>> > I ask because "transient" rings a bell (it is also a package that is
>> > often related to trouble in my scenario).
>>
>> What kind of trouble?  Packaging trouble I assume.
>
> Yes: when updating packages from the package manager, dependencies are
> sometimes in effect deleted instead of updated.  This is often
> "transient", but that could be coincidental (because it gets regular
> updates maybe).
>
> No one seems to care about this problem so far.  Looking at package.el I
> don't see a recent change that looks like it could have such an effect.
> But since I did not get any help so far, I can only ask around...

I have seen this, also with transient, and more recently with "compat",
and found it very annoying. I think I solved it by explicitly
uninstalling transient and everything that depended on it, and then
re-installing -- I haven't seen the problem since. Come to think of it
compat was also a Magit dependency, so I wonder if something about
Magit's package definition changed? Anyway I haven't seen this for a
while, so I forgot about it.





  reply	other threads:[~2023-02-12 19:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03 20:04 bug#59005: 29.0.50; Package transient installed as dependency despite it being built-in miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-24 19:40 ` Stefan Kangas
2022-11-25 14:29   ` Jonas Bernoulli
2022-11-26  8:10     ` miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-26 14:17     ` Jonas Bernoulli
2023-02-10  1:38       ` Michael Heerdegen
2023-02-10 14:38         ` Jonas Bernoulli
2023-02-11  3:38           ` Michael Heerdegen
2023-02-12 19:48             ` Eric Abrahamsen [this message]
2023-02-13  2:24               ` Michael Heerdegen

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pmaehdh6.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=59005@debbugs.gnu.org \
    --cc=jonas@bernoul.li \
    --cc=michael_heerdegen@web.de \
    --cc=miha@kamnitnik.top \
    --cc=stefankangas@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).