<nekroze>hello, I am taking the weekend to try switching to guixsd, so far it has been great. Just having some trouble using enlightnment wm as the locker it uses is not accepting my password so I get locked out. From the docs I thought I would need to define (screen-locker-service enlightenment) but that does not solve the problem, what have I missed?
<nekroze>does guixsd have something like https://nixos.org/nixos/options.html where I can search for defined serivces? so far I have been using the docs and trying to guess what category of services the service I am looking for might be but this fails me often
<Apteryx>nekroze: have you tried searching in the info manual of guix using C-s?
<catonano>I gc'd and make distcleaned, renovated all I could renovate
<catonano>ifnally I could have a new virtual machine containing the righht version of Tryton
<catonano>that's jjuust an example of naive errors I do
<catonano>Now Trytond attempts to connect to the wrong db, rather than postgres. This usually happens when the conf file can't be read. So I have to manually launch it in the virtual machine to see exactly what's the problem. It could also be that the python-postgres library should be propagated (propagated-inputs)
<ng0>I'll be looking into nightly kernels etc, but that'S beyond what we could offer in Guix upstream, and also how to address this.. I'm sure it's not just 2 people here in Guix who are affected by this. I simply thought my hw was broken and did not report it.
<ng0>actually, it *is* upstream. but, how do we deal with such bugs?
<adfeno>ng0: Could you summarize what is the status of all this glitches, is there a plan from upstream to fix these, a solution or work around from them? Or neither we nor upstream has solutions or workarounds?
<marusich>civodul, in general, if one wants to port Guix to a new platform, is it necessary to build the bootstrap binaries? Can one cross-build guix itself without cross-building bootstrap-tarballs, or is cross-building bootstrap-tarballs a necessary part of cross-building guix?
<str1ngs>manumanumanu: alternatively you could do LD_LIBRARY_PATH=/path/to guile script.scm
<str1ngs>manumanumanu: that might cause uses with guile though
<str1ngs>I've only used it couple times myself. was kinda fun though :)
<manumanumanu>str1ngs: yeah. it uses libffi iirc, and is quite nice to work with, although A bit low-level
<manumanumanu>hmmm. I could probably get things done in guixSD. I only even need emacs, weechat and a web browser
<marusich>civodul, the reason I ask is because I was hoping to maybe port Guix to another platform, and I ran into an issue similar to https://debbugs.gnu.org/cgi/bugreport.cgi?bug=24841 when cross-building the bootstrap-tarballs. I didn't know of any other way to port Guix to a new platform (since I've never done it before), which is why I updated the bug to see if anyone knew what the problem might be. However, if there is another way to port Guix
<marusich>without cross-building the bootstrap-tarballs, then I would be un-blocked. So I'm wondering if maybe there's another way to port Guix without cross-building the bootstrap-tarballs. But I think the answer is "you must cross-build bootstrap-tarballs at some point first"?
<str1ngs>generally bootstrapping requires cross compilation, even if you are targeting the same architecture
<marusich>Could one conceivably build Guix from source using system software not deployed via Guix?
<marusich>For example, if you have a system on a new platform that runs some linux distro, and you use that distro to build Guix from source.
<marusich>I have read that section multiple times.
<marusich>Does it not say that the bootstrap binanries are included in the source distribution?
<marusich>"This gets stored in the guile-2.0.7.tar.xz tarball shown in this graph. This tarball is part of Guix’s “source” distribution, and gets inserted into the store with add-to-store (see The Store)."
<marusich>So, if someone hasn't included bootstrap binaries for architecture foo, then when I go and try to build Guix from source on architecture foo using a generic GNU/Linux distribution, won't it be impossible to successfully build Guix on that system (since it lacks bootstrap binaries for the foo architecture)?
<marusich>Are you just saying that I should build the bootstrap binaries on the foo architecture, and then add them to the Guix source, and then build Guix? That would make more sense to me.
<str1ngs>I think guix build bootstrap-tarballs handles that