I just briefly looked into your code. Apparently you know how to build Go programs and you understand the Go infrastructure. Guix needs you. -- mekeor ~ EDD3 DFFA 76F6 11C0 145F 9A99 AC85 BAD8 A2F8 C
I was looking into how to write package definitions for go packages, and was searching for any work on a Go build system, and ran into this thread. I have done some work trying to write definitions f
Hi Fred, previous work focused on Gnunet. The project ended with initial Guile bindings for Gnunet, IIRC. There has been no work on IPFS. This seems like a good first step. A close second step could
There's also a discussion/open bug about finding a system for more regular tarball releases of gnunet builds. As you might or might not know, the release is equal to a certain revision in the svn of
Salut Vincent, <address@hidden> skribis: [...] I’m not completely sure and, as Jookia pointed out, the two projects share different goals, with GNUnet allowing for anonymous communications. I don
Hello! Our work last summer around sharing packages through a P2P network was tied to GNUnet’s architecture, but surely adaptable to any other system: as described last year on this mailing list, o
Ludovic Courtès schreef op do 20-05-2021 om 16:58 [+0200]: This concept LGTM (but I haven't looked closely at the patches), but as noted on #guix, some issues with eliminating labels completely: A p
Ludovic Courtès schreef op za 15-05-2021 om 19:47 [+0200]: Distributing substitutes over IPFS. The original patch series dates from 2018 <https://issues.guix.gnu.org/33899>. We now have an IPFS serv
We are pleased to announce the release of GNU Guix 1.3.0! This release corresponds to 8,300 commits over almost 6 months by 212 people. Support for the POWER9 platform is now offered as technological
My understanding is that, in case of an RCE in knot, the attacker can replace /var/lib/knot/* with symlinks to arbitrary files in the FS. When the activation procedure is run afterwards, the files be
Hi, I’m not sure I understand the threat model. If Knot has a RCE vulnerability, it can be exploited to run anything on behalf of the ‘knot’ user. At that point, all the state associated with K
On January 19 2021, we received a message from Maxime Devos describing a potential attack vector on Guix System. If an attacker can exploit a remote code execution vulnerability (RCE) in a program us
I'm not sure I think this is their git hub repo after a quick search, https://github.com/underlay,... might be worth looking at 'solid' mit project, Im not sure but I think it shares similar underlyi
Hi former mentor :) - sounds weird :/ I will tell them that we are still creating them, that we have a first version in kind of a beta phase. I don't know if they will know how to use ipfs. Or I coul
We always have trouble with my ipfs don't know why. But believe me that I am inside the container, just used my Makefile and copy/pasted my latest video subdir and everything worked properly. No diff
Pierre Neidhardt <address@hidden> skribis: Oh, we should really work towards unbundling things from ‘go-ipfs’. Any idea how difficult that would be? “guix size syncthing”, for instance, retur
Hi Ludo! OK, thanks for clarifying scanForReferences. go-ipfs is fine indeed, but that's because you've just looked at the lucky package! go-ipfs vendors all the Go dependencies, which is why there i
Hi Hartmut, Hartmut Goebel <address@hidden> skribis: Heck it would be ironic to find myself arguing in favor of centralized commercial services. So I won’t do that. :-) Clearly, I do understand the
IPFS would be great because it will allow anyone to lookup and share substitutes with a low barrier to entry and it allows for redundancy too. Unlike bittorrent it comes with a built in webinterface