unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: Carl Dong <accounts@carldong.me>, guix-devel@gnu.org
Subject: Re: 01/01: gnu: Use make-linux-libre-headers.
Date: Wed, 29 May 2019 21:31:45 -0400	[thread overview]
Message-ID: <87zhn4pw0z.fsf@netris.org> (raw)
In-Reply-To: <20190529163123.ECCE2209A5@vcs0.savannah.gnu.org> (guix-commits@gnu.org's message of "Wed, 29 May 2019 12:31:23 -0400 (EDT)")

Hi Danny and Carl,

guix-commits@gnu.org writes:

> dannym pushed a commit to branch master
> in repository guix.
>
> commit a15cee50cebddc665a16b455f44e22dcfb87d57f
> Author: Carl Dong <accounts@carldong.me>
> Date:   Wed May 29 18:04:43 2019 +0200
>
>     gnu: Use make-linux-libre-headers.
>     
>     * gnu/packages/linux.scm (make-linux-libre-headers): New variable.
>     (linux-libre): Rename to...
>     (linux-libre-5.1): ...this.
>     (linux-libre-headers): Rename to...
>     (linux-libre-headers-4.14.67): ...this.
>     (linux-libre-5.1, linux-libre-headers-4.14.67): Use make-linux-libre-headers.
>     (linux-libre-5.1, linux-libre-headers-5.1, linux-libre-headers-4.19,
>     %linux-libre-4.15-version, %linux-libre-4.15-hash, linux-libre-4.15,
>     linux-libre-headers-4.15, linux-libre-headers-4.14): New variables.
>     
>     Signed-off-by: Danny Milosavljevic <dannym@scratchpost.org>

I think we should not add linux-libre-4.15, because that version of
Linux-libre is no longer supported upstream, and therefore will have
well-known security flaws.

Also, this removes the definition of 'linux-libre', which I, for one,
reference from my OS config and maybe others do as well.  Sometimes it's
useful to break compatibility, but in this case I see no reason for it.

Finally, given I've been the de-facto maintainer of our kernel packages
since the early days of Guix, I would have appreciated a heads-up on
these proposed changes and an opportunity to comment before they were
pushed to master.

     Regards,
       Mark

       reply	other threads:[~2019-05-30  1:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190529163123.3417.15650@vcs0.savannah.gnu.org>
     [not found] ` <20190529163123.ECCE2209A5@vcs0.savannah.gnu.org>
2019-05-30  1:31   ` Mark H Weaver [this message]
2019-05-30  2:04     ` 01/01: gnu: Use make-linux-libre-headers Carl Dong
2019-05-30  8:31     ` Danny Milosavljevic
2019-05-30 21:35       ` Mark H Weaver
2019-05-30 22:13         ` Danny Milosavljevic

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=87zhn4pw0z.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=accounts@carldong.me \
    --cc=dannym@scratchpost.org \
    --cc=guix-devel@gnu.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).