IRC channel logs
2025-09-12.log
back to list of logs
<FuncProgLinux>nixtrd: I haven't used nix but the four freedoms are a useful ally when learning how to guix. You can find a lot of examples on how to package from source on the main guix repository at gnu/packages/*.scm :) there are also numerous scheme hackers with public configurations that pull sources without necessarily using a channel. <nixtrd>Franciman: thanks, so i can just tell it to fetch from git then? <FuncProgLinux>nixtrd: yes, you can git-fetch, url-fetch or import from some packages registries depending on your needs <FuncProgLinux>I liked that if I'm missing a perl module from CPAN i can always "guix import cpan" and call it a day <futurile>nixtrd: the main experience difference you'll notice is that there are no binary drivers, if you need those you need to use nonguix (do a google search for it). <nixtrd>i think it wouldnt be a problem for my use, at least on my x200 futurile <FuncProgLinux>The manual also has a Nix section, I've enabled it on my system like a month ago but haven't done a single thing to test it. Mainly because idk how2flake <nixtrd>flakes are easy, nix is really easy, so just read some and you will get it, almost forgot that nix is avalable too, could make a flake for somethning like for example neovim nightly <futurile>nixtrd: nice, definitely better if you don't need any drivers! <futurile>I should really take some time to understand flakes - sigh - too much to do <futurile>oh and overlays seemed useful from a dev perspective <nixtrd>futurile: its a 17 y old tinkpad x200, intel duo core cpu, it will be fine <FuncProgLinux>Scheme is fun. Although a bit old for my atom-raised self lol <nixtrd>so used to vim now, so will feel wrong, but its fine <nixtrd> FuncProgLinux: thanks, installing in a vm and saw the emacs window manager option, so going to try that <nixtrd>looks fun, and for now it looks better than nix for me <nixtrd>maybe i should try to use emacs for email etc now <nixtrd>so vim as a editor, emacs as everything else <Guest979>this was just to check it quickly, and i really like it, so will use it for a month on hardware and see how it is <nixtrd>see, it worked!! night and thanks for the help there <postroutine>With the command `guix pack --list-targets`, I get a target `x86_64-w64-mingw32`: Does that mean I can generate an archive with Guix containing softwares that can run on Windows ? <ieure>`guix pull: error: Git error: unexpected http status code: 429' <ieure>I suspect the IP or ASN that machine is on has been shadowbanned. <ieure>This is the only machine I have this problem on, and it's also the only Guix box on that Internet connection. <mange>I assume that's Codeberg's 429 coming through, so it could be non-Guix Codeberg traffic that's rate limiting you. <ieure>The network that's banned is the one that hosts my Cuirass instance. I wonder if its polling contributed to the ban? <ieure>Just wondering if anyone else had seen this / had success getting unbanned. <mange>Is your Cuirass instance getting 429s, too? <ieure>mange, Not sure, I mostly ignore it unless something breaks. <ieure>Heh, well, I stopped it just to see if that made a difference, and now it won't restart. <ieure>Cuirass pulled updates ~2 hours ago. <ieure>zlqrvx, Fix packages that that FTBFS. <simendsjo>What's the best way to "Verified cryptographic signature provided by upstream." for git checkouts? I want to submit a PR, but I'm not sure what to do when it comes to git checkouts. <FuncProgLinux>zlqrvx: I'm fairly new to contributing but I'll keep helping with the MATE Desktop and I'm planning to maintain some desktop xapps in the long term :) <apteryx>ah nice, anthy stops working just when I need it. <futurile>zlqrvx: the simplest way to start if you haven't done any packaging before is to do updates to existing packages; you can also help by reviewing PR's to make sure they work <futurile>zlqrvx: generally people want to "add" packages they care about - but that just means there's more to maintain heh <futurile>zlqrvx: definitely testing/reviewing PR's helps - it stops committers wasting time on PR's that have issues, and if I know a reviewer it helps as I can have trust in them <futurile>zlqrvx: and then after you've packaged / reviewed / become known - you can apply for commit rights - the manual covers it <sneek>Welcome back civodul, you have 1 message! <sneek>civodul, rlb says: the "fluids are GC'ed" test is failing on s390x (64-bit, BE, gcc15), and it succeeds if I add a (sleep 1) just before the (gc), with or without the loop. Any idea why? <charlesroelli>I tried to `guix deploy' a new machine with environment `hetzner-environment-type', and it failed with "Unable to locate package guix". Could this be fallout from Debian removing the Guix package? <janneke>ACTION looks into and prepares a fix for cross-builing automake-1.17 <Deltafire>futurile: looks good, very comprehensive! only think that stuck out to me was "Nul bytes", not sure why it's capitalised and misspelt (null bytes) <identity>not really misspelt, though it is normally capitalized as NUL <identity>‘NUL bytes’/‘NUL characters’ is also kind of redundant <Deltafire>i did a quick search, they seem to be normally referenced as "null bytes" when referring to the 0x00 string terminator <identity>Deltafire: pretty sure NULL in C refers to the null pointer, which is not necessarily represented as zeroes, but NULL = ((void *)0) is always true. in other words, 0 as a pointer is equal to (and in fact is) the null pointer, but 0 as a number (and indeed, the nul character) is not necesarilly equal to NULL <identity>some machines may not represent the null pointer as a zeroed pointer-sized integer: 64-bit CHERI architectures represent pointers as 128-bit integers, with additional 64 bits for carrying runtime pointer provenance <identity>and NULL = 0 assuming the 0 is literal, because it gets coerced to NULL, but a 64-bit integer 0 != NULL <Deltafire>i guess we can say NULL = null pointer and NUL = 0x00 ascii value <abbe>had a memory leak in shepherd :/ <abbe>root 1 7.8 76.5 14184836 6232752 ? Rl ago05 4338:51 /gnu/store/37m0a0ydy74wl2qrf2w1jdgqhxwbaxac-guile-3.0.9/bin/guile --no-auto-compile /gnu/store/zj0fawhffs6h1vcxi8djanjvhjas2v5l-shepherd-1.0.6/bin/shepherd --config /gnu/store/7dv2hq2zp0lxk69kzcnfd5zh0f8i92r6-shepherd.conf <abbe>at guix revision f799d148ad618332d7fa40d1f78184615c8d320f <abbe>i guess before revert of guile-fibers on shepherd, perhaps that was the culprit <Rutherther>abbe: recently there has been update to guile fibers 1.4.0 that should fix a memory leak, so you could try updating. On the other hand with the newer version it seems shepherd sometimes spins processor on 100 % <abbe>yes, I was bit by the latter too, and hasn't happened since we reverted the shepherd in guix to depend on guile-fibers pre-1.4.0 <Rutherther>the revision you're on is from Sep 2nd, this update wasn't in at that time <abbe>guile-fibers 1.4.0 is the "broken" one <abbe>and we reverted back to 1.3.1 <Rutherther>no, it was updated to 1.4.0 like 3 days ago and supposedly fixed reported memory leak <Rutherther>no, I meant 1.4.0, it was updated to 1.4.0 like 3 days ago, it should fix the memory leak. And then reverted due to the spinning <Rutherther>yes, guile fibers was released on august 30, but shepherd package in guix started using it only 3 days ago <FuncProgLinux>futurile: Your new blog post might actually convince me to rewrite some of my perl scripts in guile scheme lol <kestrelwx>Is there something like `rx' for Scheme? Would be nice to have. <identity>kestrelwx: GNU Emacs' ‘rx’ is based on Olin Schivers' Scheme Regular Expressions (SRE for short) :) <Rutherther>when grafing, the length of store path cannot be changed <Rutherther>this is because the strings are directly replaced even in binaries and you would be writing to memory that has different meaning, commonly it could be NULL denoting end of a C string <identity>kestrelwx: also see IrRegex and SRFI 115 <Rutherther>so the version cannot be 1.11.0, because that would make the length of the store path bigger <Deltafire>what about the string-append that isn't appending to anything? <Rutherther>probably an oversight as before it was appending the version <ieure>Deltafire, I agree with you, Y is because of the tangental relationship to Roman numerals. <identity>it also works for getting a fresh (non-literal, mutable) string from a literal string, but i assume this is not what is happening here, and for that you should probably use ‘string-copy’ instead <Deltafire>thanks for clearing that up, i'm now a bit less confused :) <janneke>ACTION rolls guix home back to end of july, hoping to get a functional emacs :-( <nixtrd>how can i install guix on an old tinkpad x200, as it doesnt ahve the drivers for the old intel network card <ieure>nixtrd, It also doesn't have drivers for new intel WiFi cards. <nixtrd>ieure: saw a iso by systemcrafters that says it uses the normal kernel, would that work? <ieure>nixtrd, Kind of, but it comes with some surprising caveats. <ieure>nixtrd, The installer has WiFi, but the installed system does not. <ieure>nixtrd, The simplest way to install Guix is by using a USB WiFi dongle, or the wired tethering mode of an Android phone, and the stock Guix ISO. <nixtrd>ieure: i can work with that, then fix the networking setup after, it's just easier when not in the iso i think. <nixtrd>can i just connect a normal usb c to my phone and to the laptop? <ieure>nixtrd, Yes. Then turn on wired tethering on the phone, and it'll show up as a USB Ethernet device to the laptop. <ieure>You can use it to install and also do whatever setup you want after the installation. <ieure>nixtrd, I would also recommend making yourself an updated installer image, the 1.4.0 ISO is quite old and the Guix infrastructure has changed a bit. You can use Guix on a foreign distro to do that, or run it in a VM and copy the newer image out. <nixtrd>do i need to do anything in the install then, or does it automaticly use it, tried from my pc with an ethernet cable and it said that the network didnt connect to internett <nixtrd>hmm, ok, can try, have guix in a vm <ieure>nixtrd, The online check in the 1.4.0 image is kind of broken. <nixtrd>are there an expleranation on guix.gnu.org for how to make the newer iso <janneke>so...rolling back my guix home to july 22 gives "failed to execute login command"; i'm running exwm <janneke>any idea how to debug this? there's no error in Xorg.0.log, it must be exwm? <ieure>nixtrd, In the installer, you can switch to VT3 and if you have internet (ex. `ping 1.1.1.1' works), you can then `touch /tmp/installer-assume-online' to skip the online check. <ieure>nixtrd, I ran into this last week, too. <ieure>janneke, Anything in ~/.xsession-errors ? <janneke>ieure: nope, that file doesn't exist <ieure>janneke, Does Emacs launch if you log into another session type and run it? <janneke>eh, it runs in the console when i log in <janneke>ACTION doesn't have gdm or sessions or somesuch <janneke>ieure: i've rolled-forward to a guix-home that works... <janneke>...but i wanted a working emacs; esp M-RET and smerge mode, so after a month of struggling i thought: let's roll back a month :) <nixtrd>ieure: i have no idea how to write the file for the iso install there, or is it a command? i usally learn by doing in the system slowly <ieure>nixtrd, You don't have to write a file? Use the gnu/system/install.scm in the Guix source repo. If you don't have a working clone, there's one in ~/.cache/guix/checkouts/ <nixtrd>im too far into the nix mind, where i have to write a iso config to make an iso properly <gabber>janneke: someone called clarkf reported similar (if not the same) issue here ~20hrs ago <ieure>nixtrd, Using this image will make the first `guix pull' on the new machine go *way* faster. <nixtrd>ieure: the installer.scm in gnu in chache? <yelninei>Is guix copy supposed to work with ssh aliases? It works for user and hostname but not for the port ? <nixtrd>ieure: no, couldn't fine one, is the repo linked on the website <nixtrd>installing first with the 1,4 iso the trying to build a new one on the laptop <janneke>starting emacs/exwm from an xterm (via startx) works fine... <janneke>...so possibly something slim related? but i'm only changing my guix home. hmm <FuncProgLinux>MATE has some upstreaming issues to the official mirrors. Would it be wise to move the url's to the main repository tags instead? <FuncProgLinux>AFAIK they have reported on their tracker that the CI/CD pipelines are failing due to some misconfigurations <Tadhgmister>I am trying to run the hello world program in rust and `guix shell rust -- rustc main.rs && ./main` throws either a floating point error or a seg fault.... is there some weird consideration I need to be able to compile a program for local testing in guix? <Tadhgmister>it is literally just `fn main() { println!("TEST!!!"); }` I'm sure I've compiled and tested rust programs outside of the guix packaging system before... <Tadhgmister>huh ok, I guess I need to clean my environment or something ty for info <Tadhgmister>oh WEIRD `guix shell --pure` does work... ok I need to figure out what the heck is going on <Tadhgmister>I think I had incompatible versions of rust-cargo and rust packages installed to my profile, removing them now behaves the way I expect <simendsjo>Even though Codeberg offers a more familiar interface for submitting patches, things like the Change Log in the commit messages just feels dated. With one change per commit, it's just unnecessary duplication. Just submitted 33 commits and found it quite tedious. <simendsjo>... and adding my name with the year to each file I edit. I doubt this will be maintained when definitions move between files. Why not have a global list? But I guess Change Log, Copyright and GNU License header is required by GNU projects? <identity>simendsjo: none of that is “required”, it is mostly convention <Rutherther>simendsjo: are you aware of the etc/committer.scm script?