IRC channel logs
2025-04-15.log
back to list of logs
<potatoespotatoes>Heyo - I'm trying to build an image with a custom uboot (for flashing to an sd card). So far all of my efforts to do this seem to result in only one partition for the image and I'm wondering if there is anything specific I need to do to get the boot partition separated from the root partition <apteryx>hi, I'm trying to use Guix on a scaled (200%) hi-dpi screen and it appears tiny. Has someone found a solution to that yet? <apteryx>oh, we have gimp 3 now. I should update. <PotentialUser-93>but in the doc it says that if it finds a `guix.scm` it will apply it automatically, which it seems to do but still cannot access neither ruby or nano from the guix shell <apteryx>yay, the new Gimp 3.0.0 resolved the scaling problems on a hidpi monitor <apteryx>hm, I can make it segfault pretty easily, by changing the eraser tool brush shape to the rectangular bar; anyone else? <anticomputer>did something change in how hibernation settings work recently? I prefer hibernate to my swap partition and hence have (handle-lid-switch 'hibernate) in my elogind config and that's been working fine until yesterday's channel update and now it's s2idle on lid close (which is too battery intensive on my thinkpad) <anticomputer>don't see anything weird in dmesg just that PM is invoking s2idle on suspend entry <anticomputer>yeah looks like there's a bug in elogind service config, the elogind conf.d files for sleep in my store are all entirely commented out <anticomputer>nope the actual config in the logind environ is proper, well that's annoying, hibernate from cli works fine, elogind's HandleLidSwitch is set to hibernate in the config, but triggers s2idle since this week's update, no config changes otherwise <jlicht>civodul: ah fiddlesticks, that’d be a change to the the build-side code of the node-build-system I’m assuming <PotentialUser-88>Authenticating channel 'sibl', commits e1ee270 to b4b9d2f (4 new commits)... <PotentialUser-88>guix pull: error: commit d6c317d44ef5ba1f50042206787f1a126e35bc8a not signed by an authorized key: F656 64BF 2D60 DA21 095F CA50 7FD2 BABC CDDE 5BF1 <jlicht>sneek: later tell civodul: Some build-side code for the node-build-system changed. I’m guessing all delete-dependencies calls need to be wrapped in a modify-json block. <jlicht>sneek: later tell civodul: in hindsight, that could have been called out in the guix pull news, at least. My bad :/ <csantosb>Hi Guix ! Regarding the /etc/profile.d/zzz-guix.sh I just discovered 🫣, that the binary installer creates in foreign installs, how do we upgrade it ? <csantosb>Asking because I just noticed a couple of obsolete copies; 2.5 Upgrading Guix doesn't mention how to upgrade foreign installs <csantosb>Not sure about running the installer in a previous install. <futurile>csantosb: how did you install on a foreign distro, if you used a package from your distros package manager you should use that <csantosb>futurile: I don't even consider installing using local package manager; always using the binary installer. <futurile>csantosb: I guess an 'upgrade' means just having a new version of the guix binary for root. I don't know how we would change that /etc/profile file <futurile>csantosb: nothing in the issue tracker about it then? <sneek>Welcome back civodul, you have 2 messages! <sneek>civodul, jlicht says: Some build-side code for the node-build-system changed. I’m guessing all delete-dependencies calls need to be wrapped in a modify-json block. <sneek>civodul, jlicht says: in hindsight, that could have been called out in the guix pull news, at least. My bad :/ <civodul>jlicht: never too late for a news entry :-) <csantosb>futurile: I haven't found anything; looking at the log of the installer, f726d616f8 fixes the problem I had yesterday, for example <csantosb>As for today, one needs to copy-paste the relevant section of the installer from time to time to upgrade the zzz-guix.sh file ... <csantosb>In 93be56a3ab it was even partially renamed <csantosb>Not a big deal, but still, worth documenting somewhere <csantosb>Having the "zzz-guix.sh" on the repo, instead of embedded on 'sys_create_init_profile' inside the installer, would help <futurile>csantosb: maybe create an issue. You are actually in a position to test a solution since you're using on a foreign distro - you're a testing unicorn (rare and special!) :-)) <z572>It seems that our git is linked with openssl and the license is incompatible <lee-thomp>where can I find information in the manual on running services as dedicated users? for example if I wanted to run ZNC or Qbittorrent as daemons under their own users respectively <untrusem2>So how to check the overall size of a program installed in guix <ruther`>lee-thomp: unfortunately not really a well supported use case <ruther`>lee-thomp: you basically need to change the shepherd service to set #:user. Changing it involves changing the service-type... so it's a bit more involves, but possible (with leaf services, other services are whole different story) <ruther`>I can share code to do it later today <lee-thomp>I'm anticipating having to write some code up for both, neither ZNC nor qBittorrent have system-level services defined in Guix <ruther`>lee-thomp: ohh. okay then it is quite easy, just setting the #:user argument in the make forkexec. I thought you were talking about changing an existing service <ruther`>lee-thomp: so to answer your original questoion, it should be jn shepherd manual with the forkexec function docs <untrusem2>I can't link devices on signal-desktop installed via either flatpak or guix, It works in my artix linux, is there something I am missing in my guix system, does signal-desktop work for you, if yes, what's your setup? <apteryx>untrusem2: there's no signal-desktop in guix proper; it's probably from a channel such as nonguix. You could check in #nonguix. <lee-thomp>In the manual there's a perfect setup for hacking on Guix, is there something similar for reviewing patches? Before diving in I'm wondering if there's any guidance on something other than manually grabbing contributed patches from the mailing list, applying them and then testing <andreas-e>I think lots of people do different things... <andreas-e>I usually go to issues.guix.gnu.org, click on an issue, and then download the patches to apply. <andreas-e>This is also where you can fill in a review form, if I remember correctly. <apteryx>lee-thomp: one of the easiest way is 'mumi current #xxxxx && mumi am', it usually works and applies the latest revision. <apteryx>it won't work if the patches were submitted as attachments (they need to be in plain git format style, submitted via 'git send-email')) <apteryx>it's very similary to apply patches with 'b4 shazam <message-id>', but with b4 shazam you need to find out the mesage id, which can be done by clicking the 'message-id' button in the issues.guix.gnu.org interface <lee-thomp>apteryx: thanks, I'm checking out mumi now that I've found the manual page (I've been looking at the non-devel manual online), this looks like what I've been after <untrusem2>so is there a comparison between flatpak and guix shell <lee-thomp>untrusem2: flatpak is a tool for distributing applications (and a package repo in flathub) and guix shell is for temporarily adding apps or software to a guix user's current environment <lee-thomp>untrusem2: is there some specific comparison you have in mind? it might be more accurate to compare flatpak and guix as a package manager <identity>or perhaps flatpak as an isolation tool and guix shell's --container option? <lee-thomp>identity: yeah I was thinking that also, though I think guix's containers are more for development sandboxing than flatpak's security-focused sandboxing right? <identity>i mean -C can probably be used either way <lee-thomp>identity: you know what I had no idea about X11 or filesystem sharing to a guix container I thought it was all or nothing <untrusem2> lee-thomp: mostly security and sandboxing comparison <yelninei>civodul: Shepherd does not really become unresponsive, if you give it enough time it will eventually finish and be extremely slow until you stop the syslog again (or run out of patience). but idk how the additional port causes this <sneek>yelninei, you have 1 message! <sneek>yelninei, civodul says: hey, would you like to give a hand with the Hurd on the build farm(s)? we need substitutes :-) <civodul>yelninei: yes, that’s what i meant by “unresponsive” :-) <yelninei>of course , what do you need and how can I export them? I have almost the entire hurd-manifest built (with the little hack for automake). gcc-final seems to be the most fragile one <civodul>yelninei: re the build farm, we have childhurds but they crash after a few builds usually (i don’t have more details) <civodul>so i think a first step would be to add a shepherd timer to restart the ‘childhurd’ service daily on those build machines <civodul>ridiculous, but would allow us to move forward <civodul>second thing would be to see if we can provide a valuable bug report for that crash upstream <yelninei>yeah i have seen that sometimes extracting big tarballs (i.e. gcc) can cause the whole vm to become unresponsive or more accurately if there is a lot of output from the live build log in a short time. Sometimes adding a -v2 helps a bit <lee-thomp>untrusem2: not sure if you'll see this but AFAIK flatpak doesn't run as a container and its security/sandboxing is managed more using Linuxy /stuff/, whereas Guix shell (without --container) has no sandboxing and with --container you get whatever security/sandboxing guarantees you'd typically expect of containers <lee-thomp>also since flatpak is primarily an application technology I think it does a lot for making applications usable i.e. installing .desktop files so you run the app like any other regular app whereas guix shells might be cumbersome to use for day-to-day stuff without some wrapper <lee-thomp>someone might be able to correct me but I don't know if there's some way to get Guix to install an app but only run it in a particular container under certain privileges. Maybe with adding a script to wrap the app to PATH? <lilyp>ahh, yes, torvalds and gpl3, name a more iconic duo <ruther>I submitted a cover letter to patches, and I haven't received e-mail back in more than an hour. Wondering if debbugs is going to ignore it indefinitely or it's going to come through eventually <ruther>in the meantime I answered other issue and mumi shows it already <gabber>has anyone worked with Arduino and/or the like in Guix? <RavenJoad>Would someone take a look at 77448? It's been a week or two and nothing has been sent back my way as a review. <ruther>RavenJoad: I don't really understand why you're adding gcc-toolchain to inputs, isn't that already added always? <ruther>RavenJoad: Apart from that, I think it would be better to use gexps rather than assoc-ref inputs with new packages - meaning to use $(this-package-input "name") <RavenJoad>ruther: The major reason is that souffle needs gcc at runtime too. I'm not 100%, but I think the gcc-toolchain provided by a build-system is part of native-build-inputs, which can be GC'd after building. <ruther>RavenJoad: it's not true that it can be GC'd after build if you reference it. But you're right it's needed then, because of cross compilation. Then the gcc toolchain from inputs and native-inputs differs. <ruther>Lastly I would be a bit skeptical about the wrapping, usually it's better to code the stuff in source. But I can't investigate more thouroughly now and gotta go now. <jmes>Hey folks, is it possible to access the Guix Home generation number during reconfiguration? e.g. One might write the current generation number a program's configuration file <jmes>s/a program/to a program/ <identity>i don't think there's a straightforward way to do that. what would it be when you 'guix home build', which does not create a generation, anyway? <lilyp>you can run a shell script post reconfigure that reads the link :) <lilyp>other than that, nope, you can't do anything of the sort as you're building the profile <lilyp>doing so would quite certainly break reproducibility <jmes>identity, lilyp: thanks, good to know! <jmes>What I'm trying to do is not important anyway. I'm just generating a new wallpaper when I reconfigure and I wanted that to include some text that says "Guix Home Generation <n>"