<dissoc>does zfs work on guix? i tried to install the package but it failed
<joshuaBPMan>dissoc I believe that you can make a zfs partition on guix, but I do not believe that you can run guix system on zfs by default.
<dissoc>i thought that was the case. im just trying to use it for non-system disks
<vits-n-guix>Hello Guixen. My system configuration.scm uses module xyz.scm. Is that OK to (raise SIGTERM) inside of xyz.scm?
<vits-n-guix>GNU doc say, "The SIGTERM signal...It is the normal way to politely ask a program to terminate."
<vits-n-guix>But i can miss something, and not wanna broke this Guix.
<wleslie>modules shouldn't normally exit the program themselves, but raise an exception. not only does it mean that callers can handle that case (e.g. by trying something different), but you can also get tracebacks so you can find and fix a problem.
<lukashevich>Good UTC morning, everyone! :) I have a little question: is there a way I can run tor browser on Guix? Or maybe there's a documentation somewhere on how to setup tor manually, so I could browse and do other things. I am learning but what I understood from when I tried to build it is that it couldn't find libraries it needed. Thank you!
<wleslie>while I'm waiting for stuff to install, I've got some broad questions. I'll find my way around things one way or another, but I might be missing something here or there so here's what I'm doing:
<wleslie>I'm porting an antique cross compilation environment. in source form, it's a bunch of patches to old binutils + gcc + a few things. I figure if I rewrite it in guix, it will be easier to try to upgrade these, updating the patches as they go. most of the patches add the new platform to makefiles etc.
<wleslie>I see that there are quite a few cross-builds going on in guix proper. there's the bootstrap, drones, etc. I was wondering if there are any special guix features I should look at for building a cross-compilation toolchain.
<wleslie>on a related note, is there some way I can set up `guix install` to run the build on a different machine?
<alextee[m]>I'd love packages that provide ready to use mingw-ized build tools
<peanutbutterandc>And I just tried to do this another thing: I took the wrapper, removed the exec line, sourced the wrapper to get the PERL5LIB env var in my environment, and then ran /gnu/store/hash-perl/bin/perl to compile App::.......::PDF and it says "no such file or directory"
<rekado>I need to go now, but I hope someone can help you with this!
<mbakke>peanutbutterandc: shebang patching only works for absolute paths (i.e. /usr/bin/perl), I don't think '#! perl' is a valid shebang
<peanutbutterandc>mbakke, Hey there.... Thank you. somebody from perl was explaining to me the same thing.... kinda'. However, this package: the html output works but PDF does not. And one of the things that all the PDF related .pm-s in the built tree seems to be '#! perl' in the shebang line... and that got me wondering if that was the culprit
<mbakke>peanutbutterandc: you can try (substitute* (find-files "pdfdir" "\\.pm$") (("#! perl") (string-append "#!" (which "perl")))) to find out
<mbakke>errh, apparently my IRC client eats escape characters
<mbakke>lol, no, according to the log it's fine, only my display is broken..
<peanutbutterandc>mbakke, I see. Thank you, sir. Should I try placing a new phase after patch-source-shebangs then. (I think I've seen you a lot in the logs, etc. I might be talking to an expert without knowing it...)
<mbakke>peanutbutterandc: you can place that code in any phase you like (as long as it's before the phase that runs those files) :-)
<peanutbutterandc>mbakke, Thank you very much. (I always have a hard time talking to maintainers for the first time. Thank you for your hard work on guix, esteemed maintainer!)
<mbakke>peanutbutterandc: heh, thank you for the kind words :-) I did not notice any communication difficulties! perhaps because you didn't know... ;-)
<peanutbutterandc>mbakke, Whoa. I've like... talked to almost all of the maintainers now. And there are some other crazy super smart people around here, too. I always realize too late how cool of a people I'm talking with.
<mbakke>peanutbutterandc: the Guix community is the nicest community I've had the pleasure of taking part in :-)
*mbakke goes AFK, hopefully back in less than six weeks this time :-)
<peanutbutterandc>mbakke, Yes, Guix people are super cool and helpful. Okay I'll work on that substitute too. Thank you for the help!
<raghavgururajan> Whenever I do `nix-env -i foo`, I get "warning: name collision in input Nix expressions, skipping '/home/rg/.nix-defexpr/channels_root/nixpkgs'".  After every reboot, I have to do `source /run/current-system/profile/etc/profile.d/nix.sh`, to execute programs installed programs from shell.
<raghavgururajan>Actually, not only for every reboot, but for every restart of shell.
<str1ngs>hello, is there any documentation how guix generates source hashes. particularly I would like manually verify git hashes before doing a guix build -S
<wigust>raghavgururajan:  you need to source nix.sh with your .bash_profile. This is because of not to colide other users by loading automatically.  Your .nix-defexpr contains strage channels_root. Try to remove it, add preferred channel, then update it.
<str1ngs>peanutbutterandc ahh guix hash looks useful thanks. I'll play with this
<peanutbutterandc>str1ngs, whoa! So glad I could be of some help. +1 for me (against so many +1s for you in terms of helping me out)
<peanutbutterandc>Hey guix, I have a question. I am packaging a program 'foo' with a dependency 'bar', which itself has 'bar-bar' as a propagated input....
<peanutbutterandc>but, I don't want 'bar' to be a propagated input of 'foo'. Rather, I want to wrap foo to point to bar...
<peanutbutterandc>now my question is: since 'bar' itself has 'bar-bar' as a propagated-input.... does that mean that the only way to make 'foo' work properly is to use 'bar' as a propagated input?
<peanutbutterandc>The reason i'm asking is because a package I'm polishing up (removing propagated inputs in favour of a wrapped program) isn't working after my local polish-up commits
<str1ngs>peanutbutterandc: what is the name of bar-bar.
<peanutbutterandc>str1ngs, There isn't really a bar-bar. I just looked at the package definitions of a few 'bars' and realized that a few of them had (propagated-inputs) and I tried to see whether or not propagated inputs become available to them just so by `guix build bar1` and it seemed to me that the propagated inputs weren't available....
<str1ngs>peanutbutterandc: I think you need to add output to PERL5LIB
<str1ngs>peanutbutterandc: also this error does not say it can't find a module it's saying it can't find a backend
<peanutbutterandc>str1ngs, I know... strange. And since I am not a perl hacker, I have no idea why that is. Also, if you try to build using the unpolished package definition (that uses propagated-inputs) it works just fine.
<peanutbutterandc>str1ngs, It does not seem to have been set to anything during the build.... looking at the final wrapped program... but I will manually set a debug phase there just to be absolutely certain
<peanutbutterandc>I am learning to, too. Scheme/LISP is truly a language of the poets at heart.
<str1ngs>it's a habit from using struct literals and scheme now
<str1ngs>peanutbutterandc: also the nice thing about using (getenv "PERL5LIB") is you get the build environment inputs which makes this functional. and it updates if the inputs change. I'm sure there are some caveats tho this approach though.
<str1ngs>someone slap my hand if that is the case :P
<peanutbutterandc>str1ngs, Yes, that does make much more sense. And that truly is the way of the functional programmer.
<rekado>I used to use the old Windows ptb editor 1.7 way back, so I still have ptb files from then
<peanutbutterandc>str1ngs, Hmmm.... perhaps I should write my own foreigner tuxguitar that inherits from tuxguitar and does all sorts of crazy stuffs. But that'll probably take quite a lot of months as I know no java
<peanutbutterandc>rekado, Yes, powertabeditor is a good one too. I remember my first time using it. It was a song called 'Sleeping Child' by MLTR. I haven't tried the newer powertab though.
<peanutbutterandc>It is good to see that the program survives because of dedicated volunteers
<sneek>nckx, raghavgururajan says: Oh cool! IIRC, MailPile had a docker image, which you could use via docker-service-type? I think it is as less work as deploying the application into the weebroot.
<sneek>nckx, raghavgururajan says: My ssh key has been changed. Could you please update my fingerprint on Bayfront? SHA256:VGr0IEtNuIiUSTIysfcXMzoj71jtD9k9x7sOiIZuQ4Q
<nckx>It's literally dark here but the fiction must be maintained.
<nckx>raghavgururajan: -ESUSPICIOUSLYSHORT. What's the content of your ~/.ssh/id_<algo>.pub file?
<nckx>You can omit the e-mail address if you like.
<peanutbutterandc>rekado, I should really check it out then. I know you play an instrument with a lot of strings. I think I saw a video somewhere. 'Billie Jean', it was, I think. Can't seem to remember where, however.
<peanutbutterandc>nckx, (: Thank you. I don't actually use KDE. But I've decided to learn KDENLive and also not use flatpak (as much as practicable). But hopefully I'll be able to make some more cleanups/contributions.
<nckx>‘Trial-and-error, asking around, ...‘ -- How else would you learn? There's nothing uniquely noobish about that. However, not doing so is a sure-fire way to *remain* a noob, although there's no shame in that either.
<peanutbutterandc>leoprikler, Hehehe But sometimes I really feel like "what is happening here?". I still feel the same way whenever I see a #:modules #:imported-modules and friends
<rekado>peanutbutterandc: oh, yes, I did play this once. I play the Chapman Stick (both 10-string Alto and 12-string Grand, and soon a 10-string Railboard).
<leoprikler>true, #:modules always feels like some advanced wizardry is going on
*nckx just wrote a (PHP+JS) Roundcube plugin and lets the noob pass over them and through them.
<rekado>I don’t use powertabeditor for notation of Stick stuff, though; I wrote a Scheme engraver for Lilypond to handle Stick notation.
<peanutbutterandc>nckx, Hmm.... Well, I hope I'll be able to learn some more and make some more contributions. Hopefully to the guix/* side of things too, someday, and not just the gnu/* side. Thank you for encouraging me, sensei. :)
<rekado>(that Billy Jean recording was from another life; was my audition tape for a Chinese show, actually)
<peanutbutterandc>rekado, whoa. You're like super cool. "I need something to write my obscure instrument's notation in": BAM: writes a scheme engraver for lilypond. And plays. I hope to be able to do the same thing someday. I'm stuck with not being able to show RH and LH fingerings in ukulele tabs.
<peanutbutterandc>rekado, You were really good, too. Where can I watch some more of your performances?
<peanutbutterandc>leoprikler, Yes. #:modules and #:imported-modules and (use-modules) inside of arguments is always quite ominous. What does it do? #:modules imports? then why do we need #:imported-modules? where is it all documented? do we have to treat guix-modules and non-guix modules differently? I have so many questions
<rekado>peanutbutterandc: after all that TV stuff (which I don’t like to share because it also involved a silly costume, a duet with someone who sang playback while I sang live, and weird interviews…) I decided that the disadvantages of recorded performances outweigh the advantages, so there’s almost nothing recent.
<leoprikler>We went over this once, didn't we? #:modules does not import
<peanutbutterandc>rekado, Oh... I see. I hope you start doing just-shows-the-fingerboard type of videos. Perhaps that'll be a good middle. I will check the score out. Thank you. You're super cool!
<peanutbutterandc>leoprikler, Yes... #:modules does not import... but what exactly does it do? I was asking rhetorically, though. Hopefully we'll get the answers someday.
<leoprikler>It makes the modules available (for importing) in the build environment
<peanutbutterandc>leoprikler, I still do not understand the utility of that. I could compare it to `git add` like staging process. But at least one can `git add -p`... anyways, thank you for trying to explain that to me. (:
<leoprikler>assume you need a procedure in (guix build utils)
<leoprikler>then you need (guix build utils) both imported (through use-modules or through #:import-modules), but you also need to have the right code file there guix/build/utils.scm
<leoprikler>how do you know, that you don't also need guix/build/foobar.scm?
<leoprikler>from gexp->derivation: MODULES is a list of names of Guile modules searched in MODULE-PATH to be copied in the store, compiled, and made available in the load path during the execution of EXP
<peanutbutterandc>Hmmm... I will note this... that does kinda' make sense... but I still need to learn a bit more about the matter