<spiderbit>So, no moving chat, I don't know if that is good or bad but I use it for my question
<spiderbit>I asked around here at some time because I need a hwdb file loaded for my thinkpad keyboard with a japanese layout. but the current stable eudev version did not support it
<spiderbit>or was buggy so that they did not support it
<spiderbit>and somebody here said that they fixed that for gnome-dev or something, I thought back then, ok I just wait for the next new guix version I don't need it instantly can wait a month or so, but I think I misunderstood how extreme long release cycles guix has.
<spiderbit>So I would need some "pinning" or something? to another branch? how can that be done in guix?
<mange>I don't think the gnome-team branch is ready to use, so you'd have to cherry-pick the changes in cde1becfaba7a5757b881a5940ef0c6c2a70794f, I guess. I'm not sure the best way to do that.
<efraim>only complaints! I can't get rust-1.73 to build on ppc64le, I have 100+ rust patches to test and apply and I still have my fosdem presentation to do. so not bad :)
<adanska>hahaha, sorry to hear that! i've been seeing the struggle with getting rust working recently and i truly lament all the pain the rust team is dealing with at the moment.
<efraim>I have decided to bring my ppc laptop to fosdem for funsies though, so that should be interesting during guix days
<adanska>but ive also been hearing about the fosdem talks on the mailing list! really excited. are the talks recorded at all? I live in Perth so there's not a chance id ever be able to attend one, sadly :(
<efraim>ibook g4. I have a 12inch and a 14 inch. 14inch I use sometimes, the 12 inch isn't in great shape and sits in my drawer until I have time to install debian on it so I can also use it as a guix offload machine
<weary-traveler>how do you add specific items that already exist in the guix store to the gc roots?
<ulfvonbelow>is there any particular magic necessary for running a guix installer image under qemu? When I try booting this particular image I made, it gets to generating ssh keys, then the screen goes blank with just a blinking cursor forever. (This is the same image that seemed to have weird corrupted files on real i386 laptops, although the same files appeared fine when looking at it from my desktop)
<efraim>ulfvonbelow: try mashing the keyboard or jiggling the mouse a lot, it might just not have enough entropy
<adanska>efraim, cool!! those old ibooks are really neat. I've heard though that the screens on them have finally started to rot, which is sad to hear
<efraim>weary-traveler: I think symlinking the output into /var/guix/gcroots should be enough but I don't remember
<efraim>my screen isn't doing too bad, it might just seem dim since new laptops try to hit like 1000 nits, but the battery isn't doing great. I took it out more than a year ago to try to keep it usable longer
<efraim>I tried to create an install tarball for guix so I could use that on the second machine but I ran into weird issues so I was going to try again from the 1.4.0 tag
<efraim>actually, I might just try building the debian guix package for ppc
<efraim>vagrant's going to be in trouble if I manage to get that working
<weary-traveler>efraim: that works. specifically, the symlinks can also go under a sub-directory of /var/guix/gcroots (say /var/guix/gcroots/manual )
<efraim>weary-traveler: we'll see if I remember that for next time :)
<ulfvonbelow>it looks like in qemu it makes it past the ssh-keygen step, last message I saw was "Error: driver 'pcspkr' is already registered, aborting...", which seems pretty benign, and then just a black screen with a single white rectangular (column) cursor in the top left. When I type stuff it gets echoed there.
<ulfvonbelow>how does one sent ctrl+alt+f2 to qemu without it getting intercepted by the host system?
<ulfvonbelow>okay, looks like sendkey is the command to use from the monitor
<ulfvonbelow>well, it's able to get to the manual via ctrl-alt-f2, so that's good, it just doesn't display the installer at all
<efraim>oh nice, it doesn't look like I need to build packages of anything before attempting to build the guix package
<adanska>Hi, packaging question here. I'm sure people have encountered a similar problem before. I'm currently packaging https://github.com/koron/cmigemo (dependency of lem, its a incremental search engine for japanese) and the compilation downloads a dictionary during its compilation. whats the best way of getting this file in so the package can build? short of packaging the thing that makes the dictionaries
<adanska>hi guix, another question. if theres a package that has a bunch of its components seperated out into different git repos, and these components are heavily coupled with the package, is it better to keep the component packages private (define) or define them regularly (ie define-public) in the appropriate file.
<adanska>these components need to be built with asdf, so it might be easier to just define another package... but thats good to know in future! that actually solves a problem i was having earlier, needing a file hosted online during build-time
<apteryx>ACTION is testing an update to the kde-framework libs
<ulfvonbelow>okay, this is quite strange. In real, physical i686 laptops, and *only* in real, physical i686 laptops, my gnu/build/activate.scm has the same size, but the start of the file has been shifted to begin with "and-line))))" and filled with null bytes at the end
<ulfvonbelow>the start of the file seems to have been shifted exactly 16384 bytes
<PotentialUser-51>I have a potentially ridiculous question that I couldn't really find an answer on. I installed guix as a package manager on some older hardware but any time I try to do a guix pull, I end up freezing. I am assuming it's running out of memory (I only have 2GB total) so I was curious if there was a way to limit the memory used when using the guix
<rekado>PotentialUser-51: unfortunately, the Guile compiler requires a very large amount of memory when compiling all of the modules that make up Guix. 2G is the minimum.
<rekado>PotentialUser-51: you can try to avoid compiling things locally by setting up a channels file that will only get the most recent version of Guix that has been built by the build farm.
<rekado>or you could set up offloading so that the builds are performed on a more powerful machine.
<PotentialUser-51>I thought I chose to only have binaries, but I could be wrong. I'll check now. For offloading, would it matter that my desktop is x86 and the device I want the packages on is ARM?
<attila_lendvai>PotentialUser-51, i'm running guix on a very small VPS, and what i do is i `guix deploy` it from my laptop.
<rekado>PotentialUser-51: you can use channel-with-substitutes-available from the (guix ci) module.
<rekado>the docstring says: “Return a channel inheriting from CHAN but which commit field is set to the latest commit with available substitutes for the Guix package definitions at URL. The current system is taken into account.”
<rekado>you can use this in your .config/guix/channels.scm file
<attila_lendvai>under a rather misleading title... i'd call it Substitute availability or something along those lines
<PotentialUser-51>It was the first result when just searching "channel-with-substitutes-available guix", which I never would have even thought of if it wasn't recommended here.
<attila_lendvai>oh, wait. this does not ensure that all packages have substitutes, only that guix pull will not compile locally. which is useless for me, becuase most of the time i need to run a patched guix.
<rekado>we’d need to export a few more lower-level procedures from (guix scripts weather)
<attila_lendvai>civodul, i'm looking into preparing my shepherd patches for submission, but some of them depend on each other. how shall we do this? would you be fine with me ordering my patches in least controversial order, and you cherry pick commits from my repo?
<attila_lendvai>civodul, then i rebase, refine, and let you know when there are more commits that i deem ready for inclusion?