IRC channel logs


back to list of logs

<mroh>I noticed the same while using as a channel: the (directory "fancy-name") in .guix-channel doesnt seem to work, because i get lots of "no code for module"...
<Formbi>you have to have stuff somewhat along those lines
<Formbi>(define-module (my-packages some-file) (…)
<Formbi>before I knew it I had no idea what was going on when I was trying to make a package
<mroh>ah, $GUIX_PACKAGE_PATH is the problem: the directory definition in .guix-channel seems to work w/o GUIX_PACKAGE_PATH, but not w/ setting it...
***jonsger1 is now known as jonsger
<apteryx>mroh: great that you found the source the problem!
<mroh>apteryx: ty!
<mroh>I think its unrelated to leoprikler's problem.
<guix-vits>Hi Guix.
<Blackbeard>Hi \o/
<Blackbeard>How is everyone
<Blackbeard>They just declared phase 2 in my city. People is filling the supermarkets today
<Blackbeard>Fortunately I have everything I need
<Blackbeard>We goth ready weeks ago
*apteryx just realizes how convoluted the file format for sudoers is
<guix-vits>Blackbeard: What is phase 2?
<jackhill>apteryx: seems appropriate here
<jackhill>Blackbeard: I'm fortunate enough to have everything I need and will be able to remain home for a while and hope things improve
<Blackbeard>Ohh just that there way more coronavirus now and people living here is infecting people here. Not people from italy or china anymore
<Blackbeard>jackhill: that is good
<jackhill>hope thins work out for you too. Where are you, if you don't mind?
<apteryx>jackhill: haha!
<jackhill>apteryx: I knew all that time I wasted on on the web reading xkcd would pay off :)
<Blackbeard>jackhill: Mexico
<Blackbeard>My fear is a mix of coronavirus + drug cartels
<nckx>sudo is like a gun that shoots you in the foot by default.
<nckx>Don't forget to un-disable the never-don't-miss-my-foot inhibitor or you'll be fine.
<nckx>Does anyone know how to weasle out of an infinite variable reference recursion in Guix?
<Blackbeard>nckx: I've been reading spstemd units documentation
***Server sets mode: +cnt
<Blackbeard>nckx: hahhaha
<Blackbeard>jackhill: thanks :)
***modula2 is now known as defaultxr
<apteryx>jackhill: after a couple wasted hours: maxim ALL = NOPASSWD: /home/maxim/.config/guix/current/bin/guix repl -t machine
<apteryx>this allows giving root access just to the right incantation of Guix, needed by 'guix deploy' :-)
<apteryx>still means that an attacker can do whatever if they gain access to your account... I guess it's marginally better than allowing SSH to root.
<jackhill>wooo! Victory. Should we put that in the manual?
<apteryx>yes, I think so! I just need to figure out how to append this to the default sudoers file now.
<apteryx>got it: (plain-file-content %sudoers-specification) returns the string, that we can append into a new plain-file of our own
<apteryx>so something like this:
<jr0>Anyone have a sample config of how to have cgit listen on 443. I do not understand the manual sufficiently to do this.
<ebrasca>Hi when I try to sign some commit I get "error: gpg failed to sign the data"
<ebrasca>I have GuixSD
<lfam>ebrasca: How are you trying it?
<ebrasca>lfam: git commit -m "Test"
<lfam>I mean, what did you do to set it up? Do you have a working gpg setup? And git configured to use it?
<lfam>For git you need to tell it which key to use and how to invoke gpg
<ebrasca>It was working in gentoo.
<Kimapr>hello everyone
<Kimapr>i succed in installing guixsd on a flashdrive
<ebrasca>lfam: I have .gitconfig done
<Kimapr>writing this from it
<lfam>Awesome Kimapr!
<lfam>ebrasca: What's the value of 'program' in your gitconfig?
<ebrasca>program = gpg
<Kimapr>but there is one problem
<Kimapr>everything that reads the disk is damn slow
<lfam>ebrasca: I would try specifying the full path. '/var/guix/profiles/per-user/ebrasca/profile/bin/gpg' or similar
<Kimapr>and booting is superslow
<lfam>Kimapr: Like a USB flash drive?
<Kimapr>because it IS USB flash drive
<lfam>Guix isn't optimized for that, unfortunately
<Kimapr>but guixsd always booted up slowly on my computers
<lfam>And those things tend to be a lot slower than hard drives or SSDs
<Kimapr>even on HDD
<lfam>Yes, it really wants an SSD
<lfam>Looking up things in /gnu/store is not fun on a spinning disk
<Kimapr>it wants to run some services but timeouts lots of times
<apteryx>jackhill: ah... it also ran Guile... hm.
<apteryx>wanted to*
<ebrasca>Can I sync my profile with root profile=?
<ebrasca>lfam: I don't have this path.
<lfam>Try '.../guix-profile/bin/gpg'
<Kimapr>anyone knows awesomewm? I wanna ask if it is possible to move windows to different workspace without a second screen
<ebrasca>lfam: gpg is only on /gnu/store/*/bin/gpg
<lfam>Did you install gpg yet?
<lfam>If it's installed, it will be in your profile, which found in that '/var/guix/...' place
<ebrasca>I have "gnupg" in packages file config.scm.
<lfam>Then you can use the path for that profile, which is '/run/current-system/profile/bin/gpg'
<lfam>Or '/var/guix/profiles/system/profile/bin'
<lfam>They point to the same place but I prefer '/var'
<ebrasca>I have /run/current-system/profile/bin/gpg
<lfam>Great, try putting that as the value of program in your git config
<lfam>You have your keys all set up, right?
<ebrasca>My keys are ok.
<ebrasca>It is not worlink with "program = /var/guix/profiles/system/profile/bin/gpg"
<lfam>You can sign files with your keys though?
<Kimapr>oooh, everything starts soo slow. when i type a command in Meta+R line, it freezes the wm for ten seconds
<ebrasca>lfam: Yes , I can encrypt with my key.
<Kimapr>and it builds xdg mime database for eternity
<lfam>Okay, next step I would strace the git command to see where it fails, ebrasca
<ebrasca>what do you mean with strace?
<ebrasca>lfam: Are you there?
<lfam>Hey ebrasca
<ebrasca>lfam: How do you trace git?
<lfam>Assuming that gpg is working, my next step would be to run the git command with strace. The error message it's printing is not very specific so tracing it should help diagnose the problem
<lfam>Install strace, then run something like this: `strace -f -o output.log git commit ...`
<ebrasca>lfam: Here
<lfam>I think you need to set the location of the gpg pinentry in '~/.gnupg/gpg-agent.conf'
<lfam>Something like 'pinentry-program /var/guix/profiles/system/profile/bin/pinentry'
<lfam>You'll have to install a pinentry program
<ebrasca>I have pinentry-program /var/guix/profiles/system/profile/bin/pinentry-tty
<ebrasca>And I have "pinentry" in my packages
<ebrasca>lfam: ^
<lfam>Git is failing to find it, based on your trace
<ebrasca>Do I need to add some pinentry service?
<lfam>Maybe try another pinentry. It's possible that git is swallowing the password prompth
<Blackbeard>barrage is now in guix ٩(◕‿◕。)۶
<Blackbeard>My first accepted patch :D
<ebrasca>lfam: Do I need to restart pinentry or someting? ( I have tested all other pinentry and get error )
<lfam>pinentry is not a service
<lfam>I'm not sure what's wrong
<ebrasca>It is guixsd.
<jr0>I have finally moved most of my public facing services to guix running on a linode.
<Kimapr>is there any way to disable building xdg mime database?
<Kimapr>it takes too long to build
<Kimapr>after each package install
<ebrasca>Is there some wiki for guixsd?
<Kimapr>type "info" in your terminal
<Kimapr>or "info guix"
<Kimapr>did it help?
<ebrasca>It is not wiki with search options
<Kimapr>then there is manual at guix's site
<Kimapr>you can open the onepaged variant and search it with your browser's search
<Kimapr>otherwise it is the same
<ebrasca>I just like to sign my git commits.
<Kimapr>then why would you need a wiki for that
<Kimapr>aren't git commits signed automatically
<ebrasca>Kimapr: It don't work, here log
<Kimapr>i have no clue how to fix this
<ebrasca>This is why I seach for some wiki.
<ebrasca>To search how to fix my problem.
<Kimapr>oof, my browser doesn't doesn't show numbers
<Kimapr>how to fix it?
<Kimapr>i remember that i should install some packages but forgot which
***apteryx is now known as Guest48020
***apteryx_ is now known as apteryx
<raghavgururajan>Kimapr: `guix package --install gs-fonts font-dejavu font-gnu-freefont-ttf` and `fc-cache -f`
<leoprikler>mroh: You can observe the same bugs with $GUIX_PACKAGE_PATH, but malformed files are ignored.
<leoprikler>but yeah, symlinks can solve the problem even if they are a bit ugly
<ebrasca>Fixed my problem with git and gpg.
<nataraj>, trying on a Slackware-current
<nataraj>Am I missing out on something?
<chiefgoat>Is PXE booting yet a thing for Guix System?
<janneke>chiefgoat: i haven't heard; but "iwbn"
<user_oreloznog>chiefgoat: not yet but it's a project
<chiefgoat>user_oreloznog: thank you :-)
<janneke>user_oreloznog: nice, ty
<user_oreloznog>janneke: with pleasure :-)
<nckx>Good morning, Guix! Is there a way around this <> that doesn't involve disgusting modular reshufflings?
<guix-vits>Another box is arrived; Now i'm wait only for the heatsink delivery.
<guix-vits>Hi nckx.
<guix-vits>How to build doc/guix.texi? `makeinfo --html` give me nothing. `guix build -f build.scm` in doc dir give me nothing too.
<janneke>try: make info
<janneke>(or make html, if you prefer slow and keyboard-unfriendly browsing)
<guix-vits>janneke: qutebrowser changes that.
<mroh>woa, lots of updates today. congrats on merging the staging branch! (now, lets wait for `guix weather webkitgtk` ;)
<brendyyn>can i apply a patch in patches that is defined as an origin?
<guix-vits>brendyyn: in my experience, one should explain what are oneself doing. Guixers are trolls that give the passage only when paid by story :) What are you struggle to accomplish?
<cbaines>brendyyn, yes
<brendyyn>guix-vits: Apply a patch without adding it to the guix repo and using search-patches
<brendyyn>i think i may have got it to work
<cbaines>I'm not sure whether this is the prefered way of packaging things for Guix though
<nckx>Hullo guix-vits.
<nckx>Whacha building?
<Kimapr>- -av- ---l--s --t- -----a-d
<Kimapr>- d-sc----ct-d t-- -----a-d a-d g--xsd d--s-'t d-t-ct -t aft-- - c----ct-d -t -ac-
<Kimapr>s---- f-- --ss--g l-tt--s
<nckx>I -av- more l-tt--s than you.
<nckx>Here, have some.
<nckx>(And it's G--x S--t-m now.)
*nckx goes back to editing OSM.
<guix-vits>nckx: Hi nckx. o/. i'm tried to build a html from doc/guix.texi, to get more recent version with: `makeinfo` and `guix build`. But janneke has pointed me to info format. `info guix` giving me new doc (as new as `guix pull`). So currently i'm not building anything :)
<guix-vits>Kimapr: Do you have some troubles with a keyboard (- is no, any other letter is yes)?
<nckx>guix-vits: I meant the heat sink 🙂
<guix-vits>nckx: RockPro64
<Kimapr>it connected back
<guix-vits>Mother bought me it, with a NAS casing.
<Kimapr>explaining what problem i had - i disconnected my external keyboard from the laptop
<Kimapr>and when i connected it back - guixsd didn't detect it
<guix-vits>nckx: i'm try to build a low-energy desctop: for emacs and Web.
<Kimapr>and laptop's builtin keyboard is broken
<mbakke>guix-vits: are you running Guix System on it?
<Kimapr>some keys don't work
<guix-vits>mbakke: no. It's not arrived completely yet. I'm have a case, a board, a ... no heatsink. Need to buy a thermal-paste and an HDMI-thing.
<mbakke>right, sounds fun (except for the waiting...) :)
<guix-vits>Also i'm wonder, if i'm really need a anti-static bracelet, or i can just touch the "heating pipe" with legs while assembling.
<guix-vits>If yes, then i'll rather need to order the anti-static stuff to, as asking around there gives me nothing about where one can be bought.
<sirgazil> is rendering incorrectly. I can't find 2019 and 2020 logs.
<sirgazil>And sometimes even 2017 and 2018 are missing.
<guix-vits>sirgazil: mayb[14:54:47] *** Quits: iyzsong (~iyzsong@fsf/member/iyzsong) (Quit: ZNC 1.7.1 -
<guix-vits>sirgazil: but look at the last message. Some glitch?
<guix-vits>there is a message about iyzsong quits the channel (embedded in my message, which is cut).
<nckx>guix-vits: Just make your own conductive bracelet (any conductive wire will do) and earth it.
<nckx>‘Really need’ isn't the question. If give you 0.1% odds to lose (say) $100 or win nothing, you'd still be a fool to take those odds.
<nckx>Kimapr: I thought you were playing a game, sorry, didn't intend to mock you. 🙂
<guix-vits>nckx: So, using a copper line wrapped around wrist and connecting to "heating pipe" count?
<roptat>hi guix!
<guix-vits>hi roptat.
<roptat>watching libreplanet live now. This morning I was able to build a package with a fully bootstrapped maven build system :D
<roptat>(it was only a parent pom, so a very easy package)
<roptat>I'll try to build an actual package, and if I succeed, I'll send some patches :)
***benny is now known as Guest38108
*guix-vits reading
*guix-vits was thought that school is boring.
<brendyyn>Is there a way to set the timezone in the build environment?
<brendyyn>for a test
*guix-vits "stand on a hard floor in bare feet." -- yeah!
<mbakke>roptat: wooow, that's huge, congrats! :D
<roptat>thanks :)
<roptat>actually, I'm stuck at the install phase for that package because I'm still missing the maven-install-plugin ^^
<roptat>but I definetely "build" it
<rekado>brendyyn: yes! See r-rstan in (gnu packages cran), for example.
<mbakke>now, if only we could get 'java-kafka-clients' to build on the CI :/
<nckx>guix-vits: If your heating pipes are grounded. Depending on where you live and the kind of power outlets you have, clamping it to an actual earth pin might be a better option.
<nckx>Assuming your house is in order, those should™ be regulated by law.
*nckx writes this from a house where 50% of earth pins go absolutely nowhere… but at least I know which.
<leoprikler>Is there a way to use non-guix guile packages (e.g. guile-json) directly in a gexp?
<leoprikler>okay, found the error, I made a typo :(
<guix-vits>nckx: thanks. i'd heard that pipes are grounded, but not even thought that they can be "grounded". i'm living in :)
<guix-vits>"panel" one.
<guix-vits>"Some theorists even considered combining toilet-bowl functions with the shower's sink, but the idea was discarded..." -- thank duct-tape!
<NieDzejkob>drainful: when you edit a file, do you get a a "note: source file newer than compiled ..." message?
<drainful>NieDzejkob: yes
<nckx>Please paste your diff somewhere. Maybe Guix isn't seeing what you think it is.
<nckx>drainful: ☝
<nckx>You could also try running make again, although that shouldn't be necessary if you just edited a package.
<drainful>Do I have to run make when using pre-inst-env?
<drainful>My diff is here (M-x magit-diff-unstaged)
<nckx>What a horrible pastebin. Not your fault, but please use in the future.
<drainful>thanks for the tip
<nckx>Or your favourite non-horrible bin 🙂
*nckx has to download the patch with FF, then scp it to another box, because they block curl. 😒
<drainful>ah sorry
<nckx>patch: **** Only garbage was found in the patch input
<nckx>Bit judgy.
<nckx>But yeah, it's not a real patch. Could you ‘git diff’ instead?
<nckx>OK, not what I'd hoped, diff is fine. ~/guix/pre-inst-env guix build bitlbee-discord works fine here.
<nckx>So what does ./pre-inst-env guix package -A bitlbee-discord show?
<nckx>The old version?
<drainful>Yes. When I ran configure i passed /var as the local state directory; is that causing the issue?
<nckx>No, that's good.
<nckx>I'd remake Guix from scratch (guix env guix, bootstrap, configure --localstatedir=/var, make, etc.) if you haven't yet.
<nckx>This is all very strange though.
<nckx>You can first try ‘guix environment guix -- ./pre-inst-env guix package -A bitlbee-discord’ first to make sure [16:43:09] <brendyyn> drainful: you may be setting stuff in your .bashrc that should be in .bash_profile
<apteryx>anyone wondering why openvpn cannot add remote DNS server automatically?
<guix-vits>apteryx: it can pull an script that will, say, rewrite your /etc/resolv.conf
<apteryx>guix-vits: isn't openvpn supposed to do this by itself? Or is it expected that the user be burdened with configuring such script?
<nixo_>Hi guix! Just found a "bug" that prevents guix from booting. I'm using libreboot+btrfs with compression enabled. After switching to a new configuration, I could not boot. Found that if I disable compression (I'm using zstd) on /boot/grub folder, it works again
<drainful>I believe I was mistaken about the pure environment solving my problem; I had already begun make at the time, and now it works with or without a pure environment. All's well that ends well.
<nixo_>Don't know where to report it, or if I should upgrade libreboot
<guix-vits>apterix: idk, seems later.
<guix-vits>nixo_: try `guix pull; sudo guix system reconfigure YOUR_CONFIG.scm; guix package -u`, reboot. i'm use lzo, though.
<nckx>nixo_: libreboot bug tracker but check if there's a new version first.
<nckx>Your GRUB payload is just missing zstd support.
<nckx>Guix boots zstd just fine.
<guix-vits>nckx: so libreboot's GRUB can't be updated with `guix`?
<nckx>Eh, no.
<zander>hey guys, any CI server that I can look at?
<nckx>Maybe using Guix tools (flashrom is in Guix). But Guix doesn't handle libreboot.
<zander>I just ran make check and one test failed on master/HEAD
<guix-vits>i'm sorry, nixo_
<nixo_>nckx: Thanks. Yes I think the problem is in the grub that lives in libreboot, as it's just that single file that leads to problems.
<guix-vits>nckx: thanks.
<nckx>Guix was probably one of the first distributions to support booting btrfs+zstd, because I like the new shiny things and then had to fix my shiny thing 🙂
<nckx>zander: Could you post the log output to or another sane bin?
<zander>the log is a bit large, fighting with the pastebin now...
<zander>ok, here is part 1. Seems I can't paste the rest, the server tells me I'm spamming
<nckx>zander: Thanks!
<leoprikler>Can someone explain to me, how git-download is able to do a git-fetch inside a gexp?
<apteryx>leoprikler: (use-modules (guix build git)
<apteryx>line 114 in git-download.scm
<rekado>leoprikler: the gexp for git-download embeds a native reference to git
<rekado>line 136 in the same file
<rekado>the build side code in (guix build git) only invokes the git command, trusting that it will be available.
<leoprikler>okay, but how can that git talk to the outside world?
***w2gz is now known as w1gz
<rekado>leoprikler: the same way url-fetch can fetch tarballs
<apteryx>rekado: it doesn't 'trust that it will be available', it receives an explicit reference to it as an argument
<leoprikler>If I have scheme code inside of #~(...), that thing fails with network unreachable
<rekado>apteryx: git-fetch in (guix build git) does not receive git itself as an argument. Just the name of the command.
<apteryx>ah, I got mislead by Geiser. Sorry ;-)
<rekado>(the argument is called ‘git-command’ and is just the string ‘git’)
<nixo_>nckx: specing on #libreboot says it's not supported
<rekado>leoprikler: the fetchers produce fixed output derivations
<apteryx>you're right
<rekado>leoprikler: the are only permitted network access because we have the hash of the result.
<nckx>nixo_: Yet? Or do they really not intend to add it?
<apteryx>but since git is added as an input to the Gexp it runs in, it is safe to do so.
<rekado>apteryx: exactly
<nixo_>nckx: I'm asking
<leoprikler>so basically in order to permit network access, I have to supply a hash?
<Blackbeard>Hello :D
<nixo_>nckx: it will be added when there will be a new release (with will include the new grub)
<rekado>leoprikler: the derivation has to include it, yes. See the docstring of ‘derivation’ in (guix derivations).
<nixo_>adding support for libreboot compile+flash from guix will be super cool then, if we could replace the bundled grub with ours
<rekado>(I don’t know if this is sufficient, but it is necessary)
<apteryx>is it possible to tell that a service should not be started automatically at boot?
<leoprikler>rekado, apteryx: thanks
<nckx>nixo_: It's been ages since I've used a non-UEFI GRUB with Guix, but you should be able to write a custom grub.cfg that chainloads a newer GRUB on a non-btrfs partition, which then reads your Guix's grub.cfg and can load the kernel+initrd.
<nckx>This second GRUB would be hand-installed to a small non-btrfs partition, not managed by Guix System.
<nixo_>nckx: thanks, but it's too much work, since it's enough to disable compression under /boot :D
<nckx>I don't think that would solve it.
<nckx>Unless you're already manually copying your /gnu/store/…{bzImage,initrd} to /boot.
<nckx>Libreboot being able to read grub.cfg alone isn't enough.
<nckx>It still has to read the actual OS.
<nckx>I'm only 98% certain here because I don't use Libreboot, but I'd be surprised if its GRUB were so very different from a normal set-up.
<nixo_>nckx: /gnu/store/..raw-initrd/initrd.cpio.gz is not compressed (according to compsize). Don't know if it's because it's uncompressible binary data or if it came from a pre-zstd compression setup
<nckx>I hadn't thought of that. I guess you could bet the bootability of your system on btrfs's bail-out heuristic correctly detecting initrd.gz and bzImage as compressed 100% of the time.
<nckx>It's obvious what I think of that but it's an option 😛
<apteryx>What is the issue with Libreboot and Btrfs? I miss the start.
*apteryx gives a fresh try to network-manager-openvpn-plugin
<nixo_>apteryx: btrfs+zstd compressed /boot with libreboot does not work
<apteryx>but libreboot just embeds GRUB, to be able to cope with reading the file system, correct?
<apteryx>and GRUB 2.04 is able to do that. Then it's just a matter of updating the Libreboot GRUB copy to 2.04? No?
<nixo_>yep, they'll upgrade on the next release
<apteryx>so it's a short lived problem :-)
<specing>who knows when it'll be released
<specing>just apply the workaround, it is simple and futureproof. And the big files in /boot are compressed anyway.
<apteryx>oh, has the workaround already been written?
<specing>It is: mv /boot/ /oldboot; mkdir boot; chattr +c boot; rsync -avi /oldboot/ /boot/; rm -r /oldboot
<lfam>Is there any documentation of the limitations of the build chroot? I'm wondering if UNIX sockets are possible in there so I can help with <https://>
<NieDzejkob>lfam: I don't know, but I feel like it wouldn't take long to test it
<lfam>There is a little documentation in the manual, Build Environment Setup.
<lfam>It would be nice to flesh it out a bit based on the code
<civodul>lfam: re, networking to localhost in the build env is possible
<sneek>civodul, you have 1 message!
<sneek>civodul, rlb says: my "clever" plan to make a more efficient pcre2 wrapper might not work out for common cases. So far it doesn't look like pcre2 can be asked to treat an ioso-8859-1 byte sequence as a unicode subset, i.e. for byte-width units, it looks like it can only do utf-8 or "not unicode" with differing behaviors.
<lfam>civodul: Okay, thanks
<civodul>so it could be that the server is just not running yet (race condition)
<civodul>or that it failed to start
<civodul>or that the software expects you to start it by yourself
<civodul>sharing wild guesses :-)
<lfam>Wild guesses are quite helpful. I started replying to email I have no understanding of!
<lfam>Got a lot of free time at the moment.
***matijja``` is now known as matijja
<TZander>I'm running guix for the second day now, on top of a host OS. The various docs gave me the incentive to set some env-variables. But it looks like two are in conflict and give me a different guix executable. It looks like the $HOME/.guix-profile should be ignored, is that correct?
<TZander>or, more specifically, sourcing the $HOME/.guix-profile/etc/profile file sets the path which gives me a bad guix executbale.
<rekado>TZander: ~/.config/guix/current/bin should be first in your PATH.
<rekado>TZander: there should be no ‘guix’ executable in ~/.guix-profile/bin
<rekado>TZander: if you’ve installed the ’guix’ package into your profile: remove it.
<TZander>ah, you guessed correctly. I managed to do an install of guix when pull didn't work. Thanks, that solved it.
<nixo_>can I override the package used by a service without working with ./pre-inst-env? (set! pulseaudio) for example seems to work, but I feel guilty
<nckx>lfam: ++ on the ...!
<lfam>nckx: It should be safe for the master branch, right?
<lfam>Alright, I will test it out shortly
<nckx>Does it require the guix package to be bumped after pushing to have any effect, is my question.
<nckx>But that will become clear on its own.
<nckx>I bet we all feel a bit silly for not making that change years ago.
<lfam>Fresh eyes are so valuable
<nckx>I made a similar patch replacing worst-of-all-worlds `…' pseudoquotes with proper ‘…’ ones y'day, now emboldened to actually post it.
<nckx>The stuff we put up with daily just to not be seen as pushing ‘noise’, silly 🙂
<lfam>Let's deprecate the command-line interface and make Guix GTK-only
<nckx>Just a dropdown with packages and an ‘I feel lucky’ button under it.
<nckx>The packages are not sorted.
<lfam>civodul: I looked at the Cuirass code but since I am not very familiar with it, I'm asking to be sure. Cuirass doesn't honor the max-silent-time property either, right? In addition to ignoring the timeout property?
<lfam>I mean... we do need a package / profile GUI
<nckx>Wouldn't that be better served with a PackageKit (or whatever's hip nowa') back-end instead of reinventing the UI wheel? Honest question, I don't use GUIs much.
<drainful>If I have 2 patches, one to fix a package and one to upgrade the package, should I post the two patches as a series?
<lfam>I would
<nckx>drainful: Yes. With the fix first.
<lfam>Especially if the patches "depend" on each other
<lfam>Like, does the upgrade patch apply without the fix patch?
<nckx>If they depend on *each other* I'd merge them, no?
<drainful>Right. The upgrade depends on the fix, so I'll do a series. Thanks.
<lfam>I think it would be nice to have the fix patch on the old version, and then upgrade the package
<lfam>It's a matter of taste, really
<lfam>Patch author's choice
<drainful>makes sense
*lfam builds new LibreOffice
<nckx>Updating a broken package to fix it in the next patch might technically fly, but it goes against the spirit of the rule to keep each patch building.
<lfam>Right. First the fix patch, then the update patch
<drainful>Is there a difference between including the patch as an attatchment and in the body of the mail? Additionally, should I sign my email with gpg?
<nckx>lfam: What do you build on and how long does it take?
<lfam>nckx: x230 laptop, limited to 2 cores so it's still pleasant to use. Should take hours
<lfam>2 "logical" cores
<lfam>drainful: It's the same either way. Signing is up to you, it doesn't really matter for this purpose
<lfam>We still have to review your code, whether it came from you or from a dastardly villain
<nckx>drainful: I prefer in-line but I'm not sure if there are good arguments for that, or just me. Same with GPG signing: not a hard requirement and your sig won't make it into the git log, but *please* do. GPG depends on people building up a record of reputation more than the web of trust these days.
<lfam>nckx is right too
<nckx>But yeah, as lfam notes, it's the signed-off-byer who vouches for you.
<nckx>And is signatorily responsible if your shit were to hit a fan.
<lfam>I was thinking of getting an x260 laptop but I'm out of work long-term due to covid
<drainful>Thanks for the advice
<nckx>lfam: With the build limited to 2 cores , or everything (SMT vulns…?)?
<lfam>Yeah, with the CPUs nerfed
<nckx>I've haven't gone that far.
<nckx>(X230 here too.)
<lfam>I just use what Debian gives me
<abralek>Regarding patches. My bug report is a mess now.
<Blackbeard>How can I unbundle libraries included in the tarball to use the ones by guix?
<lfam>abralek: What do you mean?
<nckx>Blackbeard: There's no one-size-fits all answer to that.
<Blackbeard>This is a CMake build
<abralek>7 patches, multiple version of each of them
<Blackbeard>Do I have to past flags or do I delete them?
<abralek>and also different subject
<lfam>abralek: Ah, the openjfx patches, right? :)
<lfam>They'll get reviewed, don't worry
<lfam>Yes, it's a mess
<lfam>It happens
<Blackbeard>nckx: oh
<abralek>I was using subject-prefix but it skip PATCH
<nckx>Blackbeard: You want to start with removing the bundled code in a snippet if possible, then fix the build until it works. How, depends. Many packages support --with-libfoo=/gnu/store… or --use-system-libfoo flags, some need more obscure flags, make flags, or even patches.
<nckx>Try to find a cmake example.
<nckx>You might get lucky.
<Blackbeard>Damn :(
<abralek>Today I was checking other patches and everything looks ok
<Blackbeard>It is going to be a mess then :/
<nckx>There are packages in Guix that include bundled code but don't use it (because deleting it entirely breaks the build even when not using the code).
<abralek>Does anybody use magit?
<nckx>That's not ideal because you can never be sure that none of that bundled code is used.
<nckx>So it really depends, sorry.
<nckx>abralek: Lightly.
<abralek>I was wondering maybe someone can share git config format-patch and send-email
<abralek>lfam: regarding that mess, shell I start from scratch? Close the open one, and report a new one?
<lfam>abralek: No, don't worry about it. It's not that bad for me in Mutt
<lfam>What do you mean by sharing those things abralek?
<nckx>abralek: I do both of those things from the command line, but I can share my .gitconfig if that's what you mean.
<abralek>well for example there settings for [no-]-thread, [no-]chain-reply-to
<abralek>what I am interested in is the way to post [PATCH vX ...]
<abralek>Is that the right way?
<Blackbeard>nckx: ok I'll try :)
<abralek>nckx: that would be great
*nckx doesn't use any of those. suppresscc = self, that's about it. ‘$ git send-email -v2 …’ to send V2s. 🤷
<lfam>abralek: In my shell history I have lots of commands like this: `git send-email --subject-prefix=v2 --to --thread=shallow --annotate origin/master`
<lfam>Unfortunately Git is super complicated so you just have to read the manual pages and keep trying. Maybe send test emails to yourself
<abralek>lfam: hm, does it keep the PATCH tag in the subject?
<abralek>lfam: true
<lfam>I don't know... probably?
<nckx>I'll think you'll be disappointed, there are no clever things or obscure settings in mine:
<nckx>-v2 definitely keeps PATCH and is much shorter to type 😛
<lfam>You can just type -v2 ???
<nckx>With TLDs going the way they are that'll be a premium one soon.
<lfam>Without --subject-prefix?
<sneek>I'll keep that in mind.
<lfam>sneek: forget it
<lfam>sneek: botsnack
<nckx>sneek: No you won't, silly bot, your mind is rot and we love you.
<lfam>sneek: what do you know?
<nckx>sneek: Who is sneek?
<sneek>sneek is a good bot
<abralek>nckx: Thanks
<abralek>I have still a couple of silly question
<abralek>1. is it better/easier to send a set of common patches separately or as a one bug
<nckx>Common as in related? Definitely one bug.
<abralek>yes, related,
<nckx>Side note: how to do that (‘the debbugs dance’) is explained in the manual. Never send more than 1 patch to guix-patches@.
<nckx>‘Sending a Patch Series’.
<nckx>abralek: These are not silly questions. Please ask them. A tidy bug tracker will make everyone happy and people will like you better for it.
<abralek>I have read the manual and the guix contribute notes
<nckx>Great 🙂
<abralek>Thanks, the second one is: if you have your bug with related patches and need to update one, do you send the whole series with v2 or not?
<abralek>nckx: Hm emacs doesn't show me the last character. Ah slightly smiling face =)
<nckx>Slightly? That's someone else's opinion. I say smiling.
<abralek>yep, that what C-u x = says =)
<abralek>I just wanted to say that this debbugs dance is interesting
<nckx>Hm, that's (IMO) a judgment call. If you're updating, say, one patch out of 11 I think it's clearer to send a V2 of only that one. Any sane MUA should make it quite clear what's happening. But others could disagree of have some workflow that makes a full 11-patch V2 easier. I still call it ugly.
<abralek>Hm, all those questions are the leading ones to the 3 one
<nckx>It is a beautiful dance born out of technical limitations, as all great art.
<nckx>Oh no wait it just sucks sorry.
<lfam>Thank you
*nckx smiles slightly.
<abralek>So I am in my debbugs gnus ephemeral buffer
<abralek>with a bunch of emails (consider openjfx bug as an example) How can I easily mark the latest patches and O m them?
*nckx uses mu4e and no emacs-debbugs so defers to someone more wizardly.
<abralek>nckx: hm, mu4e, so you subscribed to guix-patches list?
<nckx>I use magit for one thing: one-key ‘git rebase -i’ editing in emacs. But I git from the command line exclusively.
<abralek>Do you use a custom query in mu4e for the latest or what?
<abralek>Could you please tell me you workflow?
<nckx>The latest v of each patch in a series? If that's even possible I don't know how I'd write that.
<nckx>For review? Workflow is a big word for just invoking ‘git am’ on the buffer(s). Which is why I prefer in-line patches.
<abralek>for applying patches
<nckx>Yeah, ‘git am’.
<abralek>do you do them one by one?
<nckx>Like a pleb.
<abralek>The problem is that I have to save them to mail (mbox)
<nckx>The number of 20-patch series I review a year (0-1) simply doesn't warrant learning a new workflow for me.
<lfam>If the patch series is really long I ask the author to host a git branch somewhere
<abralek>Thanks. I am very new to the mail patching thing, hence the questions.
<nckx>abralek: What do you mean by ‘have to’? git am takes ‘mbox files’, that is true, but that's a fancy name for ‘takes any correctly formatted mail as stdin’.
<drainful>I just sent my first patch, should i have gotten an automated response right away?
<nckx>C-| git am RET
<nckx>drainful: Nope, let me moderate you.
<abralek>AFAIK I have to mark the latest patches *and* then O m them into mbox
<abralek>I do believe I had tried to mark all of them and apply, but something bad happened
<nckx>drainful: Oh, you're not stuck in moderation. Then your mail will be sent ASAP.
<nckx>drainful: It can sometimes take a few minutes.
<nckx>I should really emacsify my git workflow.
<nckx>But, you know, stuff. Also: things.
<drainful>Got it. I haven't signed it, and I included the patch as an attachment so that the web mail client doesn't mess up the formatting. I'll get a better setup, but i didn't want that to get in the way of a simple patch.
<abralek>C-| git am RET won't work If I am not in the git repo
<nckx>Why would you ever not be in the guix git repo‽
<abralek>=) Yeah you right
<nckx>I'm certainly not claiming mine is a universal workflow, or even good, but you asked.
<nckx>drainful: Signing mails is recommended but has no effect on your commit or the mailing list.
<abralek>nckx: Thanks
<nckx>Attachments are also fine (better than mangled gore) & the only reason to get a better set up is your own sanity.
<abralek>I spend all day long in magit and it's great
<drainful>nckx: Emacs has eaten most of my computer and hungers for more, so I'll have a better mail setup by the time i send in my next patch.
<nckx>drainful: What was your patch called? (And you sent it to guix-patches@, right?)
<nckx>drainful: I cannot imagine having to paste patches into a Web form.
<nckx>Or however that works.
<drainful>sent to, subject: "[PATCH 1/2] gnu: bitlbee-discord: Fix build failure"
<nckx>drainful: Hah, you literally just popped into the moderation queue after I asked that, so it was just a Yahoo → GNU delay. I approved your message.
<drainful>Wonderful. I'll send in part 2/2
<nckx>You're whitelisted now so go nuts.
<drainful>It's a shame I missed the deadline for the outreachy program since as a non-student I'm not eligible for gSoC. I'll try to catch the next round.
<janneke>from a popular messaging network right now: "There's still a little time to have your lightning talk included in #LibrePlanet2020!"
<nixo_>Stupid question, but in an operating-system definition, how do I get a package output path?
<nixo_>like ungexp, but it it's unbound and importing (guix gexp) does not help
<lfam>Are you saying that gexps aren't working?
<lfam>I have this line in my user-account section: (shell #~(string-append #$zsh "/bin/zsh"))
<lfam>It works fine
<nixo_>Yeah i forgot to gexp it
<nixo_>thanks :D
<lfam>Great :) Remember to import the package module in use-package-modules
<nixo_>lfam: no I can't get it to work. The exported file contains the #<gexp ..
<lfam>nixo_: I recommend sharing you config.scm on <>
<nixo_>lfam: relavant part:
<lfam>What's pulseaudio-modules-bt?
<lfam>That string doesn't exist in the Guix codebase
<nixo_>lfam: it's a package I've defined
<nixo_>I'm trying to add this
<lfam>And what exactly is the error message?
<nixo_>no error message, but the file (daemon.conf) contains the raw gexp (#<gexp (string-append #<gexp-input #<package pulseaudio-modules-bt@1.3 nx/packages/pulseaudio-bluetooth.scm:48 7f0837ea9b40>:out> path ":" #<gexp-input #<package pulseaudio@13.0 gnu/packages/pulseaudio.scm:136 7f0841f776e0>:out> path) 7f08404b1780>)
<aidenholmes>is anyone here familiar with guix-home-manager
<drakonis>the dev is in here
<bandali>that’d be roptat
<roptat>hi :)
<aidenholmes>hello, i followed the instructions in the README
<aidenholmes>but it didn't make a guix home command
<aidenholmes>i get "guix: home: command not found"
<roptat>yeah, there's a bug in guix where channels cannot create new guix command as the should
<aidenholmes>what should i do
<roptat>I believe this is documented on the guix home, but here is the solution: set $GUILE_LOAD_PATH to include your ~/.config/guix/current/share/guile/site/3.0
<roptat>that way guix will be able to see the modules
<aidenholmes>ok so in bashrc
<roptat>actually, it is able to load the modules just fine by itself, but it does it only *after* fetching the code for the command :/
<roptat>if you use the bash home type, it will be set for you though
<aidenholmes>i should /not/ set HOME to /data/tony right
<roptat>no, that would be a bad idea
<roptat>rather, it would defeat the purpose of the home manager
<aidenholmes>ok now i got
<aidenholmes>guix home: error: readlink: Invalid argument
<roptat>since the tool is already installed here, I didn't test the first install a lot... Do you have more than that?
<aidenholmes>one sec
<aidenholmes>what do you mean? more than what?
<roptat>more than "readlink: Invalid argument"
<roptat>this is your first install, right?
<aidenholmes>yeah above that it says
<aidenholmes>guix home: warning: consider running guix pull followed by guix home reconfigure to get up-to-date packages and security updates
<aidenholmes>yeah i just installed guix on this laptio
<roptat>mh... not very helpful ^^'
<aidenholmes>it literally has nothing installed except for what the .iso installs
<roptat>do you have $HOME set'
<davidl>I was trying to import a package from pypi just now and Im getting this error:
<davidl>ice-9/boot-9.scm:1669:16: In procedure raise-exception:
<davidl>X.509 certificate of '' could not be verified:
<davidl> signer-not-found
<davidl> invalid
<davidl>any ideas_
<aidenholmes>$HOME is set to /home/tony
<roptat>aidenholmes, does it exist now?
<aidenholmes>which is empty except for ~/.cache which just created itself
<aidenholmes>i moved everything to /data/tony already
<aidenholmes>does what exist?
<roptat>I see
<roptat>there's only one place where guix-home uses readlink, so that's actually not too hard to understand what is happening
<roptat>can you run "rm -rf /home/tony" then "ln -sv /var/guix/profiles/per-user/profiles/home /home/tony"
<seepel>davidl: Do you have the nss-certs package installed? ?
<roptat>that should create the symlink that is required (guix home should create it for you, but instead it fails because readlink is not doing what i expected it to do
<aidenholmes>as root?
<aidenholmes>/per-user/profiles doesn't exist
<aidenholmes>did you mean .../per-user/tony
<roptat>oh yes
<aidenholmes> ln -sv /var/guix/profiles/per-user/tony/current/guix /home/tony
<roptat>no home, not guix
<roptat>ln -sv /var/guix/profiles/per-user/tony/current/home /home/tony
<roptat>ln -sv /var/guix/profiles/per-user/tony/home /home/tony
<aidenholmes>that doesn't exist
<roptat>I know
<aidenholmes>then how do i link it
<roptat>it's just going to create a dangling symlink from /home/tony
<aidenholmes>ok done
<roptat>now you should be able to run guix home again
<aidenholmes>as root or as tony?
<roptat>as tony this time
<davidl>seepel: not in my user-profile but I do as root or system profile
<aidenholmes>can't even login, says Unable to cd to '/home/tony'
<roptat>mh... then symlink "/var/guix/.../home" to "/data/tony" for now
<roptat>that way you will be able to login and use guix
<aidenholmes>this is getting pretty meta
<roptat>then after the reconfigure, that symlink will be replaced with a proper guix home generation
<davidl>seepel: running sudo guix import pypi mypackage works
<roptat>I need to rework that part of the home manager
<seepel>davidl: Hmmm, by system profile I assume you mean in the packages definition in your operating-system? That is the same as my configuration and I thought that package was responsible for ssl (I'm a bit new to guix myself though).
<aidenholmes>oh boy it's compiling something now
<aidenholmes>"your home directory has been reconfigured"
<davidl>seepel: it helped to run as root, so thanks!
<aidenholmes>ok now what do i do lol
<roptat>now everything should be broken as expected :p
<aidenholmes>it's still just a symlink
<roptat>yes, now your $HOME is a symlink to /var/guix/... which itself should now be a symlink to /gnu/store/... (eventually, there might be another level of symlinks)
<apteryx>civodul: about that Btrfs udev rule fix you pushed a week ago about, had you seen this: bug#35357
<roptat>your $HOME should now be decoupled from your /data
<aidenholmes>no /home/tony -> /var...home -> /data/tony
<aidenholmes>oh nvm
<seepel>davidl: Glad it worked, Though, if your user can't use ssl you'll probably have a hard time. Can you wget some url over https as your user?
<apteryx>civodul: it is perhaps a better solution? it mentions Ricardo had a patch to build eudev with --bindir set to $out/bin
<roptat>did it work?
<davidl>seepel: yes all normal stuff works.
<aidenholmes>/home/tony -> /var...home -> /var...home-1-link -> /gnu...home
<roptat>yay \o/
<seepel>davidl: Good!
<roptat>congrats, your home is now read-only and taken over by guix :D
<roptat>you will regret this :p
<aidenholmes>do you have a manual on how to use guix home after it's installed
<aidenholmes>no i reget having an un-reproducible mess of an ubuntu install on every other computer i own
<roptat>(which is not the same as the top-level README)
<roptat>unfortunately, the home manager has some really bad bugs and doesn't support many software yet
<roptat>I'd be glad to hear any feedback you have though, even if it's "your doc sucks" :)
<aidenholmes>wait can i only use this to configure the 6 programs listed in the doc?
<roptat>yeah :/
<aidenholmes>btw i plan on also installing nix on here
<aidenholmes>so this won't help me make, for example, my i3wm config reproducible and part of the master file
<roptat>in general, you can always use the symlink-file-home:
<aidenholmes>oh ok
<roptat>that will allow you to create a symlink to your /data so the software has access to a read-write directory
<roptat>if you want i3wm support, you'll need to write it though
<roptat>I think I'm lacking that kind of documentation, though you could take a look at existing home types, they are not too difficult to understand I think
<roptat>I'm working alone on this currently, so it's really limited :)
<aidenholmes>no worries
<aidenholmes>ok now i have a question about guix in general
<roptat>go ahead
<aidenholmes>when installing a package, i know they're generally installed with "package -i" but how to i install it in such a way that i can get a list of everything installed and install them on another computer
<aidenholmes>like manifests i think
<aidenholmes>if you use spacemacs, like how the .spacemacs file controls what's in .emacs.d
<roptat>with a manifest :)
<roptat>there's "guix package --manifest"
<aidenholmes>oof i have an error already
<aidenholmes>/var...guix-profile does not exist
<roptat>what does "ls -l $HOME/.guix-profile" tell you?
<aidenholmes>it goes to /data/tony/.guix-profile
<roptat>ah but that one doesn't exist, does it?
<roptat>try this: "HOME=/data/tony guix install hello"
<roptat>then you should be able to use guix package commands without setting HOME
<roptat>(probably just creating a symlink would be enough actually)
<aidenholmes>but now i just realized my .bashrc is gone
<aidenholmes>i should configure ymlink-file-home to from
<roptat>yeah, but you could use the bash home type to create one
<aidenholmes>what do i run after edding home.scm
<roptat>guix home reconfigure home.scm
<janneke>5min lightning talks can still come in to libreplanet until 12am EDT tomorrow
<aidenholmes>guix home build?
<roptat>guix home build only builds the generation, but it does deploy it
<roptat>reconfigure will build and install the new generation
<aidenholmes>trying it edit it
<aidenholmes>it says "did you forget a use-modules form
<roptat>can you share you home.scm on
<aidenholmes>i already shutdown
<aidenholmes>also i don't have any graphics installed yet so i'd have to use one of those pastbins that lets you upload via curl or something
<roptat>as the message error suggests, you're probably missing a (use-modules) at the top of your file
<aidenholmes>i have one
<roptat>something like (use-modules (home)) and (use-modules (home bash)) or something like that
<aidenholmes>not working on this for the rest of the day
<roptat>ok :)
<roptat>stuck with maven now :/
<roptat>the plugins are built against an older version and there's a failure in maven-model 3.0...
<guix-vits>Hi Guix.
<Blackbeard>Hi :)
<Blackbeard>I've been reading about systemd, Shepherd and it is a lot to learn
<nckx>Blackbeard: What did you learn?