From: Leo Famulari <leo@famulari.name>
To: Alexandre Oliva <lxoliva@fsfla.org>
Cc: Vagrant Cascadian <vagrant@debian.org>, guix-devel <guix-devel@gnu.org>
Subject: Re: linux-libre source tarballs
Date: Thu, 6 May 2021 17:23:07 -0400 [thread overview]
Message-ID: <YJReO18l6xC9Lab2@jasmine.lan> (raw)
In-Reply-To: <orzgx8cxiy.fsf@lxoliva.fsfla.org>
On Thu, May 06, 2021 at 01:10:45AM -0300, Alexandre Oliva wrote:
> I have heard about early format changes, but since Linux itself has used
> git archive to generate tarballs on the fly, and published digital
> signatures based on archives generated this way, I presume an
> expectation that changes to the format won't be made without a very
> compelling reason.
I asked because, historically, the linux-libre project has chosen not to
store tarballs of its generated linux-libre source trees.
Linux, on the other hand, does store their tarballs in perpetuity, even
if they are created with `git archive`.
Do you know for sure that Linux generates tarballs "on the fly" and does
not simply preserve the signed tarballs forever?
Otherwise, the PGP signatures could go "stale" at some point, and that
would be unprecedented and unacceptable.
next prev parent reply other threads:[~2021-05-06 21:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-02 1:45 linux-libre source tarballs Vagrant Cascadian
2021-05-02 2:45 ` Leo Famulari
2021-05-02 4:42 ` Leo Famulari
2021-05-02 21:08 ` Ludovic Courtès
2021-05-02 22:26 ` Leo Famulari
2021-05-02 22:38 ` Leo Famulari
2021-05-03 15:44 ` linux-libre source tarballs (disable "deblob-check"?) Leo Famulari
2021-05-03 16:39 ` linux-libre source tarballs Alexandre Oliva
2021-05-03 17:13 ` Leo Famulari
2021-05-06 4:10 ` Alexandre Oliva
2021-05-06 21:23 ` Leo Famulari [this message]
2021-05-06 20:30 ` Maxim Cournoyer
2021-05-09 3:27 ` Alexandre Oliva
2021-05-30 4:50 ` Vagrant Cascadian
2021-05-31 3:42 ` Leo Famulari
2021-05-31 19:57 ` Mathieu Othacehe
2021-08-01 20:45 ` source tarballs potentially built for each derivation Vagrant Cascadian
2021-08-01 21:04 ` Vagrant Cascadian
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YJReO18l6xC9Lab2@jasmine.lan \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=lxoliva@fsfla.org \
--cc=vagrant@debian.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 public inbox
https://git.savannah.gnu.org/cgit/guix.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).