From: Stefan Kangas <stefankangas@gmail.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: 66414@debbugs.gnu.org, yantar92@posteo.net, monnier@iro.umontreal.ca
Subject: bug#66414: GNU ELPA: Require signed tags to release new package versions
Date: Mon, 9 Oct 2023 09:44:25 +0000 [thread overview]
Message-ID: <CADwFkmnNrZEJf3HLftLqWCEL4RgBtXFXzDx6mfOsX0kxT39m0A@mail.gmail.com> (raw)
In-Reply-To: <87r0m4kudf.fsf@posteo.net>
Philip Kaludercic <philipk@posteo.net> writes:
> No, my bad. I didn't know that git tags could be signed, so I misread
> the sentence.
>
> One issue might be that elpa-admin.el doesn't really do anything with
> git tags, though I guess it should be possible to verify a remote git
> tag? An alternative might be to check for signed git commits, at the
> very least for the commits that bump the version tag. That way all the
> could be kept in elpa.git.
Yes, I think a signed commit might work fine for this purpose too. It
would be a more minimal change, if nothing else.
next prev parent reply other threads:[~2023-10-09 9:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 7:15 bug#66414: GNU ELPA: Require signed tags to release new package versions Stefan Kangas
2023-10-09 8:32 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-09 8:37 ` Stefan Kangas
2023-10-09 9:01 ` Philip Kaludercic
2023-10-09 9:30 ` Stefan Kangas
2023-10-09 9:39 ` Philip Kaludercic
2023-10-09 9:44 ` Stefan Kangas [this message]
2023-10-09 21:52 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-10 11:28 ` Stefan Kangas
2023-10-10 13:07 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-10 13:18 ` Stefan Kangas
2023-10-10 13:24 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=CADwFkmnNrZEJf3HLftLqWCEL4RgBtXFXzDx6mfOsX0kxT39m0A@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=66414@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=philipk@posteo.net \
--cc=yantar92@posteo.net \
/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.