From: Marius Bakke <mbakke@fastmail.com>
To: Brice Waegeneire <brice@waegenei.re>, 40422@debbugs.gnu.org
Subject: [bug#40422] [PATCH] gnu: kmod: Update to 27.
Date: Sun, 05 Apr 2020 16:45:48 +0200 [thread overview]
Message-ID: <87y2rang83.fsf@devup.no> (raw)
In-Reply-To: <20200404071534.17291-1-brice@waegenei.re>
[-- Attachment #1: Type: text/plain, Size: 828 bytes --]
Brice Waegeneire <brice@waegenei.re> writes:
> * gnu/packages/linux.scm (kmod): Update to 27. Enable tests.
> ---
>
> This patch need to be merge on core-updates because > 2200 packages will need
> to be rebuilt. Without this patch (in particular `--sysconfdir=/etc`) it's
> not possible to pass module arguments to `kernel-module-loader` from
> <https://issues.guix.info/issue/40274>.
As the core-updates branch is frozen right now, could you submit this
patch as a 'kmod/next' variable? See e.g. 'help2man/latest' or
'automake-1.16.2' for inspiration.
After the core-updates merge, we can do a larger 'staging' round that
updates the default 'kmod'.
I wonder if we should patch eudev to use
/run/current-system/profile/bin/ instead of /gnu/store/...kmod/bin so
that we can update kmod without triggering a huge rebuild.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-04-05 14:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-04 7:15 [bug#40422] [PATCH] gnu: kmod: Update to 27 Brice Waegeneire
2020-04-05 14:45 ` Marius Bakke [this message]
2020-04-05 15:57 ` Brice Waegeneire
2020-04-05 22:14 ` Marius Bakke
2020-04-08 7:11 ` [bug#40422] [PATCH v3] " Brice Waegeneire
2020-04-13 11:20 ` Danny Milosavljevic
2020-04-13 13:39 ` Brice Waegeneire
2020-04-21 8:57 ` [bug#40422] [PATCH v4] " Brice Waegeneire
2020-04-13 13:34 ` Brice Waegeneire
2020-04-27 13:51 ` [bug#40422] [PATCH v5] gnu: Update kmod " Brice Waegeneire
2020-05-10 17:22 ` bug#40422: Pushed [PATCH] gnu: kmod: Update " Brice Waegeneire
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=87y2rang83.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=40422@debbugs.gnu.org \
--cc=brice@waegenei.re \
/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).