bug#66786: Failed to install

[Caleb Herbert]

The dump was uploaded as installer-dump-c4fd6109. Please report it by
email to bug-guix@gnu.org.

bug#66662: References to ungrafted glibc retained

[Ludovic Courtès]

Ludovic Courtès  skribis:

> As discussed while reviewing the now-applied glibc replacement at
> , I stumbled upon a case where a
> package still refers to a ungrafted glibc in addition to the grafted
> one:
>
> $ guix gc -R $(guix build libreoffice) | grep glibc-2.35
> /gnu/store/gsjczqir1wbz8p770zndrpw4rnppmxi3-glibc-2.35
> /gnu/store/ln6hxqjvz6m9gdd9s97pivlqck7hzs99-glibc-2.35
> $ guix build -e '(@@ (gnu packages commencement) glibc-final)'
> /gnu/store/gd0x2az3a0sgj5aa9fbv201g7wwfj5m7-glibc-2.35-debug
> /gnu/store/ln6hxqjvz6m9gdd9s97pivlqck7hzs99-glibc-2.35
> /gnu/store/i2g0is6wjq3ccs6m1l6w9mhf44k4042h-glibc-2.35-static
> $ guix build -e '(@@ (gnu packages commencement) glibc-final)' --no-grafts
> /gnu/store/0lzva77yj6hddmhasia65krknyi8kxsg-glibc-2.35-debug
> /gnu/store/gsjczqir1wbz8p770zndrpw4rnppmxi3-glibc-2.35
> /gnu/store/l0yryi5jsa1grnvw01c9nkz9c81cv224-glibc-2.35-static
> $ guix describe
> Generation 277  Oct 16 2023 23:15:43(current)
>   guix b437896
> repository URL: https://git.savannah.gnu.org/git/guix.git
> branch: master
> commit: b437896e87a51cc610388d4c462893652dd773e6
>
>
> The path to the ungrafted libc goes like this:
>
> $ guix graph --path -t references $(guix build libreoffice) 
> /gnu/store/gsjczqir1wbz8p770zndrpw4rnppmxi3-glibc-2.35
> /gnu/store/n8y9jk8wnvxxg54g19ds0jf5agiv5vs2-libreoffice-7.5.4.2
> /gnu/store/y392yldk4pbk4z5q587bz5n61hzbcf4g-mariadb-10.10.2-dev
> /gnu/store/cilkyfnc5fxmpviyypci3d2881ik3nih-mariadb-10.10.2-lib
> /gnu/store/gsjczqir1wbz8p770zndrpw4rnppmxi3-glibc-2.35

Fixed in 67effc1560fc175dfbcb58ef5b965b08b3942d6c, which actually
removes a few lines of code in grafts.scm.

Ludo’.

bug#65225: [bug#66640] [PATCH 0/2] Build profile hooks for the right system

[Ludovic Courtès]

Hi,

Simon Tournier  skribis:

>  ("/gnu/store/zb3vrbwv8qx9430n839ljbalnik8019g-guile-3.0.9.drv"
>   "x86_64-linux"))
>
> Therefore, it seems fixing the issue.  All the x86_64-linux above are
> turned as riscv64-linux.  However, still a naive question:
>
> Why ’guile’ is not?  Is it expected?

Oh, that’s another bug, this one in ‘guix shell’ (missing argument for
‘package-derivation’).

I pushed this:

  344e39c928 profiles: Hooks honor the #:system parameter of 
‘profile-derivation’.
  9d4b720e1f packages: Add ‘system’ parameter for ‘set-guile-for-build’.
  b3ec2a0d37 environment: Honor ‘-s’ for guile-for-build.

Thanks for reviewing and reporting the issue!

Ludo’.

bug#66659: (home-)on-first-login script broken when no gexps are added

[Ludovic Courtès]

Hi,

Nils Landt  skribis:

> I'm afraid this did not fix the issue. It results in
> (when (claim-first-run flag-file-path) (begin))
>
> which leads to the new error message "Syntax error:
> /home/nl/.guix-home/on-first-login:3:1272: sequence of zero expressions in 
> form (begin)"

Oops, my bad.  (I did check at the REPL that (begin) was fine but forgot
that I was checking the top-level ‘begin’ form, which is not the same as
the sequencing ‘begin’ form…)

Rostislav Svoboda  skribis:

> Adding *unspecified* works for me. I.e.:
>
> (when (claim-first-run flag-file-path)
>   ;; GEXPS can be empty, hence 'begin *unspecified*'. Having just
>   ;; 'begin' without '*unspecified*' leads to
>   ;; "Syntax error: ... sequence of zero expressions in form (begin)"
>   (begin *unspecified* #$@gexps))
>
> The patch is in the attachment.

Thanks Rostislav and everyone, and apologies for not replying earlier!

Ludo’.

bug#66746: LUKS password prompt invisible, prompts twice

[Saku Laesvuori via Bug reports for GNU Guix]

> Hi Caleb,
> 
> Caleb Herbert  writes:
> 
> > Hardware: ThinkPad X200
> > Firmware: Libreboot 2016
> > OS: Guix System
> >
> > Expected behavior:
> > Password prompt. Enter LUKS passphrase. Log into computer.
> >
> > Actual behavior:
> > Password prompt. Enter LUKS passphrase. Select boot option from GRUB menu. 
> > Hangs, no password prompt. Enter passphrase (again) anyway: Boots normally.
> 
> I think this is a combination of two things: first, we currently need to
> unlock the drive once for GRUB, and then once when Linux boots, hence
> the two password prompts.  This is a known limitation, but the usual
> workaround of adding a keyfile to the initrd wouldn't work in our case
> for security reasons: the keyfile would end up in the store and be
> world-readable, a disaster.

I believe a patch[1] enabling this is waiting for a review.

[1]: https://issues.guix.gnu.org/65002


signature.asc
Description: PGP signature

bug#66777: program-file silently corrupts expressions with non-ascii characters

[Tomas Volf]

Hello,

when trying to create an executable script using `program-file', I realized it
silently corrupts expressions with non-ascii characters.  Minimal reproduction I
did put together is:

scheme@(guix-user)> ,use (guix)
scheme@(guix-user)> ,build (program-file "foo" '(λ))
$1 = "/gnu/store/im07w0ilskfycpkwid3n7s80hdv263cn-foo"
scheme@(guix-user)> (call-with-input-file $1 read)
;;; :3:22: warning: possibly unbound variable `$1'
$2 = (?)

Notice that $2 is (?) instead of the expected (λ).  If there is a technical
reason why this cannot be handled correctly, it would be great if it at least
failed with an error instead of a silent corruption.

Have a nice day,
Tomas Volf

-- 
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.


signature.asc
Description: PGP signature

bug#66746: LUKS password prompt invisible, prompts twice

[Josselin Poiret via Bug reports for GNU Guix]

Hi Caleb,

Caleb Herbert  writes:

> Hardware: ThinkPad X200
> Firmware: Libreboot 2016
> OS: Guix System
>
> Expected behavior:
> Password prompt. Enter LUKS passphrase. Log into computer.
>
> Actual behavior:
> Password prompt. Enter LUKS passphrase. Select boot option from GRUB menu. 
> Hangs, no password prompt. Enter passphrase (again) anyway: Boots normally.

I think this is a combination of two things: first, we currently need to
unlock the drive once for GRUB, and then once when Linux boots, hence
the two password prompts.  This is a known limitation, but the usual
workaround of adding a keyfile to the initrd wouldn't work in our case
for security reasons: the keyfile would end up in the store and be
world-readable, a disaster.

Regarding the second prompt being invisible, I think it might be related
to the framebuffer initialization for Libreboot since there have been
lots of reports about this.  I don't know anything myself, but maybe
someone else could chime in?

Best,
-- 
Josselin Poiret


signature.asc
Description: PGP signature

bug#66659: (home-)on-first-login script broken when no gexps are added

[Clément Lassieur]

On Tue, Oct 24 2023, Rostislav Svoboda wrote:

>> > I've just pushed something similar to what you provided, Carlo, in
>> > commit e098ba2f499bbddfea50c85058e4077e39b85513.
>> >
>> > We should be good now.
>>
>> I'm afraid this did not fix the issue. It results in
>> (when (claim-first-run flag-file-path) (begin))
>>
>> which leads to the new error message "Syntax error:
>> /home/nl/.guix-home/on-first-login:3:1272: sequence of zero expressions in 
>> form (begin)"
>
> Adding *unspecified* works for me. I.e.:
>
> (when (claim-first-run flag-file-path)
>   ;; GEXPS can be empty, hence 'begin *unspecified*'. Having just
>   ;; 'begin' without '*unspecified*' leads to
>   ;; "Syntax error: ... sequence of zero expressions in form (begin)"
>   (begin *unspecified* #$@gexps))
>
> The patch is in the attachment.
>
> Cheers Bost

Applied as 2de30042674197fe451c220745186e36465d06e2, thanks!
Clément

bug#66757: missing INFOPATH for some packages (Git, Coreutils)

[Simon Tournier]

Hi,

On Fri, 27 Oct 2023 at 02:32, John Kehayias via Bug reports for GNU Guix 
 wrote:

> So I think it is just that you didn't have the "consumer" of the
> search-path, the package info-reader, in the profile. That seems like
> the expected functionality of search-path but maybe I'm missing
> something? Not closing in case it is me not you :)

Aah… yes!  Thanks.

Well, I have various profiles, for instance, coreutils is in one profile
and info-reader is in another.  That’s why it appears to me unexpected.

> (as an aside, I never remember the package for the same thing with
> man...)

That’s man-db. :-)

Well I am closing as ’notabug’; although when using Guix as environment
manager on foreign distro in some scientific context, it means that I
have to pass info-reader and man-db to all my profiles around when
working on some specific project.

Cheers,
simon

bug#66762: emacs-ess test fails

[Simon Tournier]

Hi,

On Thu, 26 Oct 2023 at 15:17, Kyle Andrews  wrote:
> The emacs-ess package no longer install as of guix revision
> 33f5b74. It's dependency emacs-julia-mode fails to build.
>
> $ guix shell --keep-failed --pure emacs emacs-julia-mode
>
> According to the build log, the test julia--test-end-of-defun-nested-2
> fails.

Reported upstream:
https://github.com/JuliaEditorSupport/julia-emacs/issues/199

It comes from a discrepancy introduced by Emacs 29; also reported:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=66763

Well, I fixed the build of emacs-julia-mode.  See attached.

But emacs-ess is not passing.  I have updated ESS to the most recent
revision, added phases for skipping the tests requiring network but it
still fails:

--8<---cut here---start->8---
Ran 187 tests, 176 results as expected, 6 unexpected, 5 skipped
(2023-10-27 01:12:40+, 17.661319 sec) 2 expected failures

6 unexpected results:
   FAILED ess-eval-line-test FAILED ess-eval-region-test FAILED
   ess-mock-remote-process FAILED ess-r-load-ESSR-github-fetch-no FAILED
   ess-set-working-directory-test FAILED ess-test-r-startup-directory
--8<---cut here---end--->8---

To be continued…

Cheers, simon

>From 5bd2f8c9b6a8065890b4ae38ec78657bcb7ef9a7 Mon Sep 17 00:00:00 2001
Message-ID: <5bd2f8c9b6a8065890b4ae38ec78657bcb7ef9a7.1698398428.git.zimon.touto...@gmail.com>
From: Simon Tournier 
Date: Fri, 27 Oct 2023 01:41:26 +0200
Subject: [PATCH 1/2] gnu: emacs-julia-mode: Exclude failing test introduced by
 Emacs 29.

* gnu/packages/emacs-xyz.scm (emacs-julia-mode)[arguments]: Add phases before
check that marks the test as expected failed.

Change-Id: I1da1077a7e7e077392458243b2d3cd44592ebd45
---
 gnu/packages/emacs-xyz.scm | 14 --
 1 file changed, 12 insertions(+), 2 deletions(-)

diff --git a/gnu/packages/emacs-xyz.scm b/gnu/packages/emacs-xyz.scm
index 0bf3096216..7511a2de21 100644
--- a/gnu/packages/emacs-xyz.scm
+++ b/gnu/packages/emacs-xyz.scm
@@ -95,7 +95,7 @@
 ;;; Copyright © 2021 Alexey Abramov 
 ;;; Copyright © 2021 Xinglu Chen 
 ;;; Copyright © 2021, 2022 Stefan Reichör 
-;;; Copyright © 2021, 2022 Simon Tournier 
+;;; Copyright © 2021, 2022, 2023 Simon Tournier 
 ;;; Copyright © 2021 Eugene Klimov 
 ;;; Copyright © 2021 Zheng Junjie <873216...@qq.com>
 ;;; Copyright © 2021 David Dashyan 
@@ -13550,7 +13550,17 @@ (define-public emacs-julia-mode
`(#:tests? #t
  #:test-command '("emacs" "--batch"
   "-l" "julia-mode-tests.el"
-  "-f" "ert-run-tests-batch-and-exit")))
+  "-f" "ert-run-tests-batch-and-exit")
+ #:phases
+ (modify-phases %standard-phases
+   (add-before 'check 'fix-test
+ (lambda _
+   (substitute* "julia-mode-tests.el"
+ ;; The test started failing with Emacs 29; see
+ ;; 
+ ;; and discrepancy reported .
+ (("julia--test-end-of-defun-nested-2.*" all)
+  (string-append all "  :expected-result :failed\n"
   (home-page "https://github.com/JuliaEditorSupport/julia-emacs;)
   (synopsis "Major mode for Julia")
   (description "This Emacs package provides a mode for the Julia

base-commit: 6d7e181ba18d11c92409a93936025fb46b9c8171
prerequisite-patch-id: b9d5f8d81be6974fb52062c781924fb5387d4602
prerequisite-patch-id: bee3c38a1dbcf56e8c3d58891dc317d8a5901be8
prerequisite-patch-id: 08e88430d6fdc51aa4afa2891fddae9865a64a7c
prerequisite-patch-id: f276d7bebe3fdcda36e27fd027fd75d1c2e6369c
prerequisite-patch-id: ef6db31909314fd83b53b6e610547064a14d9551
prerequisite-patch-id: 4311408226f9b085a893bc9c32cce00611ba8401
-- 
2.41.0

>From 9b8715d29fc1543b9d624f26e8946c5a919b4946 Mon Sep 17 00:00:00 2001
Message-ID: <9b8715d29fc1543b9d624f26e8946c5a919b4946.1698398428.git.zimon.touto...@gmail.com>
In-Reply-To: <5bd2f8c9b6a8065890b4ae38ec78657bcb7ef9a7.1698398428.git.zimon.touto...@gmail.com>
References: <5bd2f8c9b6a8065890b4ae38ec78657bcb7ef9a7.1698398428.git.zimon.touto...@gmail.com>
From: Simon Tournier 
Date: Fri, 27 Oct 2023 01:51:18 +0200
Subject: [PATCH 2/2] gnu: emacs-julia-mode: Update to 0.4-0.7a8c868.

* gnu/packages/emacs-xyz.scm (emacs-julia-mode): Update to 0.4-0.7a8c868.
[arguments]: Use G-exp.

Change-Id: I3d06dbe824ce989400d801118e8bca496ae4b3e2
---
 gnu/packages/emacs-xyz.scm | 40 +-
 1 file changed, 22 insertions(+), 18 deletions(-)

diff --git a/gnu/packages/emacs-xyz.scm b/gnu/packages/emacs-xyz.scm
index 7511a2de21..471d938910 100644
--- a/gnu/packages/emacs-xyz.scm
+++ b/gnu/packages/emacs-xyz.scm
@@ -13532,40 +13532,44 @@ (define-public emacs-eprime
   (license license:gpl3+
 
 (define-public emacs-julia-mode
+  ;; Last release was in March 2020.
+  (let ((commit 

bug#33845: test of hslua fail on i686

[Simon Tournier]

Hi,

This bug #33845 []1 is old,

https://issues.guix.gnu.org/issue/33845

is it still accurate?

Pandoc had been changed since then.  CI still says it fails:

https://ci.guix.gnu.org/build/1610305/details
https://ci.guix.gnu.org/build/1610922/details

but it seems about dependency.  Do we keep this bug still open?


On Sun, 23 Dec 2018 at 01:20, swedebu...@riseup.net wrote:
> This is a dep of pandoc.
>
> sdb@antelope ~/Desktop$ guix --version
> guix (GNU Guix) 0.16.0-5.5de5f81
>
> installed from git on
> sdb@antelope ~$ cd ~/src/guix && git log |head -1
> commit d15211c9b5b46b96c5b658329624942b6ff5c917
>
>
> starting phase `check'
> running "runhaskell Setup.hs" with command "test" and parameters ()
> Running 1 test suites...
> Test suite test-hslua: RUNNING...
> hslua
>   Haskell version of the C API

[...]

> 8 out of 113 tests failed (1.30s)
> Test suite test-hslua: FAIL
> Test suite logged to: dist/test/hslua-0.9.5.2-test-hslua.log
> 0 of 1 test suites (0 of 1 test cases) passed.
> Backtrace:
>5 (primitive-load "/gnu/store/8m1laknzqkxb8swcxlq5vj4m717…")
> In ice-9/eval.scm:
>191:35  4 (_ _)
> In srfi/srfi-1.scm:
>863:16  3 (every1 # …)
> In
> /gnu/store/n944icv9i660rrirykgv1yrvyazpkjrz-module-import/guix/build/gnu-build-system.scm:
>799:28  2 (_ _)
> In
> /gnu/store/n944icv9i660rrirykgv1yrvyazpkjrz-module-import/guix/build/haskell-build-system.scm:
> 258:6  1 (check #:tests? _ #:test-target _)
> In
> /gnu/store/n944icv9i660rrirykgv1yrvyazpkjrz-module-import/guix/build/utils.scm:
> 616:6  0 (invoke _ . _)
>
> /gnu/store/n944icv9i660rrirykgv1yrvyazpkjrz-module-import/guix/build/utils.scm:616:6:
> In procedure invoke:
> Throw to key `srfi-34' with args `(# "runhaskell" arguments: ("Setup.hs" "test") exit-status: 1 term-signal:
> #f stop-signal: #f] 80aafc0>)'.
> note: keeping build directory `/tmp/guix-build-ghc-hslua-0.9.5.2.drv-0'
> builder for
> `/gnu/store/d6ysq3vrm3ymjvwbivxja456zwhl74n0-ghc-hslua-0.9.5.2.drv'
> failed with exit code 1
> build of
> /gnu/store/d6ysq3vrm3ymjvwbivxja456zwhl74n0-ghc-hslua-0.9.5.2.drv failed
> View build log at
> '/var/log/guix/drvs/d6/ysq3vrm3ymjvwbivxja456zwhl74n0-ghc-hslua-0.9.5.2.drv.bz2'.
> guix build: error: build failed: build of
> `/gnu/store/d6ysq3vrm3ymjvwbivxja456zwhl74n0-ghc-hslua-0.9.5.2.drv'
> failed


Cheers,
simon