<CharlieBrown_>Grr... Waiting on Guix to install IceCat so I can use Riot...
<aravind>Hi, I installed irssi and use the wee-slack python plugin with arch linux and stuff works fine. The same thing under guix just sits there. I am at a loss as to how to debug this. Regular irc connections work just fine in both of them.
<mb[m]1>Apteryx_: I don't know about recommended, but I use the OpenvSwitch service on GuixSD to create arbitrary LAN ports. It can also create TAP interfaces for VMs.
<mb[m]1>Note that, if you only have one network interface, there are currently ordering issues at boot. I reboot that particular machine about every two months and haven't bothered fixing it.
<mb[m]1>To "plug" an Ethernet adapter into the "switch" (without VLANs), the command is along the lines of `ovs-vsctl add-port br0 enp7s0 vlan_mode=native-untagged`
<mb[m]1>And then, to create a regular network interface to have IP addresses etc on: `ovs-vsctl add-port br0 vlan0 vlan_mode=native-untagged -- set interface vlan0 type=internal`
<mb[m]1>Where `vlan0` is where you'll have DHCP or static networking for the machine in question (adding IPs on the openvswitch port won't work).
<numerobis>Hi! I am a Nix OS and would like to try Guix, for both GNU Guile and software freedom. Since I know that Guix uses Linux Libre, drivers for some of the components of my machine won't be available. This is not a problem, as I'm happy to buy hardware that will work with a fully free operating system, but I was wondering whether there was an easy way to check the compatibility of my current hardware? And, apart
<numerobis>from WiFi, what are the other things to watch for? Thanks!
<numerobis>brendyn,efraim:Thank you for the answers! H-node is very good indeed, but I was wondering whether there was a way around having to manually check the compatibility of each piece of hardware. I'll probably try with Trisquel first :)
<rekado>numerobis: In my experience it’s usually just WiFi and non-Intel graphics chips that are problematic.
<rekado>the new Dell server + the large storage server still need to be configured, so I’m still using the old head node. Once the new server is ready the current head node will be turned into yet another build server.
<rekado>then we have 26 build servers, a powerful head node (which could probably also build some stuff), and a couple of TB storage for /gnu/store.
<lfam>Well, we should definitely get that merged :)
<lfam>dustyweb: Is there a reason besides "not yet confident" that it hasn't been merged?
<kevinfish>When I try and install from the manual instructions from a binary tarball onto a ubuntu system (peppermint OS) when I try to do: guix archive --authorize < ~root/.guix-profile/share/guix/hydra.gnu.org.pub I get guile: warning: failed to install locale
<kevinfish>warning: failed to install locale: Invalid argument. Help!
<lfam>kevinfish: It's just a warning and it's harmless in practice. You can fix it by setting the variable GUIX_LOCPATH correctly in a few environments: 1) Wherever you run Guix from. So, your user's and root's login environments. 2) Where the guix-daemon runs. Presumably to be exported from the systemd service file.
<dustyweb>lfam: it was going to be merged but someone said "wait! this is too webroot centric"
<dustyweb>if you do that I'll get it merged in. It sounded like civodul also wanted it merged.
<lfam>I think the comment about webroot being plugin-specific is incorrect, unless I misunderstand
<lfam>Well, it means that the service is intended to be used with a running webserver, so that does limit the use case somewhat. However, I think that serving HTTPS is the primary use of TLS in practice, so it's a fine place to start
<lfam>Besides, in the long run, there are a million things that can be improved with certbot if you just want a general-purpose ACME client.
<ng0>maybe with some hooks into the acme client we can prevent that dialogue or configure what's passed to it in advance
<kevinfish>warning: failed to install locale: Invalid argument
<kevinfish>guix package: error: build failed: the group `guixbuild' specified in `build-users-group' does not exist
<lfam>kevinfish: It looks like you didn't finish the installation instructions yet. Specifically, step 4, which tells you how to make the build users and their group
<kevinfish>lfam: I went down every step even to installing the hello package but several of the steps bombed. What seems to be fixing it is skipping installing the glibc-locales package, setting the GUIX_LOCPATH variable first, then going back to install the glibc-locales package which gave me request to guix pull, etc... first
<rekado>that’s one of the steps in the instructions.
<rekado>I hope you didn’t add your user to that group
<kevinfish>I don't see building guixbuild group in the instructions. The only result for searching for that in the page is at the end of step 5 when starting the demon manually (which I didn't do cuz I have systemd)
<dustyweb>ACTION nervously crosses fingers and hopes that guix pull works on the server
<dustyweb>whew! we really need that memory leak fixing guile-2.2 patch fron civodul!
<lfam>kevinfish: Step 4 has a link to Build Environment Setup, which is an important step
<rekado>dustyweb: I’m testing these patches in a couple of hours.
<kevinfish>ah, I missed that! Got too caught up in copying/pasting into the terminal I guess
<lfam>Sorry about that kevinfish. I've wondered how we can highlight that link, since I've seen people skip it before. But those instructions are not specific to installing Guix from the binary, so I think it doesn't make sense to move them into the binary installation section
<sirgazil>Question: I ran "guix package --remove hello" and I got this output: https://paste.gnome.org/p0nrjt5rp . Is this normal? I mean updating lists of substitutes and downloading stuff before removing a package?
<ng0>sneek: later tell TaoHansen[m]: About pitivi, I've encountered some more dependencies (a new branch of dependencies actually), so I won't be able to finish it as quick as I imagined.
<lfam>I'm wishing to ungraft glibc sooner than we would have in the past, although in reality we'd have to wait a long time for armhf :(
<lfam>Rather than buying more armv7 hardware, I think we should figure out how compile armv7 binaries on more powerful armv8 hardware. I still don't know any reasonably powerful armv7 hardware that we could rely on
<rekado>the server for which Ludo shared a link is for armv8.
<kevinfish>so now if I erase /var/guix and /gnu I can start over right?
<kevinfish>lfam: yeah, it wouldn't make sense to copy the text from section 4, but since its starting the demon part appears to duplicate/conflict with the main page's maybe it would. As much as I like guix, today I'm doing it as a means to an end because it has something packaged that I've been unable to install in peppermint (even from source) so I'm skimming and jamming which made it easy to miss section 4.
<kevinfish>lfam: maybe a mention in section for to do everything BUT start the demon from the linked page then come back to the main page for that