<brendyyn>I have to add #t to one line but now I'm stuggling with a rebase conflict
<b11111000000>guixsd can't be installed from gnu server to couple of slow machines for now... It's always compile mesa or something... How to create installation media with force use of preloaded packages?
<reepca>DoublePlusGood23: for purpose of testing or for regular use? For regular use it would make sense to just install the package into your profile, for testing / development it would make sense to use the full path directly (adding it to PATH temporarily might help, or an alias, or a symlink somewhere). I don't know of any special way of dealing with that, though I do wonder what (if anything) keeps "guix build" outputs from being garbage
<brendyyn>Can fonts in /share/fonts/truetype/ not be in subdirectories?
<itsfemme[m]>DoublePlusGood23: ng0: the best would be to package torbrowser-launcher
<reepca>guix environment foo && guix build foo --no-substitutes works okay for testing the building of foo quickly until it turns out to require subversion for fallback, which guix environment foo doesn't provide for some reason.
<itsfemme[m]>b11111000000: tor browser exists so people dont try to torify a browser expecting to be anonymous because it's not, most browsers are very fingerprintable and with just torify you don't get stream isolation. I rec. reading the tor browser design document, it explains all of this very well
<Apteryx>brendyyn: You had to run fc-cache to get your fonts working?
<Apteryx>Hmm. GUILE_LOAD_COMPILED_PATH is /run/current-system/profile/lib/guile/2.0/site-ccache:/run/current-system/profile/share/guile/site/2.0 on my GuixSD system. I would have expected 2.2 or something since I reconfigured and reboot this morning.
<rekado>maybe the move to guile 2.2 didn’t work for haunt
<efraim>i forgot about he.net, only ever heard good things about them
<rekado>re haunt: it got confused by a mixed GUILE_LOAD_PATH
<ng0>I'm looking into setting up my own dynamic dns where content is served from multiple locations, if I'm not satisfied with the features I can use. And I like documenting this for another project, so that's the diy thing
<rekado>bootstrappable.org has been fixed. Thanks again.
<rekado>I can’t compile Guix on my i686 machine any more. Running out of memory with Guile 2.2 :(
<rekado_>it’s not a secret. You can post your findings to guix-devel.
<wingo>RAM usage of 2.2 .go files should be lower fwiw (in terms of RSS/PSS).
<ng0>that's not where people installing GuixSD on servers will look first. they will look somewhere in the documentation or website for limitations. right now there's nothing listed for hardware, at least last time I checked
<rekado_>ng0: the release is due this week. The switch to Guile 2.2 will be mentioned there.
<jlicht>ng0: Are you referring to publishing recommended system specs on the website?
<ng0>irc is suboptimal for good communication. what I meant is what jlicht wrote.
<jlicht>It actually left me wondering. civodul (and many, many others) spend astounding amounts of time on guix related things. Are you just very efficient with your time, or do you also work on guix during working hours?
<wingo>i think you should be able to run the build-aux/compile-all.scm script without a git checkout
<m-o>civodul: just pushed the serie, it was good to go for me anyway.
<rekado_>sadly, even without parallel compilation I get a crash on my i686 netbook trying to build Guix.
<rekado_>“GC Warning: Out of Memory! Heap size: 593 MiB. Returning NULL!”