unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: Any objections to removing linux-libre@4.1?
Date: Thu, 08 Jun 2017 16:33:24 +0200	[thread overview]
Message-ID: <87y3t2eeh7.fsf@elephly.net> (raw)
In-Reply-To: <87wp8suvs4.fsf@netris.org>


Mark H Weaver <mhw@netris.org> writes:

> Does anyone here still need linux-libre@4.1 in Guix?  If not, I'd like
> to remove it.

Is this not the only version of Linux libre that does not expose the
system clock bug Libreboot users suffer from?

I’m still using 4.1 on one of my machines for that reason until I can
upgrade Libreboot.

> Upstream security updates for it seem to be quite infrequent (2.5 months
> between the last two releases), and the recent update to 4.1.40
> neglected to include a fix for CVE-2017-6074, which does not inspire
> confidence.

Indeed.  Thank you for checking.

> What do you think?

It would be nice if it turned out that I’m wrong about 4.1 being needed
for older versions of Libreboot.  That’s my only objection to removing
it, but since that can be fixed by upgrading to a more recent Libreboot
(although that may be messy) I think it’s okay to remove it.

-- 
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

  parent reply	other threads:[~2017-06-08 14:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-04  6:11 Any objections to removing linux-libre@4.1? Mark H Weaver
2017-06-04 16:31 ` Leo Famulari
2017-06-04 19:54   ` Mark H Weaver
2017-06-04 21:47   ` Mark H Weaver
2017-06-05 21:46     ` Leo Famulari
2017-06-06  0:59       ` Mark H Weaver
2017-06-04 21:19 ` Ludovic Courtès
2017-06-08 14:33 ` Ricardo Wurmus [this message]
2017-06-09 16:50   ` Mark H Weaver

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=87y3t2eeh7.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.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).