all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alexandre Oliva <lxoliva@fsfla.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: Vagrant Cascadian <vagrant@debian.org>, guix-devel <guix-devel@gnu.org>
Subject: Re: linux-libre source tarballs
Date: Sun, 09 May 2021 00:27:58 -0300	[thread overview]
Message-ID: <orczu0a8n5.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <875yzvip10.fsf@gmail.com> (Maxim Cournoyer's message of "Thu, 06 May 2021 16:30:03 -0400")

On May  6, 2021, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:

> Alexandre Oliva <lxoliva@fsfla.org> writes:

>> recipes as to the possibilities of getting to the GNU Linux-libre
>> sources from it, how to verify signatures, etc

> I for one have not seen them.  Would you mind making them available
> somewhere?  I'd be interested in having a look.

Not as extensive as I thought ;-)
unless I found only an early version,
but so here it goes:


* Download one release as git checkout:

git clone -b sources/v$version --single-branch \
  git://linux-libre.fsfla.org/releases.git linux-libre-$version/


* Example substitutions:

version=5.7-gnu upversion=5.7
prefix=linux-$upversion/


* If you plan on verifying any releases:

git archive --remote=git://linux-libre.fsfla.org/releases.git \
  --format tar master | tar -x -O keyring.gpg | gpg --import -


* If you plan on verifying release $version:

git archive --remote=git://linux-libre.fsfla.org/releases.git \
  --format tar logs/v$version | tar -x &&
if test -f linux-libre-$version.git.tar.sign; then
  prefix=linux-libre-$version/ targit=.git
else
  prefix=linux-$upversion/ targit=
fi


* Download/archive one release as git tarball:

# Use the conditional prefix above to be able to verify.
git archive --remote=git://linux-libre.fsfla.org/releases.git \
  --format tar.gz --prefix=$prefix sources/v$version \
  -o linux-libre-$version$targit.tar.gz


* Verify one release in git repo:

git archive --format tar --prefix=$prefix sources/v$version |
gpg --verify logs/v$version/linux-libre-$version$targit.tar.sign -


* Verify one release in a (gzip-compressed) tarball:

# Must have used the conditional prefix above to verify.
zcat linux-libre-$version$targit.tar.gz |
gpg --verify linux-libre-$version$targit.tar.sign -


* Download and verify a released compressed tarball:

ext=lz comp=lzip # ext=bz2 comp=bzip2 # ext=xz comp=xz
wget https://linux-libre.fsfla.org/pub/linux-libre/releases\
/$version/linux-libre-$version.tar.{$ext,sign} &&
$comp -d < linux-libre-$version.tar.$ext |
gpg --verify linux-libre-$version.tar.sign - # no $targit


-- 
Alexandre Oliva, happy hacker                https://FSFLA.org/blogs/lxo/
   Free Software Activist                       GNU Toolchain Engineer
Disinformation flourishes because many people care deeply about injustice
but very few check the facts.  Ask me about <https://stallmansupport.org>


  reply	other threads:[~2021-05-09  3:28 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
2021-05-06 20:30     ` Maxim Cournoyer
2021-05-09  3:27       ` Alexandre Oliva [this message]
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

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

  git send-email \
    --in-reply-to=orczu0a8n5.fsf@lxoliva.fsfla.org \
    --to=lxoliva@fsfla.org \
    --cc=guix-devel@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.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.