<zacts>mark_weaver: well I've got a bbb, just got it at my front door like 20 min ago
<zacts>I would be more than interested to test guix out on it
<mark_weaver>the main issue now is that we don't have any build slaves for our build farm, so no pre-compiled binaries for it (and it wouldn't be powerful enough to build the system itself) and a lot of packages may have become broken in the meantime because of the lack of continuous integration.
<davexunit>people say things like ""Reflections on Trusting Trust" gets posted on HN regularly, and it's an interesting exercise, but you are far more likely to have an exploit hiding in plain sight in a compiler compiled from source once than you are to have one that only appears after multiple iterated compilations."
<davexunit>and ""Trusting Trust" is over three decades old, and there have been numerous response to it in the interim, with lots of study."
<civodul>the only response i know of is the one by David Wheeler
<civodul>now, the attack itself is surely difficult to do in practice
<taylanub>I'm trying to package s2tc, an optional mesa dependency, but it seems to require OpenGL headers to be built, meaning it's a circular dependency :\\ I think normally it's solved through the fact that mesa loads it dynamically, not requiring it be there at build-time, but how to solve that for guix?
<civodul>taylanub: typically we would (1) build mesa without s2tc, (2) build s2tc with mesa from (1), and (3) build mesa with st2c
<civodul>though that can only work if users of (3) don't end up with two copies of libmesa.so in memory
<taylanub>so a mesa-without-s2tc package inheriting from mesa, used only to build s2tc and not meant for installation by users?
<rekado>I'm trying to port a little offlineimap hook script to use the Guix python, but I'm failing.
<rekado>Does this error mean anything to anyone here?
<rekado>--> ImportError: could not import gobject (error was: '/gnu/store/vd8ij01bq08icp87bz5gs2v4bq53bls6-glibc-2.21/lib/librt.so.1: symbol __shm_directory, version GLIBC_PRIVATE not defined in file libpthread.so.0 with link time reference')
<rekado>never mind. I just fixed it after realising that I screwed up my PYTHONPATH...
<rekado>I should not be using ~ in the environment variable; using $HOME instead.
<rekado>BTW: I find myself adding the following snippets to many non-trivial Python applications:
<rekado>import site,sys\\nfor path in [path for path in sys.path if 'site-packages' in path]: site.addsitedir(path)
<rekado>This hack goes through every path in PYTHONPATH and adds each directory as a "site".
<rekado>This causes the *.pth file to be interpreted, resulting in more required paths to be added to the PYTHONPATH.
<rekado>I found that I need this for my offlineimap script which uses python2-gnomekeyring (packaged, but not yet submitted to the ML); I also need it for Solfege which uses pygtk.
<rekado>Both pygtk and python2-gnomekeyring have in common that their code is in a subdir of the site-packages directory, requiring a pth file.
<rekado>I suspect that Gimp with Python scripting enabled will also require this hack as it depends on pygtk.
<rekado>Currently, I'm patching the first Python file I encounter, but I feel that we may need a more general wrapper mechanism around Python rather than hacking up each application using pygtk or similar.
<Sleep_Walker>hackers, how is it possible, that you don't have packaged cscope yet?
<rekado>guess I should just install them to my profile.
<taylanub>can I query *why* a store object has another as a requisite? running ldd on all s2tc-installed ELF files, I don't see any of them link to anything in the mesa package, yet the mesa package becames a requisite of s2tc as per 'guix gc -R'
<rekado>propagated inputs from an input of s2tc maybe?
<taylanub>nope, mesa is the only input to s2tc ("mesa-without-s2tc" to be precise, which I just added)
<mark_weaver>rekado: I've also wanted a way to run 'guix gc' without removing anything I would need to build things locally.
<mark_weaver>I realize that what I want is to compute the set of derivations that would need to be built in order to build every package in guix (or maybe some subset that I specify), and then protect all of those from GC.
<civodul>mark_weaver: i think "guix-daemon --gc-keep-outputs --gc-keep-derivations" does what you want