Report forwarded
to bug-guix@gnu.org: bug#76040; Package guix.
(Tue, 04 Feb 2025 04:56:01 GMT) (full text, mbox, link).
Acknowledgement sent
to "nomike (they/them)" <nomike@nomike.com>:
New bug report received and forwarded. Copy sent to bug-guix@gnu.org.
(Tue, 04 Feb 2025 04:56:01 GMT) (full text, mbox, link).
The logging for guile errors is not sufficient when running `guix home
reconfigure`.
If you run the small self-contained example I've attached, the following
warning will be printed to the terminal:
> guix home: warning: unknown keyword or bad argument
There is an error in `prusa-slicer.scm`. If you rename it to
`prusa-slicer.scm~`, the warning is gone.
The bug here is, that the error message is very generic and doesn't tell
me what's going on. Via trial and error I can try renaming scheme files,
comment out sections of code, etc. and eventually track down the area of
the issue and then maybe spot the error there, but IMHO guix should
print more info to the terminal.
Something like this for example:
> guix home: warning: unknown keyword or bad argument 'foobar' in
./prusa-slicer.scm:12
would be much more helpful. Especially for noobs like me.
PS: This is not about the issue with `prusa-slicer.scm`, I know it's
wrong and bullshit ;-).
Severity set to 'important' from 'normal'
Request was from Ludovic Courtès <ludo@gnu.org>
to control@debbugs.gnu.org.
(Wed, 05 Feb 2025 10:14:02 GMT) (full text, mbox, link).
Debbugs is free software and licensed under the terms of the
GNU Public License version 2. The current version can be
obtained from https://bugs.debian.org/debbugs-source/.