Hello,
On Mon, Sep 03, 2018 at 01:37:54PM +0200, Ricardo Wurmus wrote:
> The first question is what ARM hardware to buy; the second is where to
> host that hardware. Here are some considerations:
concerning hosting, I could easily host one smaller machine (like the
Overdrive 1000) in my living
On Tue, Sep 11, 2018 at 11:01:08PM +0200, Pierre Neidhardt wrote:
> By the way, I could not rebase+push, upstream complains that I cannot push
> non-fast-forward commits and that I should pull first. How am I supposed to
> rebase my branch?
For wip-* branches [0], please delete the branch
Done.
By the way, I could not rebase+push, upstream complains that I cannot push
non-fast-forward commits and that I should pull first. How am I supposed to
rebase my branch?
--
Pierre Neidhardt
https://ambrevar.xyz/
signature.asc
Description: PGP signature
Hi Ricardo,
On Tue, 11 Sep 2018 13:52:16 +0200
Ricardo Wurmus wrote:
> The build logs are stored by the daemon. You can get their location by
> doing
>
> guix build --log-file something
Does this also work for failed builds - without rebuilding it again?
pgpJ9_EeqYaBB.pgp
Description:
Hi Gábor,
> I have a few questions/suggestions but I would like to get some feedback
> before implementing them. This changeset would rebuild all java, so it
> would be nice to get this right for the first time.
>
> 1. https://issues.guix.info/issue/30730 has a partial fix, icedtea-8 out
>
Hi Pierre,
> In fact, I think it's much better than
> https://www.gnu.org/software/guix/packages/. Could we use hpcguix-web on the
> official page too?
>
> As far as I remember, it's problematic because it's hosted on gnu.org. And
> there were talks about moving the website, right?
By default
Pierre Neidhardt transcribed 1.3K bytes:
>
> > Also, on build failure, it would be nice to print a hint on what to
> > invoke to get to the failed build log after all (guix-daemon still wrote
> > it).
>
> Indeed. Is there such a command?
>
> What about adding a hint, for instance:
>
>
Hi Pjotr,
> On latest
>
> ./pre-inst guix package -i something
>
> The new color scheme is nice for output. But I miss the old build
> logs. How do I get them back?
The build logs are stored by the daemon. You can get their location by
doing
guix build --log-file something
Note also
On Monday, 2018-09-10 14:27:02 CEST Ludovic Courtès wrote:
> Sure! While you’re trying things out, you may find that IRC will be
> better suited to get guidance and information on how to debug issues.
OK, noted.
> Yes. In short you would define the new package to “inherit” from
> ‘lua-5.1’, and
Thanks to both of you I can now at least get the configure script to run, but
it stops because it cannot find `cat`:
starting phase `configure'
building for Linux on localhost at Tue Sep 11 10:46:19 UTC 2018
looking for /bin/sh./configure: line 89: expr: command not found
(nope)
looking for
> Also, on build failure, it would be nice to print a hint on what to
> invoke to get to the failed build log after all (guix-daemon still wrote
> it).
Indeed. Is there such a command?
What about adding a hint, for instance:
Building
Hi!
This is fantastic news, thanks!
In fact, I think it's much better than
https://www.gnu.org/software/guix/packages/. Could we use hpcguix-web on the
official page too?
As far as I remember, it's problematic because it's hosted on gnu.org. And
there were talks about moving the website,
Hi Pjotr,
On Tue, 11 Sep 2018 11:04:25 +0200
Pjotr Prins wrote:
> Ah, the --verbose switch helps. Still I think the hash and -K should
> be displayed by default.
I agree.
Also, on build failure, it would be nice to print a hint on what to
invoke to get to the failed build log after all
Hi Ludo,
> Or am I missing something?
>
No, I don't think so. Everything is working again after your bug fix.
I have just needed to introduce a couple of concepts in order to use
the ./pre-inst-env commands in the git checkout. Firstly, I use a
development environment created by:
$ guix
Ah, the --verbose switch helps. Still I think the hash and -K should
be displayed by default.
On Tue, Sep 11, 2018 at 10:26:53AM +0200, Pjotr Prins wrote:
> On latest
>
> ./pre-inst guix package -i something
>
> The new color scheme is nice for output. But I miss the old build
> logs. How do
Le 2018-09-11 09:32, Gábor Boskovits a écrit :
Hello guix,
I have a few questions/suggestions but I would like to get some
feedback before implementing them. This changeset would rebuild all
java, so it would be nice to get this right for the first time.
1. https://issues.guix.info/issue/30730
On latest
./pre-inst guix package -i something
The new color scheme is nice for output. But I miss the old build
logs. How do I get them back? Trying different verbosity levels does
not help.
Also when I got the hash wrong I did not display the new hash value.
And -K does not show the tmp
Hello guix,
I have a few questions/suggestions but I would like to get some feedback
before implementing them. This changeset would rebuild all java, so it
would be nice to get this right for the first time.
1. https://issues.guix.info/issue/30730 has a partial fix, icedtea-8 out
output is
18 matches
Mail list logo
