<emacsomancer[m]>getting an error on "guix pull" - error: commit cea708413dd9d2d794b022f0f7bcfaba0bac97d7 not signed by an authorized key: A420 7B56 C255 109F 2CB3 157E 4990 97AE 5EA8 15D9 - is this a known issue?
<FriendFX>Dear experts, I installed the `opencv` package a while ago (I think it came as a dependency of `python-imageio`) and it's kind of a pain because every time I do a `guix package -u`, `opencv` thinks it needs to be updated. This wouldn't be so bad if it didn't want to re-build itself including a lengthy 'check' phase. Looking through `guix package -l
<FriendFX>|grep opencv`, I see that the version has always been 4.5.4 for me, but the `/gnu/store/` prefix is different every time. Is this normal? Can I somehow tell Guix to only update if there's a substantial change/improvement of this package?
<apteryx>are trained models OK to be packaged? I guess these are more like nonfunctional data per the FSDG?
<podiki[m]>I would think so, basically it means their parameters have been set
<FriendFX>vagrantc: I would hope there is a reason for it, but I get the horrible feeling that the package definition points to a master dev branch somewhere instead of a release branch, which would explain (a) why it wants to be rebuilt frequently and (b) why the version number doesn't change.
<apteryx>our tesseract package is useless without it
<vagrantc>apteryx: i do see a bunch of tesseract-ocr-* packages on debian
<FriendFX>vagrantc: Also, it is odd that the server never seems to have a pre-built substitute available, which makes me even more suspicious that what I'm getting something different from the rest of the world.
<devmsv>hello, I have my own running guix system. I want to install another system onto a USB stick so I can have a guis system on the go. I can't run ~herd start cow-store /mnt~ (it can't find the service) any tips on how to proceed?
<devmsv>Maybe I haven't explain my self. I have my own gyix system on my laptop I want to isntall another guix system directly on the USB without another USB withguix installation USB iso (I don't have two USB sticks)
<some-one>Hello everyone. Is where any intentions to complete the idea of `guix git log`? How do you find the old versions of packages that are no longer in the upstream? Via git blame? Why we don't keep old version of packages in the guix channel? Is it really hard to support?
<pkill9>because it's extra work for little payoff I guess, especially now you can build packages using an old version of guix
<unmatched-paren>some-one: "... old versions of packages ..." <- Yes, keeping everything would be impossible. Also, security problems.
<abrenon>it is serious, I'm honestly disappointed to find such a bug in guix
<abrenon>but I can understand that few people are ready to see this as a bug
<unmatched-paren>tbh, it would be nice if guile's records could be fleshed out such that we could just kill off (guix records)
<unmatched-paren>i think implementing guix-style records in guile might make declarative-style easier to implement, possibly?
<abrenon>because you're right, I'm mistaking two things, and the fact that I've been able to mistake them up to now is a proof that until now I've been lucky enough to handle well-designed, unsurprising languages which are simpler and don't require to make an unneeded distinction between them
<nckx>Because it's not a bug, you just wish it were so you wouldn't have to argue why your suggestion is better (which you've so far failed to do with the misleading (point…) example).
<abrenon>I guess I was just live-IRCing my disappointment at getting slightly less ignorant about how scheme languages can work and having to understand how deeply they differed from the other functional programming languages I'm more used to
<nckx>abrenon: I can actually sympathise. There were a lot of dreamy (and almost certainly internally inconsistent) ideas I had about Lisps when I switched to Guix. Like everything would somehow magically know everything it would need to and somehow do the right thing and… This was coming from Nix, where attrsets do have that property sometimes, but unpredictably and poorly. Still took me a while to adjust to the reality, even though it didn't end up disappointin
<nckx>PSA, and why I was briefly here in the first place: if you run Tor, you should stop it, run ‘guix pull’ instead, update Tor and make sure you're running 0.4.7.10. Even if you updated Tor yesterday.
<unmatched-paren>Lumine: Well then, you won't have to unlearn things about traditional distros :P
<apteryx>abrenon: sshd is now using an inetd style service, which fires it on demand
<nckx>apteryx: Actually, no, another hypothesis that occurred to me y'day was that sshd was looking up PTRs for new connections and they were somehow being blocked on the MDC network (even though that would make no sense) and timing out. So sshd not starting does rule that out. Thanks.
<Lumine>You could say that I'm a regular user that wants to learn Lisp but is having problems with basic concepts
<nckx>Anyway, big ups from me on dropping it as it is now. We pretend not to notice binaries when they are critical to the graph. Mono never has been that. Although it's not the leaf I expected it to be, either, seems like we'd lose a handful of mostly IM & gaming-related packages. Nothing major though.
<apteryx>seems it can be worked out via some manual hacks (Debian apparently does so)
<ggoes>yeah i just checked the channel because i'm getting the same error
<podiki[m]>sites were slow in last several minutes, just noticed it went down
<davidl>unmatched-paren: thx for your help with packaging tern (node package): I got a bit further - now Im stuck again :-( node-deno fails in the install phase with: "npm ERR! enoent ENOENT: no such file or directory, chmod '/gnu/store/0nkx2qm0b1k9lbhfajn4jd48nlxk8593-node-deno-0.1.1/lib/node_modules/deno/try-deno'". There's a bin file mentioned in package.json but Idk how to make it appear basically, https://github.com/YounGoat/nodejs.deno/blob/
<nckx>davidl: I've been kind of disappointed by the lack of feedback I got from the folks I pinged (I understand it's a weird package and we might be trying too hard to get things just right, but still).
<nckx>I think I'll just finish up ‘our’ version and push. I'm in that kind of mood.
<davidl>unmatched-paren: me neither, but it's mentioned in package.json, and if it's not significant, maybe I can just substitute* it away. However, i don't know if it's significant or not :/
*unmatched-paren looks at npm docs for package.json's "bin"
<dirtcastle>I'm trying to hack on guix home. but andrew tropin's repo is not geiser compatible - meaning geiser -edit-symbol-at-point doesn't work because of the way the directories are structured. I'm emacs , lisp, scheme and guix noob btw and trying to learn thank you very much.
<davidl>nckx: ok, thanks for letting me know what's going on.
<nckx>apteryx: Have you ever successfully pressed the virtual F11 to enter the ‘Boot Manager’? It doesn't do anything. I can enter the firmware setup with another Fn key (I forget which, but that one).
<dirtcastle>I have rudimentary knowledge of git, programming, guile. but I noted Everything you said. and the future (hopefully) Knowledgeable me will definitely look into everything you said , after coming up with something useful enough to make a pull request and get it merged.
<unmatched-paren>dirtcastle: The `send-email` and `format-patch` "patchset" features allow you to send some emails containing .patch files in the universal format, which the maintainer can then apply with `git am` or `git apply`.
<dirtcastle>nckx: most ppl I know irl do. emacs YouTubers introduced me to sourcehut. i didn't know u can do it through email until then
<dirtcastle>what does am stand for. my guess is apply modification
<unmatched-paren>There's things like hub.sr.ht (provides the stuff that appears at https://sr.ht), hg.sr.ht, paste.sr.ht, git.sr.ht, scm.sr.ht, meta.sr.ht, core.sr.ht, man.sr.ht, lists.sr.ht, builds.sr.ht, and todo.sr.ht
<nckx>unmatched-paren knew what I mean. We r best buds.
<dirtcastle>I suspect a docker container already exist for it