<ng0>no, it's a .drv file, the one of guile-2.0.13
<ng0>I get the same error like in the paste I uploaded, on a different computer
<ng0>this is stupid. really... I'll just completely switch over to git everything.
<mekeor>wouldn't it be nice if %modify-phases had supported something like “#:patch (modify-phases %standard-phases (only 'patch-source-shebangs 'build))“ ? – or is there an already existing, nice alternative to specify just two specific phases out of e.g. the gnu-build-system's %standard-phases?
<mekeor>(“only” would be a new so called MOD-SPEC for modify-phases)
<mekeor>or is there some scheme foo so that i can delete all phases except two specific ones using the “delete” MOD-SPEC
<roelj>Is there a way I can see how much disk space is saved by using hard links?
<thomasd>catonano: I finally got round to testing gspell. I also get test failures when running the tests as normal user, but for different reasons: it seems gspell cannot find en_US language. Do you know how to provide that? (I have installed aspell-dict-en)
<catonano>thomasd: no I don't know how to provide that. Maybe it should be an input ? I donß t even know if locales are pacages or if they are something else
<rekado>roelj: do you mean the same info that “guix gc” prints out?
<thomasd>catonano: unfortunately gspell documentation hardly mentions the words “language” or “dictionary” :)
<thomasd>Also, I'm not sure it's related to locale. (actually, my current locale is en_US.UTF-8)
<catonano>thomasd: whhat about the X related error ? Is it gone ?
<thomasd>at least that tells me gspell can use aspell dictionaries
<ng0>Hi. I want a new requirement for service changes: Please write an announcement of what needs to be applied to the previous version of the service configuration. Sometime I don't have the time to debug and translate what guile throws at me
<ng0>but I think I will write something up for the documentation, as it would be really good to not just let people read the documentation but to provide help and info upfront
<ng0>aspell... fdamn. reminds me of the info I wanted to pass on how Jookia progressed and what needs to be done for *spell stuff
<civodul>ng0: re openssh-service, it could be a genuine mistake, perhaps you should report your error on the list?
<ng0>no it was no mistake. It was just that I was missing an item in cons* of services
<ng0>but I really think if a service changes in some way, an announcement email should be posted so that people understand what broke and how to fix it without having to read the documentation. okay, ideal case you read the documentation, but a public post helps to understand that it's not just some random mistake you made but some change which happened, so you can compile the documentation again and look at it
<ng0>(because online documentation is always outdated)
<ng0>I might disappear without notice, this laptop is bit buuggy
<ng0>I'm a bit frustrated right now by the pull issue.. I thought I spent maybe one or two days setting up a server for testing server related stuff, and another one or two days to set up the gnunet- (and later other) services testing+debugging machine, and now I might have to start again if I can't fix it today, only because bayfront doesn't time out in pull. There's a reason why bayfront isn't in the default set
<rekado>re R reproducibility: the easiest way to fix this is to *not* build the recommended packages as part of the “r” package, but to build them separately with “r-build-system” and then using a meta-package to install them along with R itself.
<rekado>We don’t have problems with rdb and rdx files in other R packages, so I think we can circumvent this issue like that.
<rekado>Debian also does not build the recommended packages, which explains why their package builds reproducibly.
<ng0>I'm on the server which does not use bayfront now. and I can now confirm that it only happens with bayfront. A timeout for guix pull is set either much too high or guix pull just picks one machine, but when this is not reachable, it does not try another one
<ng0>the bayfront including machine does just add bayfront in addition to the default-subsitutes addrsses
<ng0>guix package + guix system address all listed urls, guix pull just bayfront
<thomasd>rekado: thanks for the push. I don't have strong feelings about the order of fields :)
<ng0>I reconfigured the system to switch back to the default (mirror.hydra) only, and now the pull "issue" is gone. I'll open a bug for guix pull on this, it should definitely time out when a server is not reachable.
<civodul>the Cuirass hack that Mathieu O. posted is really cool
<roelj>ZombieChicken: Also, the store contains hard links, they caused problems for me when rsyncing to locations that did not support that. I usually did rsync --exclude=.links/ ... in such cases (note that at that point the store should become a read-only thing..)
<ZombieChicken>rekado: Do you know if there is a way to have lsyncd hold a set of changes until a process has completed? For example, to have lsyncd not make changes to the destination until a tar archive has been created of said destination?
<rekado>ZombieChicken: lsyncd has several configuration “layers”. I guess you could express something like that with the lowest layer and a custom syncer. But there’s nothing built-in that would help you AFAICT.
<ZombieChicken>Yeah, I didn't see anything either in the docs, but I thought I'd ask just in case you knew of something
<efraim>not unsuprising, my "smartcard" is unknown
<jmd>There are so many levels of software in a smartcard, it is unreal.
<efraim>i'm not sure how smart it is, its from the transit authority
<efraim>the best part is my real card fails to load correctly
<ng0>lfam: you were interested in the live-system thing, right? I'm working on more texts, explanations, motivations etc now, and also a website so that more people can get involved and can get a picture of our vision
<lfam>ng0: Yeah, I'm curious about the vision, and how you use Guix to make it a reality
<ng0>I'm not sure wether blends of projects are applicable for the Free system list, but once it's usable I'd like to try. that will involve some much more problem and keyboard punching before the project is getting there though.
<lfam>Generally, I'm interesting in custom systems based on Guix. I think there is a lot of potential
<ng0>the problem is currently too much multitasking… that's why more people need to get involved. more people for (working title pragmaOS) - more people upstreaming to Guix :)
<lfam>I don't think that human multitasking is possible, really. The context switch is way too expensive
<ng0>it hurts to have so many construction sites when you know that more people can achieve results more quickly by doing less.
<lfam>Specifically, it's ARMv7-a architecture, and a Cortex-A7 CPU. It has great support in Linux but it's rather slow, unfortunately.
<lfam>The specific implementation in the eoma68 has a lot of potential (gigabit ethernet, SATA), but eoma68 doesn't expose all the features.
<lfam>But eoma68's explanation of why they left them out makes sense, I think: "I chose to add a second USB2 port and the option to go all the way up to USB 3.1 which I think covers way more than GbE and SATA.
<lfam>So in the future (over the next ten years) we anticipate there being low-cost SoCs with USB 3.0 and USB 3.1 so you can connect multiple GbE and SATA ports, which would be awesome. "
<bavier`>I'm working on a clamav service, which has potentially two daemons that need to be run
<luser`>How do you guys manage to install packages via package.el without installing dependencies you already have? I have avy installed through guix (I'm on a guixsd system), yet another version of avy gets installed in ~/.emacs.d/elpa when a package requires it.
<civodul>note that it really solves your problem, but maybe it helps to know you're talking to a friendly person ;-)
<lfam>That's cool. I don't keep track of exactly who I deal with when I am reporting bugs to them. But I've had some interactions that felt very unfriendly. I guess they get a huge number of bug reports and are probably feeling drained as well.