<usney>How do I default to only install binaries instead of building packages? It appears my guix installation has now switched over to compiling instead.
<raghavgururajan>usney There is no option to use 'only substitutes (binaries)'. They is only an option to prefer substiutes, if available. If substitutes are not yet built in build farm (ci.guix.gnu.org), guix will build them locally.
<raghavgururajan>usney Btw, by guix installation, do you mean installing guix on foriegn distro or installing guix system?
<raghavgururajan>Veera Hmm. Then I think its a bug. For now, you can use SLiM or SDDM.
<usney>I just have trouble with it working with other desktops that not are not gnome 3. Like the other desktops do not recognize the the correct environment variables so it shows up in the menu. Right now I figure out how to get it to show up in the terminal on openbox but not the menu yet and not the locale language used either.
<anadon>How should packaging selenium be handled, and by extension the web driver? There's a firefox one kind of available, but it isn't well documented.
<anadon>The other options are Chrome, Edge, and Safari.
<usney>I don't use desktop icons now or menu icons. since I don't really use the desktop icons. Also openbox menu doesn't display the icons well in the menu and probably speeds it up by disabling them anyways. :)
<raghavgururajan>anadon Guix provides GNU Icecat (Firefox Based) and Ungoogled-Chromium (Chrome Based).
<usney>I do use the icons on the tint2 panel though
<usney>I am going to write up when I figure it all out in the guix-devel mailing list to see if they want to include it.
<usney>other wise I will probably put it on a blog somewhere.
<usney>but the fonts are not showing up and it isn't showing up in openbox's menu either. Just works to launch them from terminal.
<usney>I fixed all those issues in gnome but it appears openbox doesn't use it like gnomes does.
<dissoc3>so how are yall writing packages? do you build it outside of a scm file and then map the process to the functions? do you just try to write the build? or are you in a REPL running it function by function?
<apteryx>nckx: no matter what I do my localhost machine can't be used in offload machines, it always gets stuck 'waiting for locks or build slots'. I'm guessing it has to do with the way locking is done.
<apteryx>(i.e., something like localhost is already locked into a 'build', so it can't grab the lock when attempting to offload to itself)
<nckx>Yay! Lock debugging. And you thought you'd be bored during quarantine.
<vagrantc-pbp>nckx: i seen it on recent debian installs ... but maybe i misunderstood what was going on
<apteryx>yes, the goal here is to disable the LUKS security (boot without any password). The machine is physically safe, and loosing completely access to it following an electricity outage is a bigger deal at the moment.
<apteryx>I`don't know much about LUKS keys... Does the LUKS metadata stores the "location" of a key? Do you need to pass the information of the key location when attempting to unlock the LUKS partition?
<vagrantc-pbp>i think it's different weather luks v1 vs. luks v2 ... and grub only supports luks v1 last i heard
<nckx>apteryx: No. The key is just stored in the LUKS header. It's encrypted with [a key derived from] your passphrase.
<vagrantc-pbp>think it's even possible to have the luks headers on a separate media?
<apteryx>vagrantc-pbp: it's a PC at work secured in the office. I put LUKS on it mostly to not worry too much about drives eventually being decomissionned with data on them.
<nckx>If need key, prompt user, else die. That's the extent of the cryptomount module.
<vagrantc-pbp>no second chance if you get it wrong, either, which is... challenging
<nckx>If I sound annoyed I'm sorry, it's because like you I once thought I could build cool things like that 😛 But the answer is always: boot a Linux kernel, script your cool stuff, kexec your coolness. Alway.
<Blackbeard>I have a problem with an emacs mode I am trying to package, it says "Opening input file: No such file or directory, /home/blackbeard/.guix-profile/share/emacs/site-lisp/dict/english.txt"
<Blackbeard>that is correct the file is in "/gnu/store/jgh8n39aia9riai0xi29d7dzzazgs3y9-emacs-typit-0.2.1-checkout/dict/english.txt" is there a way to put the file in the directory .guix-profile/share/emacs/site-lisp/
<guix-vits>Blackbeard: (plain-file obj in package definition (sorry, no better thoughts)?
<nckx>brendyyn: I take that back, I seem to have misinterpreted the ‘GPL’ wikimedia category (our Web site is under the AGPL, so the images are too, so free but not clear yet if that's OK for Wikipedia).
<guix-vits>Blackbeard: i'm id10t. dictionary in (plain-file, lol.
<nckx>GRUB is like a cool lego kit but then you take the pieces apart and it turns out some are cardboard and the back is missing on others but hey it wasn't visible and some are just 2 different colours fused together and —
<apteryx>well now the journey is heading toward my bed, so that's not that disappointing. Good night/day!
<guix-vits>Blackbeard: can you share the definition for emacs-mmt?
<marmulak[m]>one thing that confused me the other day is that my system definition seems to include %desktop-services which if I understood correctly installs gdm on the system, but I saw in the documentation settings for the use of other dm's but not clear where to put them or if they conflict with %desktop-services and how that'd get resolved
<marmulak[m]>also why desktop environments are referred to as -type, in the same document I saw examples with "xfce-desktop-service" but the documentation saying that it's called "xfce-desktop-service-type"
<bricewge>raghavgururajan : Oh nice! I had a go at it, but it didn't went far.
<mroh>is there a way to make a simple text entry (eg to insert a chainloader) into (gnu bootloader bootloader-configuration-menu-entries)? maybe overwrite/customize the (builder) in (gnu bootloader grub grub-configuration-file) somehow?
<reepca>guix-vits: well I'll be... net.ipv4.tcp_keepalive_time = 7200. That seems a rather silly length of time, but eh.
<jeko>Hi Guixters! How re you ? I m looking for help with guix deploy with which I can't figure out why it is telling me "guix deploy: error: impossible de déployer deployed0 : Wrong type argument in position ~A: ~S"
<AndreOc>Now the question is: how do I permit downloading pre-built package binaries from the project's build farms, as I have had to abort right after the installation? Guix doesn't allow me to reinstall (so I can't reinstall and choose "yes" there).
<jeko>Ok, so I think there is a problem with the file I give as input to guix-deploy...
<drainful>On the topic of guix deploy: how possible would it be to create a deploy environment for digitalocean that resolves to a managed host environment for subsequent deployments so as to modify the existing vps?
<drainful>I'm currently using nixops to deploy a personal server and I would love to switch to deploy. One solution is simply to use the digital ocean environment for the first deployment and to make a managed host environment manually for subsequent ones. From a brief glance over the source code it seems like it would be possible to create a host environment type to do it for you as long as you could somehow save the ssh key
<jeko>well I could try to take some time looking to it as soon as I am able to deploy haha
<drainful>jeko: I took a look and I think the error is raised from /gnu/machine/ssh.scm at line 394
<jeko>drainful: thank you very much for this. may I ask you how you find it out (at least if you use the repl? or hack in the repo then using pre-inst-env guix to try changes? or whatever you did), I clearly lack of debugging skills haha so any tips are time saviors
<drainful>Just searched for the words "deploy-error", found &deploy-error, and then searched for where that error was raised, and there was only one place
<jeko>drainful: cool thank you!!! I m gonna follow the lead then
<drainful>jeko: with-roll-back seems to collect errors that arise with the store monad and dump them at you unceremoniously as you've seen; so I still don't know what went wrong
<drainful>If it means anything I tried running using deployer0.scm and got the same error
<jeko>drainful: It was nice of you to help, I will see how far I can go and I may end up trying to seek for help on the mailing list haha.
<jeko>(I could try with ssh keys pasted in the deployer0.scm)
<drainful>No problem. Actually I have one idea. By the time the code that raises that error is evaluated, the droplet should have already been created. It's possible that the droplet not existing is causing that error and that either it failed to be created silently, or was somehow destroyed in the middle of deployment.
<simonsouth>cbaines: But I don't have openssl explicitly included in the system configuration. So I can try that.
<cbaines>simonsouth, what exists at those locations?
<simonsouth>cbaines: Seemingly reasonable stuff. /etc/ssl/certs has a whole bunch of .pem files named after CAs.
<reepca>simonsouth: wild guess, but may as well check to make sure your system time is properly set. It's caused issues with my certificates in the past since my motherboard's persistent clock would get reset when the power blinked.
<simonsouth>reepca: Oh, that's a good point---the time is definitely way off. Let's see...
<reepca>of course, since then I believe we've changed our ntpd configuration so it should automatically handle one-time large time steps, so I haven't had the problem recently
<vagrantc>especially if this is the rock64 ... the single-board-computers are notorious for having RTC issues
<reepca>ntpd often doesn't get automatically started for me, though, so I have to 'sudo herd start ntpd'.
<vagrantc>in my experience, ntpd doesn't actually bump the clock if the starting clock is way old, say 1970-01-01 or so
<reepca>huh, well it worked for setting mine from 2014 to 2020 ¯\_(ツ)_/¯
<simonsouth>reepca, vagrantc: I think that was it. After updating the lock (it was set to 1 Jan 2016) "guix pull" no longer fails right away.
<reepca>apteryx: great to know! I tried doing that a long time ago but ran into an issue with the emacs .so-loading where it just sort of... did nothing. But I can confirm that issue randomly went away in the past few months.
<Blackbeard>Is it ok if I send all the emacs patches from the same branch? I had doubts
<Blackbeard>If I create a branch for each one and they get accepted. Then all will create conflicts
<Blackbeard>But if I use a single branch and one gets rejected that would be bad too
<nckx>This isn't GitHub, that's fine, mail don't care which branch your patch came from. It's up to you whether to send them all with ‘git send-email --to=<nnn>@debbugs.gnu.org -<number of patches>’ or open on bug for each.
<reepca>hmm, "configure: error: found development files for Guile 3.0, but /gnu/store/i8xf43aqrfcrrc4ziskjrlmkqvmkwhbm-profile/bin/guile has effective version 2.2". Is it necessary to run 'guix environment guix' with --pure now?
<nckx>Haven't encountered that error so can't say .
<vagrantc>nckx: it's not *that* bad, it's just inconsistant :P
<nckx>I've had at least one board on loan that booted partitions by offset, so if you moved any it would break. (Calling them partitions at that point is just a desperate lie 😛). I'm not an SBC person though so happy to hear it's not all that bad.
<apteryx>mbakke: I'm not sure it'd help much, but on my aging systems I had made a cheat to accelerate at least deriving the 'current-guix' package: https://issues.guix.gnu.org/issue/37305#16, the patch is the one identified with: '[PATCH 1/5] gnu: tests: Reduce the time required to run the system'
<mbakke>the test is still not finished, but past the provenance.drv
<nckx>I've always refused to reflow descriptions to work around such a blatant bug. Emacs gets enough preferential treatment around these parts already ;-) I had no idea they tried to dress it up as a ‘convention’ though.
<mbakke>"guix system: warning: at least 1240.7 MB needed but only 1231.6 MB available in /mnt"