On Thu, Jan 15, 2015 at 11:22 AM, Ludovic Courtès wrote:
> "Thompson, David" skribis:
>
>> On Thu, Jan 15, 2015 at 4:51 AM, Ludovic Courtès wrote:
>>> (web server http) does not use threads so it should be OK. But we’ll
>>> see that afterwards. :-)
>>
>> Ah, okay. Even so, requiring a single-
"Thompson, David" skribis:
> On Thu, Jan 15, 2015 at 4:51 AM, Ludovic Courtès wrote:
>> David Thompson skribis:
>>
>>> Despite that, I tried to compress the nar with bzip2 just for fun, but I
>>> ran into another problem:
>>>
>>> warning: call to primitive-fork while multiple threads are runn
On Thu, Jan 15, 2015 at 4:51 AM, Ludovic Courtès wrote:
> David Thompson skribis:
>
>> Despite that, I tried to compress the nar with bzip2 just for fun, but I
>> ran into another problem:
>>
>> warning: call to primitive-fork while multiple threads are running;
>>further behavior u
David Thompson skribis:
> Ludovic Courtès writes:
[...]
>> 2. strace the substituter and/or ‘guix publish’ to see exactly what
>> happens on the wire. Is the end-of-file marker string sent? Is it
>> received? etc.
>
> Here's a snippet of the strace output:
>
>
> http://192.16
Back at this again after awhile.
Ludovic Courtès writes:
> Hmm, some ideas of things to try:
>
> 1. Add (force-output port) after (write-file ...).
No effect.
> 2. Display the value of ‘x’ in ‘restore-file’ at the point where the
> exception is raised.
Haven't tried this yet.
> 2.
David Thompson skribis:
> Ludovic Courtès writes:
>
>> To produce that, use ‘write-file’ from (guix serialization):
>>
>> --8<---cut here---start->8---
>> $ ./pre-inst-env guile -c '(use-modules (guix serialization)) (write-file
>> "/gnu/store/wy70n5zk8qinxjz
Ludovic Courtès writes:
> To produce that, use ‘write-file’ from (guix serialization):
>
> --8<---cut here---start->8---
> $ ./pre-inst-env guile -c '(use-modules (guix serialization)) (write-file
> "/gnu/store/wy70n5zk8qinxjz0wdk9q2hh1zjfb32j-miscfiles-1.5"
"Thompson, David" skribis:
> On Mon, Dec 15, 2014 at 12:19 PM, Ludovic Courtès wrote:
>> I think this is due to a subtly misleading file format variation.
>>
>> If you look at ‘export-paths’, it does:
>>
>> while there are files to write
>> write-long-long 1
>> export-path file
>> wr
On Mon, Dec 15, 2014 at 4:20 PM, Ludovic Courtès wrote:
> "Thompson, David" skribis:
>
>> On Mon, Dec 15, 2014 at 12:19 PM, Ludovic Courtès wrote:
>>> I think this is due to a subtly misleading file format variation.
>>>
>>> If you look at ‘export-paths’, it does:
>>>
>>> while there are files
On Mon, Dec 15, 2014 at 12:19 PM, Ludovic Courtès wrote:
> I think this is due to a subtly misleading file format variation.
>
> If you look at ‘export-paths’, it does:
>
> while there are files to write
> write-long-long 1
> export-path file
> write-long-long 0
>
> ‘restore-file-set’
I think this is due to a subtly misleading file format variation.
If you look at ‘export-paths’, it does:
while there are files to write
write-long-long 1
export-path file
write-long-long 0
‘restore-file-set’ does the opposite, which is to read that long-long to
determine whether the
David Thompson writes:
> The output of the following code in the context of the
> (guix serialization) module is "\r", it should be "nix-archive-1":
>
> (with-input-from-file "some-nar-file"
> (lambda ()
> (read-string (current-input-port
Also, note that the following code *does*
Hello everyone,
While working on a new guix command, called 'guix publish', I've run
into a snag. The archives I've exported via export-paths in the (guix
store) module are rejected by 'guix substitute-binary' due to the nar
signature being invalid. The signature is a string containing
"nix-arch
13 matches
Mail list logo
