IRC channel logs
2025-11-02.log
back to list of logs
<padtole>going to see if i can libreboot this system <meaty>just did a pull, linux building time... <meaty>is there a way to make the guile compilation cache more git-aware? like, keep seperate caches for each branch <ieure>meaty, I know some folks use Git worktrees to solve that problem. <apteryx>meaty: you can use the 'git rebase HEAD dest-branch' trick to avoid invalidating the .go files, assuming your current branch is newer than the target branch <apteryx>or maintain distinct git worktrees, as mentioned by ieure <apteryx>why are files I create under /tmp read-only by default? user mask? <apteryx>actually, it's an Emacs things; If I visit a new file under /tmp/, Emacs makes it read-only by default. Weird. <meaty>What's the quickest way to test a service <meaty>isn't there a way to "directly" put a scheme file into the running shepherd <flurando>Does anyone know how to delete root CA for icecat or firefox? I have already tweaked nss-certs and verified /etc/ssl/certs fine, but in icecat/firefox, the buildin CA manager still shows full version of nss-certs stuff, and the delete/untrust does not work at all. <apteryx>icecat currently bundles its own nss, so it's likely baked in <apteryx>maybe librewolf does better (it unbundles it) ? <apteryx>but I wouldn't be surprised if it still bundled the cert despite using a system-provided nss <flurando>but there is a lot of commented unbundle me in inputs, and --use-system-nss passed in icecat-minimal recipe <flurando>I wonder whether just tweaking nss-certs (which modifies /etc/ssl/certs) is not enough <flurando>well , correct, icecat bundles nss-rapid when it says unbundle me nss... <flurando>they closed the issue because "there is no existing issue" for using guix's nss and nspr to build firefox... <flurando>But this makes tweaking hard, if I would like to customize nss-certs, I would have to customize every mozilla related browser definition! This is an issue... <flurando>and every time I want to change system cert store, instead of generating a new /etc/ssl/certs with nss-certs package, I would have to rebuild icecat, firefox(sorry, but I do use this for testing), icedove and ephipany? <flurando>Maybe we can exclude the use of nss certs bundled in nss when building, and add p11-kit for configuring security device with p11-kit-trust.so, no idea if this could work and how though <sham1>Hmm. One of these days I reckon that I should probably report the bug in our /etc/profile that doing /etc/profile.d/*.sh doesn't work on zsh when the glob matches nothing. Damn nullopt <luca>Hi, has anyone experienced `guix pull: error: Git error: SSL error: syscall failure: Resource temporarily unavailable` ? It happens to me when I try to pull from a mirror of guix.git <luca>git cloning the repo manually from the mirror works, so I believe this may be a guix issue <sneek>yarl, futurile says: hey I've responded to your email, I need Tanguy to confirm the address just to be certain <yarl>Does the "agit workflow" works? <yarl>I probably did something wrong <yarl>I am not sure what I must have for the Refspec <identity>git push origin HEAD:refs/for/master # note refs/for/master, there is no main <yarl>identity: Ok, that was simple... but there is the "commit ... lacks a signature" error now. <luca>I don't think you as a contributor should be required to sign commits <Rutherther>yarl: you have old pre-push hook then, remove .git/hooks/pre-push <Rutherther>luca: I get the same error as you, after 45 seconds. It seems to be a timeout of sort. I cannot really git clone from that https url, it hangs for quite a long time for me without showing any progress. What seems to work is git://lucamatei.com/guix.git that somehow has lower latency <luca>`git clone` from a terminal fails for you? Hmmm. Thanks! <Rutherther>so both git clone and guix pull from git://lucamatei.com/guix.git actually do something, but I didn't leave it to clone the whole repo <vhns>Is it seen as wrong to specify commites in a channel's .guix-channel file? is it better to have something like a pinned.scm file that can be used? <Rutherther>home-service-que: that url is the default url guix uses, it's hardcoded in guix source. Any other url is treated as a 'mirror' by the warning logic <Rutherther>luca: yes indeed that's the default url that it compares with and anything else is a 'mirror' for it <Rutherther>home-service-que: yes, pretty much. Of course that once was the default url so at that point, it didn't produce that warning <sneek>montokapro, you have 1 message! <sneek>montokapro, lfam says: I think you can set #:ruby to a package variable name in your package's arguments field. Similar to how #:python can be set, and of which there are lots of examples <montokapro>guix import --insert=montokapro/par-lang.scm crate --lockfile=../../rs/par-lang/Cargo.lock par-lang <montokapro># guix package: error: =>: bad use of '=>' syntactic keyword <rrobin>montokapro: can you share the contents of the file, looks like something went wrong there <rrobin>nothing else on the top? - like some use-modules stuff <rrobin>wild guess - you are missing some imports/use-modules there <rrobin>what crate are you importing - we can turn this into a pair importing game <montokapro>Okay! I'll try copying over some imports from the gnu rust-apps package until things compile <montokapro>If anyone has examples of how to use guix import to create standalone package files, I'm all ears! Been using guix for years but never quite figured out how to hack effectively using imports haha <rrobin>that sounds like a dependency that should have been put there by the --insert import command <rrobin>or maybe you are just unlucky and picked a tricky crate :) <rrobin>what rust crate are you trying to import <montokapro>yeah it was, it is line 3 or the original file I posted. Moving that whole block to the end of the file wasn't enough <montokapro>par-lang is the crate. I could try starting with a simpler one to nail down the process <rrobin>is it in crates.io, I can't seem to find it <rrobin>still failing to build though - but it got to the build phase <montokapro>That's awesome... seems like the import was pretty close _fingers crossed_ <rrobin>something funny happening - failing to find dependency, but it is listed in inputs <montokapro>I noticed that with a hello-world package I tried as well... <montokapro>`guix package: error: cannot install non-package object: #<unspecified>` <rrobin>ah that is different - did you try to use -f and forgot to leave a variable at the end? <rrobin>ah ups there is a mistake in my file :D <rrobin>the inputs line wrong - should be (inputs (cargo-inputs 'par-lang)) <montokapro>Comparing to your file I have a few steps I still need to do, so yeah - it's on my end <montokapro>note: if you need to support cargo 1.38 or earlier, you can symlink `config` to `config.toml` <montokapro>location searched: directory source `/tmp/guix-build-par-lang-2e6049ebd60087c6f9f4271adbe8cae34fbe7263.drv-0/source/guix-vendor` (which is replacing registry `crates-io`) <montokapro>required by package `par-lang v0.1.0 (/tmp/guix-build-par-lang-2e6049ebd60087c6f9f4271adbe8cae34fbe7263.drv-0/source)` <montokapro>As a reminder, you're using offline mode (--offline) which can sometimes cause surprising resolution failures, if this error is too confusing you may wish to retry without the offline flag. <montokapro>rrobin mind if I package up your work into a tutorial of sorts? I'll follow the same process with a simpler package <montokapro>Then I'll post it and maybe some guix folk will post it for some simple folk like me to understand and use :) <rrobin>sure - i'm still facing the same issue, i feel like i messed up in some silly way - it just to find a dependency <rrobin>mmmm, the guix-vendor folder in the build is empty that is strange <rrobin>i have a work around here - it is building - and I just realized this thing is not small :D system load average is pretty high right now <rrobin>other than that weird issue - the only thing is the dependency on openssl that needs to be added to inputs <montokapro>At least it is a very straightforward workaround. Building it now <rrobin>clearly i need to go and read on cargo-inputs <montokapro>Well, for someone like me this is very helpful. I'll write up that tutorial from the prespective of a lay person (with workarounds and all) and get it reviewed by the community, likely in this channel. Maybe I'll fix one or two along the way _shrug_. <meaty>There must be a better way then writing a whole system config/spooling up a VM? <ieure>I usually test them on bare metal, and roll-back/delete the generation if it doesn't work. <rrobin>the problem i had with containers was that some errors were sent to console but not logs (still need to check why) <rrobin>also my container setup was different - instead of guix system container i just used system image and podman (for rootless) <rrobin>also another caveat if you service using least authority to setup a container, not sure if there is a way for that to work <meaty>hmm... ok. I think what I'll do is use the %test-os (i think that was what it was called) to write a small system def and use that to make quick VMs <meaty>Does anyone know if there's an example anywhere in the codebase of a service action that sends a line to the process' stdin?