From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: Re: 01/01: gnu: Use make-linux-libre-headers. Date: Thu, 30 May 2019 17:35:44 -0400 Message-ID: <87ftovpqus.fsf@netris.org> References: <20190529163123.3417.15650@vcs0.savannah.gnu.org> <20190529163123.ECCE2209A5@vcs0.savannah.gnu.org> <87zhn4pw0z.fsf@netris.org> <20190530103143.08ba1074@scratchpost.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([209.51.188.92]:60681) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hWSkR-0002BF-VT for guix-devel@gnu.org; Thu, 30 May 2019 17:38:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hWSkR-0007Kr-2Y for guix-devel@gnu.org; Thu, 30 May 2019 17:38:07 -0400 Received: from world.peace.net ([64.112.178.59]:47614) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hWSkQ-0006yE-VG for guix-devel@gnu.org; Thu, 30 May 2019 17:38:07 -0400 In-Reply-To: <20190530103143.08ba1074@scratchpost.org> (Danny Milosavljevic's message of "Thu, 30 May 2019 10:31:43 +0200") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Danny Milosavljevic Cc: Carl Dong , guix-devel@gnu.org Hi Danny, Danny Milosavljevic writes: >> 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. > > OK with me to remove. > > The headers were from 4.14.67 (and still are), though. So we'll have > headers which we don't have a Linux kernel for. (Since those change > very rarely, that's not such a big deal) Hmm, I don't understand. What do the 4.14.x headers have to do with 4.15, which is the version I'm suggesting to delete? >> 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. > > It doesn't. I think I messed up the commit *message*, but there is a > definition of linux-libre still (as before). Indeed, you're right about this, my mistake. Thanks, Mark