all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Samuel Thibault <samuel.thibault@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org, debian-hurd@lists.debian.org,
	bug-hurd@gnu.org, hurd-bug@gnu.org
Subject: Re: Hurd Security vulnerabilities, please upgrade!
Date: Tue, 10 Aug 2021 17:56:34 +0200	[thread overview]
Message-ID: <20210810155634.ysjqffwwdv6nvmpc@begin> (raw)
In-Reply-To: <874kbxl2kd.fsf@elephly.net>

Ricardo Wurmus, le mar. 10 août 2021 17:52:34 +0200, a ecrit:
> I’m a little unclear on what this means for distributions like Guix.  Should
> we just update to the latest version from git?  Are there specific commits
> we should use if it’s not just the latest?

Since Sergey's copyright assignment is not complete yet, it's not
commited yet, so you have to pick up the patches from the debian
repository.

Samuel


  reply	other threads:[~2021-08-10 15:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210810020240.wpd5pksgdh5e2e3u@begin>
2021-08-10  4:55 ` Fwd: Hurd Security vulnerabilities, please upgrade! jbranso
2021-08-10 15:52 ` Ricardo Wurmus
2021-08-10 15:56   ` Samuel Thibault [this message]
2021-08-11 13:01     ` Ludovic Courtès
2021-08-12  2:18       ` Regarding copyright assignment to FSF Damien Zammit
2021-08-13 13:42         ` Maxime Devos
2021-08-13 16:23           ` Samuel Thibault
2021-08-14 21:26             ` Svante Signell
2021-08-14 21:40               ` Samuel Thibault
2021-08-13 20:48           ` Dr. Arne Babenhauserheide
2021-08-14  3:42         ` Ivan Shmakov
2021-08-14  5:43         ` Michael Banck
2021-08-14  9:00           ` Sergey Bugaev
2021-08-14 12:19           ` Dr. Arne Babenhauserheide
2021-08-14 13:12             ` Michael Banck
2021-08-14 14:16               ` Akib Azmain Turja

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=20210810155634.ysjqffwwdv6nvmpc@begin \
    --to=samuel.thibault@gnu.org \
    --cc=bug-hurd@gnu.org \
    --cc=debian-hurd@lists.debian.org \
    --cc=guix-devel@gnu.org \
    --cc=hurd-bug@gnu.org \
    --cc=rekado@elephly.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/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.