<suitsmeveryfine>Jookia: is the part "usb-storage:xhci-hcd:usbhid:hid_generic:mbcache:hid:jbd2:ext4:i915:hid_apple:ohci-hcd:evdev:uas:xhci_pci:xhci_hcd" just a list of modules in that particular order?
<mark_weaver>some package build systems try to detect details of the build machine. we should always try to disable that kind of thing, and instead arrange for it to build for the lowest-common-denominator of the architecture.
<lfam>mark_weaver: I seem to remember that the hydra machines (at least the intel-compatible ones) are running trisquel. In that case, could you share the /boot/config-$version-amd64 file so I can compare my kernel configuration? I believe that is a standard file on Debian-derived distros
<mark_weaver>lfam: do you have CONFIG_DEVPTS_MULTIPLE_INSTANCES=y
<calher>lfam, I've been told I have Asperger's, so you may not even be able to tell then.
<mark_weaver>calher: it's not important. if you are interested in Guix, then I'd like to welcome you to our community, and I'm sure we'll learn to communicate better in the future.
<mark_weaver>when i wrote that it works for me and that I'm not sure what's going wrong on your end, I did not mean to imply anything beyond what I literally wrote. I did not mean to imply that it was somehow your fault.
<mark_weaver>mainly I wanted to make it clear that these commands normally work within M-x shell
<mark_weaver>in core-updates, polkit fails to build, even on x86_64, because its configure script doesn't think that mozjs-17 is available, although it is an input. not sure what's going on there, but if someone is looking to help, fixing it would be helpful :)
<Jookia>Well, Debian generally has already done the hard work and bootstrapped packages for other architectures
<NiAsterisk>who was it asking for an email address without previous email providing? I just remembered mailchuck.com or bitmessage.ch, getting a one time address at one of them, then providing this at an email hoster of their choice this would work if the email provider does not save the one time address after the signup is done.
<Jookia>I've always used guerillamail or ruggedinbox for that kind of thing
<rekado>thanks for the help. I think it's working with using the tarball generated by "make dist". Not quite sure why the git clone doesn't work.
<rekado>I'd like to add the generated "configure" to the repo so that people don't need to bootstrap when cloning.
<civodul>some projects do that, notably libc/gcc/gdb/binutils
<NiAsterisk>what services does `services desktop` pull in? I need to remove everything a server does not need, but I am unsure what's left if I just remove desktop. is base + dbus + networking + optional others enough then to not pull in slim and xorg etc
<NiAsterisk>barebones.scm looks like it would be okay for this I guess. should've read examples first before looking at services subdir
<rekado>I see that the ghc-package-cache derivation is always built. Could we make this conditional?
<mark_weaver>rekado: in the tarball, the modification times of the files are preserved by tar.
<mark_weaver>rekado: when you check out with git, afaik there's no guarantee what the mtimes will be of the unpacked files.
<mark_weaver>well, they will be roughly the time that you checked out, but their times will differ because it takes time to check out all the files
<mark_weaver>and I'm not sure there's any guarantee what order they will be unpacked in.
<mark_weaver>so the ordering of their mtimes will not be guaranteed, and it may end up that your .ac/.am files are slightly newer than the files generated from them.
<mark_weaver>and when that happens, 'make' will decide that it's time to rerun some of the autotools programs to regenerate files.
<mark_weaver>ACTION dislikes the practice of including auto-generated files in the git repo
<mark_weaver>NiAsterisk: when you asked about what `services desktop` pulls in, I was not sure what you meant. first I thought you meant %desktop-services, but the quoting seems to suggest otherwise. did you mean to ask: what does (use-service-modules desktop) pull in?
<NiAsterisk>my question was a bit off. I think I solved it by myself by looking further at the source
<NiAsterisk>not so easy.. if I export SSl_CERT_DIR before I do init system, will it influence the system init somehow, do I have to revert the path? i can't clone via https with what I've got, and cloning via ssh is not effective.
<NiAsterisk>i booted into a new guixsd setup. then I tried to clone a repository I needed, installed git, openssl, etc etc, ended up with wget --ignore-ssl-certs or what it was to get the master.tar.gz instead of cloning the repo
<davexunit>NiAsterisk: then you didn't set the correct environment variables.
<NiAsterisk>i changed the variables in the end, still didn't work
<davexunit>then you did it wrong. not sure what to tell you.
<jin>ok, how can i show a description of frecuently errors?
<calher>Crap, Mumble needs Linux Standard Base and that hasn't been packaged.
<mark_weaver>calher: Linux Standard Base is probably not something that can be put into Guix. It presumes things like that we follow the Filesystem Hierarchy Standard, which is fundamentally incompatible with the design of Guix.
<mark_weaver>I think Mumble would need to be modified to conform with Guix.
<mark_weaver>anyway, we often have to make modifications to software to adjust it for the way Guix does things. the most common cases of this are automated, but occasionally we need to make package-specific adjustments.
<calher>Mumble is the one thing stopping me from going to Guix.
<calher>I didn't know how hard it was to package stuff.
<lfam>jin: What is the path of nautilus.scm? I believe the module path (line 1 of nautilus.scm) should match the filesystem path. So, nautilus.scm would have to be at "gnu/packages/nautilus.com". Another example: Change the module path to (jin packages nautilus) and put the file at "jin/packages/nautilus.scm"
<alezost>jin: actually the best for contributing would be to clone the guix source and set it up, so there will be no need to use "guix build -f" to test your packages. See (info "(guix) Contributing") in the manual.