From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:42989) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jL3C8-00055O-VD for guix-patches@gnu.org; Sun, 05 Apr 2020 07:12:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jL3C8-0002eI-5E for guix-patches@gnu.org; Sun, 05 Apr 2020 07:12:04 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:33733) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jL3C7-0002d1-Lj for guix-patches@gnu.org; Sun, 05 Apr 2020 07:12:04 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jL3C6-0003Cu-HD for guix-patches@gnu.org; Sun, 05 Apr 2020 07:12:02 -0400 Subject: [bug#40274] [PATCH v7 1/2] services: Allow modprobe to use "/etc/modprobe.d". Resent-Message-ID: Date: Sun, 5 Apr 2020 13:11:48 +0200 From: Danny Milosavljevic Message-ID: <20200405131148.2eab72fb@scratchpost.org> In-Reply-To: <20200405052803.15711-2-brice@waegenei.re> References: <20200328135908.2540-1-brice@waegenei.re> <20200405052803.15711-1-brice@waegenei.re> <20200405052803.15711-2-brice@waegenei.re> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/yg6N4F6EwSLCRhKytmYze42"; protocol="application/pgp-signature"; micalg=pgp-sha256 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: Brice Waegeneire Cc: 40274@debbugs.gnu.org --Sig_/yg6N4F6EwSLCRhKytmYze42 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Pushed to guix master as commit 8c88e242292db9b35b4ae6ad788a0f8f3c94bb53. I think core-updates will be merged to master pretty soon anyway, but the question is whether we want to update it in core-updates before that, given how many dependencies that has (WTF! What's up with that?). --Sig_/yg6N4F6EwSLCRhKytmYze42 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAl6JvPQACgkQ5xo1VCww uqWImAf8CLubE2tYDe0XbISiOgoGL4mLXVf9uhGalkJgQQ/MJdtgXEG21bJCOl5t FCbXAsTyY+3BE0D+W1cSS/l9wIV+DoR5u4WWLrZIoMYjf2M33ixKC/1mKqeCQzdH 8FXMjUEsz8fyAsOwhww+Myio9nS+xRd3rHK4jDjGQ8/Ct1cBujLoG1VZ9stLwhpg 3cnz0KFDVsfiFcJ2HFjK6dVDFuH3GmnSlaR/+dAQW5LqhWr1FE1IcOGJB1XtWClN XpVqq6I6wDhQN1/M2PWCPneDRxPnc9o2+rTqP/FVK6wJTYLGrccGoLskTQ9fjPOE L6GKapURaO33i9n4fTAPIupEGPvaKw== =qjWF -----END PGP SIGNATURE----- --Sig_/yg6N4F6EwSLCRhKytmYze42--