GNU bug report logs - #70915
Request for merging "tex-team" branch

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 70915 in the body.
You can then email your comments to 70915 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Nicolas Goaziou <mail <at> nicolasgoaziou.fr>
To: guix-patches <at> gnu.org
Subject: Request for merging "tex-team" branch
Date: Mon, 13 May 2024 11:00:48 +0200

Hello,

The "tex-team" branch contains import fixes and improvements for Guix
modular TeX Live distribution. In particular, it solves the important
slowdown experienced when compiling documents, and vastly improves
modularity wrt to binaries.

Regards,
-- 
Nicolas Goaziou

Message #8 received at 70915 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: 70915 <at> debbugs.gnu.org
Cc: Christopher Baines <mail <at> cbaines.net>
Subject: Closing this bug for now?
Date: Fri, 21 Jun 2024 14:47:41 +0200

Hello Nicolas,

there are a lot of commits still being added to the top of this branch.
As I understand it, this causes it to be repeatedly evaluated and built
by QA, resulting in a waste of build power.

Should we close this bug for now until the branch has reached its final
shape for the next merge? Or maybe keep it in its current shape until it
is merged and only then add new commits?

Andreas

Message #11 received at 70915 <at> debbugs.gnu.org (full text, mbox):

From: Nicolas Goaziou <mail <at> nicolasgoaziou.fr>
To: Andreas Enge <andreas <at> enge.fr>
Cc: 70915 <at> debbugs.gnu.org, Christopher Baines <mail <at> cbaines.net>
Subject: Re: [bug#70915] Closing this bug for now?
Date: Fri, 21 Jun 2024 22:07:11 +0200

Hello,

Andreas Enge <andreas <at> enge.fr> writes:

> there are a lot of commits still being added to the top of this branch.
> As I understand it, this causes it to be repeatedly evaluated and built
> by QA, resulting in a waste of build power.

I'm sorry that my work wastes (!) build power.

About a month ago, the branch was already ready to be merged, but it
never[¹] got the chance to be allocated the few CPU cycles necessary to
start building something. I doubt it did waste anything because I hardly
got any feedback from QA since the request for merging was issued.

As the situation wasn't moving, I resumed my work on the branch. There
are some more commits to come, indeed, but I expect the last steps to be
done in the following days.

> Should we close this bug for now until the branch has reached its final
> shape for the next merge? Or maybe keep it in its current shape until it
> is merged and only then add new commits?

If your suggestion means the branch will have to wait more months before
being merged, I dislike it. The branch will be ready in a few days. What
is done with this branch does not belong to me.

Regards,

[¹] Actually, it happened once, but for some reason, builds stopped.

-- 
Nicolas Goaziou

Message #14 received at 70915 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: Nicolas Goaziou <mail <at> nicolasgoaziou.fr>
Cc: 70915 <at> debbugs.gnu.org, Christopher Baines <mail <at> cbaines.net>
Subject: Re: [bug#70915] Closing this bug for now?
Date: Fri, 21 Jun 2024 22:20:09 +0200

Am Fri, Jun 21, 2024 at 10:07:11PM +0200 schrieb Nicolas Goaziou:
> About a month ago, the branch was already ready to be merged, but it
> never[¹] got the chance to be allocated the few CPU cycles necessary to
> start building something. I doubt it did waste anything because I hardly
> got any feedback from QA since the request for merging was issued.

Well, it probably was never fully built, but it did start. I have seen
packages of the tex-team branch being compiled in the past few days.
The revisions corresponding to several commits were evaluated also.

> > Should we close this bug for now until the branch has reached its final
> > shape for the next merge? Or maybe keep it in its current shape until it
> > is merged and only then add new commits?
> If your suggestion means the branch will have to wait more months before
> being merged, I dislike it. The branch will be ready in a few days. What
> is done with this branch does not belong to me.

I suppose we can manually change the priorities of the branch merge
requests, but do not know how to do so myself.

If we do not close this bug, maybe it would be good to not push more
commits to the branch on the server until your work is finished; I am
quite certain that QA works on evaluating intermediate commits.

Andreas

Message #17 received at 70915 <at> debbugs.gnu.org (full text, mbox):

From: Nicolas Goaziou <mail <at> nicolasgoaziou.fr>
To: Andreas Enge <andreas <at> enge.fr>
Cc: 70915 <at> debbugs.gnu.org, Christopher Baines <mail <at> cbaines.net>
Subject: Re: [bug#70915] Closing this bug for now?
Date: Fri, 21 Jun 2024 23:31:28 +0200

Hello,

Andreas Enge <andreas <at> enge.fr> writes:

> Well, it probably was never fully built, but it did start. I have seen
> packages of the tex-team branch being compiled in the past few days.

I doubt it, for some value of "the past few days". "core-updates" did
build some TeX Live packages. Meanwhile, "tex-team" branch was sitting
on top of a commit QA never managed to handle.

Regards,
-- 
Nicolas Goaziou

Message #20 received at 70915 <at> debbugs.gnu.org (full text, mbox):

From: Nicolas Goaziou <mail <at> nicolasgoaziou.fr>
To: Andreas Enge <andreas <at> enge.fr>
Cc: 70915 <at> debbugs.gnu.org, Christopher Baines <mail <at> cbaines.net>
Subject: Re: [bug#70915] Closing this bug for now?
Date: Tue, 25 Jun 2024 00:35:48 +0200

Hello,

Andreas Enge <andreas <at> enge.fr> writes:

> If we do not close this bug, maybe it would be good to not push more
> commits to the branch on the server until your work is finished; I am
> quite certain that QA works onn evaluating intermediate commits.

For the record, the "tex-team" branch is now feature-complete.
I refreshed the branch one last time.

I now wait for bordeaux to start building those packages so I can fix
issues that may (will?) arise. Since this will happen after
"core-updates" merge, it may be necessary to rebase "tex-team" on top of
master at that time, or the expected feedback may be biased.

Regards,
-- 
Nicolas Goaziou

Message #25 received at 70915-done <at> debbugs.gnu.org (full text, mbox):

From: Nicolas Goaziou <mail <at> nicolasgoaziou.fr>
To: 70915-done <at> debbugs.gnu.org
Cc: Andreas Enge <andreas <at> enge.fr>, Nicolas Goaziou <mail <at> nicolasgoaziou.fr>
Subject: Re: Request for merging "tex-team" branch
Date: Fri, 06 Sep 2024 15:28:55 +0200

Hello,

Closing this report since the branch was merged along with latest core-updates.

Regards,
-- 
Nicolas Goaziou

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.