<spudpnds>Hello folks. When downloading content from ci.guix.gnu.org, sometimes it's fast, and I get like 2Mb/s, and sometimes it's really slow, and it's like 35Kb/s. Anyone know why there is such a difference?
<nobodynogroup>NieDzejkob: I did yesterday, but i have done a lot of stuff since then including restarting the device so im doing it again
<nckx>nobodynogroup: It sounds like ~/.config/guix/current isn't in your $PATH. If it isn't you can pull until you're blue in the face without making progress.
<nckx>ArneBab: I don't know what intimidates you most, but a quick test should be as easy as echoing ':ExecutableJAR:E::jar::/home/arne/jarwrapper:' to /proc/sys/fs/binfmt_misc/register, where ~/jarwrapper just basically runs java -jar "$@" (probably with some env vars to boot, but I don't know anything about Java).
<ArneBab>I hit that when checking whether running the freenet installer would work with doubleclick
<ArneBab>right now it’s bash: /proc/sys/fs/binfmt_misc/register: No such file or directory
<nckx>ArneBab: Did you load the module && mount binfmt_misc -t binfmt_misc /proc/sys/fs/binfmt_misc ?
<seepel>Hi guix, I recently spent some time fixing the g-golf guile library package. I'd like to contribute a patch, but have a couple of questions. 1) g-golf only builds for Guile 2, should the package name reflect that? 2) Both the library, as well as the tests depend on guile-lib. Does that mean that guile-lib should be duplicated in both native-inputs and inputs?
<ArneBab>no, I din’t — that‘s part of what feels tedous when you just want to do a quick check
<spudpnds>(I'm a noob, so just reading along with the manual and trying things)
<nckx>Ah. That & grafts & regenerating your profile probably do.
<coalquiercosa>hi guix! I'm attempting a guided graphical install on a thinkpad, but when I get to the partitioning step it doesn't show any disks D:
<nckx>coalquiercosa: Sorry to hear that! Does your ThinkPad use an NVME drive? There's a known bug with those, but I think it's different from what you describe. It's night in Europe and Sunday mostplace else. Please send a report to bug-guix at gnu.org if nobody answers. Include as much information about your system/storage as possible (you can switch VTs with C-M-F2).
<brettgilio>Hey, so I am working on an emacs package that uses the gnu-build-system. What I am trying to achieve is bytecompilation of a subdirectory of that emacs package. This is usually achieved using the #:include keyword for emacs-build-system, but as those emacs-build phases are called manually im not sure how to achieve this.
<apteryx>brettgilio: often I find that using the gnu-build-system doesn't bring much (it's often a shallow Makefile infrastructure that ends up byte compiling all the elisp files, which the emacs-build-system handles more directly).
<brettgilio>apteryx: Yeah, thats what I feared. It's the emacs-telega package which has a pretty sizable recipe. When I originally wrote it, I used the gnu-build-system because the package has several C components that need compiled and knows how to use the test phases without much intervention.
<apteryx>In those times, you can borrow some build phases from the emacs-build-system.
<apteryx>combining both. It's tedious, but there are various examples already.
<brettgilio>@apteryx: Yep, thats exactly what i'm doing. But the emacs-build phase itself only bytecompiles the root directory. I've tried to chdir to the subdirectory, but it just recompiles the root directory
<brettgilio>Theres a contrib subdirectory that needs to hit too
<apteryx>it's a bit strange that their build system doesn't handle the byte compilation?
<raghavgururajan>sneek, later tell nckx: I want to see if a build failure is reproducible. Could you try to build gtksourceviewmm on guix.t.gr? REPO: Guix Savannah ; BRANCH: wip-desktop ; COMMIT: 3000f52653ab08179696c57a560a3efe2dd9c338
<thomassgn>my wireless usb thingies stopped working some time back, so I keep booting into a progressively older system generation to have internet. I saw today there is a ath9k-htc-firmware package, do I include this in my config somehow to get wifi back?
<sneek>nckx, raghavgururajan says: I want to see if a build failure is reproducible. Could you try to build gtksourceviewmm on guix.t.gr? REPO: Guix Savannah ; BRANCH: wip-desktop ; COMMIT: 3000f52653ab08179696c57a560a3efe2dd9c338
<jonsger>trying to update rust-cargo-c, but it wants cargo 0.45. I wonder if thats provided by rust:cargo?
<nckx>raghavgururajan: https://paste.debian.net/plain/1157141 - two unrelated changes: setting NOCONFIGURE so we can still use upstream's autogen.sh (which needs which), and setting include paths to find glib.h and glibconfig.h.
<nckx>Now I get ‘*** No rule to make target 'cdt.c', needed by 'cdt.lo'. Stop.’.
<nckx>raghavgururajan: Meanwhile, could you briefly explain why we need this? I'm worried about the maintenance burden of an otherwise unmaintained library from nearly a decade ago, and this wasn't a promising start.
<efraim>I've been thinking some about elogind and systemd user services, 'loginctl enable-linger USER' works to prevent logging out killing your processes, but it doesn't start them at boot-up. my impression is elogind doesn't want to grow that functionality
<nckx>Note that unlike install-file it doesn't imply mkdir-p.
<efraim>we/i could create a start-user-shepherd service, give it a list of users, create/remove /var/lib/elogind/linger/USER files and launch shepherd for each user, as that user, using a one-shot service
<apteryx>nothing new for me on the machine I'm tying this from. It seems to do its own swapping to disk pre-emptively, even with 1 GiB of remaining memory, and slows down to a crawl. As it as "only" 8 GiB of RAM, that occurs rather often.
<rekado_>pkill9: one thing you could try to improve this is to build up an S-expression directly instead of working with strings.
<mbakke>NieDzejkob: possibly, do you remember which distro? I suppose I should try toggling the "is_official_build" flag which enables all Chrome release optimizations (I've been toggling the individual flags manually, but not recently) -- unfortunately that means making Clang install a cfi_blacklist.txt and using LLD for linking.
<rekado_>pkill9: I’m speaking of packages->package-inputs
<pkill9>rekado_: yea i would rather do that, but i didn't know how, because I want to generate the package name and variable, but put that in a quoted quasiquote
<brown121407>Hi! Can you guys help me understand what exactly does #:skip-build? do for rust packages? Don't they need to eventually be built too? How else would you install them? Is it some kind of CI-only instruction?
<pkill9>rekado_: where can i find documentation on (match)?
<pkill9>I search and just find regex match structures
<nckx>brown121407: Nothing CI-related. Such Rust libraries are ‘built’ only as part of the package that depends on them. They can't be assembled into anything meaningful on their own. E.g. <https://paste.debian.net/plain/1157189>: there's no concept of /bin/addr2line or libaddr2line.so, so what would the build system build? Nothing, it's only there to be a source library for others.
<nckx>terpri, hendursaga: Yeah, Guix doesn't exactly prioritise running binary blobs. We don't deliberately prevent it, but don't expect any to run easily.
<terpri>tbf, some of those blobs are free software that are difficult to package for guix directly. understandable that it's not a priority though
<terpri>flatpak support covers the most important ones from my perspective (tor browser, regular firefox for sites that break under icecat due to User-Agent differences, etc.)
<mbakke>rekado_: there are a few R packages in the patch tracker, do you think you can review them in the near future? I know nothing about R and am not comfortable with it, but can try if you're busy.
<brettgilio>mbakke: Re: the workd around. That should be applied to the cmake build system directly, not to the packages right?