IRC channel logs


back to list of logs

<joshuaBPMan>Hey #guix !
<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.
<vits-n-guix>OK, wleslie. Thank You.
<wleslie>you're welcome!
<wleslie>is there any documentation on upgrading from a very old guix (0.14.0) ? I could probably wipe the old version and re-install...
*vits-n-guix lots of compilations, btw.
<wleslie>yeah, my profile is just stuff I can afford to lose, going the dalek route
<vits-n-guix>wleslie: make a manifest file?
<wleslie>good tip, but I'll just start fresh. so much good stuff in the packages list.
<brendyyn>something bad happened.
<brendyyn>somehow a build failed and the error messages broke out and started running as code in my terminal
<brendyyn>ok scratch that the build actually completed
<apteryx>sneek: later tell zimoun the patching to emacs looks OK (not build breaking, and only *extends* the search paths to make them useful on Guix, rather than outright overriding them.
<sneek>Will do.
<wleslie>how can I configure guix to run out of a store on another partititon?
<wleslie>sneek: move store?
<rekado>wleslie: Guix respects the environment variables NIX_STORE_DIR, GUIX_STATE_DIRECTORY, and GUIX_DATABASE_DIRECTORY
<rekado>note that you can’t *just* use another store, you’ll *also* have to use the corresponding store database.
<wleslie>cool, I'm happy with my database, just need to move my store.
<rekado>database and store must match
<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!
<brendyyn>lukashevich: It has been packaged but is not quite complete. Your welcome to try apply the patch and test it:
<rain1>it is recommended to use tails rather than to browser
<rain1>it is not recommended to use it inside a VM like qemu, but doing so may be the best option
<lukashevich1>brendyyn: that sounds like fun! I will give it a try. Thank you. :)
<lukashevich1>rain1: I completely forgot about its existence :) If I were to run a system like that, though, I'd go with heads ( I will give it a shot, too!
<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
<alextee[m]>Mingw-x86_64-gcc for example
<alextee[m]>And ar, ld, etc
<hud98>Why was linux-libre downgraded from 5.8.8 to 5.8.7?
<jonsger>hud98: because it breaks something
<peanutbutterandc>Hey there
<peanutbutterandc>Can somebody please take a look at this: ?
<peanutbutterandc>`guix environment -L $(dirname that-package-definition) --ad-hoc chordpro` works but at runtime gives me this error (when I try to create a pdf):
<rekado>wleslie: about your second question: yes, see Offloading in the manual.
<brown121407>Hi. Is there a way to stop Guix from installing or upgrading packages if substitutes are not yet available for them?
<NieDzejkob>you can achieve something like that with --dry-run and --do-not-upgrade
<zimoun>brown1214: nothing I am aware of. However, you could check the avaibility before upgrading with “guix weather”. Easierif you use a manifest file. :-)
<sneek>zimoun, you have 1 message!
<sneek>zimoun, apteryx says: the patching to emacs looks OK (not build breaking, and only *extends* the search paths to make them useful on Guix, rather than outright overriding them.
<zimoun>apteryx: cool! About Emacs snippets. Thank you for having checked.
<janneke>any recent commit that builds gnome-shell?
<brendyyn>meson-for-build on core-updates fails for me, although i made some small changes elsewhere, i don't think they should have affected it
<brendyyn>sorry my bad, it was mesa, not meson-for-build
***jonsger1 is now known as jonsger
<raghavgururajan>Hello Guix!
<peanutbutterandc>If there are any perl hackers here: please do take a look at this issue that I've run into:
<peanutbutterandc>Here's the package definition:
<janneke>hmm, it seems these ruby packages won't offload
<peanutbutterandc>the funny thing is: this definition worked before (well, before 3 local commits):
<peanutbutterandc>...but was ugly. And I don't like (propagated-inputs) so I'm trying to get rid of it by using (wrap-program)....
<janneke>guix offload: error: corrupt input while restoring '/gnu/store/guix-IBTa0h/lib/ruby/....'
<janneke>hmm, possibly i need to update my guix-daemon first
<peanutbutterandc>Okay... after going over to #perl and #emacs and everything... I really think this is just a guix issue after all.....
<peanutbutterandc>I have PERL5LIB set to include a certain directory....
<peanutbutterandc>but it doesn't seem like the perl script can find the modules required....
<peanutbutterandc>package definition:
<peanutbutterandc>runtime error during PDF generation
<peanutbutterandc>Is there anything wrong with this wrapper: ?
<rekado>I what’s the exact error?
<peanutbutterandc>I've had to use `out/lib/perl5/site_perl` to wrap the main program...
<peanutbutterandc>rekado, Oh hey there, Mr. wurmus!
<peanutbutterandc>rekado, This is the exact error:
<rekado>this doesn’t look like the usual Perl error
<rekado>does /gnu/store/89vcp32zn3fg4sq7my4x1d16d6b1nvql-chordpro-0.974_017/lib/perl5 actually contain the module App::Music::ChordPro::Output::PDFClassic::PDF?
<peanutbutterandc>However, if you look at the wrapper, the very last of the PERL5LIB entry is the one that contains the 'out' of the build, whose tree (as seen here:
<peanutbutterandc>rekado, Yes sir.
<rekado>it says something about require at line 1
***jonsger1 is now known as jonsger
<rekado>what’s that thing it requires?
<peanutbutterandc>Line 1 is just a shebang, sir
<peanutbutterandc>Here is the package definition (as it stands right now):
<rekado>don’t know then
<rekado>perhaps there’s something interesting in that file
<rekado>maybe the error location is wrong
<rekado>perhaps it needs even more Perl modules to be compiled…?
<peanutbutterandc>The thing is: this package definition worked three commits before:
<peanutbutterandc>and I'm just trying to remove all (propagated-inputs)
<peanutbutterandc>and polish the definition up
<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!
<peanutbutterandc>rekado, Okay. Thank you nevertheless! Hope you have a good time!
<leoprikler>raghavgururajan: just so I know, have you packaged gtranslator?
<peanutbutterandc>Whoa! This turned out to be a guix issue after all!!!!!
<peanutbutterandc>I just found a .pm file whose source shebang wasn't patched properly, I think
<peanutbutterandc>It's just '# perl'
<peanutbutterandc>for some reason
<peanutbutterandc>If anybody wants to see for themselves what I mean, please `guix environment -L . --ad-hoc chordpro` this definition:
*mbakke finally got around to clean up and submit patches that have been brewing locally for weeks \o/
<peanutbutterandc>..........or just build, actually, and then cd to the build directory
<peanutbutterandc>APP::Music::ChordPro::Output::PDF's shebang isn't patched
<raghavgururajan>leoprikler: Nope! Though it is now known as GNOME Translation Editor. The former name, gstranslator, was misleading.
<leoprikler>hmm, okay
<leoprikler>maybe i'll package it once I'm finished with my minor translation stuff
<raghavgururajan>I wish it was a translator. But it is for editing .po files.
<raghavgururajan>Ah Cool!
<peanutbutterandc>Okay... gentlemen, I think I might have stumbled into a bug in the perl-build-system
<peanutbutterandc>Please `guix build chordpro` from and then `cd` into the built /gnu/store directory and `grep -r '#! perl'
<peanutbutterandc>the shebangs aren't all patched
<peanutbutterandc>and these all seem to be .pm files
<peanutbutterandc>(or perhaps I am doing something wrong in my build)?
<peanutbutterandc>curioser and curioser.... `find . -iname '*.pm'` in the built directory gives a few more files than the ones with the shebang errors
<peanutbutterandc>.... and their shebang is patched pretty well
<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..
*str1ngs nom nom
<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...)
<peanutbutterandc>mbakke, Whoa! You're actually a maintainer!
<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>Does anyone use Nix on-top of Guix System?
<raghavgururajan>I have set up nix-service-type.
<raghavgururajan>[1] Whenever I do `nix-env -i foo`, I get "warning: name collision in input Nix expressions, skipping '/home/rg/.nix-defexpr/channels_root/nixpkgs'". [2] After every reboot, I have to do `source /run/current-system/profile/etc/profile.d/`, 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
<raghavgururajan>str1ngs: `guix download foo`?
<raghavgururajan>It will give hash as output.
<str1ngs>right that's what I don't want to do. I'd like to generate a hash from local git tree.
<peanutbutterandc>str1ngs, this probably isn't what you want, but I've been using `guix hash -rx` to generate the hash of the entire local tree
<peanutbutterandc>`guix hash -rx .` inside a repo
<wigust>raghavgururajan: [2] you need to source with your .bash_profile. This is because of not to colide other users by loading automatically. [1] 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
<peanutbutterandc>whereas the one with propagated input worked just fine
<str1ngs>what is bar-bar?
<peanutbutterandc>str1ngs, bar-bar is a propagated input for bar, which is supposed to be an input for 'foo'
<peanutbutterandc>str1ngs, Here: This works but this does not:
<raghavgururajan>> wigust‎: raghavgururajan: [2] you need to source with your .bash_profile. This is because of not to colide other users by loading automatically.
<raghavgururajan>Thanks! How to do that? Just paste the line in .bash_profile?
<peanutbutterandc>and I suspect it is because a lot of packages in the dependency chain are propagated-inputs...
<peanutbutterandc>I just want a confirmation/denial from someone who is more competent with guix than me.
<str1ngs>peanutbutterandc: so is bar-bar the only thing that can't be found?
<str1ngs>regards to PERL5LIB
<r-7>Has anyone else had trouble setting up racket on Guix System? raco pkg install pollen within racket just generates four errors
<peanutbutterandc>str1ngs, Not really.... All things are there... but it still complains. It isn't complaining about bar-bar... it's just that 'bar does not work at all' kind of situation:
<peanutbutterandc>which is very strange because the HTML output, Text output, all work just fine. Here's the tree:
<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
<peanutbutterandc>str1ngs, already did that!
<peanutbutterandc>At the bottom: in arguments
<str1ngs>check the wrapped chordpro and make sure it's right
<str1ngs>also probably PERL5LIB is set in the build environment check if it is. then you can just do : prefix `(,(getenv "PERL5LIB"))
<str1ngs>that would simplify your expression.
<str1ngs>you can check by adding (begin (display (getenv "PERL5LIB")) (newline) (exit 1)) before your wrap let.
<peanutbutterandc>Hmmm... the wrapping is in 'prefix' mode
<str1ngs>anyways the point about the wrap is if PERL5LIB does get set. it will be based on the inputs so that you don't have to manually do book keeping which is error prone and tedious :)
<peanutbutterandc>Hmmm... I think the wrapping is pretty decent: is it not? o.O
*raghavgururajan finds flatpack better than nix, to install on-top off guix.
<str1ngs>peanutbutterandc: looks okay to mean
<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, the unpolished package definition:
<brown121407>zimoun: thanks a lot for the manifest + `guix weather` tip. I didn't know you could do that.
<str1ngs>peanutbutterandc: same here
<peanutbutterandc>str1ngs, I have a strong feeling it is because of the (propagated-inputs) in the chain of dependencies.
<str1ngs>peanutbutterandc: I'd find out what backend is needed ask via some chordpro or perl help channles
<peanutbutterandc>str1ngs, I kinda' did that... and all evidence points to the propagated input issue
<peanutbutterandc>so now I'm going to try and see and make sure whether or not it is indeed the case or not
<peanutbutterandc>and file a bug report if it is
<str1ngs>peanutbutterandc: understandable
<peanutbutterandc>str1ngs, I was correct, captain!
<str1ngs>did you find the package that is required?
<peanutbutterandc>str1ngs, Yes, 3. I will send you the updated package definition soon
<str1ngs>peanutbutterandc: guix hash -rx . does work btw
<peanutbutterandc>str1ngs, I'm glad I managed to score 1 in helping you. lol (:
<peanutbutterandc>Hmm.... strange... I messed up just now. somehow. and it does not work anymore. Dubug time again. :D
*rekado just removed /mnt/root-fs/gnu/old-store/ on
<peanutbutterandc>str1ngs, Oh, I have pushed the updates. Here: I am not sure if I should report this as a bug.... but I do think it'd be nice to heavily discourage the use of propagated-inputs
<peanutbutterandc>... since manually hunting for dependencies kinda' defeats the whole purpose of a package manager
<peanutbutterandc>Also, how do I start a guix environment with just bare-bones gnu-build-system or python-build-system ?
<str1ngs>peanutbutterandc: can you check if PERL5LIB is set?
<str1ngs>in the build environment
<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
<str1ngs>okay let me check.
<peanutbutterandc>In the meantime, how do I fire up a guix environment with just bare-bones gnu-build-system?
<peanutbutterandc>guix environment -e '(@ (guix build-system perl) perl-build-system)' does not work
<peanutbutterandc>str1ngs, Oh wow. It appears that PERL5LIB is set during build. Atleast before the 'install phase (which is where I checked)
<peanutbutterandc>so I can just trim my wrap-phase to use... (getenv "PERL5LIB"), is it?
<str1ngs>peanutbutterandc: one sec I'll give you an example
<peanutbutterandc>str1ngs, I think I got it!
<str1ngs>peanutbutterandc: this should simplify your wrap phase.
<str1ngs>peanutbutterandc: your indentations is diff then mine so you'll have to adjust it to your liking
<peanutbutterandc>str1ngs, I just made similar changes!
<str1ngs>good just, as long as you get the general gist.
<peanutbutterandc>But I like your approach of not using (append) but using two unquotes
<str1ngs>good stuff*
<peanutbutterandc>I think I'll try that
<peanutbutterandc>that looks cleaner
<str1ngs>I like to treat code as data.
<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.
<peanutbutterandc>Thank you, master foo (:
<str1ngs>I dunno about master foo lol
<peanutbutterandc>str1ngs, (:
<str1ngs>peanutbutterandc: one other thing I like to do is put the continuation #t at the vary tail of the lambda. the effect is the same. but it shows at a glance what the lambda returns.
<peanutbutterandc>str1ngs, I am also doing the same thing.... it is there after the let block... is it not? *checks*
<str1ngs>maybe it is already. don't mind me :)
<peanutbutterandc>str1ngs, You should read some of the tales of master foo. This one's quite funny:
<str1ngs>that's funny
<peanutbutterandc>lol :D
<str1ngs>I want to see master foo deal with a 10,000 line shell script.
<peanutbutterandc>But master foo's shell script would probably be poetic
<peanutbutterandc>I thought guix's installation script was one of the most beautiful thing I'd seen in quite some time
<str1ngs>so when I cloned your repo I named it peanut-packages
<peanutbutterandc>lol :D please do send me some PRs if you want to
<peanutbutterandc>I'm glad that my channel is getting some clones
<str1ngs>ahh was a one off to check PER5LIB I needed the extra depends it poovided
<str1ngs>can this be contributed to guix at all?
<str1ngs>chordpro that is?
<leoprikler>Every proof is a one-liner if you start with enough margin on the left.
<peanutbutterandc>str1ngs, Yes. It is entirely free software
<peanutbutterandc>however... I will have to upgrade it to the latest version first
<peanutbutterandc>I am going to do that in a while
<peanutbutterandc>Pulling an all nighter. It's already past midnight here
<str1ngs>peanutbutterandc: nice
<peanutbutterandc>str1ngs, do you have commit access?
<peanutbutterandc>to guix repo?
<str1ngs>peanutbutterandc: oh no, I just mail in the odd patch.
<peanutbutterandc>str1ngs, I see. Weren't you working on TuxGuitar at one point?
<str1ngs>peanutbutterandc: I did rework that declaration and added the alsa plugin
<str1ngs>though I've been to busy to practice piano. I only pickup my guitar now and again. :(
<peanutbutterandc>str1ngs, I see... cool! I haven't used tuxguitar in a while now. Does sound work out-of-the-box yet? o.O
<str1ngs>it should on guix system. using guix package with the system alsa is not ideal. if you recall
<rekado>another good one is powertabeditor
<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
<rekado>it’s a reimplementation actually!
<rekado>which is incredible to me
<rekado>back then there was some animosity between the ptb users and the Guitar Pro users; the free reimplementation supports both formats :)
<nckx>Good morning Guix!
<sneek>Welcome back nckx, you have 2 messages!
<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, Good Morning! (:
<nckx>raghavgururajan: Docker doesn't touch my machines. I wouldn't mind packaging MailPile for Guix, but I'm pretty damn happy with Roundcube and not likely to do so.
<nckx>‘A lot of strings’ 🙂
<nckx>10, apparently.
<peanutbutterandc>haha. I'm sure it was more than 6.
<nckx>Hullo peanutbutterandc.
<peanutbutterandc>okay 10
<peanutbutterandc>nckx, Long time no see (:
<nckx>There are apparently different versions.
<peanutbutterandc>Different versions?
<nckx>Of the stick.
<peanutbutterandc>I see... and oh, can I make you proud?
<nckx>peanutbutterandc: Yeh, well, 2020, y'know :-/
<nckx>peanutbutterandc: Please do.
<peanutbutterandc>nckx, Here: Your young padawan n00b has grown. :D
<peanutbutterandc>And I did get a few other patches signed off by Mr. Courtes himself too :D
<rupicapra[m]1>hey everyone
<peanutbutterandc>There aren't that many, but I hope these are a start
<peanutbutterandc>hey there!
<nckx>Hullo rupicapra[m]1.
<nckx>peanutbutterandc: Super cool. Also very happy to see another KDE user/maintainer step up 😉 We don't have many of those, chicken-eggwise.
<nckx>Ah, kdenlive seems to be used by all faiths, but my point stands.
<nckx>(Do you use KDE?)
<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.
<peanutbutterandc>This one was a long time coming, too. I actually sent a patch for the complete breeze theme. Mr. Courtes signed those off:
<peanutbutterandc>I feel like a kid showing their drawing to the parents. You've been helping me out since a long time.
<nckx>I think you sell yourself short.
<peanutbutterandc>It's very kind of you to think so. I wish that were really the case. It just was a lot of trial-and-error, asking around IRC, and stuff...
<peanutbutterandc>I did manage to get a (union-build) working. `guix show breeze`. So that's something I think was pretty cool. (:
<peanutbutterandc>union-builds are neat
<rupicapra[m]1>I'm trying to make a python package but when running "guix build -f" i get " ERROR: Failure: ModuleNotFoundError (No module named 'tests')
<leoprikler>all guix packaging is trial and error ;)
<rupicapra[m]1>Is this related to guix or the python package?
<leoprikler>probably something wrong in the test phase?
<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
<leoprikler>(because it is)
*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
<rekado>peanutbutterandc: if you’re interested in the engraver: here’s an example score:;a=blob;f=stafftab-examples/;h=3f39d1fb207b144e852f65fb160b68534adb8aeb;hb=ea79f808400a6d56c9a4043f4c009da2fda98a3d
<rekado>(it’s Gentle Giant!)
***warreq[m] is now known as shtwzrd[m]
<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
<peanutbutterandc>Thank you nevertheless
<guixy>Hello guix!
<guixy>I made changes to the common build options, and now tests/scripts-build.scm fails.
<guixy>What is a good way to debug the tests?