Re: Can't open a container-shell
Cássio Tavares writes: I have created a profile from the attached `manifest.scm`, meant to be used in a container shell, so as to isolate activity X from the everything else. After everything was setup, I tried to initiate the shell with this command: guix shell -c 4 -M 6 --no-cwd --pure --container --network \ --manifest=./etc/manifest.scm \ --share=./home/sys-conf \ --user=sys-conf \ --profile=./home/sys-conf/.guix-profile \ --preserve='^DISPLAY$' But this doesn't work, and I get this error message: guix shell: error: "--profile" can't be used with package options --profile sources an existing guix profile (which is a group of package installations), while --manifest or other package options create a new profile with the defined packages. These two things are contradictory. Is there a specific reason you included the --profile flag? I think you'll probably get the behaviour you imagine without it. signature.asc Description: PGP signature
Problem when packaging Avizo
Hello,
I've been enjoying my time with Guix so far and I've decided to packages a
few applications that
I was using before switching. I've been trying to package avizo[0], they
seem to be using meson and ninja to build the software. So I've written the
following package, but when I've tried to build it using "guix build -L .
--debug=1 avizo" I get an exception.
Maybe I've missed something in the documentation.
Thanks for your help
Package:
(define-module (avizo)
#:use-module (guix packages)
#:use-module ((guix licenses) #:prefix license:)
#:use-module (gnu packages gnome)
#:use-module (gnu packages gtk)
#:use-module (gnu packages glib)
#:use-module (gnu packages pkg-config)
#:use-module (guix git-download)
#:use-module (guix build-system meson))
(define-public avizo
(package
(name "avizo")
(version "1.2")
(source
(origin
(method git-fetch)
(uri (git-reference
(url "https://github.com/misterdanb/avizo";)
(commit version)))
(file-name (git-file-name name version))
(sha256
(base32 "02h2jbgrbl2hyq6bzwryc1r47mipgdqrdh7zi44skc25w045s6q5"
(build-system meson-build-system)
(arguments
`(#:build-type "release"))
(inputs
`(("gtk+", gtk+)))
(native-inputs
`(("vala", vala)
("glib:bin", glib "bin")
("gobject-introspection", gobject-introspection)
("gtk-layer-shell", gtk-layer-shell)
("pkg-config", pkg-config)))
(home-page "https://github.com/misterdanb/avizo";)
(synopsis "Avizo")
(description "@code{Avizo} is a simple notification daemon, mainly
intended to be used for multimedia keys for example with Sway.")
(license license:gpl3+)))
Snippet from the execution
avizo 1.1
User defined options
buildtype: release
prefix : /gnu/store/1fv2c9zhmzhbp7ry1y1qhnwql8bf83fq-avizo-1.2
c_link_args :
-Wl,-rpath=/gnu/store/1fv2c9zhmzhbp7ry1y1qhnwql8bf83fq-avizo-1.2/lib
cpp_link_args:
-Wl,-rpath=/gnu/store/1fv2c9zhmzhbp7ry1y1qhnwql8bf83fq-avizo-1.2/lib
Found ninja-1.10.2 at
/gnu/store/yqv6h38aa5809l4d8mz078knwf86mb32-ninja-1.10.2/bin/ninja
phase `configure' succeeded after 1.6 seconds
starting phase `patch-generated-file-shebangs'
phase `patch-generated-file-shebangs' succeeded after 0.0 seconds
starting phase `build'
Backtrace:
In guix/store.scm:
1320:8 19 (call-with-build-handler # …)
In guix/ui.scm:
466:3 18 (_)
In ice-9/boot-9.scm:
1747:15 17 (with-exception-handler # …)
1752:10 16 (with-exception-handler _ _ #:unwind? _ # _)
In guix/ui.scm:
453:6 15 (_)
In guix/scripts/build.scm:
626:5 14 (_)
In srfi/srfi-1.scm:
673:15 13 (append-map _ _ . _)
586:17 12 (map1 ("x86_64-linux"))
In guix/scripts/build.scm:
628:21 11 (_ _)
In guix/store.scm:
1406:5 10 (map/accumulate-builds # …)
1421:15 9 (_ # _ _)
759:14 8 (process-stderr _ _)
In unknown file:
7 (display "@ build-log 4365 150\n[1/11] Generating aviz…" …)
In guix/status.scm:
754:20 6 (write! _ _ _)
In srfi/srfi-1.scm:
460:18 5 (fold # …)
In guix/status.scm:
645:15 4 (_ (build-log 4365 "[1/11] Generating avizo-resource…") #)
179:23 3 (update-build #< building: () downloadin…> …)
In ice-9/boot-9.scm:
1685:16 2 (raise-exception _ #:continuable? _)
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 struct-vtable: Wrong type argument in position 1 (expecting
struct): #f
--
ph,
[0]: https://github.com/misterdanb/avizo
Re: Can't open a container-shell
Forgot the attatchment... On Wed, Mar 2, 2022 at 7:06 PM Cássio Tavares wrote: > > I have created a profile from the attached `manifest.scm`, meant to be > used in a container shell, so as to isolate activity X from the everything > else. After everything was setup, I tried to initiate the shell with this > command: > > guix shell -c 4 -M 6 --no-cwd --pure --container --network \ > --manifest=./etc/manifest.scm \ > --share=./home/sys-conf \ > --user=sys-conf \ > --profile=./home/sys-conf/.guix-profile \ > --preserve='^DISPLAY$' > > > But this doesn't work, and I get this error message: > > guix shell: error: "--profile" can't be used with package options > > > What does this mean? What did I do wrong? And what should I do? > Thanks, > Cássio > > > ;;\ ;; | This is the manifest for the Guix shell environment ;; + (specifications->manifest (list "guix" "bash" "coreutils" "moreutils" "guile" "git" "guile-gitlab" "openssh" "nano" "less" "grep" "exa" "vim" "neovim" "ungoogled-chromium"))
Can't open a container-shell
I have created a profile from the attached `manifest.scm`, meant to be used in a container shell, so as to isolate activity X from the everything else. After everything was setup, I tried to initiate the shell with this command: guix shell -c 4 -M 6 --no-cwd --pure --container --network \ --manifest=./etc/manifest.scm \ --share=./home/sys-conf \ --user=sys-conf \ --profile=./home/sys-conf/.guix-profile \ --preserve='^DISPLAY$' But this doesn't work, and I get this error message: guix shell: error: "--profile" can't be used with package options What does this mean? What did I do wrong? And what should I do? Thanks, Cássio
Re: cannot boot from microSD card on aarch64 machine
Vagrant Cascadian writes: > [[PGP Signed Part:Undecided]] > On 2022-03-02, Ricardo Wurmus wrote: >> I got myself a rockpro64 board. > ... >> So I then decided to build my own system and install a new u-boot onto >> the microSD card. Here’s the system I built: > ... >> (bootloader (bootloader-configuration >>(bootloader u-boot-rockpro64-rk3399-bootloader) >>;; SD card/eMMC (SD priority) storage >>(target "/dev/mmcblk1"))) > > You need to leave a pretty generous gap at the partition table of your > microSD, either a GPT partition table with various partitions for the > various u-boot bits: > > http://opensource.rock-chips.com/wiki_Partitions > > or an MBR partition table with the first partition starting at sector > 32768, and the previous sectors empty. > > Otherwise, the u-boot installation may clobber parts of your partition > table or vice-versa. Do I need to prepare the microSD card at all? There’s no documentation in the manual, so I have no idea what to do with it prior to “guix system init”. Looking at the code I assumed that the disk-image-installer procedures take care of placing whatever blobs are needed at the expected locations. > Also, if you have a different u-boot installed to SPI or eMMC, those > will take priority over microSD on most rockchip platforms. There is no other u-boot installed. The machine does not show any activity when powered on without microSD card. >> (kernel linux-libre) >> (kernel-arguments >>(list "console=ttyS2")) ; UART2 connected on the Pi2 bus > > I assume you're using a serial console. The rockchip platforms usually > default 150 for baud ... usually I use: > > screen /dev/ttyUSB0 150 > > Oh, now that I think about it, you might also want to set the speed for > your console in kernel-arguments: > >(kernel-arguments > (list "console=ttyS2,150")) I’m not yet using a serial console, but I’ll come back to this later if necessary. >> Does it perhaps install the u-boot files at the wrong offsets? How >> would I begin to debug this? > > It is also entirely possible something is wrong with rockpro64 u-boot > offsets or u-boot itself ... been a while since I've tested. Hmm, okay. Thanks for the hints! -- Ricardo
Re: cannot boot from microSD card on aarch64 machine
Efraim Flashner writes: > Are you sure the primary device is /dev/mmcblk1? On my pine64 it's > mmcblk0. There is no /dev/mmcblk0 when I boot either Guix System (from USB) or armbian (from microsd). /dev/mmcblk1 is the microSD card, at least in a booted system. The device name only matters for the installation of u-boot, doesn’t it? It has no impact on any runtime behavior, or does it? > I'd start by putting u-boot and the image on the sd-card and see if Guix > boots up that way. If it works then there's a larger chance there's a > mistake somewhere in a config. Okay. > Perhaps you need to mark the USB drive as a dependency for your root > partition? I don’t want to boot from USB going forward. I only do this so the microSD card is not used for the system. I want to have u-boot on the microsd card and then boot the system from SSD. > Actually, better idea. Try it with linux-libre-arm64-generic for the > kernel. I haven't tried recently but in the past I haven't been able to > use the linux-libre kernel with my pine64 and needed the arm64-generic > version. Okay, I’ll do that. At least I know that this one works, because that’s what the pinebook pro image uses — and that one works fine (from USB). But at this point I’m not even complaining about the kernel, because nothing at all happens when I power on the machine. U-boot does not seem to start. -- Ricardo
Re: Nix programs on path but not found
Stefan Baums writes: > I am running Guix with EXWM. Prior to Guix, in Ubuntu, I used > ~/.xinitrc to set some environment variables and run some startup > programs. Since this is apparently not read in Guix+EXWM, I put > the following at the top of my ~/.exwm instead: > > ...snip... > > From ansi-term and from async-shell-command, I am now also able to > run programs installed in my Nix profile (e.g., onboard), but NOT > from eshell (even though PATH is there shown as above), and NOT > from the .xinitrc invoked from my .exwm startup script. > > Does anybody what is going on here, and how to fix it? I'm not sure what is happening in your particular case, but I am also using Guix with EXWM (and have been doing so for several years now). What I do for setting up my environment is this: 1. Declare environment variables in ~/.bash_profile (source ~/.bashrc from here as well). 2. Declare aliases in ~/.bashrc. 3. Set up my X environment (with xsetroot, xset, setxkbmap, xrdb, etc.) in ~/.xsession. End the ~/.xsession file with "exwm" on the final line. 4. Put my Emacs configuration in ~/.emacs.d/init.el. 5. Put my EXWM configuration in ~/.exwm. 6. Put my eshell aliases in ~/.emacs.d/eshell/alias. When I log in via Guix's graphical login prompt, each of the files I listed above are executed in the order that I named them. All environment variable settings from my ~/.bash_profile are inherited by all shells (including eshell) in Emacs. Have fun and happy hacking! Gary -- GPG Key ID: 7BC158ED Use `gpg --search-keys lambdatronic' to find me Protect yourself from surveillance: https://emailselfdefense.fsf.org === () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments Why is HTML email a security nightmare? See https://useplaintext.email/ Please avoid sending me MS-Office attachments. See http://www.gnu.org/philosophy/no-word-attachments.html
Re: cannot boot from microSD card on aarch64 machine
On 2022-03-02, Ricardo Wurmus wrote: > I got myself a rockpro64 board. ... > So I then decided to build my own system and install a new u-boot onto > the microSD card. Here’s the system I built: ... > (bootloader (bootloader-configuration >(bootloader u-boot-rockpro64-rk3399-bootloader) >;; SD card/eMMC (SD priority) storage >(target "/dev/mmcblk1"))) You need to leave a pretty generous gap at the partition table of your microSD, either a GPT partition table with various partitions for the various u-boot bits: http://opensource.rock-chips.com/wiki_Partitions or an MBR partition table with the first partition starting at sector 32768, and the previous sectors empty. Otherwise, the u-boot installation may clobber parts of your partition table or vice-versa. Also, if you have a different u-boot installed to SPI or eMMC, those will take priority over microSD on most rockchip platforms. > (kernel linux-libre) > (kernel-arguments >(list "console=ttyS2")) ; UART2 connected on the Pi2 bus I assume you're using a serial console. The rockchip platforms usually default 150 for baud ... usually I use: screen /dev/ttyUSB0 150 Oh, now that I think about it, you might also want to set the speed for your console in kernel-arguments: (kernel-arguments (list "console=ttyS2,150")) > Does it perhaps install the u-boot files at the wrong offsets? How > would I begin to debug this? It is also entirely possible something is wrong with rockpro64 u-boot offsets or u-boot itself ... been a while since I've tested. live well, vagrant signature.asc Description: PGP signature
Re: installing a package not from GNU
Gottfried writes: > I wanted to install a package "gtkhash" which I could not find in GNU > packages. > How can I install it? > After downloading it and trying to install it, it said: unknown package > > guix install gtkhash-1.4 > guix install: Fehler: gtkhash-1.4: Unbekanntes Paket > > > What to do, if I don´t find a package in GNU and I would like to install it? You need to create a Guix package definition for the package you want to install. Assuming you have placed your definition in a file called gtkhash.scm, you can install it with this command: guix package -f gtkhash.scm See the Guix manual for instructions on how to write a package definition. -- GPG Key ID: 7BC158ED Use `gpg --search-keys lambdatronic' to find me Protect yourself from surveillance: https://emailselfdefense.fsf.org === () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments Why is HTML email a security nightmare? See https://useplaintext.email/ Please avoid sending me MS-Office attachments. See http://www.gnu.org/philosophy/no-word-attachments.html
Re: cannot boot from microSD card on aarch64 machine
On Wed, Mar 02, 2022 at 12:37:53PM +0100, Ricardo Wurmus wrote: > Hi, > > I got myself a rockpro64 board. I put armbian > (Armbian_21.08.1_Rockpro64_bullseye_current_5.10.60.img) on a microSD > card to check that it’s all working correctly. Then I downloaded the > latest Guix System image for a pinebook pro and dd’d it to a USB drive. > With the armbian microSD card inserted (which contains an old version of > u-boot) I can boot from USB into Guix System. > > So I then decided to build my own system and install a new u-boot onto > the microSD card. Here’s the system I built: > > --8<---cut here---start->8--- > (operating-system > (host-name "foo") > (timezone "Europe/Berlin") > (locale "en_US.utf8") > (bootloader (bootloader-configuration >(bootloader u-boot-rockpro64-rk3399-bootloader) >;; SD card/eMMC (SD priority) storage >(target "/dev/mmcblk1"))) > (kernel linux-libre) > (kernel-arguments >(list "console=ttyS2")) ; UART2 connected on the Pi2 bus > (file-systems (cons (file-system > (device "my-root") > (title 'label) > (mount-point "/") > (type "ext4")) > %base-file-systems)) > ...) > --8<---cut here---end--->8--- > > The actual system also has one more initrd module, which I can’t > remember now, but that shouldn’t matter. > > I mounted the target disk (an SSD) at /mnt, made sure that the microSD > card was inserted, unmounted, and available at /dev/mmcblk1, and then > ran > >guix system init config.scm /mnt > > This was successful. > > Unfortunately, rebooting failed. There is seemingly no activity at all > when I power on the board, so something’s not right with how u-boot was > installed on the microSD card. > > Does it perhaps install the u-boot files at the wrong offsets? How > would I begin to debug this? > > I’d appreciate any hints. Are you sure the primary device is /dev/mmcblk1? On my pine64 it's mmcblk0. I'd start by putting u-boot and the image on the sd-card and see if Guix boots up that way. If it works then there's a larger chance there's a mistake somewhere in a config. Perhaps you need to mark the USB drive as a dependency for your root partition? Actually, better idea. Try it with linux-libre-arm64-generic for the kernel. I haven't tried recently but in the past I haven't been able to use the linux-libre kernel with my pine64 and needed the arm64-generic version. -- Efraim Flashner אפרים פלשנר GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted signature.asc Description: PGP signature
Re: Guix website and CI is unavailable in Russia
Hi! I'm sorry to hear that you can't access the ci. At least, I don't think it's an intentional block from the Guix project. The website and ci are located at the MDC, in Berlin. We also have a second official build farm in Bordeaux, France. If you don't have it already configured, try it: https://bordeaux.guix.gnu.org. Now if Russia decides to create its own great firewall, we might have a solution. There's already a mirror for Chinese users, so we could set one up for Russians if need be. On March 1, 2022 12:21:46 AM GMT+01:00, w...@riseup.net wrote: >Hello. Looks like Guix website (guix.gnu.org) and guix ci in cli (can't >pull and install packages from ci.guix.gnu.org) doesn't work without a >tor for some users from Russia including me. Gnu.org works fine without >a tor. > >The website is not blocked by Russian government (at least looks like >so): > >https://www.isitblockedinrussia.com/?host=guix.gnu.org > >As far as I know they block it by domain address, but I might be wrong. > >I want to ask guix server location and ask is it some kind of ban from >guix server side or not? Maybe guix server provider or government bans >some russian ips now. Everything works fine through tor for me and some >ru users. It would be sad to stop using guix system because of war >issues. > >Also it is kinda related to GNU's freedom #1, because not everyone can >access the code and the compiled software via internet connection: "The >freedom to study how the program works, and change it so it does your >computing as you wish (freedom 1). Access to the source code is a >precondition for this." > >On a related note, do you think it might be a good idea to make offline >guix distribution? Looks like Russia has a danger of internet shutdowns >or china-like internet limitations. It can be organized like >/gnu/sources/ folder with source code of many packages and when package >name is present them, guix would choose to build from source without >trying to connect to the servers or something like it. Just an idea. > >Thanks in advance. > > >
Re: older and newer Versions of IceCat and icedove
Hi, Am 25.02.22 um 19:49 schrieb Gottfried: My answer is under your email: Am 25.02.22 um 16:40 schrieb Martin Castillo: Am 25.02.22 um 15:06 schrieb Gottfried: Sorry, I don't know any further. Try executing /gnu/store/hchyj7faw7f98njsja27i89v3jk7bbqm-icecat-91.6.0-guix0-preview1/lib/icecat/icecat --version and see what it reports. If it says 91.5, I cannot imagine, what causes this. Hi, Today I did a guix pull, guix -u and sudo guix system reconfigure etc/config.scm If I open icecat in the graphical way through an icon it gives me the version 91.5 I'll repeat what I said earlier: I use xfce4-panel, and when I added a firefox starter, it automatically saved the absolute path to the binary. In guix, this means it will always point to that one version. This means, you need to change the path saved inside the icon. I don't know whether you use a starter in xfce4-panel or another way, but try rightclicking it and see, if you find a menu where you can set a commandpath. Then set it to /home/gfp/.guix-profile/bin/icecat. It is currently probably set to /gnu/store/hchyj7faw7f98njsja27i89v3jk7bbqm-icecat-91.6.0-guix0-preview1/lib/icecat/icecat This usability problem stems from the way guix works. One would need to touch these gui softwares to make them automatically run the version of the current guix profile. Icedove starting in the graphical way through an icon it gave me the version 91.5, starting it from the menu and from the terminal it asked me to set up an email address and the following message: (today I downloaded 91.6, so it should open that one, but it didn’t) With the channel and manifest from below I ran $ guix time-machine -C g.channel -- package -m g.manifest $ guix package -I icedove 91.6.1 out /gnu/store/nmlxvxl2640r74fg9mlacmavpwg2n7xa-icedove-91.6.1 $ icedove --version Thunderbird 91.6.1 The installed version is correct. It's just the gui that launches an older version. You can fix that the way I described above. Hth, Martin -- g.channel: ;; Diese Kanaldatei knnen Sie bei 'guix pull -C' oder ;; 'guix time-machine -C' angeben, um die Guix-Version zu bekommen, mit ;; der der Inhalt dieses Profils erzeugt wurde. (list ;; Anmerkung: Manche der Pakete in diesem Profil wurden mit diesen anderen Commits installiert: ;; "33ce3f1c866231a3015411fdce18a3e72649e2f6" ;; "32ccbc3a1ebf62d90f618ababb206df57f7e767b" ;; "dd823172d86f82dedf8b0a7eb65925db4b164d26" (channel (name 'guix) (url "https://git.savannah.gnu.org/git/guix.git";) (branch "master") (commit ;"33ce3f1c866231a3015411fdce18a3e72649e2f6") ; for hchyj*-icecat-* "ed8d236eb938bc123a9ca8a079fea95edf7df6cd") ;for nml*-icedove-* (introduction (make-channel-introduction "9edb3f66fd807b096b48283debdcddccfea34bad" (openpgp-fingerprint "BBB0 2DDF 2CEA F6A8 0D1D E643 A2A0 6DF2 A33A 54FA") g.manifest: ;; Diese "Manifest"-Datei kann an 'guix package -m' bergeben werden, ;; um den Inhalt Ihres Profils nachzubilden. Sie ist "symbolisch", ;; gibt also nur die Namen der Pakete an. Um genau das gleiche Profil ;; herauszubekommen, mssen Sie auch die verwendeten Kanle ;; nachbilden, wie "guix describe" sie anzeigt. Siehe den Abschnitt ;; "Guix nachbilden" im Handbuch. (specifications->manifest (list "icedove" ;"icecat"))
Re: Guix website and CI is unavailable in Russia
I don't know anything about gnu.org's availability, but if you want to download sources ahead of time you can do so with the guix build --sources flag. It will download the source of a package or derivation and put it in the store. For instance, you could download the sources of a package manifest and all of its transitive dependencies with the following: guix build --sources=transitive --manifest=manifest.scm I'm not sure how something fully offline would work though, as the sources for all Guix packages would take up a massive amount of disk space. The number of packages each person would want offline would also depend on how much disk space they are willing to give up. w...@riseup.net writes: Hello. Looks like Guix website (guix.gnu.org) and guix ci in cli (can't pull and install packages from ci.guix.gnu.org) doesn't work without a tor for some users from Russia including me. Gnu.org works fine without a tor. The website is not blocked by Russian government (at least looks like so): https://www.isitblockedinrussia.com/?host=guix.gnu.org As far as I know they block it by domain address, but I might be wrong. I want to ask guix server location and ask is it some kind of ban from guix server side or not? Maybe guix server provider or government bans some russian ips now. Everything works fine through tor for me and some ru users. It would be sad to stop using guix system because of war issues. Also it is kinda related to GNU's freedom #1, because not everyone can access the code and the compiled software via internet connection: "The freedom to study how the program works, and change it so it does your computing as you wish (freedom 1). Access to the source code is a precondition for this." On a related note, do you think it might be a good idea to make offline guix distribution? Looks like Russia has a danger of internet shutdowns or china-like internet limitations. It can be organized like /gnu/sources/ folder with source code of many packages and when package name is present them, guix would choose to build from source without trying to connect to the servers or something like it. Just an idea. Thanks in advance. [2. image/png; guix.png]... signature.asc Description: PGP signature
Guix website and CI is unavailable in Russia
Hello. Looks like Guix website (guix.gnu.org) and guix ci in cli (can't pull and install packages from ci.guix.gnu.org) doesn't work without a tor for some users from Russia including me. Gnu.org works fine without a tor. The website is not blocked by Russian government (at least looks like so): https://www.isitblockedinrussia.com/?host=guix.gnu.org As far as I know they block it by domain address, but I might be wrong. I want to ask guix server location and ask is it some kind of ban from guix server side or not? Maybe guix server provider or government bans some russian ips now. Everything works fine through tor for me and some ru users. It would be sad to stop using guix system because of war issues. Also it is kinda related to GNU's freedom #1, because not everyone can access the code and the compiled software via internet connection: "The freedom to study how the program works, and change it so it does your computing as you wish (freedom 1). Access to the source code is a precondition for this." On a related note, do you think it might be a good idea to make offline guix distribution? Looks like Russia has a danger of internet shutdowns or china-like internet limitations. It can be organized like /gnu/sources/ folder with source code of many packages and when package name is present them, guix would choose to build from source without trying to connect to the servers or something like it. Just an idea. Thanks in advance.
missing files from aspell-dict package
I have installed the latest versions of aspell & aspell-dict-en via guix on a foreign distro: > guix package --list-installed=aspell\* aspell 0.60.8 out /gnu/store/xyz0ljdw4m25k8vhnl8261ywq7dvmr49-aspell-0.60.8 aspell-dict-en2020.12.07-0out /gnu/store/v90ifhzvln0p61i6xpadjj6qvjqvr4sb-aspell-dict-en-2020.12.07-0 However, when recollindex tries to run this aspell command it emits an error: > aspell --lang=en --encoding=utf-8 create master ~/recoll/aspdict.en.rws Error: The language "en" is not known. This is probably because: the file "/gnu/store/xyz0ljdw4m25k8vhnl8261ywq7dvmr49-aspell-0.60.8/lib/aspell-0.60/en.dat" can not be opened for reading. If I add a --data-dir option to point to the aspell-dict-en dir which contains en.dat I get a different error: > aspell --data-dir=~/.guix-profile/lib/aspell --lang=en --encoding=utf-8 > create master ~/recoll/aspdict.en.rws Error: The file "~/.guix-profile/lib/aspell/iso-8859-1.cset" can not be opened for reading. The aspell installation contains cset & cmap files in its lib/aspell-0.60/ subdir, but no dat files, whereas the aspell-dict-en contains dat files but not cset or cmap files. However, aspell expects them to be in the same directory, as they are in the debian aspell package (in /usr/lib/aspell). Joe
Re: Nss libraries not found when using guix pack
On 02/03/2022 10:46, Jean-Christophe HAESSIG wrote: > I tried to deploy Slurm using guix pack : > guix pack -R -S /sbin=sbin -S /bin=bin slurm@19.05.8 nss-pam-ldapd sssd > > User and authentication data comes from ldap (sssd). The libraries are > present but the Slurm binary does not find them, and fails with an > invalid user error. I jumped that hurdle with LD_PRELOAD, but this is not an acceptable fix of course. However, I did that only to realize that Slurm in guix is compiled without mysql support, so I'll need to change the package, which I have never done. I wanted to use Slurm from Guix because Debian does not provide every possible Slurm version. This can be a problem when a Slurm cluster must be upgraded without shutting it down completely. I hoped to gain some independence from my host distribution but it appears that won't be so simple... JCH
cannot boot from microSD card on aarch64 machine
Hi, I got myself a rockpro64 board. I put armbian (Armbian_21.08.1_Rockpro64_bullseye_current_5.10.60.img) on a microSD card to check that it’s all working correctly. Then I downloaded the latest Guix System image for a pinebook pro and dd’d it to a USB drive. With the armbian microSD card inserted (which contains an old version of u-boot) I can boot from USB into Guix System. So I then decided to build my own system and install a new u-boot onto the microSD card. Here’s the system I built: --8<---cut here---start->8--- (operating-system (host-name "foo") (timezone "Europe/Berlin") (locale "en_US.utf8") (bootloader (bootloader-configuration (bootloader u-boot-rockpro64-rk3399-bootloader) ;; SD card/eMMC (SD priority) storage (target "/dev/mmcblk1"))) (kernel linux-libre) (kernel-arguments (list "console=ttyS2")) ; UART2 connected on the Pi2 bus (file-systems (cons (file-system (device "my-root") (title 'label) (mount-point "/") (type "ext4")) %base-file-systems)) ...) --8<---cut here---end--->8--- The actual system also has one more initrd module, which I can’t remember now, but that shouldn’t matter. I mounted the target disk (an SSD) at /mnt, made sure that the microSD card was inserted, unmounted, and available at /dev/mmcblk1, and then ran guix system init config.scm /mnt This was successful. Unfortunately, rebooting failed. There is seemingly no activity at all when I power on the board, so something’s not right with how u-boot was installed on the microSD card. Does it perhaps install the u-boot files at the wrong offsets? How would I begin to debug this? I’d appreciate any hints. -- Ricardo
Nss libraries not found when using guix pack
Hi,
I tried to deploy Slurm using guix pack :
guix pack -R -S /sbin=sbin -S /bin=bin slurm@19.05.8 nss-pam-ldapd sssd
User and authentication data comes from ldap (sssd). The libraries are
present but the Slurm binary does not find them, and fails with an
invalid user error.
Excerpt of strace :
pid 22647] openat(AT_FDCWD,
"/gnu/store/rkimbfkypl6gp6sjdjrv1lm1cn3q9xfa-slurm-19.05.8/etc/ld.so.cache",
O_RDONLY|O_CLOEXEC) = 3
[pid 22647] newfstatat(3, "", {st_mode=S_IFREG|0444, st_size=8796, ...},
AT_EMPTY_PATH) = 0
[pid 22647] mmap(NULL, 8796, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fadd528e000
[pid 22647] close(3)= 0
[pid 22647] openat(AT_FDCWD,
"/gnu/store/5h2w4qi9hk1qzzgi1w83220ydslinr4s-glibc-2.33/lib/glibc-hwcaps/x86-64-v2/libnss_ldap.so.2",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
[pid 22647] newfstatat(AT_FDCWD,
"/gnu/store/5h2w4qi9hk1qzzgi1w83220ydslinr4s-glibc-2.33/lib/glibc-hwcaps/x86-64-v2",
0x7ffd828d0b60, 0) = -1 ENOENT (No such file or directory)
[pid 22647] openat(AT_FDCWD,
"/gnu/store/5h2w4qi9hk1qzzgi1w83220ydslinr4s-glibc-2.33/lib/tls/x86_64/x86_64/libnss_ldap.so.2",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
[pid 22647] newfstatat(AT_FDCWD,
"/gnu/store/5h2w4qi9hk1qzzgi1w83220ydslinr4s-glibc-2.33/lib/tls/x86_64/x86_64",
0x7ffd828d0b60, 0) = -1 ENOENT (No such file or directory)
[pid 22647] openat(AT_FDCWD,
"/gnu/store/5h2w4qi9hk1qzzgi1w83220ydslinr4s-glibc-2.33/lib/tls/x86_64/libnss_ldap.so.2",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
[pid 22647] newfstatat(AT_FDCWD,
"/gnu/store/5h2w4qi9hk1qzzgi1w83220ydslinr4s-glibc-2.33/lib/tls/x86_64",
0x7ffd828d0b60, 0) = -1 ENOENT (No such file or directory)
[pid 22647] openat(AT_FDCWD,
"/gnu/store/5h2w4qi9hk1qzzgi1w83220ydslinr4s-glibc-2.33/lib/tls/x86_64/libnss_ldap.so.2",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
[pid 22647] newfstatat(AT_FDCWD,
"/gnu/store/5h2w4qi9hk1qzzgi1w83220ydslinr4s-glibc-2.33/lib/tls/x86_64",
0x7ffd828d0b60, 0) = -1 ENOENT (No such file or directory)
[pid 22647] openat(AT_FDCWD,
"/gnu/store/5h2w4qi9hk1qzzgi1w83220ydslinr4s-glibc-2.33/lib/tls/libnss_ldap.so.2",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
[pid 22647] newfstatat(AT_FDCWD,
"/gnu/store/5h2w4qi9hk1qzzgi1w83220ydslinr4s-glibc-2.33/lib/tls",
0x7ffd828d0b60, 0) = -1 ENOENT (No such file or directory)
[pid 22647] openat(AT_FDCWD,
"/gnu/store/5h2w4qi9hk1qzzgi1w83220ydslinr4s-glibc-2.33/lib/x86_64/x86_64/libnss_ldap.so.2",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
[pid 22647] newfstatat(AT_FDCWD,
"/gnu/store/5h2w4qi9hk1qzzgi1w83220ydslinr4s-glibc-2.33/lib/x86_64/x86_64",
0x7ffd828d0b60, 0) = -1 ENOENT (No such file or directory)
[pid 22647] openat(AT_FDCWD,
"/gnu/store/5h2w4qi9hk1qzzgi1w83220ydslinr4s-glibc-2.33/lib/x86_64/libnss_ldap.so.2",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
[pid 22647] newfstatat(AT_FDCWD,
"/gnu/store/5h2w4qi9hk1qzzgi1w83220ydslinr4s-glibc-2.33/lib/x86_64",
0x7ffd828d0b60, 0) = -1 ENOENT (No such file or directory)
[pid 22647] openat(AT_FDCWD,
"/gnu/store/5h2w4qi9hk1qzzgi1w83220ydslinr4s-glibc-2.33/lib/x86_64/libnss_ldap.so.2",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
[pid 22647] newfstatat(AT_FDCWD,
"/gnu/store/5h2w4qi9hk1qzzgi1w83220ydslinr4s-glibc-2.33/lib/x86_64",
0x7ffd828d0b60, 0) = -1 ENOENT (No such file or directory)
[pid 22647] openat(AT_FDCWD,
"/gnu/store/5h2w4qi9hk1qzzgi1w83220ydslinr4s-glibc-2.33/lib/libnss_ldap.so.2",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
[pid 22647] newfstatat(AT_FDCWD,
"/gnu/store/5h2w4qi9hk1qzzgi1w83220ydslinr4s-glibc-2.33/lib",
{st_mode=S_IFDIR|0555, st_size=4096, ...}, 0) = 0
[pid 22647] munmap(0x7fadd528e000, 8796) = 0
[pid 22647] openat(AT_FDCWD,
"/gnu/store/rkimbfkypl6gp6sjdjrv1lm1cn3q9xfa-slurm-19.05.8/etc/ld.so.cache",
O_RDONLY|O_CLOEXEC) = 3
[pid 22647] newfstatat(3, "", {st_mode=S_IFREG|0444, st_size=8796, ...},
AT_EMPTY_PATH) = 0
[pid 22647] mmap(NULL, 8796, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fadd528e000
[pid 22647] close(3)= 0
[pid 22647] openat(AT_FDCWD,
"/gnu/store/5h2w4qi9hk1qzzgi1w83220ydslinr4s-glibc-2.33/lib/libnss_sss.so.2",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
[pid 22647] munmap(0x7fadd528e000, 8796) = 0
[pid 22647] poll([{fd=2, events=POLLOUT}], 1, 5000) = 1 ([{fd=2,
revents=POLLOUT}])
[pid 22647] newfstatat(2, "", {st_mode=S_IFCHR|0620,
st_rdev=makedev(136, 0), ...}, AT_EMPTY_PATH) = 0
[pid 22647] write(2, "slurmdbd: fatal: Invalid user fo"..., 62slurmdbd:
fatal: Invalid user for SlurmUser XX, ignored
---
The library exists :
$ find /opt/ -iname 'libnss_sss.so*'
/opt/slurm/gnu/store/g9zf74246si96vhp47cyhkby89gj38py-sssd-1.16.5/lib/libnss_sss.so.2
/opt/slurm/gnu/store/nz0apgr4bxfmd77iijp8jn264c65z4s4-profile/lib/libnss_sss.so.2
--
but is not listed in
/gnu/store/rkimbfkypl6gp
