unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: miha--- via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Jonas Bernoulli <jonas@bernoul.li>,
	Stefan Kangas <stefankangas@gmail.com>
Cc: 59005@debbugs.gnu.org
Subject: bug#59005: 29.0.50; Package transient installed as dependency despite it being built-in
Date: Sat, 26 Nov 2022 09:10:30 +0100	[thread overview]
Message-ID: <878rjy2l1l.fsf@miha-pc> (raw)
In-Reply-To: <871qprm7j7.fsf@bernoul.li>

[-- Attachment #1: Type: text/plain, Size: 1426 bytes --]

Jonas Bernoulli <jonas@bernoul.li> writes:

> Stefan Kangas <stefankangas@gmail.com> writes:
>
>> miha@kamnitnik.top writes:
>>
>>> With an empty .emacs.d directory and nonexistent .emacs.el init file,
>>> installing magit with 'M-x package-install RET magit RET' pulls
>>> transient from elpa. You can see it installed into ~/.emacs.d/elpa/.
>
> That wouldn't be surprising when using Melpa.  But that archive is not
> listed in the default value of `package-archives'.  What is its value
> of that variable for you and what version of magit gets installed?

(("gnu" . "https://elpa.gnu.org/packages/")
 ("nongnu" . "https://elpa.nongnu.org/nongnu/"))

and magit-3.3.0

More detailed bug recipe:

$ mkdir /tmp/emacs-tmp
$ HOME=/tmp/emacs-tmp src/emacs  # or just "emacs"

M-x package-install RET magit RET:
Emacs installs magit-3.3.0, most likely from nongnu elpa.

C-h v package-archives RET:
package-archivesis a variable defined in ‘package.el’.

Its value is
(("gnu" . "https://elpa.gnu.org/packages/")
 ("nongnu" . "https://elpa.nongnu.org/nongnu/"))

$ cd /tmp/emacs-tmp/.emacs.d/elpa
$ ls
archives
dash-2.19.1
dash-2.19.1.signed
git-commit-3.3.0
git-commit-3.3.0.signed
gnupg
magit-3.3.0
magit-3.3.0.signed
magit-section-3.3.0
magit-section-3.3.0.signed
transient-0.3.7
transient-0.3.7.signed
with-editor-3.2.0
with-editor-3.2.0.signed

Thanks and best regards.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]

  reply	other threads:[~2022-11-26  8:10 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 [this message]
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
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=878rjy2l1l.fsf@miha-pc \
    --to=bug-gnu-emacs@gnu.org \
    --cc=59005@debbugs.gnu.org \
    --cc=jonas@bernoul.li \
    --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).