all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: myglc2 <myglc2@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: Guix-devel <guix-devel@gnu.org>, 29072@debbugs.gnu.org
Subject: bug#29072: The usability of Guix configurations
Date: Mon, 06 Nov 2017 20:56:48 -0500	[thread overview]
Message-ID: <86o9oex34v.fsf__33293.8428655781$1510019835$gmane$org@gmail.com> (raw)
In-Reply-To: <20171106221621.GA2534@jasmine.lan> (Leo Famulari's message of "Mon, 6 Nov 2017 17:16:21 -0500")

Please note: these replies are separated by topics in an effort to make the
threads more topical ...

On 11/06/2017 at 17:16 Leo Famulari writes:

> On Mon, Nov 06, 2017 at 03:12:11PM -0500, myglc2 wrote:
[...]
>> Guix config errors are reported as raw scheme errors which are not
>> user-friendly, except, perhaps, to guile users ;-) Could we improve this
>> situation by adding config troubleshooting guidance to the doc?
>
> Yes, we do try to add helpful error messages, although obviously there
> is a lot more work to be done.

I didn't mean this point critically. Rather as a statement of fact. When
I said ...

>> Could we improve this situation by adding config troubleshooting
>> guidance to the doc?

... I was thinking something like ...

vvvvvvvvvvvvvvvvvv

Troubleshooting your config file:

If you get an error like:

ice-9/boot-9.scm:[...] no code for module (gnu packages <package name>)

You have either specified a package name that does not exist, or your
(use-package-modules <package module names>) does not contain the name
of a package module that contains the definition of <package name>.

You can determine which, if any, module contains a package definition by
yada yada yada

^^^^^^^^^^^^^^^^^^

... thinking that then there would be a search hit in the doc for 'no
code for module' which might enable some users to understand what they
are doing wrong.

WDYT? - George

  parent reply	other threads:[~2017-11-07  1:57 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-06 20:12 The usability of Guix configurations myglc2
2017-11-06 22:16 ` bug#29072: " Leo Famulari
2017-11-06 22:16 ` Leo Famulari
2017-11-06 23:26   ` bug#29072: " myglc2
2017-11-06 23:26   ` myglc2
2017-11-07  1:56   ` myglc2
2017-11-07 11:05     ` julien lepiller
2017-11-07 12:52       ` Hartmut Goebel
2017-11-07 13:13         ` julien lepiller
2017-11-07 14:11           ` myglc2
2017-11-07 14:52             ` julien lepiller
2017-11-07 15:59               ` myglc2
2017-11-07 16:25                 ` [PATCH] " julien lepiller
     [not found]                   ` <867ev2t13i.fsf@gmail.com>
2017-11-07 21:27                     ` Julien Lepiller
2017-11-07 22:56                       ` myglc2
2017-11-07 22:47                   ` Reporting module errors Ludovic Courtès
2017-11-08  1:26                     ` myglc2
2017-11-08 10:52                     ` Hartmut Goebel
2017-11-08 14:02                       ` Ludovic Courtès
2017-11-08 13:09                     ` [PATCH 0/6] Error reporting and hints for missing modules Ludovic Courtès
2017-11-08 13:09                       ` [PATCH 1/6] ui: Introduce (guix i18n) Ludovic Courtès
2017-11-08 13:09                       ` [PATCH 2/6] ui: Define and honor '&error-location' and '&fix-hint' conditions Ludovic Courtès
2017-11-08 13:09                       ` [PATCH 3/6] services: 'fold-service-types' honors its seed Ludovic Courtès
2017-11-08 13:09                       ` [PATCH 4/6] services: 'fold-service-types' includes (gnu services) Ludovic Courtès
2017-11-08 13:09                       ` [PATCH 5/6] services: Add 'lookup-service-types' Ludovic Courtès
2017-11-08 13:09                       ` [PATCH 6/6] gnu: Improve error reporting of the use-.*modules macros Ludovic Courtès
2017-11-11  2:02                         ` Chris Marusich
2017-11-11 13:56                           ` Ludovic Courtès
2017-11-11 17:00                             ` Chris Marusich
2017-11-08 15:33                       ` [PATCH 0/6] Error reporting and hints for missing modules julien lepiller
2017-11-08 17:42                         ` myglc2
2017-11-08 19:07                           ` myglc2
2017-11-08 21:42                             ` Ludovic Courtès
2017-11-09 23:04                             ` Ludovic Courtès
2017-11-10 14:47                               ` myglc2
2017-11-10 23:01                                 ` Julien Lepiller
2017-11-11 22:00                                   ` Ludovic Courtès
2017-11-11 22:02                                 ` Ludovic Courtès
2017-11-14  1:12                                   ` myglc2
2017-11-30 10:44                                     ` Ludovic Courtès
2017-11-07 14:45           ` The usability of Guix configurations Hartmut Goebel
2017-11-07  1:56   ` myglc2 [this message]
2017-11-07  2:30   ` bug#29072: " myglc2
2017-11-07  2:30   ` myglc2
2017-11-07  3:03     ` myglc2
2017-11-07  2:59   ` myglc2
2017-11-07 20:54   ` myglc2
2017-11-07 10:23 ` bug#29072: " Ludovic Courtès
2017-11-07 10:23 ` Ludovic Courtès
2017-11-08 19:40   ` myglc2
  -- strict thread matches above, loose matches on Subject: below --
2017-10-30 20:34 bug#29072: guix system: error: qemu-CVE-2017-7493.patch: patch not found myglc2
2017-11-06 20:12 ` bug#29072: The usability of Guix configurations myglc2

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='86o9oex34v.fsf__33293.8428655781$1510019835$gmane$org@gmail.com' \
    --to=myglc2@gmail.com \
    --cc=29072@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.