<civodul>search for "reproducib" or "determinist" :-)
<brendyn>Sometimes the 1970 date bubbles up into a user facing program. It wouln't be nice if documentation said it was made in 1970. I wonder if there is a better option.
***cuckle[m] is now known as bighugmug
<civodul>i've never faced this situation, except sometimes in --version output or similar
<bighugmug>hey, I know proprietary firmware is not supported, but I was wondering if anybody has had any success installing iwlwifi? I've looked for anywhere on the USB image file and the initrd to see if there's any directories containing .ucode files, but can't see anything
<civodul>as you wrote, it's not supported, which is why you didn't find these files :-)
<nee`>brendyn: patching out the line that prints the date would probably be the best option. Maybe replace it with "Built in GNU Guix". ;-)
<rekado>on the file server itself it’s XFS; that’s high-speed connected to a server, which exports the file system over NFSv4
<civodul>got it (i'd call that NFSv4 over XFS, a matter of perspective ;-))
<rekado>the file server itself is just a bunch of disks with RAID cards and cache, really
<str1ngs>is there away to start with a fresh profile?
<str1ngs>I should probably use environments for this I think
<civodul>"guix package --switch-generations=0" may work
<civodul>environments should be nice for development
<rekado> try pure environments if you don’t want to mess with your profile.
<str1ngs>I'm kinda new to guix methods. so environments are a bit complex for me right now.
<str1ngs>ahh removing binutils and gcc did the trick
<rekado>str1ngs: they might be easier than profiles, actually. You just run “guix environment --ad-hoc this that here there” and you end up in a sub-shell where “this”, “that”, “here”, and “there” are available.
<rekado>you can further control your environment by adding “--pure”, which resets some environment variables.
<rekado>or with “--container” for even more isolation.
<str1ngs>thing is I'll be using this in profile anyways.
<str1ngs>but... it would be good to use containers, and or environments for testing.
<str1ngs>I think I need to convince the GNU farm admins to install guix
<str1ngs>does guix use ~/.guile ? or only when using the a REPL?
<vagrantc>if i run: "guix pack -s x86_64-linux --localstatedir guix" does that build a tarball for guix i can basically unpack on a foreign distro? and what version of guix does that tarball contain? the version used to build the tarball?
<g_bor>I just got some more info from the gtk+ irc channel:
<g_bor>17:49 < EmmanueleBassi> gabriel_: It's fine to ignore 17:49 < EmmanueleBassi> gabriel_: GLib added a new marshaller in its public API 17:50 < EmmanueleBassi> gabriel_: And the `abicheck.sh`in GTK+ 2.24 hasn't been updated because GTK+ 2.24 is in deep maintenance mode and very few people test it against newer versions of GLib 17:50 < EmmanueleBassi> There's the question as to whether GLib should have added a new marshaller in the public AP
<g_bor>EmmanueleBassi> But that happened a long time ago
<g_bor>so, I think it is fine to update the abicheck.sh in a way to ignore glib marshaller symbols.
<myglc2>Oops, Sorry, trying to figure out erc doctor
<str1ngs>when I do something like. guix package -i git -n . it does not say it needs to build anything other then some drv's . however when I actually run guix package -i git. there is more to build then with -n
<str1ngs>should -i git and -i git -n not show the same actions?
<efraim>228 minutes to compile qt@5 with ccache added, now to time it without