<civodul>mbkamble: it's in gcc-toolchain (it's actually part of glibc)
<mbkamble>yeah. thanks civodul. I installed glibc and got it
<nikola`>What do you all think about rust in the kernel
<lhp22>Same powerness of C ? With more memory management guards ? It can't be totally wrong
<mekeor[m]>hello guix! i'm trying to build/run a rust project with cargo. i set RUSTC_BOOTSTRAP=1 and added 'cargo-features = ["edition2021"]' to the Cargo.toml. but 'cargo build' still fails with "feature `edition2021` is required". what's wrong?
<mekeor[m]>vagrantc: why is there no way to track deps? they are listed in cargo.toml
*mekeor[m] realizes how ugly cargo-build-system is, regarding #:cargo-inputs
<GNUtoo>Hi, is it possible to reuse an operating-system declaration for both guix system image and guix deploy?
<GNUtoo>I was thinking of spliting it in 2 files with one being a module that export the operating system with something like (define base-server-system (operating-system [...])) and the other that use base-server-system, though for some reasons that doesn't work, do I need some special quoting for that?
<vagrantc>mekeor[m]: there are ways to track dependencies, there are too many to track practically
<mekeor[m]>GNUtoo: maybe it's with packages where you can use (define-public custom-package (package (inherit another-package)))
<abrenon>well as with any open source software, you can tweak the source to modify your version of guix and generate whole systems with that, but you can of course redistribute your changes as patches so that the rest of the community may benefit from your improvements
<abrenon>does that help ? I'm not sure I get the meaning of your interrogation perfectly
<abrenon>are you perhaps confused by the "source" describing a system to build and the source code of the guix package itself, allowing to alter its behaviour, the list of packages it knows, etc.
<mlan_>sometimesthere is a problem, I have no idea how to continue building this OS guix
<abrenon>ok, what kind of problem ? could you tell us when it occurs ? what are you concretely trying to achieve when you say "building this OS" ? are you installing from a live CD/USB onto a new machine ?
<horizoninnovatio><maximed> "horizoninnovations: "guix show..." <- would there a reason why "guix pull" isn't updating to show 7.8?
<maximed>horizontalinnoatio: what does 'type -P guix' say?
<NaturalNumber>Oh, I finally got Guix up and running. It feels great and what a learning experience. Most of my issues ended up having nothing to do with Guix per se. I wonder if some others might be interested in some tips or if I should let them figure it out on their own.
<maximed>NaturalNumber: Please share before you end up with stockholm like many old Guix contributors and don't recognise the issues for issues anymore.
<attila_lendvai_>i wonder if this is due to user code, or due to some change in guile: "gnu/services/mail.scm:431:0: warning: shadows previous definition of `%namespace-configuration-location-procedure' at gnu/services/mail.scm:431:0"
<attila_lendvai_>and why it's not showing up at all the other uses of define-configuration
***attila_lendvai_ is now known as attila_lendvai
<attila_lendvai>and i'm still seeing regularly this: "substitute: In procedure write_wait_fd: unimplemented"
<fps>btw: the installer produced a config.scm that guix system warns about. like using target instead of targets, etc..
<fps>is there a way to produce a nop-derivation for places where a derivation is expected?
<maximed>I think you have mentioned it previously, but is there a bug report yet?
<maximed>(with backtraces, which command is run, etc.)
<attila_lendvai>maximed, i haven't created one, because i thought i'm not the only one seeing it. maybe it depends on the network config on my side that occasionally causes the send buffer to get full. e.g. i have QoS set up on my router, because without it the ping goes through the roof (vodafone landline in hungary)
<silicius[m]>libmpv patch is almost ready but the check phase doesn't want to end at all, it just stops giving any output after one of the tests
<maximed>In case anyone likes running signal-condition! after the run-fibers instead of inside the fiber, and in case people like to start fibers in run-fibers, waiting on a condition but never succeeding (because it is only signalled after run-fibers returns and all fibers were abruptly stopped)
<silicius[m]>I meant python-mpv eariler instead of libmpv (this one is already included with mpv). running the tests by hand has the same effect, it stops doing anything at test_wait_for_prooperty_event_overflow
<nckx>My cargo-culted was a bit too strong, lots of things are coded by example in Guix, and it's fine, but hence important not to tolerate too many ugly things. You'll come back in a year and they'll have magically reproduced.
<silicius[m]>nckx: It plays the test video, sets a trap that tests mpv.eventOverflowError exception is raised in its block (the first with block). In there it waits for 0.001 and then sends a command to mpv 10k times. It appears to be nullyfying all errors in the most-inner block though
<vagrantc>civodul: yeah, that PDF was a nice read ... not much i didn't already know, but ... nice to see it all put together in one very well worded document :)
<vagrantc>i feel compelled to read one-off licenses roughly in the same way i feel compelled when someone says "wow, that smells really awful! smell this ..." ... and i just do not resist
<nckx>Restrictions on fork names *might* be an issue (I don't actually know) and 'requested' is always a facepalm when amateurs cosplay as licence authors. It might not be free. It's definitely going to be a pain.
<mbkamble>Hi. After installing emacs-geiser and emacs-geiser-guile packages, the info for Geiser is missing. Is the package definition for emacs-geiser incomplete?
<ulfvonbelow>well, at some point I got the impression that I should be looking for keyboard layouts in /run/current-system/profile/share/keymaps, and I didn't see anything about workman in or below that subidrectory, so I was gonna try adding the linux_console subdirectory of https://github.com/workman-layout/Workman as a package similar to kbd-neo
<ulfvonbelow>according to the manual there are three different places keyboard layouts can be specified: bootloader, console, and xorg. Do those all use the same file formats and look in the same places?
<nckx>(In case it's not clear, my main concern is if & how you can claim & licence a keyboard layout to begin with, although I know Dvorak tried. The 'official Workman repo' might be non-free, but maybe the raw data as distributed in xk-c can't be.)
<singpolyma>IANAL but no way is a keyboard layout copyrightable :P
<nckx>How did you look? Keymaps aren't distributed as <name>.xkb or anything like that. It is much different.
<nckx>And yes, everything is generated from XKB layouts. GRUB, Linux, ... it all just works, even with xkb modifiers where possible. It's really very im.ressive.
<ulfvonbelow>find -L /run/current-system/profile/share/keymaps -iname '*work*' is what I tried
<nckx>You don't need different formats of each layout packoged.
<mbkamble>If a given package (say emacs-geiser) is available in multiple channels (eg. guix and third-party channel), is there any command option to show which channel it uses to fetch/install the package?
<nckx>mbkamble: Asking 'Is the package definition for emacs-geiser incomplete?' is rather meaningless then. How could we know.
<nckx>mbkamble: The Guix CLI will pick the one witt the highest version, here the custom channel one. Also: guix show PACKAGE