<cbaines>Does anyone know of any attempts to do data processing using Guix? I've been thinking about doing processing of database dumps, perhaps with intermediate stages involving starting PostgreSQL, loading in some data, doing some transformations, and dumping it back out again.
<lfam>cbaines: Yes, I think so. Try searching the guix-devel archives for 'pipeline' and 'workflow management'.
<detrout>lfam: the downside is you somehow need to get apt-transport-tor
<ng0>lfam: I've been a bit out of the loop since I stopped using gentoo. iirc they switched to git to syncing. but previously (and maybe still). it's believed to not be necessary to have default signed tree updates, this was an very optional and hidden item (though in the handbook), but the priority wasn't so high. a very small minority of the gentoo mirrors offers https. that's all I remember right now
<lfam>detrout: Well, it probably doesn't make a big difference either way. I doubt these bugs are first discovered by those who disclose them.
<lfam>The libarchive / FreeBSD bug analyses were leaked anonymously.
<ng0>to add a native tor option to the layman application (for gentoo-overlays) was welcome, but the idea came from our side and as soon as I got the clearnet thing in, we just dropped the idea of investing any effort into that application
<lfam>I haven't looked, but I presume that the difference between `sha256 | base32` and `guix hash` is that `guix hash` gives the base32 representation of the "raw" hash, before it's encoded as a hex string.
<geemili>lfam: Oh, I just reread what you said about the license. I didn't know that. I'm staying up to late. >.<
<geemili>It says that the source code hasn't been released under an open source license
<lfam>The client source code is available for users to inspect and compile (no binaries are provided), and several components are free software, but the license is not a free software license. The license only allows the user to use the software with the Tarsnap service.
<lfam>geemili: Basically, put it ("bash" ,bash) in the (inputs) field of your package definition. Most packages have some inputs, so you should be able to refer to them. Make sure to import the correct module, which is (gnu packages bash)
<sneek>roelj, efraim says: you can work around the auto-offload problem with the --no-build-hook flag
<sneek>roelj, rekado says: Your problem seems to be that you build Guix in “guix environment guix”, which contains “guile-ssh”. Offloading is enabled when GuileSSH is found at build time. When you run Guix later, however, you do not seem to have GuileSSH available, which results in an error. To fix this: 1) remove guile-ssh from the environment in which you build Guix, or 2) install GuileSSH, or 3) pass “--no-build-hook”
<roelj>efraim: rekado_: Thanks! I will try the --no-build-hook when the current builds succeed.
<Petter>I need a Guix revision, because we have a checkout after the release. So, if "cutoff" is something to keep, it would be "1.0-cutoff-1.<commit>"?
<roelj>Petter: Usually we try to avoid specific commits. Can you pursuade the author to make a new release?
<Petter>I'm following the Syncthing manifest, and they use this one specific commit (for some reason) of a library. I think we'll see this regularly with Go projects, so I think we better deal with it.
<roelj>Ok. In that case, maybe avoid using the version at all and use the commit ID instead.
***piyo` is now known as piyo
<Petter>Yeah, that's an idea. I've used "release-revision.commit" numerous times already though, so to be consistent I should either do it one way or the other.
<Petter>For libraries with no releas at all I've used "yyyymmdd.commit".
<lfam>Okay. The basic idea is clone our Git repo and build it. You will a file 'pre-inst-env' in the root of the source code repo. Prefix your Guix commands with `./pre-inst-env` to use the Guix you've built from source.
<lfam>To try the Rust patches, apply them to your Git tree and rebuild
<lfam>See the manual, section 8 Contributing for more detailed instructions on building Guix
<lfam>Make sure to read the note about setting localstatedir properly in section 8.1
<lfam>Please let us know if you have more questions :)
<lfam>"You will a file 'pre-inst-env' in the root of the source code repo."
<kahiru>hey, I'm trying to get guix working on my arch installations and all attempts to install any package end with ERROR: In procedure getaddrinfo: Name or service not known. I tried starting nscd (as suggested somewhere) but it didn't help at all. Any ideas what might be the cause?
<cbaines>This is the target of the broken symlink: '/gnu/store/c7kr9pdni867k2778pykh16sw003kl1s-nss-certs-3.27.2/etc/ssl/certs/AC_Ra??z_Certic??mara_S.A.:126.96.36.199.188.8.131.52.184.108.40.206.220.127.116.11.12.pem'
<davexunit>sorry everyone, but functional package management doesn't work except for simple libraries.
<cbaines>At the Guix level, I'm seeing errors of the form ERROR: Throw to key `gnutls-error' with args `(#<gnutls-error-enum Error while reading file.> set-certificate-credentials-x509-trust-file!)'.
<cbaines>Which is I think when it tries to read the broken symlink
<lfam>I pushed the NSS update about 3 hours ago. Did you see that issue before then?
<cbaines>I don't think so, but I haven't managed to track down exactly what I did to introduce it, as I think I have a bug in the way I'm isolating Guix for my projects, as the Guix checkout that I'm using for this project doesn't include that commit
<lfam>Okay, I'll try to reproduce the issue on GuixSD. I didn't notice it on my Debian system
<lfam>Yes, I recommend first testing your development setup with the code on the master branch
<lfam>geemili: From commit 27fab2bf659 (gnu: python-cryptography: Update to 1.7.1.), I used `guix environment guix` to set up a Guix development environment. Then I did `./bootstrap && ./configure --localstatedir=/var && make && ./pre-inst-env guix build hello`. That works for me on GuixSD
<ng0>I'd say I can finish 0ad when I have cut my roadmaps into pieces where I'll also allow myself flexibility. right now I feel like the only thing the 0ad package needs is the build-time symlink, but you need time to work on it because the data is big
<ng0>I started working on some film company software, lightning etc but then I thought I have other things to spent my time on, if companies want this, they can pay someone to package it.. I should post the minimal progress I made there