<civodul>ok, i can reproduce with the full "guix deploy"
<civodul>always tricky to choose a machine as a guinea pig :-)
<minikN>Good evening, is it possible to call the `search-patches` proc without specifying the strings inline? I tried (search-patches my-patches) with (my-patches (values "1" "2" "...")) but I get an "unexpected end of input while search for ~A". Thanks
<civodul>minikN: hi! you can do (apply search-patches my-list-of-patches), or (map search-path my-list-of-patches)
<apteryx>civodul: yeah I'm a bit worried too -- still deploying to my offload machine with the key local-file commented outs
<civodul>'search-patches' is a procedure that takes any number of arguments
<apteryx>thanks for entertaining my debugging, civodul!
<ajarara>I've found an app that is a couple of major versions behind releases... if I send a patch to update it upstream should I keep the old one around? I've seen nixpkgs do this, like app_2_3, app_2_4, app -> app_2_4
<nckx>If you're just worried about testing wether 2_4 broke something, or need to rescue 2_3 data somehow (again, rare, because 2_4 should be backwards compatible), guix time-machine is good enough, at the cost of any old security updates not being backported.
<civodul>drakonis: ah yes, IceCat says "weak encryption"; not great, but i don't control that server :-/
<ajarara>time machine sounds like 'rewind the channel and eval my system declaration then', instead of 'I want app from checkout xyz, everything else stays the same'. But that's my first impression, probably clearer after reading an info page
<excalamus>vivien, did what you said and included Qt as an input and computed the plugin path
<excalamus>aka, stole code that did that from another package :)
<minikN>civodul: Correction, it didn't work. I tried both map and apply, I get (exception syntax-error (value #f) (value "source expression failed to match any pattern") (value #f) (value search-patches) (value #f)), I did (define my-patches (list "1" "2" "...")) and (apply search-patches my-patches)
<civodul>minikN: ah sorry, i was wrong about search-patches; but (map search-patch my-patches) should work, no?
<ajarara>Noticing lack of poetry/gradle usage in package definitions. These both have the 'resolve dependency constraints into specific versions, fetch from network, build, all in one command' workflow, which is a problem when you've got no network during the build step. Has no one attempted either of these?
<excalamus>I'm running org-mode to document the packaging I'm doing. I'm running the guix shell commands through a source block. Works great except, it seems the shell wants to put spinner characters and other non-printable things in the output.
<excalamus>if I check echo $TERM inside the shell block, it says dumb
<dragestil>Hi, why are there two node packages in guix show node?
<apteryx>dragestil: there are two versions available
<jlicht>newb: I have the technoethical N150 usb adapter, which works well enough for my needs
<jlicht>any particular reason tests for c-ares on core-updates-frozen are disabled? The provided GTEST_FILTER seems to get all tests to pass on my machine consistently.
<liltechdude>Hello. How I can change "remote component" of branch in .config/guix/channels.scm? For example, for now I have "my-branch", but when change to "fork/my-branch", error ocured "guix pull: error: Git error: cannot locate remote-tracking branch 'origin/fork/my-branch'"
<jlicht>liltechdude: your branch is called 'fork/my-branch'? Or do you have a branch called 'my-branch' on a different remote called 'fork'?
<apteryx>do you think we could disable that without consequence? seems unfortunate to depend on qt for our gtk package
<civodul>rekado: recoll has an invalid home-page field
<jonsger>In procedure car: Wrong type argument in position 1 (expecting pair): () means that there is nothing (empty pair) coming back instead of a pair?
<pinoaffe>jonsger: yes: the empty list '() is not a pair, therefore (car '()) fails
<pinoaffe>if code gives that error, that probably means that something that is expected to return a list of one or more items returned the empty list instead (or that something that is expected to return some other sort of pair returned the empty list instead)
<jpoiret>i just saw a use of "make system-check" in a mail, is there any documentation about these? how do they work, what do they do?
<jonsger>pinoaffe: thx. I found the root case in the mean-time. Now onto fixing it :)
<Olivetree>jlicht: abrenon: I also have an issue with guix shell in /tmp, but not in some other directories. However, I do get the same error on a directory in my $HOME that's mounted from a different btrfs subvol. Maybe different mount points have something to do with it?
<abrenon>Olivetree: my "bug confirmation" was explained by civodul I think — it's not a bug, it was my misunderstanding the behaviour of guix shell (which, in auto-load mode, apparently creates a development environment and not a full environment like with -f guix.scm)
<abrenon>I find it confusing but if that's the way it's defined, I think it does work, within /tmp or not
<Olivetree>I htink you're talking about a different issue
<apteryx>civodul: had to redeploy a quick fix to a production machine today; 'guix deploy' was a fine tool to use again :-)
<Olivetree>If I use the same manifest.scm in different directories I get different behaviours
<abrenon>doesn't it use (load or something) a relative file which content differs between both directories ?
<roptat>hey rekado I think you might be interested in https://issues.guix.gnu.org/51351? pplacer is currently broken, and I found a way to fix it. Do you think you would be able to create another miracle and port it to a more recent ocaml again?
<Olivetree>jlicht: There goes my theory... I have a sibbling subvolume in which running guix shell works. It's in everyway similar to $HOME/some-mount/ of before
<Olivetree>If I run "guix shell -D -f manifest.scm" instead of only "guix shell" in one directory everything is fine, in another I get manifest.scm:1:1: error: specifications->manifest: unbound variable
<Olivetree>hint: Did you forget `(use-modules (gnu packages))'?
<Olivetree>in either directory, if I add (use-modules (gnu packages)) guix shell throws an exception
<Olivetree>In both directories guix environment -m manifest.scm works as expected
<Olivetree>Now I understand.. I needed to use `guix shell -m manifest.scm'... My bad. This one works correctly
<Olivetree>So summing up: in some directories `guix shell' says manifest.scm is not found but `guix shell -m manifest.msc' runs just fine!
<Olivetree>I meant to say `guix shell -m manifest.scm' runs just fine
<podiki[m]>is the new style package inputs in the manual somewhere I'm missing?
<roptat>podiki[m], I don't think it is, it's not merged in master yet
<attila_lendvai>is there somewhere any example of a package downloading a platform dependent binary? i know it's against the philosophy of guix, but this is a special situation (go-ethereum, crypto stuff)
<singpolyma>I think build usually runs in a container with no network, but if you can download it in the phase that downloads the source it should work out
<attila_lendvai>apparently the binary runs on my guix when started as ~/.guix-profile/lib/ld-linux-x86-64.so.2 geth version
<attila_lendvai>singpolyma, yeah, that's my plan, but i was hoping i can copy from somewhere the dispatching on the target platform
<nckx>I'm hella failing at lurking, so I'll close me client now. Night Guix o/
*attila_lendvai much appreciates nckx's failure, though
<vagrantc>running on foreign distro (Debian) with 0e6470b47f00470c213fbf20bddc5bcf1e2f8e2a (recent guix master) guix shell --pure --check --development guix guix git less ... complains about missing PKG_CONFIG_PATH variable ... then running guix shell --pure --development guix guix git less ... PKG_CONFIG_PATH is defined
<podiki[m]>what is the easiest way to modify a build function? i'm playing with make-dynamic-linker-cache and wanting to change something in its function definition
<nckx>Adding it to any file is not supported, and you just plain shouldn't, at best it does nothing, and it probably leads to bugs somehow.
<jpoiret>how is guix pulled in when making an image? I've been searching the source to no avail. One thing I want to know is if it uses the current installed guix, or the guix package, or the guix you're using to `guix system image`
<podiki[m]>simple (I think) question: how do I replace a build phase with a new function; I have it in the file as a (define* (the-new-thing...)) and then in the modify-phases try a (replace 'old-thing the-new-thing)
<pkal>Olivetree: Great, that looks like exactly what I wanted!
<nckx>florhizome[m]: I understand the frustration, but not everyone has an answer to every questions, and apparently some questions have none. It helps to give more useful info: not ‘some util’ but ‘a binary provided by binutils, but not found’, not ‘the source paths seem kind of off’ but the actual path & why. Vague statements that promise a long back & forth tend to discourage people who might pounce on an ‘Q: X? A: Y!’ question that the
<nckx>y feel is quick and easy to answer (even if they get sucked into a nerd snipe *after* :). Most people feel/are busy, not just staring at their IRC client. Anyway, not blaming you for the lack of responses at all (you are not to blame, nor is the channel), just giving some tips.
*nckx going to close their client, shut down their PC, superglue it shut, and throw it out of the window, so perhaps they will go → 😴💤
<florhizome[m]>I‘m not frustrated with anyone in particular. If I was pointing out something, it‘s that people can be super nice but still a lot gets thrown under the bus, because of the nature of a chat system where messages deprecate pretty fast.
<jpoiret>podiki[m]: note that when building, the build system doesn't have access to the whole file where you defined the packaged. Guix only sends the build phases themselves, so you can't reference a symbol outside of it. That's also the reason why the arguments are passed as a list.
<jpoiret>personally, if I do need some modularity, I just (define myfunc (quasiquote (lambda ...))) and then do ,myfunc in the arguments
<podiki[m]>jpoiret: okay. so I could inline that function within the package or load path maybe
<jpoiret>yes, you'd need to inline it. I'm not sure which modules can be used using the #:modules keyword of arguments
<florhizome[m]>Anyways, if anyone wants to help I would ofc post the scheme file and a backtrace. ofc I’m happy to provide more context... but it doesn’t make much sense to flood the room with that unless.
<florhizome[m]>On a broader note I wanted to point to maybe it makes sense at some point to open more channels to narrow topics on the individual ones... like one for packaging, one for system and services, one main for general stuff. But if and when I don’t know ;)
***namtsui_ is now known as namtsui
<podiki[m]>there's also help-guix (mailing list), perhaps a bit slower but visible in another way
<acrow>podiki: Regarding the unbound variable. Have you tried binding your function to a variable that is, literally, in the package with a let or let*?