<hwpplayer1>Can we have Emacs included for the next build or commit
<stuebinm>pinapples: we do! i use it quite a lot — be prepared for it to occasionally crash on you (and afaik anything with webrtc/video conferences doesn't work rn), but apart from that i really like it
<stuebinm>pineapples: I think it's pretty new — I only found it a couple months ago (there was a talk at fosdem iirc), and even in the time I've used it it's gotten noticably better, so now i just use that and keep a backup icecat install around for video calls and stuff (at least on my laptop, which runs guix – i also have a NixOS machine, where I never really got it working beyond showing a blank window
<roelj>I sent a patch to fix LDC to guix-patches yesterday. Normally I can simply wait a week for a response, but I'd like to migrate more packages to the "guix-science" today which needs a working build of sambamba, which needs a working build of LDC. Would anyone be able to review the fix today? It's bug #48541. :)
<civodul>roelj: hi! i review this one and you review another one; deal? :-)
<roelj>that would be really great in the long run, but sambamba seems to be very critical on how it is compiled ;)
***maddo is now known as maddovr
***maddovr is now known as Mad_Hatter
***Mad_Hatter is now known as ACatIsFineToo
***ACatIsFineToo is now known as maddo
<ecbrown>not sure if Maxim Cournoyer hangs here but i'd like to thank/confirm that email@example.com builds with small modifications of patch. 64-bit qt containers and i dont have to compile it myself :-) [bug#47684]
<ruffni>i'm looking for the font called "Monospace". does anybody know whether it's in guix packages (`guix search Monospace\W` returns nothing)? it's ruther difficult name to search for (since every monospace font has this string in the description)
<lfam>I would only put shell-agnostic stuff in ~/.profile. And then shell-specific things can go into ~/.bash_profile and ~/.zprofile
<lfam>It may be overcomplicated. Maybe it's better to just get comfortable using the defaults
<Carcaj0u>Yep, it would only pose problems if zsh used a different value for variable defined in the .profile too.
<Carcaj0u>And the separation shell-agnostic - shell-specific is a cleaner approach, I agree.
<mothacehe> civodul: do you think we could have an "all-guix-tests" procedure similar to "all-system-tests" but for Guix unit tests? The idea would be to add them to the CI to detect breakage as soon as possible.
<civodul>mothacehe: that'd be great; it's a bit of work though because we'd have to translate the makefile/test-env machinery to Guix
<ruffni>why does `guix show python2` show a package (which is supposed to be defined in (gnu packages python)) but when i try to build or even import the module in the repl i get "error: python2: unbound variable"?
<ruffni>it works when i substitute for package "python2-called-python", but still. is this a bug?
<lfam>There is a package named python2, but the Scheme variable is named python-2.7
<lfam>Look in (gnu packages python), it's the first package
<lfam>Anyways, if you are working in Scheme, you need to use the variable name, which is different from the package name
<roptat>ekaitz, sorry I had something else to do and didn't follow. from the look of the manifest, you're installing a cross gcc, but a native libc and linux headers, so crti.so is going to be the wrong architecture I think
<ekaitz>/gnu/store/8n3cdnafvlpg0m68gz4spns4lx87x1sf-glibc-cross-riscv64-linux-gnu-2.31/lib/crt1.o: ELF 64-bit LSB relocatable, UCB RISC-V, version 1 (SYSV), for GNU/Linux 2.6.32, with debug_info, not stripped
<nckx>I think comparing user counts is misleading. There are 266 users left in old #guix. At *least* 72 of those are Matrix users, and the Libera Matrix bridge is still ‘under construction but coming soon’. Probably more, since I just grepped for [m] :) Worse, ~146 of those 266 haven't said *anything* in 2021. There are users like ‘nckx[m]’ who never will.
<tissevert>sorry, I meant that I know what happened to roptat could have happened any time to me, but in spite of this, once formulated like roptat did «don't share /etc», it sounded quite «obvious»
<tissevert>the kind of «obvious» any one misses a couple times on a daily basis
<pineapples>I've been wrestling with auditd to read my `audit.rules' for the last two days, and I've discovered that the daemon itself doesn't read the `.rules' files; it has a helper program for that purpose
<Digit>:D i keep joining chans on libera, half expecting to be the first, and keep finding the exodus is well ahead of me. :) wtg guix. :) [ guix getting praise in other distro chans, regarding its hosting solutions and their freedomness, which is nice. :) ]
<civodul>lfam: from issues.guix.gnu.org; leoprikler: i think you just need to add /patchset to the URL?
<maximed>Lately (past ~2 days), my computer screen occassionally temporarily (2-5 seconds) becomes bright (as in white, not referring to (energetic) intensity) and seems to dither or something. Any ideas what even is happening?
<maximed>Also, did someone ever encounter that on non-Guix System?
<joshua>I DO NOT see the "closed" button icon in the chat screen.
<vagrantc>joshua: sounds like a bug somewhere, then, given it works under X but not under sway
<joshua>vagrantc: let me try starting gajim from a terminal to see if it shows any bug messages.
<joshua>I did get an error message...just a second and I'll post it.
<maximed>roptat: problem is it only happens rarely (two times a day or so) and I don't have much time to debug things. (Difficult assignment with deadline in ~10 days). But yes, that seems a reasonable course of action
<vagrantc>fwiw, i haven't used gajim on guix, but gajim running under sway on Debian works fine
<lfam>People are surely using it via custom kernel packages, but support is not included in GNU Guix
<dstolfa>lfam: yeah, guess i'll have to build my own kernel, which i don't mind doing but still sad times that linux-libre doesn't support it
<civodul>cbaines: does the Data Service have an API to map a .drv to the corresponding channel commits?
<lfam>There's not many different wifi chips with free firmware. It's basically just 802.11n Atheros (ath9k) and then there is 3rd party firmware for some chips via the aircrack-ng project: https://github.com/aircrack-ng/
<lfam>I actually don't know the full set of what's supported by aircrack-ng. I just learned about it recently
<dstolfa>i'll look into aircrack-ng, maybe it has some of the stuff i need
<ArneBab>My computer spent the past 30 hours or so on guix system reconfigure --no-substitutes — it now arrived at rust 1.30.1.drv and it’s crazy to think that it will still have to walk up to rust 1.44.1, version by version.
<lfam>ArneBab: Do you mean to build it from source? Or could you wait a little while for substitutes?
<ArneBab>I’m building it from source, because building from substitutes is broken for me (I do not know why — I reported a bug)
<lfam>It's incredibly expensive to build Rust things from source due to the bootstrap chain
<ArneBab>yes, and I really do not understand why they do that — can it be so hard to limit themselves to basic rust for a compiler-core?
<sundbry>I presume he means they have to use the new rust features in the rust compiler itself
<ArneBab>If rust 1.44.1 needs the whole chain from 1.27.1 upwards it means that 1.44.1 cannot be compiled with 1.27.1 — but I would hope that they could define a minimal core of the compiler that suffices to build the rest and write that compiler in rust 1.27.1
<lfam>I hope that in 5 years things will have stabilized and their values will shift a little bit
<ArneBab>it’s like with all the cool things the basics are getting lost
<lfam>Maybe it would have been like this for C if Guix was created in 1980, for example. Although that would have been impossible since cryptographic hashing did not exist and computers were too slow for such hashes anyways
<lfam>We are roughly at that stage of Rust development, compared to C