unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Adam Van Ymeren <adam@vany.ca>
Cc: 30847@debbugs.gnu.org
Subject: bug#30847: Cannot upgrade GuixSD due to check-device-initrd-modules
Date: Tue, 27 Mar 2018 15:19:46 +0200	[thread overview]
Message-ID: <87605hwt8t.fsf@gnu.org> (raw)
In-Reply-To: <87fu4wuhyz.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 19 Mar 2018 17:51:16 +0100")

Ping!  :-)

ludo@gnu.org (Ludovic Courtès) skribis:

> Hello Adam,
>
> Adam Van Ymeren <adam@vany.ca> skribis:
>
>> My root device is on NVMe.
>>
>> In my current kernel config CONFIG_NVME_CORE is set to a module, which is
>> included in my initrd.
>>
>> However upstream defconfig has been changed to CONFIG_NVME_CORE=y
>
> Out of curiosity, what’s the current and target kernel versions?
>
> Like Danny wrote, ‘check-device-initrd-modules’ can have false positives
> as it is, in which case you have to use ‘--skip-checks’.
>
> We could arrange to not have false positives, but the UX would be a
> little less good because we’d first need to build the target kernel.  So
> I wonder how frequent the situation you experienced is.
>
> Thanks for your report!
>
> Ludo’.

      reply	other threads:[~2018-03-27 13:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-18 16:32 bug#30847: Cannot upgrade GuixSD due to check-device-initrd-modules Adam Van Ymeren
2018-03-18 22:33 ` Danny Milosavljevic
2018-03-19 16:51 ` Ludovic Courtès
2018-03-27 13:19   ` Ludovic Courtès [this message]

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=87605hwt8t.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=30847@debbugs.gnu.org \
    --cc=adam@vany.ca \
    /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).