IRC channel logs
2023-08-05.log
back to list of logs
<nckx>Yeah, as does ‘guix build -f’, this is clearly just a bug. <nckx>Not an uninteresting one, but I'm afraid I don't have time to dive into it at this time. <fries>hmm, gdu has an official source tarball on its github releases page, but i do see that theres a "mirror://" protocol <fries>does that guix protocol support github releases? <nckx>It's a simple hard-coded list and GitHub ain't on it. <nckx>But… they don't have ‘mirrors’ anyway, no? <nckx>Just a big cee dee en behind the github.com name. <unmatched-paren>why is there a LET around %MIRRORS that unconditionally defines GNU-MIRRORS but there's no LET for any of the others <unmatched-paren>fries: if you want to download a github release, generally you use (method git-fetch) <fries>is that more reliable then using a packaged tarball? <nckx>unmatched-paren: Because of the map cut right below it. If you mean ‘no, but *WHY*’, then I don't know. <unmatched-paren>now, whether or not (commit version) will works depends on the format of their versioning tags <unmatched-paren>if they look like 1.0.0, it will work; if it looks like, say, v1.0.0, you'll have to do: <podiki>oh neat, guix build will show dependency cycles now instead of just exhausting itself <nckx>guix import pypi -r heisenbridge | wc -l → 349 <podiki>nckx: happy to help with a bridge/hosting in needed, just let me know <podiki>my quick try showed dependency cycle with pytest-enabler but I have to dinner now <podiki>nckx: I've gotten thousands of lines before so anything with like ~10 packages seems reasonable....but that says more about the pain I've inflicted on myself more I guess <nckx>podiki: Thanks, but having thought about it for more than 2 seconds that would mean manually herding everyone over to #guix:podikispotatopie.biz for… presumably a short while until we set up something more official-looking, and that will irritate people even more than my constant harping about Matrix in this channel lately. <podiki>unmatched-paren: I don't know! but I like it <nckx>If there is a big manual migration, let's keep it to once. <podiki>nckx: right. you do need a matrix server you can access to allow the appservice (bridge) <podiki>anyway, must run for now, let me know what I can do to help <nckx>Run! While you still can! And thanks for your offer! <viaken>Is it just me, or does tlpui fail a build because lspci is in a different place in pciutils? <viaken>nckx: I imported dendrite the other day and it was 7k lines. Nothing comoared to nushell's 13k, tho. <fries>does go-build-system have a way to output a debug output <fries>since it seems to strip symbols and theres a problem with the go program hanging <zmhanham[m]>probably the "operating-system-services" part in my modify-services is incorrect? But I'm unsure <zmhanham[m]>also apologies if this counts as discussing proprietary software, but I thought it should be ok since this is a generic problem not really nvidia specific <viaken>zmhanham - I don't have it near me, but I had to use suchandsuch-user-services. <nckx>zmhanham[m]: This is due to an ugly abstraction leak (or maybe not enough abstraction, depending on your viewpoint). There are implicit services, so that (operating-system-services OS) returns more than what you wrote under (services …). When your write anything resembling (operating-system (services (operating-system-services another-operating-system)), those implicit defaults are added twice. Replac <nckx>e operating-system-services with operating-system-user-services to modify the latter. <nckx>viaken: I've entered the ‘let's disable all the test suites’ neighbourhood of rock bottom. <nckx>It's not very effective. <nckx>What would cause a Python package to install itself as version 0.0.0? <nckx>There is a ‘Version: 4.3.0’ in PKG-INFO. <nckx>It's a PyPI tarball. I don't see any mention of git (but then where would I look?). <nckx>Something's off. *All* these packages are installing themselves as 0.0.0. <nckx>Calling it ‘suchandsuch-user-services’ would have been more honest. <ulfvonbelow>is there a good way to associate extra information with a running shepherd service? For example, I have a process running in a container whose PID I need to remember, as well as a parent process of its that I need to remember, as well as a monitoring process. All of these processes should be shut down when the service stops. <ulfvonbelow>I know the 'running' value can be other than just a pid, but I need shepherd to still understand the various PIDs involved <Kabouik_>I noticed that the vscodium package forcefully sets the architecture to x64 from the download url in the package definition, and installs it on non-x64 systems. I think there are other architectures available to download, but I don't know how to detect the architecture in a package definition. Is the packager here? <jackhill>Kabouik_: I don't think vscodium is yet packaged for Guix. Probably best to ask whereever you got that definition. Besides, generally source code isn't achitecture-specific. <Zambyte>Hi, does anyone know why a racket/gui program compiled with raco exe would be crashing with the following error: "system error: libfontconfig.so.1: cannot open shared object file: No such file or directory <sneek>Welcome back Zambyte, you have 1 message! <sneek>Zambyte, RavenJoad says: Now wally-cli is pushed to Guix. Bug report 64778. <Zambyte>I checked the package definition of racket and it has fontconfig as an input, so I'm not sure why it would be missing that shared object file <Zambyte>I also just checked: same error when passing the --gui flag to raco exe. <Guest28>Will Guix transition from pulseuadio to pipewire as the default? <nckx>Probably. Nobody can say for sure.