<nckx>lispmacs: What did help me get my remote printing set-up working was (log-level 'debug) (access-log-level 'all) and tail -f /var/log/cups/error.log. Then you can at least figure out who's not talking to whom.
<nckx>rekado: I can reach them both from berlin. I noticed that the port numbers are swapped in the tunnels (i.e. 2222:dmitri.tobias.gr:5551 will take you to sergei instead) but that doesn't matter in practice. I'll swap them on my end.
<nckx>lispmacs: Did you restart cups? This sometimes happens when I update splix & CUPS gets out of sync (using an older store path). We'll probably need the exact 'debug error from error.log (see above) to get much further.
<talope>nckx: thanks for your help yesterday. My laptop is now hibernating. I ended up cloning guix and using channels.scm to direct to my clone rather than the environment approach you pointed me too -- basically because I couldn't get it to work with the nonguix channel I still have to use for my wifi card. loginctl has ample support for hibernation -- too bad the patch is not in, i'm going to refresh it and try to mainline it somehow.
<pkill9>note: im using the gnome desktop environment
<leoprikler>I'm sure this issue has already been reported w.r.t. GDM.
<leoprikler>I'm not sure how to fix this however, since you deliberately suspended your laptop (rather than inadvertently through GDM).
<valignatev>Hello-hello! Maybe kinda dumb question, but is is there some way for cargo-build-system to figure out needed cargo-inputs automatically without specifying them manually? It looks like that it's possible considering that packages in crates-io.scm doesn't always have cargo-inputs explicitly specified
<raghav-gururajan>leoprikler Thanks so much for your email. After `guix environment --pure guix -- ./bootstrap && ./configure && make`, should I stay in env or leave the env, for doing guix lint?
<leoprikler>I don't think it matters as long as you prepend ./pre-inst-env
<leoprikler>You can't do your git stuff inside the pure environment though, so if you want to reuse it, you have to spawn a second shell to do things in parallel.
<raghav-gururajan>Ah, that is the issue I am facing. When I do `./pre-inst-env guix lint package-name`, I get no package found error.
<leoprikler>(I prefer this approach, because then I don't accidentally use the normal guix, as it's not available in the pure environment.)
<kirisime>raghav-gururajan: Which version of GNOME are you on currently? I might've had your issue and simply thought that the video I was watching was partly corrupt, but after upgrading to 3.32 the video in question seems to play fine.
<raghav-gururajan>kirisime 3.32. But the issue started with 3.30. Things were fine before 3.30 upgrade.
<kirisime>And I might've had my issues even in 3.28. Odd.
<bandali>rekado_, do you if adding some ;; comments here in and there to a package definition will cause a rebuild by cuirass? not commenting anything out, just adding a TODO or something
<sneek>mehlon, raghav-gururajan says: : flatpaks require FHS, which is not supported in guix yet. I have seen some conversations regarding a service for that. If you are looking for featured web browsers, you can use icecat and ungoogled-chromium. If substitutes are unavailable and you do not have high CPU power, you can wait for the build farm to finish building those substitues.
<navik>mehlon: I stand corrected - there's obviously more to it.
<valignatev>Can you some how give an entry that gets created during "reconfigure" a custom name? Something like guix system reconfigure --name "experiment with dangerous stuff". And then this "experiment with dangerous stuff" appears in grub
<mehlon>I'd figured that coreboot cannot boot UEFI stuff
<navik>mehlon: anyways, thanks for your guidance, I might post more thoughts here another day
<mehlon>you should probably ask in a librem-specific channel
<navik>I guess I'll have to look into the details of librem boot process.
<guixy>I'm guessing the wrapper belongs in the clojure package itself. Like how plantuml has its own wrapper (and its own problems).
<immodicus>Immodicus:I was trying to install guix on an external hard disk,out of pure curiosity, but suddenly it gives me the error "corrupt input while restoring the archive from # <closed: file 3bd97e0>". I used the graphical installer and automatic partitioning ...can anyone tell me how can i eventually resolve?can it be an installer bug?
<guixy>That sounds deadly. How does your main disk look?
<guixy>I think I encountered something like that once. I tried to make two disks in a virtual machine. One as the system root, and the other as /gnu/store. It didn't install back then. But this was in August.
<guixy>There's a guix matrix channel. You might find that easier to use.
<valignatev>Hm, I just encountered another weird thing about cargo-build-system. There is already packaged rust-clap-2 in crates-io.scm that I'm using as a #:cargo-inputs for my package. But when I'm trying to build it, cargo-build-system complains that it can't find dependencies of clap-2. AFAIK these dependencies are packaged in guix already.
<valignatev>If I'm starting to add these dependencies explicitly to already existing clap definition it seems to work, but I wonder why clap-2 was packaged without explicitly specifying cargo dependencies in the first place? Is there some flaky cargo-build-system feature that suppose to resolve cargo dependencies automatically as long as they are packaged but
<valignatev>I also see that there's some overhauling work going on to improve cargo-build-system, so maybe it's better to just wait and see
<civodul>rekado_: re mumi, looking at /proc/39559/fd, it seems that it's leaking socket file descriptors
<civodul>so maybe it's the web server module that forgets to close client file desc.
<bandali>civodul, hey, thanks for the feedback on my emacs-next patch. if you prefer to not change the package definition for emacs until next release, i can probably get away without touching it, but there'll be code duplication
<civodul>bandali: it's not that i do not want, it's just that it would trigger a huge number of rebuilds
<civodul>and thus it wouldn't be able to go to master
<civodul>i guess it's ok to have some duplication here in the meantime
<civodul>we just need to add a comment with an arrow pointing to the one thing that's different :-)
<civodul>so that we can more easily merge both in the future
<bandali>understood :) i'll probably add a ;; comment to emacs's definition with what needs to be changed later