IRC channel logs
2025-12-28.log
back to list of logs
<radhitya>3-guix-packages-base.drv' timed out after 3600 seconds of silence <radhitya>i have 2 gb ram, 1 cpu, 20 gb ssd for guix vps <radhitya>i did a guix pull and ended up like that <radhitya>no, it was not guix pull, but guix reconfigure <radhitya>gabber: are you there? the issue is closed and i see the docker.scm was changed <radhitya>i did a guix pull and guix reconfigure and the results was the same <jj>hi, i'd like to install guix on my server, but it's got a nonfree wifi card. the unofficial nonguix releases have been broken for about a year. do y'all know of any way to get the wifi driver i need onto an official install medium? <jj>(in the mean time i am compiling my own image, but i expect this to take quite a while) <ieure>jj, Creating an installer image doesn't take very long. #nonguix is where you can ask about Nonguix questions. <jj>ieure: hm, still compiling. i think you have a much faster computer than me. but thx for channel link <apteryx>would someone know how to get the 'host -6' command to function? It's from the bind:utils package/output. <apteryx>currently I get: $ host -6 example.org -> ;; communications error to ::1#53: connection refused, ;; no servers could be reached <cdegroot>Soo... question. Well, two. I am setting up Bacula backup and it uses configuration files that are a tad large and have references to paths where utility programs live in them, so these need to be expanded to the store path of the package. The best I've come up with is https://pastebin.com/5s563kM2 which takes local .conf files as templates of sorts, does a search/replace, and all is well. It does feel all a bit round-about-ish though <cdegroot> and I can't imagine that there's no shorter version. Also, I don't understand why in this case I need to hand `local-file` a full path. I'm gonna focus on making the actual backup bits work, but would really love it if someone can share some insights :) <csantosb>Could someone replace `unzip` by `zip` as input of `emacs-tldr`, then try to `./pre-inst-env guix build --no-grafts emacs-tldr` ? <csantosb>I get an annoying "package `emacs-tldr@0-2.1b09d20' has an invalid input: ("_" #<procedure zip (clist1 . rest)>)" <Rutherther>seems that you're supplying zip from (srfi srfi-1), not the zip package <Rutherther>you will either have to reorder the #:use-module list so that (gnu packages compression) comes after (srfi srfi-1), or refer to it with a module - (@ (gnu packages compression) zip) <identity>or import everything from (srfi srfi-1) but zip (i doubt the procedure is used in that file) <ieure>My kingdom for a convention shift away from importing all symbols when using a module. <identity>hm, it seems there is no ‹everything but these› for Guile modules. you can probably use ((srfi srfi-1) #:select (stuff that is used)) instead <ieure>identity, Correct, you can omit, prefix, or rename. <ieure>Sorry, uh, select, prefix, or rename. <identity>i still wonder how useful (@ (srfi srfi-1) zip) is in a world where ‘map’ takes any amount of lists <csantosb>And now it's time of the day to figure out how to get the "*Org PDF LaTeX Output*" buffer produced during a package build <jonsger>should be the switch to QT@6 and the update of a package version be separate commits? <identity>are/were there plans for a fossil-fetch method? <dariqq>newguixbie: For the i686 qtdeclarative you can fix the build by setting QT_BUILD_TESTS=OFF, depending on how much ram you have you might also need to skip the 'make-dynamic-linker-cache phase <Rutherther>dariqq: why don't we change the package in that way if it cannot be built on i686 right now? <dariqq>Rutherther: cores=1, no there is a bug in the test code that fails to compile <dariqq>Rutherther: Sure but it wont solve anything for the greater picture. The dynamic-linker-cache needs to be also skipped for qtbase guix/guix#1262 and this is a limitation of the current guix implementation loading the entire elf into memory <dariqq>then there are lots of other problems, test failures in gtk, gstreamer, ... the list is only increasing after every update <newguixbie>it would be ideal to have the primary packages rely on qt5 rather than qt6 to ease developers running i686 reaching master <newguixbie>gstreamer-plugins-good has some disabled tests on riscv5 that should also be disabled on i686 and then builds <dariqq>why? Instead fix qt6 if you care about it. <newguixbie>well I don’t have an up-to-date system to test contributions to your upstream <newguixbie>building a minimal system requires qt and can take hours or days depending on load <newguixbie>but if the substitutes for i686 were built with qt5 they would just download <newguixbie>but yes I do hope to just fix it :) and you basically said and linked to how <newguixbie>additionally the guix system command does not accept package transformation options <newguixbie>it’s clear that the challenges in running guix master on i686 relate to its lack of maintenance; the developers are not running i686 <newguixbie>well everybody running i686 needs more developer aid <Rutherther>newguixbie: it's not really easy to apply transformations to a system. The transformations apply to packages and it's not easy to collect all the packages of the system like that, and transform them <manfred>which desktop would you recommend me? <newguixbie>Rutherther: guix relies on dense developer effort, it seems a nice philosophy. it’s good to see what works for non guix <newguixbie>manfred: I don’t use desktop yet on guix but would recommend trying gnome if it works because it is common and easy to find information on <newguixbie>manfred: sounds like sway is tiling, that’s cool you’d learn a classic experience that can be very efficient. but kde is more similar to windows and macosx if you are used to that. <manfred>like malware on it or probably not=? <ieure>Do you think Guix contributors package malware? <identity>if they are good at it, nobody knows. i highly doubt that is the case, though <identity>only so many people are good at doing malware in the open <ieure>Well, okay, anyone can contribute, but only identified developers can actually push commits, which must be signed by one of the keys in that branch. <ieure>manfred, Guix takes supply chain security seriously, there is not malware packaged in Guix. But there's also not malware packaged in any normal distro. <ieure>manfred, That's a #nonguix question. <ieure>manfred, DE choice is heavily based on personal taste. Try a couple and see what you prefer, then use that. <ieure>Except GNOME! That's the one we put all the malware in. <identity>that must be why it is making my laptop run hot <ieure>identity, It's the crypto miner we put in there as part of the Guix fundraising initiative, yep, definitely that. <tux0r>CDE is the only good desktop <ieure>I think a toolchain update broke the build entirely. Before that, you could log in and it sort of worked, but not 100%. <ieure>tux0r, You could start a session, but it would display an error and not everything was functional. <ieure>But it built, added the session to the display manager, you could log into it. <manfred>guix installer is soooooooooooooooooooo slow <ieure>tux0r, It's that or get destroyed by garbage-ass LLM scraper bots hammering the site. <ieure>tux0r, You can send your complaints to Sam Altman and the hordes of even dumber CEOs aping his awful ideas. <tux0r>"make our site not usable for real people so LLMs stop reading it" <ieure>tux0r, The choice is "usable for people using normal web browsers, or nobody at all" so yeah. <identity>hell, it works fine in my text-only browser! <tux0r>not really. i couldn't care less whether codeberg works for people, tbh <ieure>My ignore list grows fatter by the day. <tux0r>ieure: it seems like "normal web browsers" are a very specific subset. <tux0r>how do they identify "normal web browsers" in opposition to "crawlers"? by reading user agent strings? bad news then, i'm afraid.. because obviously webkit isn't "a normal browser" then <manfred>can someone pls ask for me in there to make available for people with no account <ieure>tux0r, I don't know the specific mitigations, and the nature of the LLM scraper arms race means it's a very bad idea to disclose how you're identifying them, since they will then do things to avoid it. <ieure>tux0r, It's the email spam problem, but for web sites. And it will likely never, ever get better. <ieure>Poor form to blame the defenders in this scenario. <tux0r>i protect my code server with anubis and that works within webkit, so i *assume* that the codeberg guys are just doing it wrong. anyway, this might be the wrong room for this <identity>…if you know what you are doing, which the crawlers clearly do not <ieure>tux0r, #codeberg for questions. Codeberg uses or used Anubis, but in conjunction with other protections. And as identity mentions, Anubis is an old weapon in this war. <ieure>There is no single thing you can do to solve the problem, and the higher profile your site is, the worse you get attacked. <ieure>manfred, I ran it on a secondary machine for months earlier this year, it worked fine. <manfred>ieure no idea what iso I installed there then <manfred>h06i72zs7hr387xcgwq6l2kpk3bbxg52-image.iso <ieure>manfred, I don't understand what you're asking, or if it's even a question. <ieure>manfred, Based on the filename, it's an installer image you created, so whatever you told it to use. Why would the installer kernel have anything to do with an installed system's KDE? <manfred>ieure I am not qualified to answer that question <ieure>manfred, The installer kernel has absolutely nothing to do with your installed system's KDE. <ieure>manfred, I have to step away for lunch and some errands, but I'm reenabling KDE on my other laptop to see if I can reproduce your problem. <manfred>how can I leave the installer to console <Rutherther>that is built periodically from current guix master <ximon>can I take it? for gaming pc? <ximon>or master is not for gaming? <identity>master is pretty much the only valid way to use Guix before 1.5.0 releases <ximon>identity ohh I thought guix is rolling release <identity>having a stable release (for once!) does not mean that a distribution can not be a rolling one <Rutherther>no, I have not said it is rolling release. Rolling has nothing to do with releases <Rutherther>there are releases that are meant mainly for installation, because they're not updated. So you get all the CVEs that are there. And you should use the rolling master <ximon>am I using the rolling master with the link I just sent? <identity>rolling release is the same as rolling, just with the word «release» on it <Rutherther>ximon: no, you use that by doing guix pull periodically. It has nothing to do with what you download initially <ximon>guix dev trying to make windows user understand guix windwos user has clapping ape in head <ximon>how to install firefox in guix? <ximon>do you only use the guix install command? <ximon>does guix come with preinstalled firewall? <sneek>Nessah, Rutherther says: you could use changes from this PR https://codeberg.org/guix/guix/pulls/4681 locally, easiest is going to be to just guix time-machine or guix pull to that commit in a local repo. Optionally you could rebase it on top of origin/master so that other packages are up to date <Nessah>Rutherer: sorry for missing this, but thanks for sharing this <Nessah>ximon: firefox is not included, closest available is librewolf <fmarl>Hey! Does anyone know when the rust-team will merge rust-1.90 to master? It's already on their branch. :) <ieure>fmarl, Just guessing, but probably after the release code freeze. <ieure>sneek, later tell manfred I can't reproduce your KDE problem, windows move around just fine when I drag them by the titlebars. <fmarl>ieure: Thanks, makes sense. I'm relative new, can you point me to a resource when the freeze is planned? Just curious :) 