GNU bug report logs -
#75894
Request for merging "node-team" branch
Previous Next
Reported by: Jelle Licht <jlicht <at> fsfe.org>
Date: Mon, 27 Jan 2025 10:51:02 UTC
Severity: normal
Done: Andreas Enge <andreas <at> enge.fr>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 75894 in the body.
You can then email your comments to 75894 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
guix-patches <at> gnu.org
:
bug#75894
; Package
guix-patches
.
(Mon, 27 Jan 2025 10:51:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Jelle Licht <jlicht <at> fsfe.org>
:
New bug report received and forwarded. Copy sent to
guix-patches <at> gnu.org
.
(Mon, 27 Jan 2025 10:51:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Hi Guix,
The node-team branch contains the bump of node-lts to the 22.X.Y series,
and supporting changes that make this possible.
Since some of the leaf packages depending on node are quite important and hard to
build on underpowered hardware, I'd like to get the ball rolling this
way so we have some substitutes before merging this into master.
NB, there is no real node-team yet, but there might be soon enough :)
Thanks,
- Jelle
Information forwarded
to
guix-patches <at> gnu.org
:
bug#75894
; Package
guix-patches
.
(Mon, 24 Mar 2025 14:30:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 75894 <at> debbugs.gnu.org (full text, mbox):
Hi Jelle,
I still see node-team on QA, it should probably be javascript-team
now. Or is QA's node-team polling properly from javascript-team branch?
--
Best regards,
Nicolas Graves
Information forwarded
to
guix-patches <at> gnu.org
:
bug#75894
; Package
guix-patches
.
(Mon, 24 Mar 2025 21:27:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 75894 <at> debbugs.gnu.org (full text, mbox):
Hi!
Nicolas Graves <ngraves <at> ngraves.fr> writes:
> Hi Jelle,
>
> I still see node-team on QA, it should probably be javascript-team
> now. Or is QA's node-team polling properly from javascript-team branch?
Good catch! I'll look into it this weekend so we can start getting
everything we have now merged before the next Node.js LTS is released.
- Jelle
Information forwarded
to
guix-patches <at> gnu.org
:
bug#75894
; Package
guix-patches
.
(Tue, 01 Apr 2025 20:53:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 75894 <at> debbugs.gnu.org (full text, mbox):
Hello!
QA goes strictly by branch names. It picks up all branches not starting
with wip-. Then if your issue is named
Request for merging "node-team" branch
it will build the branch named "node-team".
The team name plays no role.
Maybe it is enough to rename the issue. Or you delete the node-team branch
and create a new one with the same content as javascript-team.
By the way, I see lots of node related branches:
remotes/origin/node-team
remotes/origin/wip-node-14
remotes/origin/wip-node-18-updates
remotes/origin/wip-node-importer
remotes/origin/wip-node-reproducibility
remotes/origin/wip-node-riscv64
Maybe you could go through them at some point in time and clean them up.
Andreas
Information forwarded
to
guix-patches <at> gnu.org
:
bug#75894
; Package
guix-patches
.
(Sat, 05 Apr 2025 21:40:02 GMT)
Full text and
rfc822 format available.
Message #17 received at 75894 <at> debbugs.gnu.org (full text, mbox):
Hey folks,
Andreas Enge <andreas <at> enge.fr> writes:
> Hello!
>
> QA goes strictly by branch names. It picks up all branches not starting
> with wip-. Then if your issue is named
> Request for merging "node-team" branch
> it will build the branch named "node-team".
> The team name plays no role.
>
> Maybe it is enough to rename the issue. Or you delete the node-team branch
> and create a new one with the same content as javascript-team.
The branch predates the team, but I guess for now we'll keep using the
branch.
> By the way, I see lots of node related branches:
> remotes/origin/node-team
Removed this branch, rebased our current javascript-team branch on
master, renamed it to node-team, and pushed yet again.
> remotes/origin/wip-node-14
> remotes/origin/wip-node-18-updates
> remotes/origin/wip-node-importer
> remotes/origin/wip-node-reproducibility
Removed as these were (cleaned up and) merged into master
> remotes/origin/wip-node-riscv64
This branch seems to be in use, so left alone.
In addition, I've deleted the javascript-team branch, as that one will
(for this round of the merge train) be called node-team. Thanks for the
guidance!
Thanks!
- Jelle
Information forwarded
to
guix-patches <at> gnu.org
:
bug#75894
; Package
guix-patches
.
(Mon, 07 Apr 2025 11:57:02 GMT)
Full text and
rfc822 format available.
Message #20 received at 75894 <at> debbugs.gnu.org (full text, mbox):
Hello Jelle,
thanks a lot for cleaning up the branches!
The node-team branch is currently built on QA:
https://qa.guix.gnu.org/branch/node-team
There are not so many affected packages, so maybe you can apply it to
master rather quickly.
Andreas
Information forwarded
to
guix-patches <at> gnu.org
:
bug#75894
; Package
guix-patches
.
(Wed, 09 Apr 2025 07:20:02 GMT)
Full text and
rfc822 format available.
Message #23 received at 75894 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Andreas Enge <andreas <at> enge.fr> writes:
> thanks a lot for cleaning up the branches!
>
> The node-team branch is currently built on QA:
> https://qa.guix.gnu.org/branch/node-team
>
> There are not so many affected packages, so maybe you can apply it to
> master rather quickly.
Looks like the builds are mostly complete, one package that stood out
was libnode, as that seems to fail to build on 32bit architectures.
I'm not sure if that's more flakyness (since some builds for other
architectures failed as well) or not:
https://data.qa.guix.gnu.org/repository/1/branch/node-team/latest-processed-revision/package/libnode/22.14.0?locale=en_US.UTF-8
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
guix-patches <at> gnu.org
:
bug#75894
; Package
guix-patches
.
(Sat, 12 Apr 2025 10:40:01 GMT)
Full text and
rfc822 format available.
Message #26 received at 75894 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Christopher Baines <mail <at> cbaines.net> writes:
> Andreas Enge <andreas <at> enge.fr> writes:
>
>> thanks a lot for cleaning up the branches!
>>
>> The node-team branch is currently built on QA:
>> https://qa.guix.gnu.org/branch/node-team
>>
>> There are not so many affected packages, so maybe you can apply it to
>> master rather quickly.
>
> Looks like the builds are mostly complete, one package that stood out
> was libnode, as that seems to fail to build on 32bit architectures.
>
> I'm not sure if that's more flakyness (since some builds for other
> architectures failed as well) or not:
>
> https://data.qa.guix.gnu.org/repository/1/branch/node-team/latest-processed-revision/package/libnode/22.14.0?locale=en_US.UTF-8
The test looks to be regarded as flaky by upstream, so I've pushed a
commit to skip the test on 32 bit architectures and rebased the branch.
Obviously there's work ongoing on the python-team branch at the moment,
but hopefully either python-team or node-team are ready to merge shortly
(and given the small number of builds on the node-team branch, I think
it's likely that it might be node-team).
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
guix-patches <at> gnu.org
:
bug#75894
; Package
guix-patches
.
(Sat, 12 Apr 2025 15:55:05 GMT)
Full text and
rfc822 format available.
Message #29 received at 75894 <at> debbugs.gnu.org (full text, mbox):
On 2025-04-12 11:39, Christopher Baines wrote:
> Christopher Baines <mail <at> cbaines.net> writes:
>
>> Andreas Enge <andreas <at> enge.fr> writes:
>>
>>> thanks a lot for cleaning up the branches!
>>>
>>> The node-team branch is currently built on QA:
>>> https://qa.guix.gnu.org/branch/node-team
>>>
>>> There are not so many affected packages, so maybe you can apply it to
>>> master rather quickly.
>>
>> Looks like the builds are mostly complete, one package that stood out
>> was libnode, as that seems to fail to build on 32bit architectures.
>>
>> I'm not sure if that's more flakyness (since some builds for other
>> architectures failed as well) or not:
>>
>> https://data.qa.guix.gnu.org/repository/1/branch/node-team/latest-processed-revision/package/libnode/22.14.0?locale=en_US.UTF-8
>
> The test looks to be regarded as flaky by upstream, so I've pushed a
> commit to skip the test on 32 bit architectures and rebased the branch.
>
> Obviously there's work ongoing on the python-team branch at the moment,
> but hopefully either python-team or node-team are ready to merge shortly
> (and given the small number of builds on the node-team branch, I think
> it's likely that it might be node-team).
I was working on both recently.
I don't think what I worked on in node-team is ready yet (I had some
updates going on and did some work to auto-delete unwanted dependencies
just as I did on python too, but I'd say it's not ready yet and could be
delayed until a later revision of the branch if that's blocking for some
other team).
I don't know if Jelle had other plans but if not, node-team can be
merged IMO, and we'll open another one when I'll have more time to
iterate / mature on my idea (I might start a GCD because it might be
useful for several build-systems).
On python-team, there's still maybe a week of work. I'll dedicate some
time this evening and tomorrow to advance on my part.
--
Best regards,
Nicolas Graves
Reply sent
to
Andreas Enge <andreas <at> enge.fr>
:
You have taken responsibility.
(Sun, 13 Apr 2025 12:26:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Jelle Licht <jlicht <at> fsfe.org>
:
bug acknowledged by developer.
(Sun, 13 Apr 2025 12:26:02 GMT)
Full text and
rfc822 format available.
Message #34 received at 75894-done <at> debbugs.gnu.org (full text, mbox):
Hello,
and thanks for the update! The node-team branch has been built without
further problems, thanks a lot to Chris for taking care of the 32bit
build failure.
So I have pushed the branch to master and am closing this bug.
I will also delete the node-team branch as per policy, and anyway
I think you wanted to rename it to javascript-team for the next run.
In any case, whenever you are ready, please feel free to push a new
branch and to open a corresponding merge request.
Andreas
Information forwarded
to
guix-patches <at> gnu.org
:
bug#75894
; Package
guix-patches
.
(Sun, 13 Apr 2025 12:55:02 GMT)
Full text and
rfc822 format available.
Message #37 received at 75894 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Andreas Enge <andreas <at> enge.fr> writes:
> and thanks for the update! The node-team branch has been built without
> further problems, thanks a lot to Chris for taking care of the 32bit
> build failure.
I think the builds are still flaky, but at least there should be some
substitutes, and this can be further worked on directly on the master
branch.
Thanks for pushing this Andreas!
[signature.asc (application/pgp-signature, inline)]
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Mon, 12 May 2025 11:24:18 GMT)
Full text and
rfc822 format available.
This bug report was last modified 4 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.