unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 32593-done@debbugs.gnu.org
Subject: bug#32593: bad error message when kernel module does not exist
Date: Sun, 02 Sep 2018 15:48:12 +0200	[thread overview]
Message-ID: <87d0twau3n.fsf@gnu.org> (raw)
In-Reply-To: <87ftyvandx.fsf@elephly.net> (Ricardo Wurmus's message of "Thu, 30 Aug 2018 17:24:10 +0200")

Hello,

Ricardo Wurmus <rekado@elephly.net> skribis:

> When a system is built that requests a kernel module that does not
> exists, this is the error message a user will see:
>
> Backtrace:
>            8 (primitive-load "/gnu/store/vz7ci9rh483f2zps2cl174rd91b?")
> In ice-9/eval.scm:
>     619:8  7 (_ #f)
>    626:19  6 (_ #<directory (guile-user) 7cf140>)
>     159:9  5 (_ _)
> In gnu/build/linux-modules.scm:
>    184:47  4 (recursive-module-dependencies _ #:lookup-module _)
>     98:14  3 (module-dependencies _)
>     85:18  2 (modinfo-section-contents _)
> In ice-9/ports.scm:
>    439:11  1 (call-with-input-file #f #<procedure get-bytevector-al?> ?)
> In unknown file:
>            0 (open-file #f "r" #:encoding #f #:guess-encoding #f)
>
> ERROR: In procedure open-file:
> Wrong type (expecting string): #f
> builder for `/gnu/store/0ahsvp7wx52zzh1rywbdbq78llcwb7id-linux-modules.drv' failed with exit code 1

This project is incredible: the bug was fixed even before you had
reported it, in commit 4db7a9dc663c5b26e45ec35538bf68ff87acdf7b.  :-)

You still get a backtrace, but at least the error message is somewhat
clearer.  (Should we do away with the backtrace?)

Ludo’.

      reply	other threads:[~2018-09-02 13:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-30 15:24 bug#32593: bad error message when kernel module does not exist Ricardo Wurmus
2018-09-02 13:48 ` 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=87d0twau3n.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=32593-done@debbugs.gnu.org \
    --cc=rekado@elephly.net \
    /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).