-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/03/2014 04:35, Mark H Weaver wrote:
Pierre-Antoine Rault p...@rigelk.eu writes:
On 10/03/2014 22:09, Ludovic Courtès wrote:
The initial discussion [0] left open the question of where
binaries themselves should be stored. A possibility
Pierre-Antoine Rault p...@rigelk.eu skribis:
On 10/03/2014 21:56, Ludovic Courtès wrote:
I’ve applied a stripped-down version of the patch: I ended up
removing “Packaging 101” because it was redundant with the
“Packaging Guidelines” section of the manual, so I moved the
missing bits in that
Apologies for the sloppy reporting. Let me explain why it’s the case.
I ran ‘make check’ multiple times. These tests failed when I cloned the
repo and ran ‘make check’ for the first time: tests/derivations.scm,
tests/store.scm, tests/guix-build.sh, tests/guix-register.sh. These
ones failed
I think the current docstring of ‘assert-valid-signature’ is not correct
since ‘signature’ must be a string (as produced by
‘canonical-sexp-string’), not an sexp.
In guix/nar.scm, the comment is:
(define (assert-valid-signature signature hash file)
;; Bail out if SIGNATURE, an sexp,
Hello Guix , Hello Hurd
Most of you already know me from the irc ,lurking around as phant0mas and
that I am working towards porting Guix to GNU/Hurd.
In order to be able to do that I have already packaged mach headers ,hurd
headers and mig and I am currently working on packaging and
Nikita Karetnikov nik...@karetnikov.org skribis:
Which log files would you like to see?
The SRFI-64 $top_builddir/*.log files, and $top_builddir/test-suite.log.
The topological sort issue is normally solved by 58cbbe4.
Ludo’.
Mark H Weaver m...@netris.org skribis:
In recent weeks on my system, it has become fairly common for the daemon
to get into a bad state, where all build attempts fail with messages
like this:
mhw:~/guix-core-updates$ ./pre-inst-env guix build -n emacs
error (ignored): aborting transaction:
Hello!
Manolis Ragkousis manolis...@gmail.com skribis:
Here is a simple roadmap explaing what is there to be done.
1) Successfully cross-build the hurd's glibc
2) Make the appropriate changes to cross-base.scm so the toolchain will
use the new glibc when hurd is targeted with guix build
Cross-refs and a small glossary would help a lot to start with Guix. However, I
was thinking about an explanation of folders, sub folders and main files as
seen in the GNUnet manual [1].
[1] https://gnunet.org/book/export/html/37
Of course, these are just ideas to help brainstrom :)
- rigelk
Pierre-Antoine Rault p...@rigelk.eu skribis:
On 10/03/2014 22:09, Ludovic Courtès wrote:
[...]
The initial discussion [0] left open the question of where
binaries themselves should be stored. A possibility would be to
use GNUnet’s DHT simply as a discovery mechanism, and then to
establish
Pierre-Antoine Rault p...@rigelk.eu skribis:
Cross-refs and a small glossary would help a lot to start with Guix. However,
I was thinking about an explanation of folders, sub folders and main files as
seen in the GNUnet manual [1].
[1] https://gnunet.org/book/export/html/37
Sure. Again
On 03/11/2014 12:19 AM, Pierre-Antoine Rault wrote:
The initial discussion [0] left open the question of where
binaries themselves should be stored. A possibility would be to
use GNUnet’s DHT simply as a discovery mechanism, and then to
establish a connection directly to the user’s machine,
Pierre-Antoine Rault p...@rigelk.eu writes:
On 11/03/2014 04:35, Mark H Weaver wrote:
FWIW, I think it might be worthwhile to support BitTorrent magnet
links as well, as a middle ground between these two extremes. Most
users will not be able to host binaries via HTTP; even if they have
a
13 matches
Mail list logo
