<rekado_>ilikeheaps: it’s computing something but it should tell you pretty soon what it’s working on.
<ilikeheaps>Oh, actually just a couple minutes. It just printed "building /gnu/store/..." line
<roptat>rvgn, I'd prefer to make sure the renewal is automated
<roptat>changing the CNAME doesn't seem like a good idea since it impacts users
<rekado_>ilikeheaps: building things can take a long time; depends on what it is building.
<rvgn>roptat Yeah, renewal is still automated because we are not chaning the CNAME.
<roptat>mh... but then you have the same issue, no?
<roptat>also we can't have a CNAME for guix.gnu.org since we have other records (NS)
<rvgn>roptat guix.gnu.org --> CNAME and CNAME --> IP. The CNAME will be kept unchanged and used by certbot for renewal verification. The IP of that CNAME though, can be changed which doesn't affect the renewal process I believe. If IP1 fails, the vaule can be change to IP2.
<ilikeheaps>rekado_: Alright, it just output the first line so I'm happy with it
<rekado_>…other services for which DNS lookups with 2 resulting IPs would cause problems?
<roptat>rekado_, I think the other possible behavior is that it will try only one IP and fail if the server is down
<roptat>directly on guix.gnu.org? I don't think so
<rekado_>roptat: yes, that’s the behaviour I’m aware of.
<rekado_>I’d rather not leave the host selection up to the client
<roptat>rvgn, although now if the load-balancer is down, we have no more website :)
<rvgn>roptat Yeah. In that case, we have to provide only the one IP (load balancer) to the certbot. So easy automated renewal. But we have to make sure that load balancer is hosted somewhere with good uptime reputation.
<rvgn>roptat I think the best way is to use third-party load-balancer (like cloudflare etc.) then have our own hosts (berlin and bayfront). In this way, the load-balancer is less likely to be down because the third-party will be using reddancy for their service.
<ilikeheaps>Speaking of foreign distro: is there a way to use services from Guix? I suppose they are too tied to the init system
<nckx>erudition: Hm, I've definitely run into that in the past, and it was easily solved by deleting something, I just can't say what off the top of my head. I'd say go for it, move it instead of deleting if you want to be safe.
<nckx>current-guix is only used to provide ‘guix’ itself, it won't break anything you've installed with the guix package manager.
<erudition>It worked! But I've just moved onto a new permission error lol
<erudition>(Perhaps the install script could do this stuff automatically)
<nckx>I'm not sure (literally). It still amounts to deleting user data. We'd have to think of any way that it could have unintended consequences, but maybe it's harmless.
*nckx has only used the install script once, reluctantly, and it didn't go exactly well 🙂
<erudition>well I tried the manual steps too, with the same end result
<minall>What does 'guix system init' exactly do? I'm trying to install guix on a machine, and I got an error that says that the disk is full, so it cannot continue? I assume that it downloads everything and then copies it in to the target? so the usb of guix would be a normal guix system? what should I do to 'release' space so I can do a succesful 'guix system init'? Or should I redo the USB again?
<roptat>bandali, ok, so it seems we have more work to do before redirecting users, but I'm not sure how to list the content of gnu.org/s/guix to make sure every old page is redirected to a page on the new website
<bandali>roptat, would looking through guix’s web pages repo help?
<ilikeheaps>Oh well, I'll check in later. Or maybe I'll just rebuild everything
<rubic88>Hi guix. I just installed 'cheese' to test my X220 cam, but it says "no device found". Where should I start looking to debug? (Guix System)
<atw>rubic88: I also grabbed cheese to test my librem's camera and got stuck at a similar point. Let me do it again while looking at dmesg and I'll tell you how far I get
<atw>yeah, about the same: dmesg and lsusb don't seem to indicate that anything went wrong but cheese can't find the camera: "** Message: 12:03:57.273: cheese-application.vala:211: Error during camera setup: No device found"
<minall>quiliro: How should we install freedombone?
<rubic88>lsusb output: Bus 001 Device 006: ID 04f2:b217 Chicony Electronics Co., Ltd Lenovo Integrated Camera (0.3MP)
<ilikeheaps>Repeating question from before: can I reuse /gnu/store from a broken installation when reinstalling? I'd like to not redownload all packages (the problem with installation was misconfigured file system)
<bricewge>What is the recomended way to test modification to a services from a local guix repo?
<bricewge>At the moment I commit, guix pull and reconfigure system but it doesn't seems right.
<deadman007>Hi Guix, I want to mount a separated partition for `/gnu/store`, for this I added a new file-system entry in system configuration file and set the `need-for-boot?` flag to #t . but after reboot, GRUB theme wont load correctly and I receive `no such device` about store files and kernel won't boot. does anyone has any experience about this?
<rickbutton>question about encrypted filesystems, this is a minor inconvenience, but my install makes me type in the password twice, one at the grub prompt, and once again after grub, any idea how to stop that?