> Check “strings /nix/store/qn*-glibc-intermediate-2.17/bin/sh | grep ld-linux”.
> Most likely that points to a loader that doesn’t exist.
It didn't output anything.
Nikita
pgpD7njqelsUp.pgp
Description: PGP signature
Hello,
the test suite of openssh fails as follows:
Privilege separation user sshd does not exist
FATAL: sshd_proxy broken
Apparently, the sshd daemon expects to be run by a user named sshd. Is
there a way to create such a user just during the test run?
Apart from that, I disabled the tests, an
Hello!
With commits a7b6ffe and bdcf35a, you should notice that ‘guix-build’
and similar are more than twice as fast as two days ago.
This was achieved by adding caches in the now obvious places, which
noticeably reduces the number of round trips and the amount of data sent
to the daemon.
Ludo’.
Am Dienstag, 29. Januar 2013 schrieb Ludovic Courtès:
> I finally installed Gobby, and it works beautifully!
>
> Perhaps if we type in using Org-mode “syntax” we can then use Org’s HTML
> export facility in the cron job. WDYT?
I do not know how to write it; is it difficult? How about recutils in
Nikita Karetnikov skribis:
>> The obvious thing to do here is to check whether that binary works
>> correctly. It’s supposed to be the statically-linked bootstrap Bash,
>> see base.scm.
>
> The files are there. But if I try
> '/nix/store/qn*-glibc-intermediate-2.17/bin/sh --help', I'll get 'No
> The obvious thing to do here is to check whether that binary works
> correctly. It’s supposed to be the statically-linked bootstrap Bash,
> see base.scm.
The files are there. But if I try
'/nix/store/qn*-glibc-intermediate-2.17/bin/sh --help', I'll get 'No
such file or directory'.
> This is t
Andreas Enge skribis:
> So I set up a gobby server. I do not know whether there are console based
> clients, but you can use the gtk program "gobby". Upon connecting, it
> allows to edit files, with contributions by different persons highlighted
> in different colours. And there is a little ch
Nikita Karetnikov skribis:
> starting phase `build'
> rm -f mksyntax
> make:
> /nix/store/qn9m4cjncna9mcac98fynialsv2l28jm-glibc-intermediate-2.17/bin/sh:
> Command not found
> make: *** [mksyntax] Error 127
The obvious thing to do here is to check whether that binary works
correctly. It’s su
Andreas Enge skribis:
> Am Samstag, 26. Januar 2013 schrieb Ludovic Courtès:
[...]
>> Did you check whether it does DNS lookups or similar?
>
> Not that I could tell and there is no reason for it, but the file has over
> 2000 lines. I ended up disabling two tests; the remaining tests pass,
>
Andreas Enge writes:
> Am Dienstag, 29. Januar 2013 schrieb Florian Friesdorf:
>> I think having version control and history is quite beneficial for
>> keeping track who closed what when.
>
> There is already the git for the project itself, and at some point in time,
> we might need a bug tracker
Am Samstag, 26. Januar 2013 schrieb Ludovic Courtès:
> So I would suggest adding Libtool/bin as an input, and adding a phase
> that does (copy-file (which "libtool") "libtool") right after
> ‘configure’.
Thanks for your help in implementing this!
> Did you check whether it does DNS lookups or sim
> Can you change that and try again?
It worked, but there is a new error:
[...]
starting phase `build'
rm -f mksyntax
make:
/nix/store/qn9m4cjncna9mcac98fynialsv2l28jm-glibc-intermediate-2.17/bin/sh:
Command not found
make: *** [mksyntax] Error 127
phase `build' failed after 0 seconds
builder
Am Dienstag, 29. Januar 2013 schrieb Ludovic Courtès:
> Cyril Roelandt skribis:
> > Is it possible to have a read-only access to the files ? It would be
> > nice for potential contributors to be able to read our TODO list.
>
> I agree that would be nice.
>
> If the tool doesn’t support it, perhap
Cyril Roelandt skribis:
> Is it possible to have a read-only access to the files ? It would be
> nice for potential contributors to be able to read our TODO list.
I agree that would be nice.
If the tool doesn’t support it, perhaps we could have a cron job that
periodically exports the file some
Am Dienstag, 29. Januar 2013 schrieb Florian Friesdorf:
> I think having version control and history is quite beneficial for
> keeping track who closed what when.
There is already the git for the project itself, and at some point in time,
we might need a bug tracker. Here it is more about intra p
15 matches
Mail list logo
