On Wed, May 17, 2017 at 01:46:16PM -0400, myglc2 wrote:
> ISTM these can be addressed ...
>
> - behind: save everything hydra builds, or at least the last few
> installation images. Can't we just accomplish this by never doing
> "guix gc" on hydra?
We need more storage!
> - new-commit: Here
On Wed, May 17, 2017 at 04:17:18PM +0200, Marius Bakke wrote:
> Marius Bakke writes:
>
> > Leo Famulari writes:
> >
> > [...]
> >
> >> In gnu/packages/mes.scm:
> >> 79: 1 [native-inputs]
> >> In unknown file:
> >>?: 0 [string-prefix? #f "x86_64-linux" ...]
> >>
> >> ERROR: In procedure str
On Wed, May 17, 2017 at 02:38:13PM +0200, Ludovic Courtès wrote:
> Hi Leo,
>
> Leo Famulari skribis:
>
> > From 1c9ad17ea0b64b29117e49526ff07d2e7e7c6c13 Mon Sep 17 00:00:00 2001
> > From: Leo Famulari
> > Date: Sat, 13 May 2017 20:44:36 -0400
> > Subject: [v2] maint: The 'release' target builds
On 05/17/2017 at 14:45 Ludovic Courtès writes:
> Ricardo Wurmus skribis:
>
>> I think that a first step towards improving the experience with “guix
>> pull” is to build Guix continuously on Hydra and tell “guix pull” to
>> download that. Users would no longer have to wait for compilation on
>> t
Oops, sent before done, please see corrections ...
On 05/17/2017 at 12:06 myglc2 writes:
> On 05/16/2017 at 17:55 Ricardo Wurmus writes:
>
>> myglc2 writes:
>>
>>> I believe there will be many guix "users" that want to run from git
>>> checkout. They just may not know it, yet. They will want it
On 05/16/2017 at 17:55 Ricardo Wurmus writes:
> myglc2 writes:
>
>> I believe there will be many guix "users" that want to run from git
>> checkout. They just may not know it, yet. They will want it not just
>> because they are trying to get around the limitations of git pull. For
>> example, ev
The warning/error shown below sounds alarming but seems to be
harmless. But it leaves me wondering, is there a way to fix it?
TIA - George
root@g1 ~/con/4# guix system --fallback --cores=4 --max-jobs=4
reconfigure sys.scm
[...]
activating system...
;;; WARNING: loading compiled file
/gnu/store/z
Marius Bakke writes:
> Leo Famulari writes:
>
> [...]
>
>> In gnu/packages/mes.scm:
>> 79: 1 [native-inputs]
>> In unknown file:
>>?: 0 [string-prefix? #f "x86_64-linux" ...]
>>
>> ERROR: In procedure string-prefix?:
>> ERROR: In procedure string-prefix?: Wrong type argument in position 1
Leo Famulari writes:
[...]
> In gnu/packages/mes.scm:
> 79: 1 [native-inputs]
> In unknown file:
>?: 0 [string-prefix? #f "x86_64-linux" ...]
>
> ERROR: In procedure string-prefix?:
> ERROR: In procedure string-prefix?: Wrong type argument in position 1
> (expecting string): #f
This seem
On Wed, May 17, 2017 at 03:04:28PM +0200, Pjotr Prins wrote:
> Absolutely! Japper is on. Git service is another.
Japper is the new jabber ;)
--
On Wed, May 17, 2017 at 02:26:20PM +0200, Cl??ment Lassieur wrote:
> Thanks for working on this, I like the idea, and I have always wanted to
> do something similar.
Yes, I am surprised so few people here run their own :)
> I don't understand how your server can run phases 1 to 3, since Postfix
>
Hi Ricardo,
Ricardo Wurmus skribis:
> I have built shepherd with guile-2.2, but I noticed a couple of
> warnings/errors during the build:
I’m pretty sure those warnings are due to IOFBF and friends. They’ll
haunt us for years to come. :-)
(But you can happily ignore them.)
> And lastly: sh
Maxim Cournoyer skribis:
> ng0 writes:
[...]
>> + (list (shepherd-service
>> + (documentation "Run the gopherd geomyidae")
>> + (provision '(geomyidae))
>> + (requirement '(user-processes loopback networking))
>> + (start #~(make-forkex
Pjotr Prins skribis:
> On Tue, May 16, 2017 at 08:29:17AM +0200, Pjotr Prins wrote:
>> On a recent guix-publish server I get many of these
>>
>> gzip: stdin: invalid compressed data--format violated
>> r-annotationdbi-1.36.0
>> 1.7MiB/s 00:02 | 3.0MiB transferredguix substitute: error:
Ricardo Wurmus skribis:
> I think that a first step towards improving the experience with “guix
> pull” is to build Guix continuously on Hydra and tell “guix pull” to
> download that. Users would no longer have to wait for compilation on
> their local machines, removing a big incentive to go wit
Leo Famulari skribis:
> On Mon, May 15, 2017 at 10:12:01AM +, ng0 wrote:
>> Since the switch to Guile 2.2 and guix pull taking much more
>> computing time and resources, all my virtual hosting servers
>> time out when I run guix pull on them without using mosh
>> and just openssh, because the
Hi Leo,
Leo Famulari skribis:
> From 1c9ad17ea0b64b29117e49526ff07d2e7e7c6c13 Mon Sep 17 00:00:00 2001
> From: Leo Famulari
> Date: Sat, 13 May 2017 20:44:36 -0400
> Subject: [v2] maint: The 'release' target builds a VM image.
>
> * Makefile.am (GUIXSD_VM_SYSTEMS, GUIXSD_VM_IMAGE_BASE,
> GUIXSD
Hi Pjotr,
Thanks for working on this, I like the idea, and I have always wanted to
do something similar.
Pjotr Prins writes:
> Plan for a secure E-mail server
>
> The idea is to have a secure setup which can be replicated fast and
> parameterized - i.e., there will be installation options. We'l
Plan for a secure E-mail server
The idea is to have a secure setup which can be replicated fast and
parameterized - i.e., there will be installation options. We'll
develop this so anyone can fire up a VPS instance and get a secure
communications environment - especially when people are on one host
hydra-eval-guile-jobs returned exit code 1:
[...]
Backtrace:
In ice-9/eval.scm:
432: 19 [eval # #]
In unknown file:
?: 18 [call-with-input-string "(apply (module-ref (resolve-interface
'(hydra-eval-guile-jobs)) 'eval-guile-jobs) (cdr (command-line)))" ...]
In ice-9/command-line.scm:
181: 17 [
Hello!
Leo Famulari skribis:
> On Tue, May 16, 2017 at 07:51:36PM -0500, sirgazil wrote:
>> On 16/05/17 13:19, Leo Famulari wrote:
>> > Although, I am wondering why 'installer.svg' seems specific to the VM
>> > image now. The VM image is not an installer.
>> Hi Leo :)
>>
>> I don't know if I un
Hi Alex,
Alex Kost skribis:
> This is almost the same message as:
>
> http://lists.gnu.org/archive/html/guix-devel/2016-09/msg01570.html
>
> I mean this is a reminder on the subject.
Yes, I haven’t forgotten about it, contrary to what one might think.
;-)
> Ludovic, I think you suggested a g
On Sun, May 14, 2017 at 11:32:06PM +0200, Ludovic Court??s wrote:
> For Guix developers, I think it???s reasonable to have a traditional GNU
> build system. After all, Guix is also a regular software package that
> people can build from source with ???./configure && make && make install???.
This
On Mon, May 15, 2017 at 03:28:58PM +0200, Ludovic Court??s wrote:
> >> For Guix developers, I think it's reasonable to have a traditional GNU
> >> build system. After all, Guix is also a regular software package that
> >> people can build from source with './configure && make && make install'.
> >
On Tue, May 16, 2017 at 08:29:17AM +0200, Pjotr Prins wrote:
> On a recent guix-publish server I get many of these
>
> gzip: stdin: invalid compressed data--format violated
> r-annotationdbi-1.36.0
> 1.7MiB/s 00:02 | 3.0MiB transferredguix substitute: error: corrupt
> input while resto
25 matches
Mail list logo
