IRC channel logs

<abbe>could someone give their attention to seemingly forgotten (due to my fault mostly) PR: https://codeberg.org/guix/guix/pulls/5558

<apteryx>I'm totally lost as to where is the latest build of openjdk supposed to be on ci.guix.gnu.org

<apteryx>ci is the only place where it's not substitutable; I'd like to fix that

<apteryx>I suspect a cancelled derivation build may have led to that confusion

<kvt>Hi. Can anyone by chance recommend a (modernish) laptop on which they've succesfully installed Guix? I've been looking at the ath9k-compatible laptops list on kernel.org and they're generally old. I saw Dell XPS 13 uses Atheros but often it's ath11k rather than ath9k; is ath11k fully free?

<ieure>kvt, ath11k is not free.

<ieure>kvt, Any laptop with a m.2 wireless card can get it replaced with an ath9k. Some manufacturers have been soldering them for a while, though.

<ieure>I have a ThinkPad X13 Gen 2 AMD, it's a m.2 card on those.

<kvt>A card is definitely a more affordable option too. I've got a Thinkpad X270 on which I'm typing this, maybe it's simply time to get the screwdrivers out. :-)

<kat>I am using a Thinkpad X270 with Guix myself

<kat>one thing to note

<kat>when you replace the wireless card, make sure you are buying the right key of M.2

<kat>the vendor I saw that produces M.2 wireless cards was thinkpenguin

<kat>you can get ath9k wireless cards on AliExpress, but they will be mPCIe and you will be disappointed. thinkpenguin's card(s) are pretty expensive

<kat>in my searching, i did not find a suitable M.2 ath9k card, but maybe i am just bad at looking!

<kvt>Is there something noticeable about the cards if they have the right key? Something I can see?

<janneke>there's also technoethic[al]

<kvt>Oh, I see the key: the different shape of the connectors.

<kat>for what it's worth the X270's M.2 slots that aren't the NVMe are type A NGFF / M.2 (WLAN) and type B NGFF / M.2 (WWAN)

<kat>mhhm

<kat>the X270 is in a relatively nice position at the moment (libreboot pretty much just got support for it and i am finishing the PR for upstreaming support to coreboot awaiting a test from a skylake user instead of what i have, a kbl x270) so

<kat>if you already own an X270, you can certainly work towards more freedom for yourself o:

<kvt>Luckily it's only iwlwifi dirtying up my computer but it would definitely be cool to get rid of it; and Guix is intersting because it's like supported-by-GNU GNU Guix :D

<kat>janneke: and they only sell USB or mPCIe cards, no? that's what i saw, anyway...

<kat>i should really just buy a thinkpenguin card myself, i am using an ath9k usb dongle :p

<ieure>You can get some expensive ath9k m.2 cards.

<kvt>mPCI on TechnoEthical, yeah. But ThinkPenguin ship to the EU too, although customs are going to get their calculator out for me :D

<kvt>Hah! I emptied my "computer stuff I might some day need again" box and there's a TechnoEthic dongle in there. I barely remember buying it. That's a good start.

<janneke>kat: ah right that could be -- and prices have gone up, i see

<kvt>I'm guessing everybody's going to up prices :( Tariffs on one side and no available affordable RAM on the other.

<kat>it's more important now than ever to be able to make the most of your older hardware and to liberate it by whatever means you can, i guess? :p

<kvt>Exactly. Thanks to free software the old stuff will keep running.

<kat>also, are you aware of the prochot issue with the x270 and third-party 9-cells?

<kat>you should make yourself aware of it, if you aren't o:

<kvt>I'm on my last original battery so I'll be reading!

<kvt>Ugh, time for work :-( THANK YOU for your help! <3

<sunless>i'm having a problem with "guix pull", it giving the error "guix pull: error: unsupported manifest format"

<sunless>i don't know what caused it, and rolling back isn't fixing it

<thanosapollo>Hey Guix, I have this PR here https://codeberg.org/guix/guix/pulls/6140 that fixes git-http regex pattern and prevents git-http-backend from serving arbitrary files outside of Git

<thanosapollo>operations if anybody can check it out.

<futurile>Morning

<efraim>o/

<user_oreloznog>\o

<futurile>thanosapollo: a team has been assigned to your PR, you could try reaching out to any of them to see if they are interested in it

<futurile>efraim: I'm having a good time trying out Jujutsu - if you don't 'love' git it's definitely worth looking at

<futurile>efraim: I'm going to stick with it for 2 weeks and then see where I am

<efraim>thanks. I don't love git but I don't hate it either. I guess I've been using it long enough that I'm just used to it and not really looking at changing right now

<efraim>I guess to think about it probably too much, I'd rather keep vim and ditch git than keep git and ditch vim

<futurile>heh heh

<futurile>yeah messing with tools endless is annoying - at some point you _just_ want to get work done!

<futurile>I've never been good with git - it has always felt like I'm in footgun territory - so the much better user-experience and the fact you can 'undo everything' will probably be worth it for me

<identity>Jujutsu is more-or-less a Mercurial UI to the git backend, with some new fancy stuff here and there

<futurile>identity: yeah, the "on git backend" is critical

<futurile>identity: for me it means I'm "derisking" my interactions with git - I always worry I'm going to mess up my team-mates with some stupid mistake

<futurile>identity: AND I get a better user experience

<futurile>identity: ... without learning Emacs ... cos I hear that's the True Way (TM) to git heaven ;-))

<futurile>we'll see where I am in a couple of weeks

<identity>Magit only helped me plunge deeper into git hell, really. i stick to vc.el now, and minimize my interactions with git either way

<futurile>I tried using EasyGit (what capitalisation that uses I'm not sure) for a "Magit like" experience; and Jujutsu has a similar thing built-in - where you can select chunks.

<trev>i didn't see a good reason to use jj instead of magit

<futurile>I didn't look into more complex editor integratin yet

<identity>well, git has that too with git commit --interactive

<futurile>trev: yeah, if you are happy with your current tool there doesn't seem to be a reason to move. It has some interdiff coolness, but it's too advanced for me right now.

<identity>trev: apples to oranges

<identity>magit is just a different interface to git, while Jujutsu is a different version control system altogether that just so happens to use git as its storage backend at the moment

<trev>right

<futurile><nod> if the outcome (files in git your coworkers can use) is the same, then it's primarily "is the overall experience better"

<futurile>versus - oh I have to learn another tool

<futurile>and honestly who wants to learn _more_ about version control!

<identity>try jj and see if you like it

<trev>i suppose i meant more in terms of the high level workflow. magit is pretty painless once you understand what is going on

<futurile>ack

<trev>if someone can show me a better way to work with jj then i would learn it. I've watched a few videos on it too

<futurile>someone announced a 'magit' for Jujutsu - but since I don't know Emacs I didn't look into it

<trev>perhaps it has come along a bit more now. I haven't looked into it since 1-2 years ago

<trev>futurile: forgot to ask, did anything come of sourcing guix funding from "bitcoin focused" companies?

<trev>(context: guix is fundamental to bitcoin core's release builds)

<futurile>trev: no I didn't hear back from anyone

<futurile>trev: if you know the person/email of someone and could introduce me to them I could try and follow-up?

<futurile>trev: the SUSE donation was literally caused by me asking a 'random' KDE foundation person about foundations and they decided to ask within

<futurile>SUSE about helping us - I knew nothing about it - someone's a conversation goes interesting places

<trev>futurile: i can do that. do you have a sort of "cover letter" or introductory thing that I should mention? I can come up on my own with certain benefits of Guix and how they apply to Bitcoin, but probably not so formal

<trev>identity: nice

<futurile>trev: I would come up with your own as that will be your tone of voice - I've done three blog posts that you could steal some words from about why Guix needs support - cc me on the email

<futurile>trev: you've got my email address right?

<trev>futurile: yes, of course, you're a local legend

<futurile>trev: heh heh - I'm both embarrased and preening myself with that comment heh heh heh

<trev>known by AT LEAST 100 IRC nicks!

<futurile>trev: pretty sure you're all figments of my imagination - beautiful mind style

<untrusem>so I have trying to bump zulip-term but it requires some older deps, I don't want to make a older version for each one of them, anything to make it somewhat easy?

<untrusem> https://github.com/NixOS/nixpkgs/blob/master/pkgs/by-name/zu/zulip-term/package.nix#L98

<untrusem> https://github.com/NixOS/nixpkgs/blob/master/pkgs/by-name/zu/zulip-term/package.nix#L50

<untrusem>they have pythonRelaxdeps phase or something I guess

<futurile>untrusem: you could patch the python requirements?

<futurile>untrusem: for rust pkgs the recommendation is to update the crates in a source checkout

<untrusem>yeah, I could do that,

<efraim>for zulip-terminal, it looks like they haven't had a release in a few years, maybe a more recent commit?

<untrusem>yep

<untrusem>I am upgrading to the latest commit

<futurile>so you can't relax the deps to upgrade them? And you're already on the latest commit

<untrusem>I mean its only needed for `sanity-check` phase, the packages builds fine though So I have just deleted sanity-check phase for my personal use

<futurile>untrusem: it also looks like there's a patch to update it to be compatible with a later version of Python - https://github.com/zulip/zulip-terminal/pull/1593

<trev>futurile: do you want to review my email or should i just SEND IT??

<futurile>trev: SEND IT!!

<trev>aaaaaaaahhh

<untrusem>futurile, thanks :)

<untrusem>futurile, see this https://guix.gnu.org/manual/devel/en/guix.html#Channels-with-Substitutes

<untrusem>then it will only pull till where substitutes are available?

<futurile>untrusem: as I understand it, the limitation there is that it's checking whether the commit 'has built a substitute of the list of packages' is available - not that _ALL_ the packages themselves have been built.

<futurile>untrusem: it's a bit weird and the language isn't great - but when I looked into some of the Issues around it that's what I understood.

<mange>I mean, that's what the linked page says, isn't it? "Note that this does not mean that all the packages that you will install after running ‘guix pull’ will have available substitutes."

<futurile>mange: yes it does if you read it carefully.

<futurile>mange: if you don't really understand how Guix works then the sentence above the config is not really explicit. It says "that guix pull uses the latest commit with available substitutes for the package definitions" ... that could mean "all binary packages"

<futurile>at least speaking as "one human" that's how I read it before I went back and reread it again

<trev>just tested it out and i don't know what URL to put cause it just warns: "guix pull: warning: could not find available substitutes at"

<untrusem>trev, https://bpa.st/OJZA

<trev>untrusem: i did something similar but with a different substitute url

<untrusem>yeah I tried with a different url too, I get the same warning as you

<trev>consider me confused now cause i thought that any substitute url would work and then download all the .drv stuff that gets built when doing a 'guix pull'

<untrusem> https://bpa.st/OD4A

<sunless>is there another solution to the error "guix pull: error: unsupported manifest format" other than reinstalling the os

<trev>sunless: `guix gc --verify=contents,repair' maybe?

<trev>never had that issue

<GuixSurKVM>Bonjour

<GuixSurKVM>Je voudrais m'entraîner à utiliser la distribution linux Guix System. Je ne sais pas si ce salon est francophone.

<seres_>GuixSurKVM: bonjour! c'est un salon très majoritairement anglophone (mais avec des gens de tout les coins du monde j'ai l'impression)

<GuixSurKVM>J'ai pour l'instant rencontré deux problèmes:

<GuixSurKVM>1. Impossible de vérifier l'iso guix-system-install-1.5.0.x86_64-linux.iso.

<GuixSurKVM>2. Après installation dans une machine virtuelle en utilisant virtmanager avec hôte NixOS l'affichage Spice se bloque à chaque fois qu'une veille de gestion d'énergie se produit dans la machine invitée Guix System.

<GuixSurKVM>Bonjour seres_

<GuixSurKVM>Y a t il un salon spécialisé francophone ?

<seres_>GuixSurKVM: pas à ma connaissance

<GuixSurKVM>Avez vous déjà réussi à verifier la signature de l'iso ? Voici ce que j'ai obtenu de mon côté, en suivant le manuel Guix 1.5:

<GuixSurKVM>gpg --list-keys

<GuixSurKVM>[keyboxd]

<GuixSurKVM>---------

<GuixSurKVM>pub rsa4096 2014-08-11 [SC] [expire : 2026-04-07]

<GuixSurKVM> 3CE464558A84FDC69DB40CFB090B11993D9AEBB5

<GuixSurKVM>uid [ inconnue] Ludovic Courtès <ludo@gnu.org>

<identity>GuixSurKVM: <https://paste.debian.net/>

<GuixSurKVM>J'imagine que j'ai mal rédigé mon message. Je me dois d'utiliser paste.debian.net pour les comptre rendus de console ?

<seres_>GuixSurKVM: oui de préférence, c'est plus lisible

<GuixSurKVM>Je remets cela. Je n'ai jamais utilisé. Merci seres- pour ton aide.

<GuixSurKVM>seres_

<GuixSurKVM>J'essaie

<GuixSurKVM> https://paste.debian.net/hidden/a9660dac

<GuixSurKVM>Je crois aue mon paste n'est pas pertinent, désolé. Je le reforme.

<seres_>GuixSurKVM: et à la vérification ça dit "Pas de clé publique" ou quelque chose dans ce genre c'est ça? la clé publique utilisée pour signer l'iso a changé mais le changement n'est pas encore refleté dans le manuel Guix https://codeberg.org/guix/guix/issues/5946

<seres_>does anyone know what is blocking https://codeberg.org/guix/guix/pulls/6213 from getting merged?

<futurile>I don't think it's _blocked_, it's waiting for someone to do it

<GuixSurKVM>seres_: ah oui c'est très vraisemblable mon pastebin https://paste.debian.net/hidden/397ac04e.

<FuncProgLinux>o/

<futurile>heya FuncProgLinux

<FuncProgLinux>futurile: Hello :D what's cooking?

<futurile>FuncProgLinux: Guix-wise all-quiet; I'm playing with Jujutsu this week - in between work work work heh

<seres_>futurile: is there anything i can do to "bump" that PR, in a friendly way? i guess i just did by mentioning it in here...

<FuncProgLinux>futurile: Nice! I've fallen behind schedule with some MATE updates on my end :/ haven't had enough free time to focus and finish another merge request.

<futurile>seres_: probably not, Rutherther is going to do it, and I know they are taking a break from Guix work. I guess wait a couple of weeks and then ping in the PR.

<futurile>FuncProgLinux: also there's about 40k builds waiting at the moment due to the security issue causing the whole graph to be grafted or something - so your builds might wait a bit

<FuncProgLinux>futurile: I see. That gives me time then. Is that issue in Codeberg? I haven't seen it in the Guix blog :(

<seres_>futurile: thanks for the infos! also, how's jujutsu?

<futurile>FuncProgLinux: oh looks like it cleared a lot: https://ci.guix.gnu.org/metrics <-- half way down the page it shows 'Pendng builds'

<futurile>FuncProgLinux: it doesn't show the architecture, so I imagine a lot of those are the alternative archs

<futurile>seres_: loving Jujutsu so far, I fear git generally - so a 'better' git that's compatible is perfect for me - hoping it goes well!

<trev>futurile: please write a blog post on your findings so i can read it instead of nerd sniping myself into another "thing"

<seres_>+1

<guixSurKVM2>Re j'ai voulu enregistrer ta page web et j'ai ma fenêtre iceCat qui a frisée.

<graywolf>How do you typically create /run/user/$UID on servers? elogind is not trigger by ssh iirc, so what do people do?

<mwette>web search indicates that is created via pam

<RavenJoad>So I sorted out why texdoc does not pull up the package's documentation PDF. texlive-scheme-* and texlive-collection-* packages don't actually do anything with the doc output on the individual TeX packages. Is there a nice way to install all the documentation too? Or do I need to do a tree-traversal of the package inputs and do this manually?

IRC channel logs

2026-02-26.log