Hi,
When using guix import crate flamer, it generates a pattern like
(arguments
`((#:cargo-inputs
(("rust-flame" ,rust-flame)
("rust-quote" ,rust-quote)
("rust-syn" ,rust-syn)
the correct pattern would however be
(arguments
`(#:cargo-inputs
Hey all! I'm really excited to say that there's a new episode of Libre
Lounge out (a podcast I co-host) and we interview Ludovic Courtès about
Guix! There's a lot of cool stuff in here, including some discussion
about reproducibily, Mes, etc.
Hello,
Andreas Enge writes:
> In this case, there is hope though, from SPKG.txt:
> "NOTE: the ratpoints package has been assimilated by PARI/GP. Therefore,
> this package (as Sage package) is deprecated. In the future, it will be
> removed from Sage."
>
> So maybe we could move it (again,
Tobias Geerinckx-Rice wrote:
(new nar field?)
Actually, that won't work, since NAR URLs are hash-based and we're
hardly interested in packages that do have substitutes available.
One'd have to grow another /api//build-times wart or
something.
Kind regards,
T G-R
signature.asc
Swedebugia, Guix,
I was about to answer on IRC when I saw this thread :-)
swedebugia wrote:
Maybe we could have an additional time measurement:
Ghzminutes. E.g. if the build took 60 minutes on a 3 Ghz machine
it
took 20 Ghzminutes.
The build node would have to communicate the total
Ghz
swedebugia transcribed 385 bytes:
> Hi
>
> On 2019-06-21 18:01, Andreas Enge wrote:
> > On Fri, Jun 21, 2019 at 05:43:54PM +0200, swedebugia wrote:
> > > Maybe we could have an additional time measurement:
> > > Ghzminutes.
> > > E.g. if the build took 60 minutes on a 3 Ghz machine it took 20
Hi,
(CCing guix-devel because I'm confused about this and more eyes can't
hurt)
On Sat, May 18, 2019 at 05:50:13AM +0200, Ricardo Wurmus wrote:
> Thanks for giving it a try. The build system works on “ins” files by
> default. I guess it should try “dtx” files as well.
Should this be a patch
Hi
On 2019-06-21 18:01, Andreas Enge wrote:
On Fri, Jun 21, 2019 at 05:43:54PM +0200, swedebugia wrote:
Maybe we could have an additional time measurement: Ghzminutes.
E.g. if the build took 60 minutes on a 3 Ghz machine it took 20 Ghzminutes.
180 GHzmin?
Yes, thanks for correcting me!
On Fri, Jun 21, 2019 at 05:43:54PM +0200, swedebugia wrote:
> Maybe we could have an additional time measurement: Ghzminutes.
> E.g. if the build took 60 minutes on a 3 Ghz machine it took 20 Ghzminutes.
180 GHzmin?
Andreas
Hi
I would like to estimate how long building the rust toolchain would take
on my 2-c 2.2 Ghz laptop.
I asked on irc and had an idea of improvement:
swedebugia: you can check the build duration for past builds
on ci.guix.gnu.org
most of the build nodes are pretty old and weak, though
Hello!
Ricardo Wurmus skribis:
> the search at ci.guix.gnu.org now recognizes ^ and $ to designate the
> beginning or end of a query. You can now also search for arbitrary
> build names (previously the query would always end on “-%”).
>
> Examples:
>
> ^r-3 system:aarch64-linux
> Show
Hello!
I’d just like to say that we should think not just in terms of a web
interface, but also in terms of an HTTP API + CLI/Emacs.
Things like ‘guix challenge’, ‘guix weather’, and build-farm.el are
pretty nice to me as a user, so I think we should keep an eye on how we
can make such tools
Hello!
Vagrant Cascadian skribis:
> On 2019-06-18, Ludovic Courtès wrote:
>> After seven years of service, the continuous integration service and
>> ‘guix publish’ service running at hydra.gnu.org, as well as its mirror
>> at mirror.hydra.gnu.org, are now discontinued.
>
> Curious how this will
13 matches
Mail list logo
