From: Philip Kaludercic <philipk@posteo.net>
To: Stefan Kangas <stefankangas@gmail.com>
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, 09 Oct 2023 09:01:29 +0000 [thread overview]
Message-ID: <871qe4maom.fsf@posteo.net> (raw)
In-Reply-To: <CADwFkm=pdagsFnyy1wWwXS+R5AOn6yyuN+y2+oCY9GCzhEUcXQ@mail.gmail.com> (Stefan Kangas's message of "Mon, 9 Oct 2023 07:15:47 +0000")
Stefan Kangas <stefankangas@gmail.com> writes:
> Severity: wishlist
>
> I propose optionally releasing a new version of packages on
> NonGNU/GNU ELPA only if there is a valid PGP signature. We can't make
> it mandatory, at the very least not initially, because it would break
> too many existing workflows.
I am not sure what the context here is, so sorry for the potentially
stupid question, but what PGP signatures are we talking about? Are you
suggesting that the commit should be signed?
> The standard feature to do that in git would be a signed git tag.
> However, (Non-)GNU ELPA currently rebuilds package tarballs every time
> the "Version" comment header is updated, while git tags are ignored.
>
> Forwarded from
>
> https://lists.gnu.org/r/emacs-devel/2023-02/msg00120.html
next prev parent reply other threads:[~2023-10-09 9:01 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 [this message]
2023-10-09 9:30 ` Stefan Kangas
2023-10-09 9:39 ` Philip Kaludercic
2023-10-09 9:44 ` Stefan Kangas
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=871qe4maom.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=66414@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=stefankangas@gmail.com \
--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.