Help neeeded to package guile-wiredtiger and microkanren
Héllo I am willing to pay 100€ or offer equivalent work for someone that will package guile-wiredtiger and microkanren. guile-wiredtiger [1] is a binding of wiredtiger for guile using ffi. It doesn't have autotools, I'd rather keep it that way. The guix package must run the test suite as per guix standard. wiredtiger is already packaged. [1] https://framagit.org/a-guile-mind/guile-wiredtiger microkanren is a micro version of minikanren. That is a single file project that should be straightforward to package. Same I'd rather not have to deal with autotools. microkanren doesn't have any dependency outside guile 2.2. [2] https://framagit.org/a-guile-mind/microkanren Payment will happen upon the patches are accepted in guix. Please do not work on packaging this stuff before contacting me to agree on a payment method. I am amz3 on IRC. Thanks in adavance, Amirouche ~ amz3 ~ http://hyperdev.fr
Re: offload daemon
James Richardson skribis: > Ludovic Courtès writes: [...] >>> Hmm, I move the key pair to /tmp and set the perms to 644 and offloading >>> works for my regular user... Not quite sure I understand why. >> >> The ‘guix offload’ command is invoked by guix-daemon as root. So when >> it is invoked, (getenv "HOME") returns "/root" or similar. Could that >> be the problem? >> >> HTH, >> Ludo’. > > Well, I think there is an issue with the offload. I don't (yet) know > guile well enough to understand the code to help :( OK. > Here is what I am finding: $ guix build blah seems to offload builds > properly. $ guix package -i blah, guix package -u blah, and $ guix > system reconfigure config.scm does not offload builds. Without more info, it’s hard to tell, but there are derivations that are marked as “non-offloadable”, essentially because it’d take more time to transfer them and build them remotely than to build them locally. Among those derivations are profiles (built by ‘guix package’) and many of the small items built by ‘guix system’. It could explain what you’re seeing. Something like ‘guix build libreoffice --no-substitutes’ should be offloaded, provided --max-jobs is appropriate as discussed before. HTH, Ludo’.
Re: Kernel panic - not syncing: attempting to kill init! when booting GuixSD
Hi Christopher, Christopher Baines skribis: > So I deleted some system generations from one of my GuixSD systems, then > rebooted. Unfortunately, I can no longer get it to boot. I think the > latest system generation should work, and at least one of the previous > generations should work. > > Excluding the generations that I removed, the others don't boot. All I > can really gather so far is a call stack, and the message: > Kernel panic - not syncing: Attempted to kill init! Weird. Is it because the root file system could not be found? Or something else? Like Ricardo wrote, could it be that the file system label changed or something? > I'm uncertain that this is something I have done wrong, I'm pretty sure > I was using the latest system generation when I ran guix gc, and I'm > assuming that it is the garbage collection that has stopped things working. It’s unlikely. You could have run ‘guix’ with a wrong database location (see ‘--localstatedir’ in the manual), but even that wouldn’t have reclaimed store items used by the processes currently running. > I'm going to try and make some time to see if I can get this system back > working again. I'm not sure how realistic this is, but I'm planning to > start by using the installation image, and somehow running guix system > reconfigure. I would suggest booting from an external medium such as the installation image, mounting the file system that holds /gnu/store, and inspecting there. Also worth trying: you could edit the command line in the GRUB menu to have it refer to /var/guix/profiles/system-NNN-link, where NNN is the number of a previous generation known to be on disk. HTH! Ludo’.
Re: guix system reconfigure
Oleg Pykhalov writes: > Hello. > > I have issue with: $ sudo guix system reconfigure /etc/config.scm > > > $ sudo guix pull # One warning > > Some deprecated features have been used. Set the environment variable > GUILE_WARN_DEPRECATED to "detailed" and rerun the program to get more > information. > > > $ sudo guix system build /etc/config.scm # No error or warning > > > $ guix system reconfigure /etc/config.scm > > It hangs shell until kill. > > substitute: updating list of substitutes from > 'https://mirror.hydra.gnu.org'... 100.0% > The following derivation will be built: >/gnu/store/8a2h3fs5n30r2akn13ri9yzrnkq101pr-grub.cfg.drv > substitute: updating list of substitutes from > 'https://mirror.hydra.gnu.org'... 100.0% > /gnu/store/j9b4jh7kvywgf7y7wg5q5ckya9y2p6rk-system > /gnu/store/1b84ib011a3850flzgqvwxh1p6i6f6da-grub.cfg > /gnu/store/ipwgwqaarp304r82b97748shwzmwa9k0-grub-efi-2.02 > /gnu/store/msm7xx7f7gs3rdg6qmbq7nbxkiy9y4a5-bootloader-installer > activating system... > ;;; WARNING: loading compiled file > /gnu/store/zz52nz789h6a34z609x79asxl7qnwiyq-module-import-compiled/gnu/build/activation.go > failed: > ;;; ERROR: In procedure load-thunk-from-memory: not an ELF file > ;;; WARNING: loading compiled file > /gnu/store/zz52nz789h6a34z609x79asxl7qnwiyq-module-import-compiled/gnu/build/activation.go > failed: > ;;; ERROR: In procedure load-thunk-from-memory: not an ELF file > making '/gnu/store/j9b4jh7kvywgf7y7wg5q5ckya9y2p6rk-system' the current > system... > setting up setuid programs in '/run/setuid-programs'... > populating /etc from /gnu/store/hbygivm12yf9rjigxkk56lzhgnfibdwk-etc... > usermod: no changes > usermod: no changes > usermod: no changes > usermod: no changes > usermod: no changes > usermod: no changes > usermod: no changes > usermod: no changes > usermod: no changes > usermod: no changes > guix system: unloading service 'user-homes'... > shepherd: Removing service 'user-homes'... > shepherd: Done. > guix system: loading new services: file-system-/srv/videos user-homes... > shepherd: Evaluating user expression (register-services (primitive-load > "/gn...") #). > > > > After system reconfigure cannot boot. I boot in the first generation after installation and made: $ sudo guix pull $ sudo guix system reconfigure /etc/config.scm It wasn't clear to me that I cannot build new system commits ontop of "dirty" generations. Warning $ sudo guix pull is gone. I'm not sure why it didn't work on last commmit. May be because I experimented too much as newbie and because of that had many dirty system commmits.
