From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56385) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gLuvj-0007mJ-0y for guix-patches@gnu.org; Sun, 11 Nov 2018 13:57:58 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gLuhK-0007Du-Ew for guix-patches@gnu.org; Sun, 11 Nov 2018 13:43:07 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:42457) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gLuhK-0007Dk-AW for guix-patches@gnu.org; Sun, 11 Nov 2018 13:43:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gLuhK-0003El-2Q for guix-patches@gnu.org; Sun, 11 Nov 2018 13:43:02 -0500 Subject: [bug#33329] [PATCH] gnu: Deprecate linux-module shpchp and tell user to remove it. Resent-Message-ID: References: <87h8jbang2.fsf@elephly.net> <01fa8c80-c57c-f73a-cec1-af91cacb58bf@riseup.net> <290b28ec-cd1e-e5e8-275e-133771c7d4f3@riseup.net> <87lg60va39.fsf@gnu.org> <87muqglbak.fsf@posteo.net> <87lg5zu9ws.fsf@gnu.org> From: swedebugia Message-ID: Date: Sun, 11 Nov 2018 19:42:13 +0100 MIME-Version: 1.0 In-Reply-To: <87lg5zu9ws.fsf@gnu.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: rekado@elephly.net, 33329@debbugs.gnu.org On 2018-11-11 12:32, Ludovic Courtès wrote: >> swedebugia skribis: snip >> Ok. Would my patch have worked anyway? > > I spotted a typo: (eqv? (missing 'shpchp)) is wrong because ‘eqv?’ > should take two arguments and ‘missing’ is not a procedure. Ok. Thanks for taking your time. > > Apart from this the patch could have worked I guess. > >> So where would that error message be produced? >> In gnu/build/linux-modules? load-linux-modules? > > An error message is produced while building the initrd; see commit > 4db7a9dc663c5b26e45ec35538bf68ff87acdf7b. Good, I had not seen that. > > For now, what about closing this issue and opening a new one when we > have an idea on how to improve on this? Fine with me :) -- Cheers Swedebugia