<vagrantc>font selection is a really annoying thing. i feel like "back in the old days" i never had to worry about fonts. nowadays it tends to make various things unusable on major system upgrades (not guix specifically)
<terpri>yeah, noto is 1.5gb installed, vs 18mb for unifont
<terpri>noto might have better emoji support too (just guessing because it's from google; i think android uses noto these days?)
<nckx>It's why I have it installed (swaybar mainly).
<nckx>Full-colour monstrosities. I keep an older copy of Noto around with better ones.
<marusich>Does debbugs-gnu-search work for anyone? It sends me in an infinte loop, asking me to supply attributes etc.
<terpri>dissoc, isn't that what "guix system image -t iso9660 $foo.scm" does? produce a preconfigured image? (i've only used vm-image, never tried it for normal installation)
<marusich>It asks, "Enter search phrase", I hit enter because I don't want to specify one, it asks "Enter attribute," I enter package, it asks "Enter packages:", I enter "guix", it asks "Enter attribute:", I hit enter because I'm done, it asks "Enter severities:", I hit enter to accept the defaults, it asks "Enter attribute:", I hit enter because I'm done, it asks, "Enter severities:", and from here we loop.
<nckx>I think they want an image that will itself install that system, unattended, which I don't think exists. Although it sounds like the kind of thing someone might've written for their own use and not advertise.
<dissoc>with custom-images i think DO would be fine. there's always linode and vultr too. i would be interested in using custom-image on DO myself. i could probably try it really quick. assuming it goes smoothly
<dissoc>look at the DO api and see what is required. if i recall correctly i got that message as well. im pretty sure a tag was required and that fixed mine. but maybe you are missing something in addition to that. ssh-key maybe?
<fnstudio>dissoc: yeah, good point, i'm cross-checking my script, the DO API, and what's in gnu/machine/digital-ocean.scm
<terpri>ah right, i'd forgotten about guix deploy, and didn't realize dissoc was talking about VPSes (still mentally stuck in the pre-cloud era ;))
<dissoc>fnstudio: well i got the custom image uploaded to DO and droplet created. it booted and i can see the console but i dont have time to do much else right now
<dissoc>fnstudio: so i did 'guix system disk-image -t qcow2 config.scm' . then uploaded to custom image in DO interface. make sure to upload image to the region you wish to deploy to. and make sure you select one that's actually available to deploy droplet
<dissoc>but word of caution: i have no clue what im doing so dont do anything i say
<dissoc>terpri: i was initially wanting to create a iso with unattended install, or minimal, maybe just hostname input for installing on physical machines
<apteryx>I wonder what's that caused by: unexpected build daemon error: stoi
<apteryx>probably from this in local-store.cc: return stoi(str);
***apteryx_ is now known as apteryx
<timmydo>i'm trying to write a service for guix... is there a way to get more logging out of shepherd? it's failing to start my service
<dissoc>timmydo: yeah. check the output of the file you configure there first
<timmydo>i had a paren in the wrong place earlier and i think #:log-file was probably going to the command line of the app so the file wasn't appearing
<dissoc>i struggled quite a lot for the first service i wrote. if you need any help i'll be around for a few hours
<dissoc>i would recommend avoiding doing any kind of crazy configurations and just start with static values. get it to work that way first
<timmydo>yeah, it's been an experience. i'm picking up scheme at the same time. i'm not sure if i have fully gotten the feel of what the development cycle (where to store my source, how i should edit the guile load path, etc.).
<dissoc>if you're creating services and packages probably best to just have them in a git repo and add it as a channel
<timmydo>looks like the service started correctly. but i'm running it as a user instead of root so i'm listening on a nonstandard port. once i figure out how to get nft to redirect the port maybe i'll write it up
<timmydo>i had a little trouble getting the auth to work on the git repo but it's working now. but my set up isn't ideal since i have another computer that i'm testing on so i don't want to make a commit every time i fix a typo
<timmydo>having the file local and using --load-path was probably easiest for me until i got that working
<timmydo>do you happen to know the guix way to do something like this? sudo sysctl net.ipv4.ip_forward=1
<hapster>nckx: so you mean that even if something is visible to the shell I need to export it (probably via (setenv), right?) in order for it to be visible to emacs?
<nckx>In order for it to be visible to any child process. Unexported variables ($ i=foo) are just local.
<nckx>Guix doesn't export GUIX_PROFILE because AFAIK it's an implementation detail, and the notion of ‘the current profile’ is flawed (they should compose & layer, e.g. system -> user -> guix environment -> ... on a Guix System).
<hapster>when I want to install an earlier version of a package, the correct command is "guix package -i PACKAGE@VERSIONNUMBER", right?
<hapster>does that mean that it is necessary to keep around the definition of the older package?
<hapster>I am saying that because I recently updated a package (pioneer) which built fine but which errors out on execution. Thus, I wanted to see if I could install an earlier version of but couldnt
<nckx>hapster: Yes, Guix can only build/install the exact package versions/variants that come with that Guix version. We don't keep older packages around unless there's a good reason to. But! guix time-machine should do what you want. Read up on it, try it, & ask any questions you might have.
<nckx>You will need to look at the git repo to know the commit that updated Pioneer, there's no way to automatically query that (yet).
<nckx>Guest57293: There should be a lot of context, and an en error log file name printed along with that message. Paste both to paste.debian.net. If the log file is .bz2, use bzcat to view it.
<nckx>Guest57293: That exact derivation builds fine here, so it's somehow related to your machine. A substitute (pre-built binary) is also available from ci.guix.gnu.org, the default substitute server. Did you disable it on purpose?
<hapster>can anyone tell me what is needed for 'guix import nix' to be successful?
<hapster>do I need to fetch nixpkgs manually or is there something else that I need to do in preparation?
<hapster>because the videos on the guix hp use 'guix import cran' in a straightforward manner, and it is now not the first time that I try to search for a nix package definition of a package I suspect to be packaged - and running into errors while doing so
<zimoun>g_bor[m]: hey! Do you plan to be there tomorrow?
<fnstudio>cbaines: great talk, thanks (any chance the slides are or will be published online?)
<nckx>hapster: I'm afraid the Nix importer is prone to bitrot, and might require a running & configured nix-service-type to even work.
<nckx>In short it's probably the most temperamental of the mainline importers.
<efraim>is it worth fixing or should we just take it out? I feel like we've had this discussion about it for years
<zimoun>even “guix import nix hello hello” fails with an ugly BackTrace.
<nckx>I've never even tried it. Nix packages are so trivial to port, and the importer can't do any of the non-trivial stuff anyway.
<dissoc>spice-vdagent-service just calls (service spice-vdagent-service-type config)
<PotentialUser-60>Finaly I can run: guix package --export-manifest > /tmp/boom && guix weather --display-missing -m /tmp/boom
<dissoc>fnstudio: i got a reasonable digitalocean guix custom image going now. if you try it dont forget to also add --image-size
<dftxbs3e>hello, does "$ guix build --check lz4" work for anyone? I'm getting failures for email@example.com but a substitute is available so I very much wonder how that's possible, it's due to failing tests and the failures look very deterministic.
<lfam>Well, if you are getting a substitute, then it did build at some point
<lfam>In my experience, the lz4 test suite is flaky
<lfam>It probably depends on some details of the hardware being used
<lfam>It likely expects to be run on something quite powerful
<dftxbs3e>bluekeys, check out other GNU/Linux distribution without systemd check if they successfully packaged it, from the description it looks like it may be a big problem but also looks like it could be patched out easily.
<raghavgururajan>So I created a new user "test" in my config.scm and reconfigured the system. But when I login as test and do guix pull, I get "guix pull: error: while creating symlink '/home/test/.config/guix/current': No such file or directory"
<civodul>bqv: Guix "channels" and Nix "channels" are two different things
<civodul>Guix channels provide some of the functionality of flakes (pinning Guix to a specific revision)
<bqv>So i see, but should i want to move my config to a new machine it still requires shifting and pulling the channel manifest as well as the system config. im a bit spoilt from using flakes, but i much prefer having that all in one
<bqv>not to mention not having to worry about root channels vs users' channels
<pineapples>bqv: I, too, much prefer having my channels specified in my system configuration. Would be nice if I didn't have to (extra-special-file my channel.scm file) but just declare it in the system configuration, and if I could use my remote channels from the live installation environment, without having to split the system configuration
<gn21[m]>Hi, I'm trying to install the telegram by guix on my trisquel gnu/linux and give this message at the end of the compilation: the compilation of /gnu/store/n68qcxi8xpb0ic1a01gkmfh3871rgwp-materialdecoration-1.1.0.drv failed
<pineapples>Btw, yes, I can generate an installation image that contains modules from the channel I need, but, in the case I need to install the OS somewhere else, I'd like to be able to reproduce my work environment, using the stock ISO images from the Guix website