IRC channel logs
2025-08-18.log
back to list of logs
<Aurora_v_kosmose>I was looking at some Eclipse project and despairing on the sheer amount of work it'd be to patch out & rewrite all the parts so it won't grab random stuff off the Internet. <Aurora_v_kosmose>And yeah, in retrospect it would legitimately be less work to just write an ant config from scratch. <Kabouik>After a million attempts, this ended up installing fine on aarch64 ieure, but it feels incredibly hacky that I had to disabble this many tests/checks: https://0x0.st/Ksrn.txt <Kabouik>Thanks again for pointing that emacs is an input for all emacs-* package and therefore they all need to be tweaked. <sturm>is it possible to define a channel that's a subset of an existing channel? I'd like one or two binary packages from non-guix, but want to avoid accidentally installing other non-free packages <fractal> /msg NickServ IDENTIFY firefly707 ZPvDaW387w73629G8U49sNbMukM9RS9j <fractal>did I really just... welp, time to figure out how to change my password lol <tux0r>firefly707: good password spying bots change your password before you do <tux0r>that reminds me that mine hasn't joined here yet. hmm. <firefly707>I'm really surprised it let me send a message under fractal? I don't have that nick reserved, somebody else does. <tux0r>reserved nicks are not really "banned" instantly <firefly707>anyways, I think I might've botched the guix.texi file in my local repo. I'm trying to open it with `info -f guix.texi` and it's saying it couldn't find top node <ieure>Kabouik, Glad you got it working. Seems like `no-tests-for-emacs-async' does the same thing as `with-emacs-arg', so I think you can remove it. Curious what the issue with emacs-org was, removing the 'build step means you won't get any .elc or .eln files in the package. <adanska>Why are so many of the workers on ci.guix.gnu.org idle when theres so many scheduled builds? <jlicht>sturm: inferiors might do the trick <sneek>Welcome back civodul, you have 1 message! <sneek>civodul, zimoun says: Any chance that you give a look to PR #1108 about load-path (user experience) before your summer break? :-) <reyman>guix science is not compatible for jupyter due to nss-certs <reyman>python-jupyterlab into packages.scm <andreas-e>reyman: See my reply on codeberg. Incompatibility since yesterday, easy to fix in guix-science. <decfed>how to I mount a FUSE filesystem automatically as the use in a operating-system definition? By specifying in file-systems the mount point gets created with root <decfed>I want the filesystem to be mounted with user permissions but on a path only writable by root (/srv) <untrusem>ACTION I think there should be some sort of announcement for these major upgrades, change or builds <andreas-e>It was actually not a really big upgrade... What broke channels was moving the package to a different module. <andreas-e>In principle, I agree. At the same time, it would be nice to move faster and break more :) <andreas-e>Well, not the latter, but I am afraid it will be inevitable. <civodul>it’s a real reputational issue though <andreas-e>Hm, my issue is rather that we are not going fast enough... <andreas-e>So it would be nice to announce big changes. At the same time, we should have them about once or twice per week. <untrusem>andreas-e: what package was moved to different module, nss? <untrusem>andreas-e, civodul: I mean atleast we can announce them in communication channels like irc by putting it in channel topic, and people can do the rest is unofficial channels <andreas-e>commit af9e540b716402df983935eeabedc4572d6565ce <andreas-e>nss-certs-for-tests was moved from certs to nss. <andreas-e>Right now we have 7 branches queued up to be merged on QA. So if we merge once per week, that gives a cycle every two months for updating mesa, the python packages and so on. <andreas-e>Rather every three, because there is also gnome, qt, kde, and maybe others I forget. <andreas-e>So my point is, without moving particularly fast, we should have an announcement per week. <csantosb>andreas-e: Why not an atom feed with news, so that anyone interested can subscribe to ? <noe>It seems mumi is broken on issue pages <andreas-e>csantosb: Why not, something simple. For instance, to announce a merge, so that people are not surprised when things break. That would already be useful, and then they can check the issue tracker. <reyman>libreoffice seems also broken by nss-certs change, recompilation of my guix home script failed <Deltafire>andreas-e: i doubt guix users are that surprised when things break <Deltafire>would be nice for a weekly summary or similar for what's going on <untrusem>Deltafire: yeah, when guix break breaks, I am like <reyman>Deltafire: Not surprised, when it's holliday this is not a problem, when this is during a "dev rush" to add something lib/soft needed, this is more complicated <Deltafire>that's why we have the rollback, or roll-back feature :) <ieure>Deltafire, You can subscribe to the daily digest of guix-commits. <jab>whoever added "uninstall" from the guix installer script...THANK YOU! I am currently re-installing guix by the way! <reyman>and when you guix pull and you need to rework your broken howmade packaged channel app :) <reyman>but this is the game with rollback release <Deltafire>i wonder why "guix package" doesn't have an action, like guix system and home do <untrusem>We could make bot that post a commit when the commit message have a particular trigger. It might be helpful. <civodul>reyman: “rollback” or “rolling”? :-) <podiki>been thinking for a while to do some sort of weekly (or some time frame like that) "what's going on in guix" roundup <podiki>just haven't had the time to do it yet, but the idea would be to highlight upcoming and recent changes, discussions, etc. <untrusem>that would be very good, we can volunteer to write things as well <podiki>i wonder what would be easiest to coordinate, maybe like an issue on (what?) git repo every week people can add bits and then it just gets quickly edited and sent at the end of the week <podiki>so once people know, they can easily help out: you are working on finishing a big branch, drop a note there that merge is upcoming, please test <podiki>still, would be nice to not add to overhead of those doing that hard work already <untrusem>So, a community that I am part of, We publish a zine every month and for the sign we have a file that everyone can edit. It might be through Git or we can use something like Etherpad or Cryptpad and that file get uploaded in website page every week itself. <untrusem>we can use ci action to build the website every week once set up, and just focus on editing the file <podiki>website is already built on changes to git if i remember; i was thinking this would be more internal (via email list), though i suppose could be on the website if it works well <jab>hello, I believe that someone was working on packing bitcoin-knots for guix...does anyone have a link to that? <fnat>Is the general recommendation to use `define-configuration/no-serialization` instead of a simple record? <fnat>I mean `define-configuration`, not necessarily the `no-serialization` version. <jab>I'm running guix on Chimera Linux...I believe that I just updated the guix-daemon via <jab>and I restarted the guix daemon... <jab>but now when I try to guix pull again, it is trying to update the git repo from guix.gnu.org ... not codeberg. <jab>Does this mean that my guix daemon perhaps did not update properly ? <jab>maybe I need to restart chimera...Maybe it just needs to be restarted. <identity>jab: git.guix.gnu.org redirects to codeberg <jab>identity: sure. How do I verify that I am running the latest guix daemon? Is there a command invocation? <jab>I suppose ... doas -s ; guix --version <jab>I see commit 7448f7572 <jab>I'll check the commit history to see how old that is in a moment.