bug#66866: aarch64 system cross compilation + pinebook pro image broken?

> The issue seems to be that grafting ends-up dragging the bootstrap > packages into the closure when cross-compiling which is quite scary. I could narrow it down somehow. This commands drags the bootstrap and fails: --8<---cut here---start->8--- guix build

bug#66866: aarch64 system cross compilation + pinebook pro image broken?

Hey, > ./pre-inst-env guix system build --target=aarch64-linux-gnu > gnu/system/images/pine64.scm > > > which cause an issue in gawk-mesboot: > > checking host system type... Invalid configuration `aarch64-linux-gnu': > machine `aarch64' not recognized > configure: error: >

bug#66866: aarch64 system cross compilation + pinebook pro image broken?

Hello, I can reproduce the error by running: --8<---cut here---start->8--- ./pre-inst-env guix system build --target=aarch64-linux-gnu gnu/system/images/pine64.scm --8<---cut here---end--->8--- which cause an issue in

bug#67109: ‘efi32-esp’ image support pulls in host-side code

Hello, > guix system: error: # initialize-efi32-partition root #:grub-targets # (quote ("i386-efi" . "BOOTIA32.EFI")) gnu/system/image.scm:142:28 > 7fef96f85390>:out> args)) gnu/system/image.scm:146:8 7fef96f85360>: > invalid G-expression input Expressed that way, I no longer have this error

bug#67109: ‘efi32-esp’ image support pulls in host-side code

Hey, Thanks for investigating this! > Thus I’m proposing the fix below. How can I test it though? I get: > > $ ./pre-inst-env guix system image -t efi32-raw > gnu/system/examples/bare-bones.tmpl > guix system: error: EFI bootloader required with GPT partitioning I added this check recently

bug#66207: Cannot boot VMs with grub-efi-bootloader

Hey, Some context around that. Before recent commits, when we were producing qcow2 or raw images, those were MBR images with an EFI partition. If the grub-bootloader was used, then Grub was installed both in the post-MBR gap and in the EFI partition. This means that a single image could be

bug#48468: substitute server connection timeout

Hey, So the debug mechanism is in place. Requesting a non-existing derivation on a worker gives: --8<---cut here---start->8--- mathieu@hydra-guix-104 ~$ guix build /gnu/store/yd1p7069rs4xbbfwj5p7nzp9psw7d3vv-hello-2.12.1.drv substitute: could not fetch

bug#37513: Subject: Installer finish backtrace, umount dispatch exception /mnt device busy

Hello, > Therefore, I guess it would make to close. Any objection? Thanks for the feedback, lets close it. Mathieu

bug#48468: substitute server connection timeout

Hello, > It means that upstream (i.e., ‘guix publish’) closed the connection, > right? > > And it means that it closed it prematurely I guess? Looks like it yes. >> However, like suggested in your hypothesis number 1, it seems instead >> that we are replying 404 to the worker which resets the

bug#48468: substitute server connection timeout

5c2yqh1q* ls: cannot access '/gnu/store/007zgflsl5xkr377wpakbsis5c2yqh1q*': No such file or directory --8<---cut here---end--->8--- As I don't have much clue about what are those derivations, I think we should instrument a bit the publish server and maybe the

bug#48468: substitute server connection timeout

>From 725d5ba21a0fc0108b60c37bbc8d947fab6ac938 Mon Sep 17 00:00:00 2001 From: Mathieu Othacehe Date: Tue, 27 Dec 2022 10:49:04 +0100 Subject: [PATCH 1/1] scripts: publish: Add a log when replying 404 due to baking. * guix/scripts/publish.scm (render-narinfo/cached): Add it. --- guix/scripts/publish.scm | 10 +++--

bug#60265: Unbootable system after guix gc

Hello, > do you have other channels added, or did this happen on a vanilla Guix > install? > > it's a duplicate of https://issues.guix.gnu.org/57838 Right it is a duplicate and it is related to the use of an extra channel. Good news is that I found a fix. Closing this one. Thanks, Mathieu

bug#59823: [1.4.0rc1] Installer fails to identify installation device on Ventoy-made images

Hola, > Anyway, all in all, calling out to dmsetup looks reasonable for now; I > have a slight preference for using ‘open-pipe* OPEN_READ’, but no big > deal. Perhaps add a comment showing what the line we’re parsing should > look like. Yeah, I agree that open-pipe would be a bit clearer, but

bug#59884: ‘gui-installed-desktop-os-encrypted’ test intermittent failures

Hello, > ice-9/eval.scm:619:8: Throw to key `marionette-eval-failure' with args > `((quote (complete-installation installer-socket)))'. > builder for `/gnu/store/wgw64jfyqrrg27afqmlj70a22d1mr5mv-installation.drv' > failed with exit code 1 > @ build-failed

bug#59823: [1.4.0rc1] Installer fails to identify installation device on Ventoy-made images

Hello, The attached patch fixes it for me. We could maybe use libdevmapper instead of the plain "dmsetup" call but that's not critical in my opinion. Thanks, Mathieu >From 0afda5b3ed32e73bece9db96ab970d83f9f2e74b Mon Sep 17 00:00:00 2001 From: Mathieu Othacehe Date: Thu, 8 Dec

bug#59823: an installer dump was sent

Hello, It's really good that you managed to install it anyway. Thanks for persevering :) Nevertheless we need to fix the problem. > I already managed the installation by burning the iso directly to my > usb drive and not via Ventoy. Turns out Ventoy was the crux of the issue here. Ventox

bug#48468: substitute server connection timeout

Hello, > /gnu/store/qmzr030rzgikdxv3g9msqv0l8qp5j6y2-btrfs-raid-root-os.drv, > which was marked as failed earlier today due to missing .drv. It’s a > 4KiB file, and the cache-bypass-threshold is ‘guix publish’ is typically > set to something much higher than that. So ‘guix publish’ won’t

bug#48468: substitute server connection timeout

Hello, > You mentioned on IRC that nginx logs show that ‘guix publish’ times out. > Looking at /var/log/nginx/error.log, I see “Connection reset by peer” > and “Broken pipe”, which could indicate that the client closed the > connection (which was open) prematurely, maybe due to an internal >

bug#59823: an installer dump was sent

Hello, So I had a closer look and we do have this strange kernel warning: --8<---cut here---start->8--- Dec 4 10:49:05 localhost vmunix: [ 1351.610773] device-mapper: ioctl: remove_all left 1 open device(s) --8<---cut

bug#59823: an installer dump was sent

vice-in-use?" procedure is probably not high enough. Here is an attached patch to bump it from 16 to 96 seconds. I also uploaded an image built on top of of the version-1.4.0 with this patch if you are up for a retry :), you can download it this way: --8<---cut here---sta

bug#59493: cuirass-remote-worker crash

Hey, > Oh I see. It would be nice to avoid non-backward-compatible changes in > the protocol so we can upgrade more smoothly. Right, sorry. We should introduce a protocol version to avoid that in the future. > Fixed in Cuirass commit 9fb6f21d29c5398b35f4c1a77cf6c20f207c9ebb. Awesome, thanks

bug#59514: Stuck builds in Cuirass

Hello Marius, > Cuirass has a tendency to not notice when a build is finished, leaving > it in a "running" state. > > The phenomenon can be observed by going to > and look at builds that are running for > a suspiciously long time. I suspect this is caused by

bug#59510: cuirass-remote-server: put-char encoding failed

Hello, On Cuirass 1.1.0-13.1341725, the fetch workers are experimenting the following issue: --8<---cut here---start->8--- 2022-11-22 00:28:15 In cuirass/scripts/remote-server.scm: 2022-11-22 00:28:15415:12 3 (_) 2022-11-22 00:28:15 387:7 2

bug#55336: Graphical installer: Selecting a partition scheme always takes me back to the start

Hello Simon, > I just ran into this same problem with an old machine. Interesting, thanks for the report. > Disk image is: axygxkgkgcgbk2gjd6q521h85shp7hwf-image.iso from > https://ci.guix.gnu.org/build/125952/details. > > Please find attached some logs too: It looks like you experimented

bug#59493: cuirass-remote-worker crash

Hello Ludo, Thanks for gathering those information. > 2022-11-21 14:27:24 1685:16 0 (raise-exception _ #:continuable? _) > 2022-11-21 14:27:24 > 2022-11-21 14:27:24 ice-9/boot-9.scm:1685:16: In procedure raise-exception: > 2022-11-21 14:27:24 Throw to key `match-error' with args `("match"

bug#59405: Bug Report Screenshot on Lenovo Yoga 700 14ISK Device (which has flawed BIOS/unPatchable)

Hello, > FYI - Failed Installation attempt: Thanks for the report. Did you use the 1.3.0 release installer? If so, you might have better luck with the latest version (https://guix.gnu.org/en/download/latest/) that includes a dump upload mechanism. Thanks, Mathieu

bug#59447: Offload fails with: Throw to key `match-error'

> Fixed in b2b9571935f9188086b2e7b434840eeda6c42805. > > We’ll have to update the ‘guix’ package to deploy it, though. Thanks for fixing that one, closing! Mathieu

bug#59467: GUIX Installer Bugs

Hello, > Hello I'm trying to install Guix 1.3.0 the last release but the > graphical installer throw an issue, attached you images. The 1.3.0 installer is a bit old and many issues, including the one you are experimenting have been fixed. Could you please retry with the latest installer

bug#59447: Offload fails with: Throw to key `match-error'

Hello, I'm trying to offload an aarch64-linux build on Berlin and it fails this way: --8<---cut here---start->8--- process 75612 acquired build slot '/var/guix/offload/10.0.0.9:22/3' Backtrace: In ice-9/boot-9.scm: 1752:10 12 (with-exception-handler _ _

bug#55336: Graphical installer: Selecting a partition scheme always takes me back to the start

Hey, > I tried again with w0wi4jvanaddk1zcvwzhlnn7fkfwab82-image.iso in the > same machine and the issue is gone. I could install the system almost > flawlesly. So no oportunity to try out the new mechanism :) Thanks a lot for testing again and reporting :) Mathieu

bug#53594: no matching pattern #

Hey Ludo, > If we cannot reproduce this bug, I propose that we remove it from the > list of release blockers at . I haven't had this issue for a long time, seems fair to unblock the release issue. Thanks, Mathieu

bug#37513: Subject: Installer finish backtrace, umount dispatch exception /mnt device busy

Hello, Sorry for the very late reply. We recently added a bunch of error reporting features to the installer. Any chance you still have the hardware around and would be able to test again using the latest installation image available here: https://guix.gnu.org/en/download/latest/? That would

bug#42054: installer: "invisible" screens, partitioning step fail

Hello, Sorry for the very late reply. We recently added a bunch of error reporting features to the installer. Any chance you still have the hardware around and would be able to test again using the latest installation image available here: https://guix.gnu.org/en/download/latest/. That would

bug#47053: The installer has encountered an unexpected problem

Hello, > Attempted to install Guix System on a Librebooted machine and this > happened. Sorry for the very late reply. We recently added a bunch of error reporting features to the installer. Any chance you still have the hardware around and would be able to test again using the latest

bug#52767: Unexpected problem with Guix System installer

Hello Mathieu, > This is not the drive that was used to boot the Guix installer in the > first place. > > Thanks, hope someone can understand what the issue is. Sorry for the very late reply. We recently added a bunch of error reporting features to the installer. Any chance you still have the

bug#54966: Guix Installer Bug

Hello, Sorry for the very late reply. > I tried to install Guix on the Framework laptop, and up until the > partitioning, everything goes smoothly. However, after this is > reached, any attempt at mounting a partition to / results in this > error statement We recently added several error

bug#56485: Graphical Installer Partitioning Bug

Hey, > I believe this issue was with the 1.3 installer and not the latest > version. When I used the latest version I don't think I encountered > this. Sorry I forgot to update. Thanks for your answer :) Mathieu

bug#33555: test.iso-image-installer.i686 got stuck after kernel oops

Hey Mark, > The most recent build of 'test.iso-image-installer.i686-linux', which > was performed on hydra.gnunet.org, hit a kernel oops, and subsequently > got stuck. > > https://hydra.gnu.org/build/3194778 All installation tests are now passing on Cuirass. Closing, Mathieu

bug#37264: null pointer dereference in visual installer

Hello, > I try to install Guix System 1.0.1 ISO on VirtualBox 6.0.10. I just > select default values (press Enter every time) and get error after > choosing options for disk partitioning. Closing this old issue that is very likely fixed now. Thanks, Mathieu

bug#53459: installer: uuid->string failure backtrace (again)

Hello, > ice-9/eval.scm:159:9: Throw to key 'match-error' with args '("match" "no > matching pattern" (#f ext4))' This is very likely fixed by: ab974ed709976d34917c8f6f9e5cc0004547af45. Thanks, Mathieu

bug#53978: installer crash

Hello, > I have tried to install the stable version of guix using the graphical > installer and got the error on the attached screenshot. Thanks for the report. This is very likely fixed by: ab974ed709976d34917c8f6f9e5cc0004547af45. Closing, Mathieu

bug#55011: let user drop into REPL from installer

Hello, > Long story short I got an error related to mkfs.btrfs, this I think has > already been reported, but Mumi's search is not great so I haven't > verified that yet. Installer now reports failing partitioning commands and offers to re-run them or keep things going. This should cover your

bug#55336: Graphical installer: Selecting a partition scheme always takes me back to the start

Hello Luis, > Using the latest installer image > (l6dfrnjhhjf3axjndk290qsgxj0bzpgm-image.iso) I can't install the > system because everytime I select a partition scheme, the installer > takes me back to the language selection step. The latest installer offers a core-dump upload mechanism that

bug#56485: Graphical Installer Partitioning Bug

Hello, > The bug: When I tell it to go ahead and partition the drive according > to what I set up, the screen flashes and resets the entire installer > to the beginning of the installation i.e. takes me back to the locale > setting screen. However, when I don't create a swap, it seems to >

bug#59179: BUG: (./guix/base32.scm:296:65: ERROR)

Hello, Fixed by Andrew with: 0760a8511d512ebac388eda0b9e18fd7451ca4b3. Sorry for the breakage! Mathieu

bug#58923: Malformed core dumps on Guix System

Hey, Thanks for trying to reproduce it. Turns out, it is now working both on Berlin and on installation images but still failing on my machine. It's not often that those kind of issues do resolve by themselves. I would suspect a kernel regression here. My machine has the following kernel:

bug#58732: installer: finalizers & device destroy segfault

Hey, > Looking at device.c in Parted, that’s probably the right thing because > PedDevice objects are kept in a linked list whose head is stored in the > ‘devices’ global variable of device.c. So you cannot just free them > asynchronously from a finalizer thread because they might still be >

bug#58732: installer: finalizers & device destroy segfault

with my reasoning :) Thanks, Mathieu >From 066220a75c020b818aab9c2f5c3a7db835fa871a Mon Sep 17 00:00:00 2001 From: Mathieu Othacehe Date: Wed, 9 Nov 2022 16:12:52 +0100 Subject: [PATCH 1/1] Remove the finalizer on device pointers. Fixes: <https://issues.guix.gnu.org/58732> * parted/d

bug#58732: installer: finalizers & device destroy segfault

Hola, > Finalizers are set on pointer objects, so they’re invoked when the > pointer object goes out of scope. But: > > (eq? (make-pointer 123) (make-pointer 123)) > => #f I agree, but somehow this works: --8<---cut here---start->8---

bug#58732: installer: finalizers & device destroy segfault

Hey, I made some progress on that one. I think, this is what's going on: 1. Two new PedDevice A and B are malloc'ed by the libparted when opening the installer partitioning page. 2. They are added to the %devices weak hash table by pointer->device! and their respective finalizers are

bug#40682: Installer hangs while connecting to WiFi network

Hey, >> Are these still in your plans? Otherwise let's close this old, >> high severity bug. > > Friendly ping. :-) Yeah, we didn't have other reports regarding WiFi connections, so lets close it. Thanks, Mathieu

bug#58732: installer: finalizers & device destroy segfault

Hey, Thanks for your help :) > 1. Bindings create wrappers for C pointers—e.g., with > ‘pointer->device’. If several C functions return a pointer P, you > must make sure to return always the same wrapper and not create a > new one. Agreed. > > ‘pointer->device!’

bug#58923: Malformed core dumps on Guix System

Hey zimoun, > #0 0x00401106 in main () > (gdb) bt > #0 0x00401106 in main () > (gdb) exit OK so it must somehow be related to Guix System or the Linux kernel we ship. Thanks for your feedback, Mathieu

bug#58733: installer: coredump generation

Hey, > Both look reasonable to me, thanks! Thanks for reviewing :) > Now, we should probably focus on Guile-Parted… Yes, I saw you sent a few pointers, that will be my next focus! Mathieu

bug#58923: Malformed core dumps on Guix System

Hey, > Could it have to do with /proc/sys/kernel/core_pattern or with the fact > that your /tmp file system was full or something? What if you try to > have the core dump on another file system? I suspected that at first, but I then reproduced it on Berlin so I would rather bet on a recent

bug#57068: Resizing mcron job in vm-image.tmpl interferes with settings

Hey, > Oh, I wasn’t aware of that, that should certainly be fixed. (I fixed a > similar issue in GNOME some years ago, and I’m confident it’ll be easier > to fix in Xfce because it doesn’t have all those layers and daemons and > JavaScript and DBus interfaces. :-)) Fixing this behaviour in

bug#49508: Implement --allow-insecure-transport for `guix pull`

Hello, > ‘verify_server_cert’ in src/streams/openssl.c is called > unconditionally. So it seems that the first thing to do would be to > submit a patch upstream that would allow users to disable certificate > checks via ‘git_libgit2_opts’. While this seems like something that we definitely

bug#58733: installer: coredump generation

:00:00 2001 From: Mathieu Othacehe Date: Mon, 31 Oct 2022 16:43:09 +0100 Subject: [PATCH 1/1] installer: Skip the backtrace page on user abort. When the user aborts the installation because a core dump is discovered or the installation command failed, displaying the abort backtrace doesn't make

bug#58926: Shepherd becomes unresponsive after an interrupt

Hello, When running the following command: --8<---cut here---start->8--- sudo herd restart service-that-hangs-upon-restart --8<---cut here---end--->8--- then hitting C-c, Shepherd becomes totally unresponsive:

bug#58733: installer: coredump generation

ting the proposed mechanism. Mathieu >From f4d2a1bb4df2f65b650be704bffb7ea469ae0232 Mon Sep 17 00:00:00 2001 From: Mathieu Othacehe Date: Mon, 31 Oct 2022 13:03:46 +0100 Subject: [PATCH 1/1] installer: Add core dump support. Fixes: <https://issues.guix.gnu.org/58733> * gnu/installer.scm (

bug#58923: Malformed core dumps on Guix System

Hello, Working on https://issues.guix.gnu.org/58733, I noticed that there is something wrong with the core dumps we are generating on Guix System. --8<---cut here---start->8--- mathieu@meije ~/tmp [env]$ cat test.c #include int main() { int *t =

bug#53194: System test partition.img differs in size across hosts(?)

Hello, > FYI, I pushed this workaround in > 3c3c9d259f87fbc8c1d9551af32e79f9f168f596. I'm not able to reproduce this issue with or without the workaround, by running the openvswitch test on Berlin and on my laptop. I think we can close it for now and re-open it if someone finds a more reliable

bug#53541: [installer] backtrace during fresh Guix System install after during formatting

> Fixes: . > > * gnu/installer/parted.scm (read-partition-uuid/retry): New procedure. > (check-user-partitions): Use it. Pushed as ab974ed709976d34917c8f6f9e5cc0004547af45. Mathieu

bug#53541: [installer] backtrace during fresh Guix System install after during formatting

Hey, > I was able to reproduce it on real hardware, following those > instructions. The dump is available here if people want to join the > party: dump.guix.gnu.org/download/installer-dump-304492ff. So the backtrace suggests that we are trying to open /dev/nvme0n1p1 to read its superblock:

bug#58733: installer: coredump generation

Hello, This installer sometimes sadly segfaults, most of the time in libparted. To be able to catch this coredump[1], I ran those commands: --8<---cut here---start->8--- echo /tmp/core > /proc/sys/kernel/core_pattern prlimit --core=unlimited --pid=1234

bug#58734: installer: backtrace page in final step

Hello, When an error occurs in the pseudo terminal displaying the "guix system init" command output, the backtrace is not displayed correctly and the keyboard cannot be used (arrows, tab, enter keys) to scroll down the backtrace or dump it. It can easily be reproduced by introducing an error

bug#58734: installer: backtrace page in final step

> + (error 'fake) >(installer-log-line "running command ~s" command) >(define result (run-external-command-with-line-hooks >(list %display-line-hook) command Fixed with bf5e78d59fcb188d0bce02d93c93d06069178837. Thanks, Mathieu

bug#58732: installer: finalizers & device destroy segfault

Hello, I found a segfault in the installer by running those steps: - Run an automatic partitioning with separate home and no encryption - In the final configuration page, come back to partitioning - Remove all partitions but the ESP one, create a new btrfs root - partition - Repeat until the

bug#53541: [installer] backtrace during fresh Guix System install after during formatting

s another story. I'll open a ticket about that later on. Thanks, Mathieu >From 4407374ff4087772bd8226824cf4883537752f01 Mon Sep 17 00:00:00 2001 From: Mathieu Othacehe Date: Sat, 22 Oct 2022 22:27:57 +0200 Subject: [PATCH 1/1] installer: parted: Retry failing read-partition-uuid call. F

bug#52943: Cannot build guix as part of guix system reconfigure after commit 224d437fb4 on aarch64

Hello, > Also, substitute availability for aarch64-linux and armhf-linux is > OK. Does that mean this issue can be closed? The guix package for armhf-linux is not built anymore by ci.guix.gnu.org, but guix for aarch64-linux seems to be working. Closing, Thanks, Mathieu

bug#55360: bug#58375: Installer does not show what is being downloaded

Hey, Thanks for having a look! > I haven’t actually tested the patch but it LGTM. One thing to check is > whether ‘terminal-window-size’ returns something sensible for the > pseudo-terminal; it could be that we need an extra ioctl so the > pseudo-terminal has the same size as the actual

bug#58375: Installer does not show what is being downloaded

re" to the "run-install-failed-page". Thanks, Mathieu >From c6286404e9c4c0dc302c3d398a8f27b050cf4ce0 Mon Sep 17 00:00:00 2001 From: Mathieu Othacehe Date: Fri, 14 Oct 2022 17:28:27 +0200 Subject: [PATCH 1/2] installer: Run the "guix system init" command in a PTY. Fixes: <https://

bug#53480: i686 ISO image from CI is installing an x86_64 system

Hello, Fixed with: 84b4216e988ec6791b6df8f894d5a01cbf2e5fa5. Thanks, Mathieu

bug#57232: [installer] ENTER in guided partitioner destroys partition table

Hey, > Fixes: . > > * gnu/installer/newt/partition.scm (run-label-confirmation-page): New > procedure. > (run-label-page): Call the above procedure before proceeding. I pushed a slightly edited version of this patch. Thanks, Mathieu

bug#55360: bug#58375: Installer does not show what is being downloaded

Hey Ludo! > I’m not sure it’s a good idea for ‘guix system init’: we’d be logging > mostly progress bars, package names, and the likes to syslog—not super > useful. So I’d suggest not capturing stdout of ‘guix system init’. In the bug report https://issues.guix.gnu.org/57983 capturing the

bug#57827: Shepherd 0.9.2 possible regressions

Hey, > This is fixed by 6abdcef4a68e98f538ab69fde096adc5f5ca4ff4; the log > contains extra details. Thanks for fixing it! Turns out we still have an issue on all four installer tests. The error messages look like: --8<---cut here---start->8--- Sep 22

bug#57983: Error installing on a Framework Laptop

Hey, > Here is a fix for the second issue, as well as a little bonus commit for a > mistake that made it past my refactoring. That's awesome. I tested by running an install with "automatic encrypted partitioning" then killing the "guix init" process. The installer is able to resume the final

bug#57983: Error installing on a Framework Laptop

Hello Dan, Thanks a lot for the bug report. > The dump was uploaded as installer-dump-11a1087c. As you are the first one reporting an installer bug using the new dump mechanism, a small precision: the dump can be downloaded this way: --8<---cut

bug#57933: Gtk is unsupported on i686-linux

Hello, I had the following error while trying out `make release` for `i686-linux` specifically. --8<---cut here---start->8--- + for example in gnu/system/examples/*.tmpl + case "$example" in + options= + guix system -n disk-image

bug#57928: GNOME Calendar online account issue

Hello, Since the GNOME upgrade to 42.2 the GNOME Calendar, as well as the calendar widget of GNOME Shell do not show my appointments from configured online accounts. Thanks, Mathieu

bug#57827: Shepherd 0.9.2 possible regressions

Hey Chris, > Since empty files is a possibility with wait-for-file, I've sent a patch > to [1] which prevents the eof issue, plus another change to make it > easier to debug. Nice! I wonder if we should maybe block in wait-for-file until the file has some content. In the cgit/gitile tests, we

bug#57827: Shepherd 0.9.2 possible regressions

Hello, Since Shepherd 0.9.2 the following tests are failing: * cgit: https://ci.guix.gnu.org/build/1427375/details * gitile https://ci.guix.gnu.org/build/1427377/details It seems that an unexpected # object is received on the marionette socket. * gui-uefi-installed-os

bug#57642: [PATCH] gnu: linux: Fix unnecessary let clause in make-linux-libre.

Hey, > * gnu/packages/linux.scm (make-linux-libre*)[arguments]: > Remove unnecessary let clause in 'configure phase. You should send such patches to "guix-patc...@gnu.org" instead as it is not a bug report nor correction. Pushed as 2183db8d2 :). Thanks, Mathieu

bug#57232: [installer] ENTER in guided partitioner destroys partition table

Hey, > “You can change a disk's partition table by selecting it and pressing > ENTER.” > > Er, I was… expecting that to mean it would pop up a pretty window or > something. Is this really a feature? Should it be? I'm not sure what's the point here. > I have to be honest: I was extremely

bug#57215: ci: Fail to evaluate Guix specification

Hey, > So, I think there's some involvement of grafts that mean you end up > building things when just trying to compute the derivation. But that's > as far as I got, I don't really understand why this is the case, or what > can be done about it. Thanks for sharing Chris, I tried to disable

bug#57229: ‘guix system image’ forces commit authentication?

Hey, > λ ./pre-inst-env guix system image -t iso9660 > gnu/system/install.scm --disable-authentication > guix system: error: disable-authentication: unrecognized option That's probably a side effect of https://issues.guix.gnu.org/53210 that includes the "current-guix" inside the installation

bug#57232: [installer] ENTER in guided partitioner destroys partition table

>From 4a9c1fb1fe7f9a65b2b7d1f9e4419b1d28a8082e Mon Sep 17 00:00:00 2001 From: Mathieu Othacehe Date: Tue, 16 Aug 2022 10:49:07 +0200 Subject: [PATCH 1/1] installer: partition: Add a confirmation page before formatting. Fixes: <https://issues.guix.gnu.org/57232>. * gnu/installer/newt/partition

bug#53463: ci.guix.gnu.org not building the 'guix' job

Hello, > https://ci.guix.gnu.org/jobset/guix It is now fixed for the following architectures: x86_64-linux, i686-linux and aarch64-linux. I'll try to repair it for powerpc64le-linux soon. We can close this one I guess. Thanks, Mathieu

bug#57215: ci: Fail to evaluate Guix specification

Hello, Some news on this one: I discovered that the evaluation failure of the "guix" specification is correlated with the selected systems. When disabling "aarch64-linux" and "powerpc64le-linux", the evaluation succeeded. Now, when running: --8<---cut

bug#57215: ci: Fail to evaluate Guix specification

With symbols: #0 0x7f63a4b15030 in raise () from /gnu/store/5h2w4qi9hk1qzzgi1w83220ydslinr4s-glibc-2.33/lib/libc.so.6 #1 0x7f63a4aff526 in abort () from /gnu/store/5h2w4qi9hk1qzzgi1w83220ydslinr4s-glibc-2.33/lib/libc.so.6 #2 0x7f63a5091198 in scm_dynstack_unwind_1.isra.0

bug#57215: ci: Fail to evaluate Guix specification

Hello, > [pid 74060] --- SIGPIPE {si_signo=SIGPIPE, si_code=SI_USER, si_pid=74060, > si_uid=997} --- > > The evaluation process receives a SIGPIPE when trying to write the > evaluation result to the pipe connecting it to "cuirass register". I think this is a wrong lead. The cuirass evaluation

bug#57215: ci: Fail to evaluate Guix specification

Hello, Since commit 0565cde, Cuirass fails to evaluate the guix specification. The error messages do not give any clue, for instance: https://ci.guix.gnu.org/eval/504294/log/raw. I tried to strace an evaluation process of the guix specification, it ends this way: --8<---cut

bug#57180: Graphical Installer Failure

Hello, Thanks for the report. This looks like to be a manifestation of https://issues.guix.gnu.org/56005 within the installer. Mathieu

bug#54483: ‘guix system image’ chokes on host's /var

Hey, > However, fundamentally, ‘guix system image’ shouldn’t be reading > /run/current-system/parameters because it has not use for it. > > Mathieu, do you happen to have an idea where to remove that > ‘read-boot-parameters-file’ call? :-) Yes, that's because profile-boot-parameters was

bug#53210: installer: referring to N-1 guix is problematic.

Hey, > Let me know if you have comments! Thanks for taking care of this! Looks like we have a small regression on 'system-tests and 'guix specifications: https://ci.guix.gnu.org/eval/528053/log/raw https://ci.guix.gnu.org/eval/528056/log/raw I think this is because channel-source->package

bug#54786: Installation tests are failing

Closing as all the installation tests are now fixed. Thanks to everyone involved :) Mathieu

bug#57037: Package `guile-newt' cannot be cross-compiled

Hello, > The `guile-newt' package that is used for the installation UI can't > be cross-compiled as it tries to load the `newt' dynamic library when > the Guile code is compiled. I've tried to find a solution/fix but I > don't know much about how Guile byte-code compilation works. Fixed with

bug#55549: Parted 3.5 update breaks installer tests

Reported the problem upstream with: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=56996. Mathieu

bug#55549: Parted 3.5 update breaks installer tests

Hey Ludo, > Mathieu, I’m guessing the cause of the problem, when using Parted 4.5, > is that the installer partitions disks somewhat incorrectly, as reported > by ‘grub-install’. I wonder if it might be due to an API or ABI change > that goes unnoticed in Guile-Parted because it uses the FFI.

bug#55206: Intermittent ldap test failure

Hey Timotej, > After increasing the memory limit for the test VM, I was able to run the > test successfully ten times on two different machines. The patch is > attached. Great, that wouldn't be the first time that the RAM limitation causes strange transient issues. I'm pushing the proposed

  1   2   3   4   5   6   7   >