build-system-asdf errors if a system name is too short

  • Done
  • quality assurance status badge
Details
2 participants
  • Katherine Cox-Buday
  • Guillaume Le Vaillant
Owner
unassigned
Submitted by
Katherine Cox-Buday
Severity
normal
K
K
Katherine Cox-Buday wrote on 21 May 2020 17:13
(address . bug-guix@gnu.org)
87o8qhb9sk.fsf@gmail.com
#+BEGIN_EXAMPLE
10:06 katco says: guix --version
guix (GNU Guix) c660779722f4130e95cda89c0eb0cff534a89ef2
#+END_EXAMPLE

I am packaging a system called ~sbcl-1am~, and I discovered that unless
I make the package name longer, I receive this cryptic error when
issuing ~guix build -L. sbcl-1am~:

#+BEGIN_EXAMPLE
Backtrace:
1 (primitive-load "/home/katco/.config/guix/current/bin/g…")
In guix/ui.scm:
1936:12 0 (run-guix-command _ . _)

guix/ui.scm:1936:12: In procedure run-guix-command:
Value out of range 0 to 4: 5
#+END_EXAMPLE

--
Katherine
G
G
Guillaume Le Vaillant wrote on 8 May 2021 14:43
(name . Katherine Cox-Buday)(address . cox.katherine.e@gmail.com)(address . 41437-done@debbugs.gnu.org)
87o8dlief3.fsf@kitej
Katherine Cox-Buday <cox.katherine.e@gmail.com> skribis:

Toggle quote (19 lines)
> #+BEGIN_EXAMPLE
> 10:06 katco says: guix --version
> guix (GNU Guix) c660779722f4130e95cda89c0eb0cff534a89ef2
> #+END_EXAMPLE
>
> I am packaging a system called ~sbcl-1am~, and I discovered that unless
> I make the package name longer, I receive this cryptic error when
> issuing ~guix build -L. sbcl-1am~:
>
> #+BEGIN_EXAMPLE
> Backtrace:
> 1 (primitive-load "/home/katco/.config/guix/current/bin/g…")
> In guix/ui.scm:
> 1936:12 0 (run-guix-command _ . _)
>
> guix/ui.scm:1936:12: In procedure run-guix-command:
> Value out of range 0 to 4: 5
> #+END_EXAMPLE

Fixed in 2fa8fd4af59af0de392352915fa50fc21a4cf98a.
Closing.
-----BEGIN PGP SIGNATURE-----

iIUEAREKAC0WIQTLxZxm7Ce5cXlAaz5r6CCK3yH+PwUCYJaHgA8cZ2x2QHBvc3Rl
by5uZXQACgkQa+ggit8h/j+WZgEAlekHs5sCumiwS1dy5BvNppPiII3e4mdF14Ph
Ko32jXoBAJQmFq1FN3WsZ0vr2z952/4TWyQSyYK+UtSgCeSgMBR9
=BOIS
-----END PGP SIGNATURE-----

Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 41437@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 41437
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch