<pkill9>apteryx: could you send a link to the service? i want to add it as a service, but didn't get round to fixing the one i wrote
<pkill9>i did it wrong because I think it killed the shepherd, lol
<apteryx>pkill9: hehe. I'll write a quick doc for it, then append to your existing patch on guix-patches
***Drakonis__ is now known as drakonis
<apteryx>pkill9: hmm. Wondering in which service category (in the manual) a user space, OOM software should go. I was going to add a new "Linux Services", because it's explicitly tied to the Linux kernel. Any ideas?
<raghav-gururajan>nckx I see. So if there is tarball that contains 90% files that are free and 10% files are unlicensed/non-free, and if we use that source with snippets to remove non-free parts, where will that 10% be stored in the users system?
<leoprikler>if it is, you-ll have to do something like $package-$version$$, where $$ is a literal $ (end of line)
<raghav-gururajan>leoprikler I am confused. Based on what you are telling, we should only use a source that contains 100% free parts correct? But nckx mentioned something about snippets to remove non-free parts.
<leoprikler>If you use snippets as nckx says, you'll be left with a modified version, that contains 100% free parts.
<apteryx>drainful: guix build will list them all. You could grep the result.
<raghav-gururajan>leoprikler So in that case, the unmodified source is first downloaded, then patch applied to modify the source, correct? What happens to the unmodified source?
<vagrantc>pretty sure it stays in the store, like when building linux-libre, you end up with several linux-libre-VERSION.tar.* in the store ... i presume some are the cleaned sources and some are the originals
<raghav-gururajan>Wait a sec. So if linux-linux haven't got around a minor point release, that means their patches to deblob are not ready yet, correct? Then how come guix can use that patches when it is not ready?
<raghav-gururajan>vagrantc I think we should stop using vanilla linux as a source in package definitions. Because, we showing the end user where the unmodified/non-free source is. This also *gives* opportunity to use that source without patches/snippets. This is bad, right?
<vagrantc>raghav-gururajan: you bring this up quite often
<vagrantc>i know in the founding of guix it was discussed with the fsf and rms and it was deemed fine...
<raghav-gururajan>vagrantc I don't know why. Whenever I work on pakages, this thing keeps bugging me like an OCD>
<vagrantc>linux-libre does it as well ... just waiting for linux-libre would be hiring out the dirty work to someone else
<raghav-gururajan>Ah I see. Was that discussion public? May the contents of that discussion could satisfy me. :)
<apapsch>How do filesystems in a operating-system relate to testing in a vm (or deploying via ssh)? Should I just assume there's a /dev/sda1? no reference by id?
<bandali>leoprikler, hey, sorry, had already passed out. i have a question about ‘building emacs packages using emacs-next’ that we discussed yesterday. let me know when would be a good time for me to ask
<bandali>leoprikler, hmm, i see, will try that. there’s also an interesting use of it in the guile-emacs definition where they supply a new list on the fly. any reason to do it that way? (add #:parallel-build? and #:tests? there)
<joshuaBPMan>Hey debian! I've got a question for you. Which is "better": 1) Install Wordpress on debian via the Wordpress package ya'll provide....OR downloading the wordpress source code directly and using that?
<raingloom>hey, could someone help me debug evolution? i finally have some time to dig deeper into it but i could use some help.
<raingloom>it doesn't show any of my emails but it does seem to successfully download them through POP. i tried using my existing config in a VM, but when i copied it over it just ignored it and showed the setup wizard.
<mfg>Does anyone know a decent Tutorial which explains how to write a parser in guile?
<raingloom>mfg: idk if there are tutorials but you should probably look into parser combinator or PEG libraries.
<mwette>mfg: Can you be more specific? Guile comes with PEG and LALR parser generators; I have written a separate LALR parser generateor
<mfg>i want to update the android tools. Since android8 they are using .bp files instead of makefiles. those files have a JSON-like structure. i need to parse them and (maybe) construct makefiles out of them.
<mfg>i thought this was a better way than hardcoding everything
<bandali>leoprikler, great, ty; will check it out shortly
<thomassgn>leoprikler: the '(packages->manifest (map (compose list specification->package+output)' is what specification->manifest is defined as in gnu/packages.scm Already tried it, gives me the same result.
<leoprikler>perhaps, but one of them is significantly nicer to read
<thomassgn>I could also write them out plain, but I'd have to add a bunch of module imports, I find this easier. Though just now it's become harder... :)
<thomassgn>haha. Yes. The spec->manifest requires an import though. :) I'll try again with it.
<leoprikler>You can try splitting it up into multiple files as I already showed you. That keeps imports per file minimal in my experience.
<thomassgn>yea, I might just have to do that. I just don't understand why this does not work anymore, been using it for a while now without problems.
<leoprikler>or would this file still work with an old version of guix?
<bgardner>Good afternoon guix; I'm trying to add guile-json to my system packages and getting weird conflict errors ("guix system: error: profile contains conflicting entries for guile-json") that are new to me. Any advice to resolve this?
<bgardner>terpri: So says the error message, yes. Let me read that and come back
<bgardner>terpri: This bug report seems to hint that "guix" is an installed package in the user's profile. I'm calling 'guix system reconfigure' with guile-json added to the package section, and I take that to be a different use case, no?
<bgardner>terpri: Although possibly a distinction without a difference, I guess
<mwette>Given a package is there a way to find it's guix package spec (in Scheme)? I get a hit from "guix search bytestructures" but I need the #:use-module part to add to my own package spec.
<dctrud>Hi guix - had an interesting question from Compute Canada about an issue where they use Nix userspace and are running Singularity on HPC cluster