On Mon, Aug 24, 2020 at 04:36:22PM +0200, Ludovic Courtès wrote:
> Hi!
>
> Justus Winter skribis:
>
> > Ludovic Courtès writes:
>
> [...]
>
> We can introduce signature verification in (guix download): every time
> code is downloaded and signature metadata is available, we verify its
> signat
Hello, Mark,
On Aug 25, 2020, Mark H Weaver wrote:
> Alexandre Oliva wrote:
>> On Aug 15, 2020, Mark H Weaver wrote:
>>
>>> If I were to implement this, what would you suggest I do if the patches
>>> fail to apply
>>
>> Look at the conflict presented by the rebase, and resolve the likely
>>
Hey,
> Yeah, this is a ridiculous situation. We should do a hackathon to get
> better monitoring of useful metrics (machine load,
> time-of-push-to-time-to-build-completion, etc.), to clearly identify the
> bottlenecks (crashes? inefficient protocol? scheduling issues? Cuirass
> or offload or g
Mathieu Othacehe writes:
> As most of the issues are only observed on Berlin machines, which access is
> restricted, we will also have to find a way to reproduce them locally.
You can access all Berlin build nodes from the head node at
ci.guix.gnu.org, either as “root” or “hydra” (both with ro
Hi,
I have started handling major updates of linux-libre for Guix, starting
with version 5.7 (collaborators are invited!).
I didn't read this discussion because it's quite long and I don't
perceive that anything needs to change with how we package linux-libre.
It has worked well for several years
On Tue, Aug 25, 2020 at 05:01:07PM -0400, Leo Famulari wrote:
> If there are concrete problems to report or changes to request, please
> let us know by opening a bug ticket at , or by sending
> a patch to .
I'd like to explain more clearly what I meant by my last message.
First, it's important to
