bug#28858: make fails: In procedure allocate-struct: Wrong type argument in position 2: 5

eated make invocation. Martin Castillo [Is it okay to attach logs or should I put them better in the message body?] [env]$ make -j 2 make all-recursive make[1]: Verzeichnis „/home/mcd/guix“ wird betreten Making all in po/guix make[2]: Verzeichnis „/home/mcd/guix/po/guix“ wird betreten make[2]: V

bug#29356: 1 test-suite test fails

Hello, I built guix from 84bd92438. The test suite fails with the attached log. Martin Castillo GNU Guix UNKNOWN: ./test-suite.log # TOTAL: 746 # PASS: 739 # SKIP: 6 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR

bug#29356: 1 test-suite test fails

Hi Ludo’, On 20.11.2017 10:23, Ludovic Courtès wrote: > Could it be that there are stale gnu/packages/qemu.{scm,go} files in the > working tree? > > Thanks in advance, > Ludo’. > yes, there was qemu.go. It works now. What does the apostrophe at the end of your name mean? Martin.

bug#29368: Unreliable failing tests / segfaulting guile

Hi, > It’s seems to be the Guile running ‘list-runtime-roots’ that’s > segfaulting. Could you try running it manually to see what happens? > (The expected behavior is to write a list of store file names on > standard output.) When running in a loop, I see the expected output. However, after a fil

bug#29368: Unreliable failing tests / segfaulting guile

Hi, On 24.11.2017 18:02, Ludovic Courtès wrote: > Hi, > > l...@gnu.org (Ludovic Courtès) skribis: > >> Martin Castillo skribis: >> >>> test-name: derivation-prerequisites-to-build when outputs already present >>> location: /home/mcd/guix/tests/derivati

bug#23274: Misleading error message when running guix-daemon as unprivileged user

Hi, “Address already in use” makes me directly think that there is already another daemon running. Strangely, starting another daemon as root works. It seems to take the socket from the other daemon away. Is this intended? Or can two daemons run in parallel without problems? What is your use case

bug#23274: Misleading error message when running guix-daemon as unprivileged user

Hi, I could have expressed myself more clearly. > “Address already in use” makes me directly think that there is already >another daemon running. This was in response to OP, saying that I don't think that needs to be changed. The rest was about testing it with root and I (half) expected an err

bug#29761: guix gc doesn't error out on false --verify= options

guix gc --verify=foo should maybe error out instead of just ignoring it.

bug#29662: 'guix gc' as user makes system unbootable

I had a similar situation today. guix gc removed the grub background png from the store. the one, that was used by /boot/grub/grub.cfg. the boot menu then had a black and blue background. rebuilding the configuration refetched the background image, but guix gc removed it again. after rebooting and

bug#29662: 'guix gc' as user makes system unbootable

Hi, On 18.12.2017 10:54, Ludovic Courtès wrote: > Hi Martin, > > Martin Castillo skribis: > >> I had a similar situation today. guix gc removed the grub background png >> from the store. the one, that was used by /boot/grub/grub.cfg. the boot >> menu then h

bug#29662: 'guix gc' as user makes system unbootable

Hi, On 18.12.2017 15:31, Ludovic Courtès wrote: > Under what circumstances did you have a system without > /var/guix/gcroots/bootcfg? > I cannot tell. I had some fs errors and run e2fsck several times. Maybe that removed the link? But since then, I had done several reconfigures. I'd expect those

bug#29813: doc: localstatedir is used ambigously

In the documentation, localstatedir is sometimes used as if it was /var and sometimes as /var/guix. examples: the doc page 'the store' contains LOCALSTATEDIR/guix/db. but the doc page for guix-daemon contains LOCALSTATEDIR/daemon-socket/socket

bug#29814: impossible to pass spaces in GUIX_BUILD_OPTIONS

guix/util.scm:(arguments-from-envirenment-variable) uses char-set:graphic to split the string. this makes it impossible to pass spaces in the arguments. This makes it impossible to pass more than one substitute-url via the environment.

bug#29814: impossible to pass spaces in GUIX_BUILD_OPTIONS

> Yes, this is annoying. I think --substitute-urls (plural) was > misguided. Instead we should instead have --substitute-url (singular), > which could be repeated several times. That would solve the troubles > with spaces. > > During a transition period we could keep accepting --substitute-url

bug#29662: 'guix gc' as user makes system unbootable

Hi, On 08.01.2018 15:34, Ludovic Courtès wrote: > Hi Martin, > > Sorry for the delay. No problem. > Looking at guix/scripts/system.scm, ‘install-bootloader’ definitely > installs the ‘bootcfg’ symlink, except if ‘grub-install’ fails—which is > apparently the case in your transcript above. Ok,

bug#30476: failing test-suite

on my raspberry pi, building from commit 7e0a6fac0b4ebffda322eff6e803363ee72a257a. the test-suite fails. my current guix is from november or so. the first log was created with -j 4. the second with -j 1. not sure, how critical the errors are. somehow i still can't read the test-suite logs.

bug#30476: failing test-suite

On 16.02.2018 14:00, Ludovic Courtès wrote: > Martin Castillo skribis: > >> ++ guix build superseded -d >> accepted connection from pid 22991, user pi >> random seed for tests: 1518709083 >> guix build: package 'superseded' has been superseded by &

bug#30868: test-suite fails: publish.scm

make check TESTS=tests/publish.scm results in the attached log -- GPG: 7FDE 7190 2F73 2C50 236E 403D CC13 48F1 E644 08EC == GNU Guix 0.14.0.3450-be5ed: ./test-suite.log == # TOTAL: 18 # PASS: 17

bug#30916: Request: add a short description field for os-configuration

hi, the grub entries for old system generations aren't very helpful. It would be nice, if there was a field in the operating system declaration stating what was changed in this generation, that would be added to the boot entry label. Martin -- GPG: 7FDE 7190 2F73 2C50 236E 403D CC13 48F1 E644 0

bug#30916: Request: add a short description field for os-configuration

Hi, On 23.03.2018 15:15, ng0 wrote: > Could you be a more specific what you think is missing? > Your request is written in a very open way, and the space in GRUB menus is > limited as far as I assume. Sure, Currently the grub menu looks like GNU with Linux-Libre 4.15.12 (beta) GNU system, old c

bug#30916: Request: add a short description field for os-configuration

> So basically you want a field in the operating-system declaration where you > can _manually_ set a description of a certain maximum length which will be > added to the GRUB entry of the generated system generation? yes -- GPG: 7FDE 7190 2F73 2C50 236E 403D CC13 48F1 E644 08EC signature.asc

bug#31023: --verbosity=4 breaks build?

Hi, On 02.04.2018 23:48, Ludovic Courtès wrote: > Hello Martin, > > As a foreword, note that ‘--verbosity’ is almost useless, even to Guix > developers. I think we should hide it under a weird name, maybe > ‘--daemon-debug’? Ok. > > Your Raspberry will handle the build if and only if you’re r

bug#31330: guix a2cfe broken after update from ~month old guix: util-linux-2.31.1: unbound variable

Hi, I updated guix (on guixsd) from a version from about beginning of april to a2cfe. After that, guix system (and other commands depending on it) give me a backtrace. Backtrace: In ice-9/boot-9.scm: 222:29 19 (map1 _) 222:29 18 (map1 _) 222:29 17 (map1 _) 222:29 16 (map1 _) 222:29

bug#30993: OpenSSH sshd killed by Shepherd 0.4.0

(resending because I forgot to CC the list) On 06.04.2018 14:41, Leo Famulari wrote: >> Hmm, where could that SIGTERM come from? ‘make-kill-destructor’ uses it >> when a service is stopped, and otherwise it’s sent when we’re shutting >> the system down. But here?… > > Indeed, that is the questio

bug#31330: guix a2cfe broken after update from ~month old guix: util-linux-2.31.1: unbound variable

On 01.05.2018 15:38, Ludovic Courtès wrote: > Hello Martin, > > Martin Castillo skribis: > >> I updated guix (on guixsd) from a version from about beginning of april >> to a2cfe. >> After that, guix system (and other commands depending on it) give me a >>

bug#30993: OpenSSH sshd killed by Shepherd 0.4.0

On 01.05.2018 22:43, Ludovic Courtès wrote: >> Maybe one could somehow strace herd, or change the make-kill-destructor >> to log every time it is being executed? > > ‘herd status sshd’ displays the last time sshd was respawned, but the > info ‘herd’ receives actually includes the dates of all th

bug#30993: OpenSSH sshd killed by Shepherd 0.4.0

Sorry, I forgot to mention that I have the same problem. But I had it already with shepherd 0.3.

bug#30993: OpenSSH sshd killed by Shepherd 0.4.0

On 06.05.2018 21:50, Leo Famulari wrote: > On Fri, May 04, 2018 at 04:01:52AM +0200, Martin Castillo wrote: >> Sorry, I forgot to mention that I have the same problem. But I had it >> already with shepherd 0.3. > > Interesting. Did it ever work for you on that system? >

bug#31450: guix pull ignores GUILE_WARN_DEPRECATED

I have exported GUILE_WARN_DEPRECATED=no but the new guix pull still shows the warning about used, deprecated features. -- GPG: 7FDE 7190 2F73 2C50 236E 403D CC13 48F1 E644 08EC

bug#31456: guix size tries to fetch substitute information for installed package.

I'm on guix 563ab27bd4caead5676bbd515c54b25100c98960 on guixsd. $ guix package -I; contains lilypond2.19.80 out /gnu/store/jhmz7wpb93hryzqq32kcb4fs9cd84jyi-lilypond-2.19.80 I installed lilypond with that guix version. $ guix size lilypond; gives me guix size: error: no available substitute

bug#31456: guix size tries to fetch substitute information for installed package.

On 14.05.2018 22:10, Martin Castillo wrote: > I'm on guix 563ab27bd4caead5676bbd515c54b25100c98960 on guixsd. > $ guix package -I; contains > lilypond 2.19.80 out > /gnu/store/jhmz7wpb93hryzqq32kcb4fs9cd84jyi-lilypond-2.19.80 > I installed lilypond with that guix versi

bug#31456: guix size tries to fetch substitute information for installed package.

3 2C50 236E 403D CC13 48F1 E644 08EC From 337bf474edc91c09bf172091ed2c6ec4cb6e5f94 Mon Sep 17 00:00:00 2001 From: Martin Castillo Date: Tue, 15 May 2018 12:14:18 +0200 Subject: [PATCH] doc: Add note to guix size * doc/guix.texi (Invoking guix size): Note that guix size ignores grafted packages

bug#31450: guix pull ignores GUILE_WARN_DEPRECATED

> > Fixed in 30d722c392960373bb45c3248d318ef6e248fb67. > That commit has the following: + /* Map root and the current user. */ + int len = snprintf (id_map, sizeof id_map, "%d %d 1\n", id, id); This only maps `id' to itself, but not the root user? -- GPG: 7FDE 7190 2F73 2C50 236E 403D CC

bug#30993: OpenSSH sshd killed by Shepherd 0.4.0

(label "Grub Nixos") ; (multiboot "(hd0)") ; still unsupported ; ))) ; )) (file-systems (cons (file-system (device (file-system-label "guix-root")) (mount-point "/")

bug#32296:

Am 2. August 2018 09:05:51 MESZ schrieb "Gnu Röoty" : >I did that and I have this error, > >(use-modules (gnu) (gnu system nss)) >(use-service-modules desktop networking dbus cups) >(use-package-modules certs mate wicd glib cups) > >(services (cons* (service-cups-service-type >(cups-configuration >

bug#62460: Upgrading manifest based profile while keeping an intentionally older version of one package.

Hi, if someone has a profile made with a manifest like (specifications->manifest '("gcc@11")) and they want to update it, they might run guix package -p the-profile -u which would currently install gcc@12, or they would run something like package -p the-profile -m manifest.scm -u which a

bug#62406: “! failing-command” pattern in shell tests is wrong

Sorry for my answer. I overlooked that Eric already answered.

bug#62406: “! failing-command” pattern in shell tests is wrong

Hi, Am 23.03.23 um 17:00 schrieb Ludovic Courtès:> In (commit > d8934360d2453a403b5433e71d09188e4ed23b57), we changed: > >if command that should fail; then false; else true; fi > > to: > >! command that should fail > > I had reservations back then, an

bug#55287: make-file-writable adds the executable bit on some files added to the store

Hello Ludovic, since you wrote the ;XXX: symlinks annotation, you must have been aware of the problem, but still decided to use lstat. Can you tell why? Martin

bug#62710: Man page of loginctl is invalid troff.

Hi, man loginctl prints stuff like .SH "NAME" loginctl - Control the elogind login manager .SH "SYNOPSIS" .HP 216u loginctl [OPTIONS...] {COMMAND} [NAME...] .PP /lib/elogind/system-shutdown Indeed zcat /run/current-system/profile/share/man/man1/loginct