rednotebook.x86_64-linux 2.22 falis wrap-library-paths phase

  • Open
  • quality assurance status badge
Details
One participant
  • Maxim Cournoyer
Owner
unassigned
Submitted by
Maxim Cournoyer
Severity
normal
M
M
Maxim Cournoyer wrote on 30 Dec 2023 03:14
(name . bug-guix)(address . bug-guix@gnu.org)
871qb4tp0x.fsf@gmail.com
Hi,

cuirass@gnu.org (Cuirass) writes:

Toggle quote (6 lines)
> <p>The build <b>rednotebook.x86_64-linux</b> for specification <b>master</b> is broken. You
> can find the detailed information about this build <a
> href="https://ci.guix.gnu.org/build/3100837/details">here</a>.</p>
>
> https://ci.guix.gnu.org/build/3100837/details

The problem from the log:

Toggle snippet (29 lines)
starting phase `wrap-with-library-paths'
error: in phase 'wrap-with-library-paths': uncaught exception:
wrong-type-arg "string-append" "Wrong type (expecting ~A): ~S" ("string" #f) (#f)
phase `wrap-with-library-paths' failed after 0.0 seconds
Backtrace:
9 (primitive-load "/gnu/store/agiwn3qhkh65y37n7984nkkwyb0…")
In guix/build/gnu-build-system.scm:
908:2 8 (gnu-build #:source _ #:outputs _ #:inputs _ #:phases . #)
In ice-9/boot-9.scm:
1752:10 7 (with-exception-handler _ _ #:unwind? _ # _)
In srfi/srfi-1.scm:
634:9 6 (for-each #<procedure 7fffeef6d0c0 at guix/build/gnu-b…> …)
In ice-9/boot-9.scm:
1752:10 5 (with-exception-handler _ _ #:unwind? _ # _)
In guix/build/gnu-build-system.scm:
929:23 4 (_)
In ice-9/eval.scm:
304:50 3 (_ #(#(#<directory (guile-user) 7ffff77f7c80>) (# # …) …))
In unknown file:
2 (string-append #f "/lib")
In ice-9/boot-9.scm:
1685:16 1 (raise-exception _ #:continuable? _)
1685:16 0 (raise-exception _ #:continuable? _)

ice-9/boot-9.scm:1685:16: In procedure raise-exception:
In procedure string-append: Wrong type (expecting string): #f
builder for `/gnu/store/vck7l65hqxgfc7by81r9h27qbnjiiapa-rednotebook-2.22.drv' failed with exit code 1

--
Thanks,
Maxim
?
Your comment

Commenting via the web interface is currently disabled.

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

To respond to this issue using the mumi CLI, first switch to it
mumi current 68128
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