Hi Ludovic,
l...@gnu.org (Ludovic Courtès) writes:
> Mark H Weaver skribis:
>
>> Furthermore, it will be important for a static code analyzer to be able
>> to infer that phases and snippets always return #t, so let's try not to
>> be too clever about it. We'll need a static analyzer to gain con
Hello, Ricardo!
Yes, I've taken a look at Hydra. I think my problem is that I don't totally
understand what means some pages at Hydra and how it is related to Cuirass
database tables. Hydra has Projects, Jobsets for each project, Evaluations
and Jobs for each Jobset. And Cuirass has Specifications
Hi Ricardo,
I have made necessary changes to ui, patch file is attached. Please
review changes and additionals to be added.
> to apply a different colour to different parts of the strings, e.g. using
> blue for
> the name of the build phase and green for the rest.
>
> You will need to use regula
Hello!
Ricardo Wurmus skribis:
> I think these are enough hints. I’d be happy if you could try to
> implement a bit more than a single “if” expression and send us your
> draft implementation within the next few days. If you have questions
> please feel free to ask for help on #guile or #guix.
Hello,
jerem...@pdp10.guru skribis:
> As running make clean breaks the bootstrap script.
Could you clarify what the problem is?
(Besides I agree with Mark that “make clean” should not delete files it
doesn’t know about.)
Ludo’.
Hello!
Ricardo Wurmus skribis:
> qtbase sometimes fails to build on core-updates. I now know that it
> only fails on Linux < 3.17, which is why I’ve seen the failure only on
> RHEL6 and RHEL7 systems with Linux 2.6.32 and 3.10, respectively.
Good catch!
> With the attached patch, qtbase build
Hello Mark,
Mark H Weaver skribis:
> Furthermore, it will be important for a static code analyzer to be able
> to infer that phases and snippets always return #t, so let's try not to
> be too clever about it. We'll need a static analyzer to gain confidence
> that we can start ignoring the retur
Hi Sahithi,
> I used /cond/ conditional and gave a try. This worked out with
> following line.[…]
Good.
Currently, you have always the same code that runs for any match.
Looking at my example you might be able to figure out how to apply a
different colour to different parts of the strings, e.g
Hello,
Pierre Neidhardt skribis:
> But now I get the following error:
>
> starting phase `validate-runpath'
> validating RUNPATH of 8 binaries in
> "/gnu/store/gh7rda7y5nfh7v5njlll45ckbm4aigmd-lvm2-2.02.177/lib"...
> /gnu/store/gh7rda7y5nfh7v5njlll45ckbm4aigmd-lvm2-2.02.177/lib/device-mapper/li
Hi, Leo
> From: "Leo Famulari"
> I've noticed several different dependency manifest formats for Go
> software "in the wild". So, this one is specific to Go software using
> the Gopkg tool?
Yes, Gopkg it's specific for Go software, it's not used by all Go
projects, but lot of big project use it.
Hi Ricardo,
I used /cond/ conditional and gave a try. This worked out with
following line.
I also included string-match which also worked.
All I need to look for next step is to use regular expressions instead
of string.
> You also see that “if” alone is not sufficient here, because you have
>
11 matches
Mail list logo
