Re: wip-ungrafting builds stuck

2021-04-30 Thread Leo Famulari
On Fri, Apr 30, 2021 at 06:32:54PM +0200, Ludovic Courtès wrote: > I’ve just merged ‘wip-ungrafting’ in master! It was at 76% according to > , with mostly ARM builds missing compared to > ‘master’. Now we have fresh binaries to download (or build)! Hooray! > Thanks Leo

Re: wip-ungrafting builds stuck

2021-04-30 Thread Ludovic Courtès
Hey there! I’ve just merged ‘wip-ungrafting’ in master! It was at 76% according to , with mostly ARM builds missing compared to ‘master’. Now we have fresh binaries to download (or build)! For the record, ‘wip-ungrafting’ was merged in ‘version-1.3.0’ a few days ago

Re: Why is glib still grafted on the 'wip-ungrafting' branch? (was Re: wip-ungrafting builds stuck)

2021-04-22 Thread Leo Famulari
On Thu, Apr 22, 2021 at 12:27:52PM -0400, Mark H Weaver wrote: > I don't understand why it's relevant how many patches are involved. It > sounds like if I had concatenated all of the CVE-2021-27219 patches into > a single file, you would have judged that as "simple", and therefore > ungrafted it,

Re: Why is glib still grafted on the 'wip-ungrafting' branch? (was Re: wip-ungrafting builds stuck)

2021-04-22 Thread Mark H Weaver
Hi Leo, Leo Famulari writes: > On Wed, Apr 21, 2021 at 04:47:06PM -0400, Mark H Weaver wrote: >> I just noticed that 'glib' is still grafted on the 'wip-ungrafting' >> branch. Was that intentional? >> >>

Re: Why is glib still grafted on the 'wip-ungrafting' branch? (was Re: wip-ungrafting builds stuck)

2021-04-21 Thread Leo Famulari
On Wed, Apr 21, 2021 at 04:47:06PM -0400, Mark H Weaver wrote: > I just noticed that 'glib' is still grafted on the 'wip-ungrafting' > branch. Was that intentional? > > https://git.sv.gnu.org/cgit/guix.git/tree/gnu/packages/glib.scm?h=wip-ungrafting=e12210dc92098d8581cea3007d57dbb6be16bb41#n171

Why is glib still grafted on the 'wip-ungrafting' branch? (was Re: wip-ungrafting builds stuck)

2021-04-21 Thread Mark H Weaver
I just noticed that 'glib' is still grafted on the 'wip-ungrafting' branch. Was that intentional? https://git.sv.gnu.org/cgit/guix.git/tree/gnu/packages/glib.scm?h=wip-ungrafting=e12210dc92098d8581cea3007d57dbb6be16bb41#n171 Mark

Re: wip-ungrafting builds stuck

2021-04-20 Thread Maxim Cournoyer
Hi, Mark H Weaver writes: > Mathieu Othacehe writes: > >>> Any idea what could be wrong, Mathieu? What would you suggest to do >>> when investigating such issues? >> >> Yes I noticed it. The main problem here is that almost all workers are >> stuck building Rust. >> >> I see two actions here:

Re: wip-ungrafting builds stuck

2021-04-18 Thread Mark H Weaver
Mathieu Othacehe writes: >> Any idea what could be wrong, Mathieu? What would you suggest to do >> when investigating such issues? > > Yes I noticed it. The main problem here is that almost all workers are > stuck building Rust. > > I see two actions here: > > 1. Understand why Rust is taking

Re: wip-ungrafting builds stuck

2021-04-18 Thread Mathieu Othacehe
Hello, > Any idea what could be wrong, Mathieu? What would you suggest to do > when investigating such issues? Yes I noticed it. The main problem here is that almost all workers are stuck building Rust. I see two actions here: 1. Understand why Rust is taking so long to build. 2. Implement

Re: wip-ungrafting builds stuck

2021-04-18 Thread Mathieu Othacehe
Hello, > Any idea what could be wrong, Mathieu? What would you suggest to do > when investigating such issues? Yes I noticed it. The main problem here is that almost all workers are stuck building Rust. I see two possible actions here. 1. Understand why Rust is taking so long to build. 2.

wip-ungrafting builds stuck

2021-04-18 Thread Ludovic Courtès
Hi! The ‘wip-ungrafting’ branch that Leo set up has been building for ~36h. It was at 26% 24h hours ago and it’s now stuck at 33%, even though all but two workers are idle. shows that many x86_64 builds are missing. Any idea what could be wrong,