IRC channel logs

2026-01-02.log

back to list of logs

<oliverD>I
<oliverD>* I'm having difficulties with some packages `guix install torbrowser` gives error: unknown package
<oliverD>And so I tried installing dpkg, but it gives the error unable to access the dpkg database directory [...]/var/lib/dpkg: Read-only file system
<oliverD>in the gnu/store directory
<oliverD>when i try to install anything
<radhitya>time to guix pull
<oliverD>Thanks, I found the problem yesterday I did guix pull in root (after su -) and tried to install torbrowser in my user profile.
<oliverD>(for some reason I thought that would work)
<ieure>oliverD, You should basically never run `guix pull' as root.
<kaizer>ieure: What if it's on a server? Can't you just wing it?
<ieure>kaizer, It still doesn't make sense to pull as root on a server. I don't know what you mean by "wing it."
<ieure>kaizer, Every user has their own Guix -- meaning channel state and `guix' binary built from that. Pulling as root doesn't update the system, it updates the root user's guix. And there's no reason to use that, so there's no reason to pull as root.
<ieure>Pull as user, `sudo guix system reconfigure'. That's the typical way you want to do things.
<kaizer>ieure: I agree with you, that's how it should be done and for security best practices you need to have a dedicated user on the server. However, if you're feeling a bit lazy or a bit adventerous, you can just use root like any other user if you're careful. It'll save you like 3 commands...
<ieure>There are way more entertaining bad ideas, IMO.
<csantosb>Good morning Guix, how can one know more about #:modules and #:imported-modules ? I'm basically blindly copy pasting things around
<csantosb>This is accepted, `#:modules '((guix build gnu-build-system)(guix build utils))`
<csantosb>This is not `#:modules '((guix build gnu-build-system)(guix utils))`, ???
<Rutherther>not accepted in what sense?
<csantosb>Copy-paste in the arguments of the parallel package, then build it
<csantosb>s/parallel/abc
<yelninei>janneke: Hi, do you remember why you filtered out some of the guix dependencies in the hurd manifest? Can these be removed with https://codeberg.org/guix/guix/pulls/5308 ?
<yelninei>janneke: With the other change fixing the libgit2 tests on 32bit systems i can finally build the guix package, however guile ooms at ~90% of compiling.
<janneke>yelninei: we filter-out linux-specific dependencies
<janneke>the guix package has something like
<janneke>,@(if (target-hurd?)
<janneke> '()
<janneke> `(("guile-avahi" ,guile-avahi)))
<yelninei>janneke: linux specific should only be guile-avahi and slirp4netns, not po4a,graphviz and locales
<janneke>yelninei: right...i'm not sure about those; i guess because they're not essential/optional and either didn't build, or were very expensive to build
<janneke>the reason for the devel-hurd* templates is to be able to build the a guix git checkout, on the hurd, and thus work on hurd package builds using ./pre-inst-env guix build ......
<janneke>it could even be that i used guix shell --bootstrap as to not having to build guile natively...but i really don't remember; i would have thought that guile would build on the hurd...
<yelninei>they don't build currently I am addressing that :) , but also they are a bit expensive because they depend on boost, doxygen, glib.
<yelninei>would it make sense to not remove them in etc/manifests/hurd to let ci at least try to build them + their dependencies?
<janneke>right; yes i guess that makes sense
<janneke>at least, if we (you) have any hope of actually building them some time (soon)
<janneke>as long as we know they will fail for the coming years...
<yelninei>see the pr i linked above :)
<janneke>...in that case better let them out
<janneke>right :)
<yelninei>guile itself is fine it is just that (on 32bit) running make (or guix build guix) there are a lot of " Repeated allocation of very large block" warnings and eventually "GC Warning: Failed to expand heap by 64 KiB
<yelninei>GC Warning: Out of Memory! Heap size: 2360 MiB. Returning NULL!
<yelninei>Warning: Unwind-only out of memory exception; skipping pre-unwind handler"
<test202020>hello everybody. how to right use guix edit command? this open read only file, but what that mean? i can change dire
<identity>test202020: you need to put the packages in $GUIX_PACKAGE_PATH or use the --load-path option, see (info "(guix) Invoking guix edit")
<ngz>Hello. Do you have any example of use for `home-shepherd-transient-service-type' and `home-shepherd-timer-service-type'? The Guix manual is rather terse on the topic.
<test202020>identity: this must be git repo of guix?
<identity>ngz: i think (info "(shepherd) Transient Service Maker") and (info "(shepherd) Timer Service") have what you are looking for
<identity>test202020: not necessarily, you just need point to files that define packages
<test202020>i think to modify package in guix repo, finding way how to use guix refresh too. I can clone repo from my checkout or need to create another directory from remote git?
<ngz>identity: I’m probably missing something, but I’m looking for some configuration to put into my Guix Home, while the documentation you mention only shows commands to be executed in the shell.
<ngz>identity: More accurately the Guix manual illustrates how to use `home-shepherd-service-type' to create a new timer (albeit it doesn’t make use of home-shepherd-timer-service-type), but there is nothing similar for transients. In particular, I’d like to autostart some command from a Guix Home configuration.
<identity>ngz: …so did you read the last part of (info "(shepherd) Transient Service Maker")?
<identity>hm, okay, sorry, i think i misunderstood
<identity>you are looking for one-shot services
<identity>so you want a service with #:one-shot? #true
<identity>but if you really are looking for a transient service, make that #:transient? #true
<identity>(info "(shepherd) Defining Services")
<ngz>indentity: Thanks. I kind of get this, but I was expecting that `home-shepherd-transient-service-type' would provide a shorthand to run a command (in my case, I want to run Davmail in the background). Also, this documentation is not specific to "home-shepherd-transient|timer-service-type".
<ngz>IOW, what I’m looking for is an example which would look like the following: (simple-service 'whatever home-shepherd-transient-service-type ... something to do here...). I assume it was obvions for the person who introduced home-shepherd-transient-service-type, but it isn’t, IMHO.
<ngz>obvious*
<identity>ngz: you can not extend those services, you need to create a new one
<ngz>identity: OK so it would be (service (home-shepherd-transient-service-type (list (shepherd-service …)))), am I right?
<identity>ngz: no, you *need to create a new service*
<identity>as in, a new service-type
<abbe>Hi, how do I go about disabling a kernel configuration option in default guix configuration ? configuration option in the question: CONFIG_CFG80211_REQUIRE_SIGNED_REGDB
<ngz>identity: Then what home-shepherd-transient-service-type is for?
<identity>or, i guess, you do not need a new service-type, you can just create a new service directly with the shepherd-service constructor
<identity>ngz: for the ‹spawn› action
<identity>sorry, no, the -type is for specifying service dependencies requirement
<identity>the system service depends on ‘user-processes’ while the home service does not
<ngz>I saw that in the source code, but somehow, that didn’t help me :)
<identity>just create a new service with #:one-shot? #true
<cbaines>efraim, I think there's an issue with default-guile-json in (guix build-system cargo), should it be cargo-guile-json?
<identity>this is definitely going to be easier than figuring out if there is some magical way that would make it easier
<moe>Guys
<ngz>identity: I assume creating a new service doesn’t mention home-shepherd-transient-service-type at all? So the documentation may be lacking (i.e., a bug) in that area.
<identity>ngz: why would it?
<ngz>identity: Why would the new service use home-shepherd-transient-service-type? No idea. The point is I’m failing to find any example making use of this service type. Shouldn’t there be at least an example in the manual?
<moe>Is there no binaries on guix
<ngz>identity: But it’s probably me misunderstanding that service stuff.
<identity>ngz: this service type, effectively, has no uses apart from instantiating, which is done in %base-home-services
<ngz>That makes sense.
<identity>and, i think, the system version is instantiated in %base-services
<ngz>identity: So I just use (service '(davmail) #:start ... #:stop (make-kill-destructor) #:respawn? #t) and home-shepherd-transient-service-type would take care of it?
<identity>ngz: what do you mean? you just put (service '(davmail) … #:one-shot #t) in the services list and your user shepherd takes care of it
<identity>why does it need to be a one-shot service anyway?
<ngz>I never talked about one-shot services, did I?
<identity>or a transient service, whatever
<ngz>It is the same thing?
<identity>why does it have to be a transient service?
<ngz>Because it is not a timer service, and I assume this is what should be used to launch daemons at startup?
<identity>ngz: a transient service is a one-shot service that gets ‹forgotten› after it is done running
<identity>no, you use a Normal service to run a daemon
<identity>one-shot services are for, like, running mkdir
<ngz>OK, I understand that.
<identity>what made you think that you want the ‹temporary service› facility for running a daemon at startup?
<ngz>The documentation: "These are the ‘timer’ and ‘transient’ Shepherd services. The
<ngz> former lets you schedule command execution for later, while the
<ngz> latter can run commands in the background as a regular service."
<ngz>(sorry for the paste)
<identity>i guess the wording could be improved
<ngz>And I want to run a command in the background as a regular service.
<ngz>(i.e., something I can manage with herd command)
<identity>the wording in the shepherd manual, «The “transient service maker” lets you run commands in the background, and it does so by wrapping those commands in transient services. It is similar to the ‘systemd-run’ command, which you might have encountered before.» is less confusing
<ngz>It would even be less confusing with an example. After all, there is one for shepherd timers.
<identity>i mean, there *are* examples for what the service is supposed to do, but there should be a more prominent «You may be looking for a way to define a service» or something
<ngz>Also, is should be mentioned that those services are part of %base-home-services, as is done for home-log-rotation-service-type just above.
<ngz>identity: I cannot see any example showing how to add a transient service in a home configuration. Where are they?
<ngz>Even if they are defined as regular services using #:one-shot?, this should be put forward.
<identity>ngz: right, that is what i am talking about
<ngz>Gread :)
<ngz>great even
<identity>the transient service maker is just a script that you can invoke through the herd CLI to create a transient service that runs a shell command, but if you want to put a transient service in your configuration you need to do the job of the script yourself
<janneke>yelninei: right, how much memory are you using? i've been using 4G for my development childhurd's
<ngz>identity: I tried (simple-service 'davmail home-shepherd-service-type (list (shepherd-service (provision ...) (start ...) (stop ...) (respawn? #t)))), it almost works, but the davmail daemon crashes.
<yelninei>janneke: I also have 4GB in the qemu setting. "free -h" reports 2.9GiB total, when building guix the guile heap grows to 2.5, less of a problem in the 64bit childhurd of course
<janneke>hmm
<untrusem>How would I check what are the dependent of a package?
<Rutherther>untrusem: you can use guix refresh, ie. "guix refresh -l <package name>"
<untrusem>I don't use GNOME, but I am now downloading GNOME online account, so I wanted to check what package of mine depends on that.
<untrusem>ohh thanks Rutherther
<RavenJoad>Quick question. After a "system reconfigure", I did a "reboot --kexec". The laptop is not actually booting. The screen is black, keyboard backlight is off, and is unavailable from the network. Does the kexec reboot only work on "small" updates? Does it only work where full disk encryption is turned off? Just trying to see of this is a gotcha I hit or user error.
<Rutherther>RavenJoad: it does work with disk encryption. However the screen won't show you prompt for the password. Type the password and hit enter, it should work
<ieure>RavenJoad, There's some kind of issue where the LCD backlight gets turned off when you use `reboot --kexec' on a laptop. If you type it blind, it'll turn on at a very low setting.
<ieure>I don't know why it's like that, it's very confusing behavior.
<RavenJoad>ieure: That's the exact bug I saw!
<yelninei>this should be the bug https://issues.guix.gnu.org/76554
<RavenJoad>Ok, cool. Good to know. This was my first time using kexec at all, and I thought my laptop was the problem here. I so rarely system reconfigure that I usually just reboot instead.
<jlicht>are package properties for commits/revisions some fancy new standard way of doing things that I missed?
<jlicht>it looks nice, but I've not really seen it be used before :-)
<identity>could you give an example?
<jlicht>as used in https://codeberg.org/guix/guix/pulls/4980/files
<jlicht>and if you grep for "properties '((commit", you'll find some other existing packages also doing it
<identity>first time i see that
<identity>seems pointless, as the commit and revision information are encoded in the output anyway
<Rutherther>where exactly?
<identity>in the output name, rather. package-x.y.z-REVISION-COMMIT
<ieure>That's only if you use git-version, right/
<identity>right, which the linked code does
<Rutherther>right, but you need to parse it out of the version then. And it's harder to know for sure if the version is actually the git version string or not. With the package properties you can check if a package is tracking git commit instead of a version easily
<jlicht>A bunch of packages already do this; python-i3ipc, python-orbitalpy, python-parabam, cmudict, fortran-forutils, evtest-qt
<identity>right, but most opt for the (let ((commit "…") (revision "…")) (package …)) style instead
<jlicht>as is of course tradition
<ieure>Nice to avoid diffs without the whitespace changes from indent/dedenting as you add/remove the let, when packages switch between releases and snapshots IMO.
<moe>Why is it so hard to setup voidlinux with sway
<identity>probably the wrong channel to ask that in
<Rutherther>moe: this channel is about guix, not about voidlinux or sway
<alice-person-fro>Hi, i currently have a small problem. I wanted to test a project to help them, a wm, but i cannot manage to launch it, i should probably start over on that. tried to get xorg-server to be ran and adding a .desktop for gdm
<PotentialUser-98>Why does Guix sticks to Guile 3.0.9, and keeps 3.0.10 as 'guile-next' when the release notes for the latest releases keep saying they are mostly bug-fixes?
<Rutherther>there have been issues with 3.0.10, building for 32bit systems. It should be fine with 3.0.11, so that one will hopefully be able to become the default guile eventually
<PotentialUser-98>Thank you. The Python interpreter is another story, right?
<PotentialUser-98>I should have said "a different story".
<Rutherther>I am not aware about any specific problems with going to 3.12 or 3.13, so probably just lack of the time necessary to do the switch - a lot of packages can break and it might be necessary to update them or change how they're built
<PotentialUser-98>I think there is a new Python module build system and conversion effort. I was wondering if it was conditioning the upgrading of the interpreter, either technically or due to priorities of the team.
<PotentialUser-98>Do Guix Teams have a page with contact information?
<ieure>No.
<Rutherther>the contact information is contained in etc/teams.scm, you can do "./etc/teams.scm list-members <team>" or even use Cc to get just the cc header for email
<Rutherther>however please also send it to guix-devel so that others can also see it :)
<Rutherther>or help-guix in case you're looking for help
<PotentialUser-98>But... Cc-ing the message would create additional noise and instead of bothering just one person I would be bothering many. That feels a little... unpolite?
<PotentialUser-98>I mean, if I was a smart and knowledgeable person like you guys, asking relevant and important questions, sure, I understand it. Spread the information and the discussion.
<Rutherther>wdym? you wanted to contact the team and the team consists of multiple people
<gabber>PotentialUser-98: no need to be afraid, just ask! people join teams so they can help (guix but also specific users). if people don't have time to answer they will simply not (or take some time to do so)
<PotentialUser-98>I was referring to the part where you suggest sending a copy to guix-devel (mailing list). I suppose there are hundreds of people subscribing to it.
<gabber>guix-devel is there to discuss development relevant guix topics. it has many subscribers but it (still) is *the* place to discuss these issues
<gabber>it's not as fast to get /some/ response but is the better option if you want to get a response (especially to niche topics)
<gabber>to your question: i doubt the python version bump is related to the switch to pyproject-build-system. but you need to realize: when we upgrade a version (like python) we will build *all packages relying on the current python version*. so, when we upgrade we need to take time and fix probably occurring problems in our (python) packages
<gabber>do you need the most current python interpreter for some reason? you could inherit the python package and call the new variable python-newest or something and have your way with it
<PotentialUser-98>I see. I thank you all for the information. BTW, what would be the proper way to do it? Email the guix-devel and CC to the team members or just send it to guix-devel assuming the team members will see it there?
<gabber>you can do both, but CC-ing team members could make them realise faster that they are addressed
<gabber>for example: my guix mailing list subscriptions all go to an specific folder which i consult whenever i feel like it, but emails CC'd to me land in my inbox (which i see instantly)
<gabber>does the default `out' output of a package always contain everything built?
<ieure>No. What would be the point of having multiple outputs if one contains everything?
<gabber>i'm just wondering why `guix shell supercollider` (which i guess uses it's `out' output) contains the supercollider IDE
<PotentialUser-98>My problem / situation is that I would like to make Guix OS my work environment. However, the Python version packaged is very close of unsupported.
<ieure>gabber, Because the package puts it into the "out" output.
<PotentialUser-98>My work colleagues may say that I am constraining them and holding back the project because (as a result of my limitations) we would be missing out on features and bug fixes. Then the conversation may continue by criticizing my preferences for Free Software and so on.
<PotentialUser-98>In short, I would like Guix to align better with the more common versions of Python to facilitate team work.
<gabber>ieure: so, what is the extra `ide' output for?
<luca>lowkey should use a devcontainer regardless of distro so that everyone runs the same versions of everything. If not guix then some docker thing
<ieure>gabber, Presumably for the IDE, but also if the IDE is in multiple outputs or not in that one, the package definition is also presumably buggy.
<ieure>PotentialUser-98, What version are you seeing? Default Python is 3.11, which is supported until October 2027; I wouldn't call 22 months "close to unsupported." Python 3.12 is packaged and available, just not the default. That' supported until October 2028.
<gabber>the programmer side of our output mechanisms aren't really documented, right? i'd love to gain some insight (and fix the issue) but i haven't really understood how that works yet
<ieure>gabber, I believe that is documented, there's also many packages in Guix which use them you can reference as working examples.
<gabber>ieure: do you know of an insightful example (preferrably a relatively easy package) that i can look up?
<ieure>gabber, Not offhand. glibc and bind both have multiple outputs. You can also look for "doc" in the code, I know many packages have an output for documentation named that.
<gabber>ieure: thanks!
<ieure>gabber, No problem.
<ieure>Hmm, after PotentialUser-98, I half expected to see PotentialUser-98SE, PotentialUser-Me, PotentialUser-XP, etc
<gabber>lol
<Guix1800>Hi may anyone here help me?
<Guix1800>I have been trying to install Guix for 2 days
<Guix1800>I get these stupid annoying errors without doing anything
<Guix1800>Ai didn't help me
<identity>we will not help you until you tell us what the errors are :3
<Guix1800>Wait I thought I can send a picture here
<identity>it is a surprise AI can help you at all
<Rutherther>please don't send a picture, send text
<ieure>Same.
<identity>the pastebin is in the topic
<Guix1800>Are you ok guys
<Guix1800>Why you don't have discord
<Guix1800>Why you living in 1800
<Guix1800>I need to send picture
<Guix1800>I'm not going to paste the whole error message here smh
<Guix1800>I'm so mad this guix wasted 2 days of my life
<identity>then nobody is going to help you
<Rutherther>yes, don't do that, paste it to a paste site
<Guix1800>Wait
<Rutherther>not here, IRC is line based protocol, so sending it here will trigger send of many messages
<Guix1800> https://postimg.cc/NKPPqVqB
<Guix1800>First errors
<Guix1800> https://postimg.cc/vDtyFQPG
<Guix1800>Second one
<Guix1800>It does loaded most of it I guess
<Guix1800>But always giving error in the end phase
<gabber>the image says: boost gives a hash mismatch
<ente`>sounds like the checksum for the boost .tar.bz2 archive isn't matching
<Guix1800>And doesn't even go to bootloader installatio which is what I needed
<ieure>Guix1800, What installer image are you using?
<Guix1800>The latest one from their website
<ente`>boost has some history of moving distfiles around
<identity>who are they?
<Guix1800>Guix website
<identity>we are not a ‹they›, we are ‹you›!
<Guix1800>What you want bro
<Guix1800>Don't waste time
<Guix1800>I'm mad enough from this bs
<identity>do not fucking call me ‹bro›, bro!
<Guix1800>Stfu kid
<Guix1800>Grow tf up and if you can't help then stfu
<identity>you are not going to get any help with that attitude
<ieure>Guix1800, Be kind or leave.
<Guix1800>I'm kind to whoever is beneficial
<Guix1800>I can't please everyone
<ente`>Guix1800: I suggest deleting the offending boost files and download them again
<ieure>Doesn't work like that, bucko. I was midway through writing you a helpful message when you decided to start telling people to shut the fuck up. But now I'm telling you to stop doing that instead.
<ente`>and yes, don't take your frustration out on people
<Guix1800>It's ok bro if you don't wanna help you don't have t
<Guix1800>Don't make up excuses
<ieure>Guix1800, Fix your attitude and you will receive help. Insulting the same people you're asking for help is idiotic.
<Guix1800>How can I delete offending boost files though? I'm new
<Guix1800>None insulting anybody
<Guix1800>Instead of helping this guy chose to focus on useless stuff
<ieure><Guix1800> Grow tf up and if you can't help then stfu
<Guix1800>He think I got time for that
<ieure>That is an insult.
<Guix1800>So ?
<Guix1800>He tried wasting time
<Guix1800>I can't be nice to everyone bro stfu omg
<ieure>Anyway, adding you to my ignore list. Wish you the best luck installing whatever OS you like, on your own.
<Guix1800>Don't be a sensitive kid
<gabber>Guix1800: and please don't assume people's genders. they/them are the preferred pronouns if you don't know
<Guix1800>It's not ur first day in the world
<ieure>My ignore list grows fatter by the day.
<Guix1800>Lmaooo ignore list
<Guix1800>U r such a nerd
<Guix1800>I never even go on here
<Guix1800>Wtf is this website lmfao
<ente>dude I'm not helping you any more than that. you can google for yourself
<Guix1800>Instead of using discord u stuck in the ICQ era
<gabber>can we silence/ban people?
<ente>instead of spamming here
<Guix1800>Guix community is shit
<Guix1800>That for sure
<ente>no, you should learn to behave in a public space
<Guix1800>Stop doing kaka in ur pants
<ieure>gabber, You can't mute individuals in a channel, but a chanop can kick/ban.
<ente>you're acting like a 5 year old
<ieure>gabber, IRC does the inverse, you can set a channel to moderated, then only users with +v (voice) can send to it.
<Guix1800>Instead of helping u all always hating
<ente>ieure: I think libera has mute
<Guix1800>It's always these nerds chat who does this
<Guix1800>They never like to help
<Guix1800>Just to argue
<ente>ieure: it'
<Guix1800>This is why nerds groups are ass
<ente>s mode +q
<PotentialUser-98>ieure 3.11 is not entirely unsupported, but those are 22 months of security fixes only; bugs will stay. The Amazon runtime for 3.11 will enter the deprecation state in 6 months. 3.12 will also receive security updates.
<PotentialUser-98>This situation is fine for code that is deployed and under maintenance, but for new development I find it less than ideal.
<PotentialUser-98>No jab at community efforts. I appreciate what I am getting, but if there is something I could do to help unblock 3.13, I would be happy.
<PotentialUser-98>Maybe I could tweak the build script and get something running, but I am too noob and I would not trust that effort. I think that, if it was easy, someone would had done it by now.
<ente>+q hostmask, like +b hostmask for bans
<Guix1800>Lollz
<Guix1800>U get stuck in ur own shit lmfaoo
<Guix1800>So funny u can't even ban ppl
<gabber>PotentialUser-98: is it blocked?
<Guix1800>U don't know how to use ur own system
<Guix1800>What a joke
<gabber>PotentialUser-98 we can help you trying to craft the right package definition. this could lead to your first PR for the guix project
<ieure>PotentialUser-98, You can reach out to the python-team or look at the python-team branch. Packaging the new Python usually isn't the hard part, but actually making everything use it, which requires package rebuilds and usually some fixes.
<Guix1800>Ok help me with PR
<gabber>Guix1800: no one is talking to you (anymore)
<Guix1800>Ok so you not gonna help me with my issue?
<Guix1800>Guix is weird I didn't touch it and it has already errors
<Guix1800>Guys I need help with this error
<Guix1800>I'll pay you
<Guix1800>Help me please ty
<Rutherther>just use substitutes or a newer image, the source is no longer available at the original url, the site redirects to a HTML page
<Guix1800>I mean what? But it's the newest image
<Guix1800>And how to do it? Sorry but I'm really nub
<Rutherther>it is 1.4.0, isn't it? It's 3 years old
<Guix1800>Wait I'll check
<Rutherther>the newest available is 1.5.0rc1 https://lists.gnu.org/archive/html/guix-devel/2025-12/msg00182.html
<Guix1800>Yes it's 1.4.0
<Guix1800>Omg idk why they keep the 3 yo verzion on their site
<FuncProgLinux>o/
<Rutherther>because there haven't been a newer release yet
<gabber>FuncProgLinux: hi!
<FuncProgLinux>just got the rc update while upgrading my system!
<FuncProgLinux>at least it downloaded it, idk if it applied it system-wide
<gabber>FuncProgLinux: cool!
<FuncProgLinux>what's good on guix after the holidays?
<gabber>FuncProgLinux: helping each other liberating computing for good (:
<FuncProgLinux>gabber: aye, I see the PR number elevated to 500 again x.x
<FuncProgLinux>Hopefully good numbers will arise on the contributor survey this year
<PotentialUser-98>OK. Thank you for all the help. I'll write an email an then see what I can find the time to help with.
<gabber>PotentialUser-98: HTH! hope to see you soon. the python version bump *will* happen, the only question is when (and how you can help us land it)
<ieure>Probably a good idea to target 3.14 at least when we do update.
<Guix1800>Guys
<Guix1800>Ruthers
<Guix1800>What exactly to install in your link? Which file
<Rutherther>presumably you're looking for the ISO and the one for x86_64, it has that in the link
<Rutherther>specifically it's in the name of the file
<Guix1800>Ye I just saw it
<Guix1800>Ok I'll try it and let you know if it fixed the thing
<identity>if the next update after python 3.14 is not 3.141 it all was for nothing…
<Guix1800>Ty soo so much bro
<gabber>identity: lol
<ieure>Pi-thon
<ieure>identity, Wait until you find out about TeX.
<FuncProgLinux>Is the guix-mentors team similar to the Debian Sponsors/Mentors mechanic?
<identity>ieure: i know about TeX's version number
<FuncProgLinux>I want to give a second shot to maintaining MATE. Fortunately only 1 package is missing from the full suite now. Other updates need libraries not available on Guix just yet
<FuncProgLinux>I tried fixing the screensaver issue but ended up bricking a VM with PAM
<identity>FuncProgLinux: for Guix, people with commit access are like Debian Mentors, if i understand correctly
<PotentialUser-98>FuncProgLinux Are there plans for another survey in 2026? Any idea when in the year?
<identity>i think mentors are people you CC (or i guess mention on the issue?) if you really want help with something
<identity>something committing related, that is
<FuncProgLinux>identity: Only reviews/merging. I try to test my patches before submitting to avoid breaking things
<ieure>identity, Debian Mentors are developers who help new Debian developers onboard, essentially. Guix committers tend to be a helpful bunch, but I do think that guix-mentors is much closer to Debian's thing than just having commit access.
<identity>ieure: ah, okay, <https://mentors.debian.net/> puts the «committing on the behalf of the package writer» front-and-centre, which skewed my perception
<PotentialUser-98>gabber Sad that I only pop in here to ask for help. So many possibilities in Guix, so much to learn, so little time...
<PotentialUser-98>Hoping to level up this year (sorry, ieure, I'd like to skip Me -- was it like 5 times the disk space of '95!? How do you justify that?)
<FuncProgLinux>PotentialUser-98: I don´t organize such surveys. So I cannot answer with dates :( but I'm looking forward to read it as well :)
<gabber>PotentialUser-98: being here is the first step in answering questions for others (: in a similar way in what using Guix is the first step in helping others using it
<gabber>what's the guix way to execute one command (that is not available through other services) upon boot of a system?
<luca>Make a one-shot service?
<PotentialUser-98>gabber Isn't there s service for that?
<dajole>How d'yall deal with Haskell packages often being rather out of date? I just looked at hledger, and the Guix version is from 2022. I'm aware this is more of a Haskell problem than a Guix problem, but I'm just wondering how you deal with it in a Guix-y way.
<FuncProgLinux>dajole: I don't use haskell but I do use the guix importer for my Go projects. If a package exists you can "inherit" it and create a new definition inside your manifest.scm file
<identity>… i think haskell-xyz.scm was not touched since 2023
<identity>maybe the ecosystem is truly stable
<identity>or maybe everyone Haskell uses Nix instead
<dajole>Interesting, thank you both for the input! I'm still a little intimidated by writing my own package definitions, but I should probably get over that and learn how to properly do it in any case.
<FuncProgLinux>dajole: I advocate for "learning by doing" :) It took me like 3 days to learn but the more you practice the easier it becomes
<identity>dajole: (info "(guix) Invoking guix refresh") might help with updating packages
<FuncProgLinux>The Spritely Institute website has a nice manifest.scm example to see how you can refresh guix packages "per-project"
<dajole>Thank you, I'll take a look.
<RavenJoad>If I have (native-inputs (list (origin ...))) to bring in an asset, does it have a name I can use to refer to it? Or do I have to do the older (native-inputs `(("my-name" . ,(origin ...)))) syntax?
<Rutherther>I believe it should have a name, specifically based onthe "file-name"
<ieure>Was poking at related stuff the other day, was very surprised to find that all package object inputs are an alist of (("package-name" package-object) ...) even though they're specified as (list package-object).
<ieure>But the nice thing here is that you can stick an origin in your package definition, eval it in the Guix REPL, then run (package-native-inputs your-package-object) and see exactly what the name will be.
<RavenJoad>Oh, duh. I can give a Guix-internal file name with the (file-name ...) field on origins. That's the easiest thing to do.
<RavenJoad>ieure: Yeah, from what I remember of gexp's being added, the input lists with gexps are syntactic sugar over the alist format.
<ieure>RavenJoad, There are no gexps involved here.
<ieure>RavenJoad, If you just have a normal (package (name "whatever") (native-inputs (list some-package))), then call package-native-inputs on it, you'll get (("some-package" some-package)) out.
<Rutherther>they aren't, but the rewrite to gexps has included the removal of the necessity to use input labels, or sort of. Not fully. At least not yet. As you can see still the implementation relies on it. Previously you had only assoc-ref on inputs, so it must've been an alist
<RavenJoad>Right. I forget where/when it was, but the syntax for human-writing of inputs changed some time ago.
<RavenJoad>Ok, last question about using an origin as an input. This package is currently written with copy-build-system. I don't see an obvious way to use the origin input in the #:install-plan. Am I being dense? Or is that something only possible in a separate phase?
<Rutherther>I believe it installs from cwd, so as long as you make a phase where you copy it to cwd, it should pick it up
<Rutherther>just make sure to do it prior to 'install
<ieure>Yeah, I don't think there's a good way to copy directly from the input.
<ajarara>hi #guix, is there a reason the guile shepherd (and by extension, guile-fibers) module is avoided in the guix source set? It is, as far as I can tell, only used in gexps. I want to use shepherd timers instead of mcron jobs to define my tasks (for better task management), but that means I have to have shepherd (the guile module) on my load path. I can do it, it's just weird that guix itself doesn't bundle it in.
<Rutherther>ajarara: why would it bundle it? You use shepherd timers inside of shepherd, not inside of Guix. That is why all of them are in gexps or quoted, because they are then passed to shepherd
<Rutherther>ajarara: Guix is meant to build the shepherd config that contains the timers, not to actually run the timers
<RavenJoad>Oh well. No big deal. I'll probably just make a phase after install to install-file the SVG from the input then. Easy enough.
<ieure>RavenJoad, You can cheat even harder, if you like: https://codeberg.org/ieure/atomized-guix/src/branch/main/atomized/packages/makemkv.scm#L57
<ieure>Maybe you can put a call to search-input-file in your #:install-plan?
<RavenJoad>I'm not that invested in putting everything in the #:install-plan. search-input-file could work, but I just put the install-file call in the phase where I make the .desktop file too, so all's well.
<ajarara>Rutherther: oh duh, makes sense, I mistook needing it on the load path for jump-to-definition implying it needed to be on the load path to evaluate. It doesn't. Thanks!
<abbe__>Does anybody know how to get wireless regulatory DB working in Guix ?
<abbe__>I believe, I need it for using 6GHz band my wireless card supports