IRC channel logs
2025-11-06.log
back to list of logs
<pomel0_>hmmm still no `c99` command with that. But ok, I guess I can do `alias c99=gcc` and it should still work, maybe <pomel0_>ah, dumb, the makefile won't read your shell alias :P <ekaitz>pomel0_: CC="gcc --std=c99" make <ekaitz>makefiles normally use CC as a variable you can set <pomel0_>yeah I had to just do CC="gcc --std=c99" <ieure>Sad times when --stds are even spreading to our commandline arguments. <sys-service-ques>ieure thrown out my sleep service abd replaced it with networking "(requirement '(user-processes networking))" ...works <apteryx>Deltafire: I've been experimenting fixing the video issue in IceCat, and perhaps as a quick try for icedove you could try also running it with this environment variable set: MOZ_PERMISSIVE_CONTENT_SANDBOX=1 <apteryx>I saw some tzdata was blocked by the sandbox on IceCat, though it doesn't seem to cause any issue. <tomenzgg>Is it possible to upgrade Home packages with "guix upgrade --profile=" or do all Home upgrades always have to be done through a reconfigure ("guix home reconfigure /path/to/file")? <pomel0_>hi, sorry my phone turned off so I'm joining back not knowing if there's another question before me, but has anyone here had trouble with fonts and how did they fix them? I'm running a build script that requires unifont to be installed, but can't find it even though I did in fact insall it with guix <pomel0_>ok I managed to "fix" in a janky way the font problem, but I have another problem, where the build script is trying to run `cc`, but I don't have that command, I only have `gcc` <pomel0_>anyone knows if I should install another program or is there a way to ln -s my way out of this? <pomel0_>ok... I fixed that, but I realized I have a problem with my channels.scm file... idk how, but .guix-home is now a read only filesystem, so I can't change the channels at all, has this happened to anybody else here? <flurando>hi, does anyone know how to get full screen recording work on guix Gnome Wayland? I have obs installed, and xdg-portal stuff come with gnome-service-type, but not only default Gnome screen recording doesn't work, obs log says pipewire got denied or cancelled by user, so blank screen. I wonder what to do then. <flurando>I'll try to add home-pipewire-service-type to see if that makes a difference. <flurando>Amusing, home-pipewire-service-type requires dbus, which is not documented nor preconfigured <flurando>good, adding home-dbus-service-type and home-pipewire-service-type make both gnome builtin screen cast and obs screen recording work <flurando>A pity that this is not documented (I mean the part "you need pipewire home service and dbus home service to record screen on wayland" <flurando>well, it works, but not in default gnome manner anymore, I have to choose capture device (alsa) to record voice, without the red microphone icon by gnome anymore <flurando>Seemingly from the log and search, this is an error in RTkit. Which, unfortuanlly, is upstream buggy and unsolved, and no corresponding guix definition. <civodul>i feel i’ve been out of touch with IRC lately <civodul>crap, second Emacs/EXWM crash of the week, grr <csantosb>civodul, which emacs are you using exactly ? I'm on emacs-no-x-toolkit. <csantosb>civodul, I'm also using emacs-exwm-no-x-toolkit <cbaines>now begins my fight with the static-networking-servie, and it's not going well... :( <civodul>and i have no clue what’s happening! <csantosb>Ok, I'll switch to your setup, let's see what happens;is it an option for you trying the no-x-toolkit in parallel ? <csantosb>`./pre-inst-env guix build --no-grafts --check emacs-racket-mode` build for me. I'm lost. <ekaitz>Deltafire: reports on the build? <Deltafire>the JS errors are gone, calender opens, 'burger' menu working again <ekaitz>and what's the difference between their lib and ours? <Deltafire>they delete some directories to reduce file size, skip tests, add about 10 patches <Deltafire>there's a .sh file in the firefox source that automates it <ekaitz>did you write this in the issue? i think it's very important to have this information <Deltafire>i was thinking we either use the bundled version, or make our own mozilla-specific icu that could be used for the other gnuzilla apps also <ekaitz>Deltafire: the Guix way i believe is making the mozilla-specific thingie <rekado>is "guix shell -m manifest.scm --with-source=something@0.1=something-0.2.tar.gz" supposed to work? In my tests the "with-source" transformation appears to be ignored. <hanker>I think you should just put `something` instead of `something@0.1` <rekado>tried that, too, but without effect <hanker>Do you put an URL for `something-0.2.tar.gz` ? <rekado>background is: I'm working on GWL and I'd like to build guile-drmaa (currently at 0.1.1) with an unreleased tarball (for 0.2.0). <hanker>i'm not certain `with-source` grabs the file from local filesystem <rekado>no URL, I have the tarball here. I gave it the absolute file name. <rekado>guix build guile-drmaa --with-source=guile-drmaa=/path/to/guile-drmaa-0.2.0.tar.gz works fine <cbaines>I'd maybe try the --with-source bit before -m? <rekado>as does "guix shell guile guile-drmaa --with-source=..." <rekado>I'll try to simplify the manifest first <rekado>weird. This is the manifest: (specifications->manifest (list "guile-drmaa")) <rekado>and this is the command I use: guix shell --with-source=guile-drmaa=guile-drmaa-0.2.0.tar.gz -m m.scm <rekado>the manual says that "guix shell" supports package transformations, but perhaps it doesn't when a manifest is used <sham1>Couldn't you have the package transformation in the manifest? <rekado>but it's not just about getting my work done; looks like a bug to me. <rekado>oh, I accidentally pushed an update to master because I mistyped the AGit command (forgot the "origin HEAD:refs/for/master" thing) <rekado>I haven't broken anything by doing this, but I'd really liked to stick to the review process. <rekado>kestrelwx: nice, I'll install it <Kabouik>I'm having "line xx: [: : interger expression expected" errors when running github.com/sdushantha/tmpmail in Guix. That looks like a Bash/Posix issue. The tmpmail script starts with the #!/usr/bin/env sh shebang. Is there something that could make such a POSIX script unhappy in Guix? <ieure>Kabouik, The script is buggy, the shebang declares /bin/sh which is the POSIX-compliant shell. Then it uses bash features. <ieure>Change the `sh' to `bash' and I suspect it'll work. <Kabouik>Hum, but I tried to change the shebang to declare Bash instead and that didn't work. I think I used this script already in the past, before I was on Guix, so I assume this may have been related. Maybe I just used an earlier commit that was less bugged. <ieure>Do you get the same error with the updated shebang? <ieure>Okay, then either the script is buggy in a different way, or isn't accounting for some Guix behavior. <ieure>You can file an issue upstream, or debug it yourself. Add -x to the shebang (so `#! /usr/bin/env bash -x') and it'll print a full trace as it runs, so you can figure out what's going wrong. <Kabouik>Removing the shebang altogether and then running `bash tmpmail` generates the same errors. <ieure>You don't have to remove the shebang to run it with `bash tmpmail' FYI. <rkazak>when using the "--development" option with "guix shell", what controls the tools that are included within the environment? <ieure>The packages you specify, and the inputs they specify. <ieure>Blah... zfs won't build against Linux 6.17, it's not supported. Our zfs package is the current version, so I guess it's just unsupported. <ieure>6.16 got removed, guess back to LTS for me on anything I need ZFS on. <untrusem>I am also using btrfs, but no subvolumes :( <untrusem>I didn't know about those at the time of installing <rkazak>is "guix environment" still being deprecated? <graywolf>Out of curiosity, do you have a specific need not fulfilled by `guix shell'? <rkazak>No I was just reading the docs and saw that 'old' notice. <rkazak>just going through docs seeing what is there :) <ieure>Deltafire, Not sure I trust btrfs with the stuff I use ZFS for, which is critical system backups. And TV shows. <ieure>Had a disk in my pool fail earlier this year. Bought bigger and less failed ones, then rotated new disks into the pool one at a time. Pretty good stuff. <graywolf>btrfs (if one stays away from raid56) is pretty solid these days <ieure>Yes, I've heard that, but I've also heard things like "the build farm is broken because we have to btrfs balance and it's killing IO, stalling every process." <ieure>So, feeling pretty okay about where I landed. <graywolf>oh, yeah, there is that, btrfs balance hurts, luckily on properly sized fs it is not necessary often (array size 141.88TiB for now) <graywolf>But if zfs works for you, that is great :) I admit I am scared of having to depend on out-of-tree modules for critical filesystem <ieure>That's a hefty array! I have just under 90tb of disk (4x22TB), but a bit under half that usable after parity and overhead. Running raidz2, which is probably overkill, but I really don't want to lose anything. <graywolf>I run raid1 for data, and raid1c4 for metadata. So yeah, slightly under half as well. I probably should get another drive soon, but need to sort out sata ports first. :/ consumer-grade hardware is *not* design with data hoarding in mind <ieure>I've been thinking about my next build, but no decisions yet. Need minimum 6x 3.5" SATA bays, but 8 would be nice. And NVMe for the OS. <graywolf>I am very happy with the case, best one I have owned up to this day <ieure>I guess since everyone uses phones now, there's not much market for undistinguished utilitarian beige boxes. <graywolf>yeah it's bit pricy for sure, but one can actually see some thought was put into designing it, easy to open, swap drives, etc. <ieure>The whole computer running my homelab cost less than that case :( <graywolf>Also, it is surprisingly silent, given that it has 8 WD RED drives and was living next to the sofa for past few years :) <ieure>I can afford it, I'm just a perennial cheapass and don't like to. <ieure>That's good to hear. Or uh... not hear, in this case. <graywolf>I mean, realistically the drive very quickly become the biggest expense anyway ¯\_(ツ)_/¯ <ieure>Oh yeah, my first real home NAS build was a $60 used HP ProLiant and $1000 of disks. <ieure>But both those felt worth it, you know? <cdegroot>I heard ZFS is great but LVM+ext4 works and works everywhere and is good enough for me :) <ekaitz>apteryx: did you see Deltafire 's findings about icedove? <graywolf>My problem with ext4 (and xfs for that matter) is lack of checksums on (meta)data. But I never gave a try to dm-integrity, just having it in a file system seemed... easier. <Deltafire>i'm not convinced checksums are required, since the drive hardware has its own checksum <ieure>Deltafire, That protects against different failures. <ieure>Drive checksum ensures what's on disk is what it received, not that what it received is correct. The checksumming on the host is what makes sure the drive got the correct data in the first place. And ECC RAM makes sure the data being checksummed isn't corrupt in memory. <graywolf>huh, I cannot busybox cannot extract guix-pack tar <tesseract>is it ok to do guix pull every day on a foreign distro <rkazak>depends how "current" you want to be? <trev>tesseract: never hurts to just pull when you need something (until it does hurt) <ngz>Hello. I’m looking for the pyside6-uic tool in Guix repository, but I can’t find it. There is python-pyside-2-tools for PySide2, which includes uic, but no equivalent for PySide6. Am I missing something? <civodul>branch, “Request for merging”, wait? <civodul>i know it’s the theory, but clearly doesn’t scale <ngz>ieure: I’m going to check, but I think I looked at it already and couldn’t find the uic tool. <ieure>Been a good while since I was up in any of that, but uic = user interface compiler, right? I think? <ngz>ieure: I have no idea, a package I want to update is just complaining about it. <ieure>ngz, Sounds like you're missing whatever qt input has that. <ngz>Nope, "error: [Errno 2] No such file or directory: 'pyside6-uic'".