GNU bug report logs

#79004 Request for merging "rust-team" branch

Package	Source(s)		Maintainer(s)
guix-patches		PTS Buildd Popcon

Reported by Hilton Chain <hako@ultrarare.space>
Date 2025-07-13T09:13:01
Severity normal
Done Hilton Chain <hako@ultrarare.space>

Reply or subscribe to this bug. View this bug as an mbox, status mbox, or maintainer mbox

Report forwarded to guix-patches@gnu.org:
bug#79004; Package guix-patches. (Sun, 13 Jul 2025 09:13:02 GMT) (full text, mbox, link).

Acknowledgement sent to Hilton Chain <hako@ultrarare.space>:
New bug report received and forwarded. Copy sent to guix-patches@gnu.org. (Sun, 13 Jul 2025 09:13:02 GMT) (full text, mbox, link).

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

Apologize for the long delay, since all build work is already there, I should
start the merge process earlier.

rust-team has been rebased with Rust 1.88
(https://codeberg.org/guix/guix/pulls/989), except the one patch changing the
default Rust version.

I need help to finish transfering https://codeberg.org/hako/guix-rust-registry,
there's a button to accept it.

The remaining work is:
1. Address reviews in https://codeberg.org/guix/guix/pulls/387.
2. Add a news entry.
3. Test guix-rust-past-crates.

I expect to finish most of them within today.  Since there's also a build job on
ci.guix.gnu.org, the merge process should not take too long.

Information forwarded to guix-patches@gnu.org:
bug#79004; Package guix-patches. (Sun, 13 Jul 2025 15:06:02 GMT) (full text, mbox, link).

Message #8 received at 79004@debbugs.gnu.org (full text, mbox, reply):

Hello,

Am Sun, Jul 13, 2025 at 05:12:01PM +0800 schrieb Hilton Chain:
> I need help to finish transfering https://codeberg.org/hako/guix-rust-registry,
> there's a button to accept it.

I have clicked on the button.

> 1. Address reviews in https://codeberg.org/guix/guix/pulls/387.

Suggestion for links as above: Even if it is typographically ugly, leave
a space between the URL and the punctuation mark; this makes it possible
to directly click on it.

Andreas

Information forwarded to guix-patches@gnu.org:
bug#79004; Package guix-patches. (Sun, 13 Jul 2025 15:30:02 GMT) (full text, mbox, link).

Message #11 received at 79004@debbugs.gnu.org (full text, mbox, reply):

Andreas Enge <andreas@enge.fr> writes:

> Hello,
>
> Am Sun, Jul 13, 2025 at 05:12:01PM +0800 schrieb Hilton Chain:
>> I need help to finish transfering https://codeberg.org/hako/guix-rust-registry,
>> there's a button to accept it.
>
> I have clicked on the button.
>
>> 1. Address reviews in https://codeberg.org/guix/guix/pulls/387.
>
> Suggestion for links as above: Even if it is typographically ugly, leave
> a space between the URL and the punctuation mark; this makes it possible
> to directly click on it.

Thanks!  I'll note that.

I'm going to rebase rust-team to address a CI issue:
https://codeberg.org/guix/guix/issues/1170

Information forwarded to guix-patches@gnu.org:
bug#79004; Package guix-patches. (Sun, 13 Jul 2025 15:32:02 GMT) (full text, mbox, link).

Message #14 received at 79004@debbugs.gnu.org (full text, mbox, reply):

Em 13 de julho de 2025 12:05:24 BRT, Andreas Enge <andreas@enge.fr> escreveu:
>Hello,
>
>Am Sun, Jul 13, 2025 at 05:12:01PM +0800 schrieb Hilton Chain:
>> I need help to finish transfering https://codeberg.org/hako/guix-rust-registry,
>> there's a button to accept it.
>
>I have clicked on the button.
>
>> 1. Address reviews in https://codeberg.org/guix/guix/pulls/387.
>
>Suggestion for links as above: Even if it is typographically ugly, leave
>a space between the URL and the punctuation mark; this makes it possible
>to directly click on it.

I like using <>:

<https://codeberg.org/guix/guix/pulls/387>

Thunderbird for Android seems to also add it automatically.

-- 
Gabriel Santos

Information forwarded to guix-patches@gnu.org:
bug#79004; Package guix-patches. (Sun, 13 Jul 2025 15:33:02 GMT) (full text, mbox, link).

Information forwarded to guix-patches@gnu.org:
bug#79004; Package guix-patches. (Mon, 14 Jul 2025 15:14:02 GMT) (full text, mbox, link).

Message #20 received at 79004@debbugs.gnu.org (full text, mbox, reply):

Added draft news entry to the pull request.
Rebased rust-team to a revision processed by the data service.

Information forwarded to guix-patches@gnu.org:
bug#79004; Package guix-patches. (Fri, 25 Jul 2025 14:33:02 GMT) (full text, mbox, link).

Message #23 received at 79004@debbugs.gnu.org (full text, mbox, reply):

Hello all,

the rust-team branch is moving slowly, but surely to the front; you may
wish to already rebase it, since the core-packages-team push has
shuffled quite a few things.

And I wanted to ask if the team is happy with the changes and the branch
close to final shape, also with respect to
   https://codeberg.org/guix/guix/pulls/387

All the best,

Andreas

Information forwarded to guix-patches@gnu.org:
bug#79004; Package guix-patches. (Fri, 25 Jul 2025 16:37:02 GMT) (full text, mbox, link).

Message #26 received at 79004@debbugs.gnu.org (full text, mbox, reply):

Hi Andreas,

Andreas Enge <andreas@enge.fr> writes:

> Hello all,
>
> the rust-team branch is moving slowly, but surely to the front; you may
> wish to already rebase it, since the core-packages-team push has
> shuffled quite a few things.
>
> And I wanted to ask if the team is happy with the changes and the branch
> close to final shape, also with respect to
>    https://codeberg.org/guix/guix/pulls/387

I haven't checked the build status after the core-packages-team merge, I'll take
a look locally.  I'll also address the remaining reviews on next push.

Thanks

Information forwarded to guix-patches@gnu.org:
bug#79004; Package guix-patches. (Sat, 26 Jul 2025 07:31:03 GMT) (full text, mbox, link).

Message #29 received at 79004@debbugs.gnu.org (full text, mbox, reply):

Hilton Chain <hako@ultrarare.space> writes:

> Hi Andreas,
>
> Andreas Enge <andreas@enge.fr> writes:
>
>> Hello all,
>>
>> the rust-team branch is moving slowly, but surely to the front; you may
>> wish to already rebase it, since the core-packages-team push has
>> shuffled quite a few things.
>>
>> And I wanted to ask if the team is happy with the changes and the branch
>> close to final shape, also with respect to
>>    https://codeberg.org/guix/guix/pulls/387
>
> I haven't checked the build status after the core-packages-team merge, I'll take
> a look locally.  I'll also address the remaining reviews on next push.

Build failures of dev86@0.16.21 and python-pytorch@2.7.0 blocked a handful of
packages.

Information forwarded to guix-patches@gnu.org:
bug#79004; Package guix-patches. (Wed, 30 Jul 2025 11:45:02 GMT) (full text, mbox, link).

Message #32 received at 79004@debbugs.gnu.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

I used guix time-machine to do a build run on Berlin and everything
built except for xen-guest-agent (dev86), niri and (python-pytorch).
With the update to dev86 from master applied on the rust-team branch
xen-guest-agent built without problems, and niri built locally.  I'm
sending it through again on berlin to see if I can figure out why it
didn't work there.

I haven't gotten a chance to try any builds yet on aarch64 or riscv64

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[signature.asc (application/pgp-signature, inline)]

Information forwarded to guix-patches@gnu.org:
bug#79004; Package guix-patches. (Sun, 10 Aug 2025 17:49:02 GMT) (full text, mbox, link).

Message #35 received at 79004@debbugs.gnu.org (full text, mbox, reply):

Hello,

we expect to merge go-team tomorrow. nss-updates currently has a problem
that may or may not be fixed till then. Is rust-team ready to jump to
the front of the queue if necessary?

Please rebase in any case on the latest master commit known to the data
service, see the green badges at
   https://data.qa.guix.gnu.org/repository/1/branch/master


Thanks,

Andreas

Information forwarded to guix-patches@gnu.org:
bug#79004; Package guix-patches. (Mon, 11 Aug 2025 11:33:01 GMT) (full text, mbox, link).

Message #38 received at 79004@debbugs.gnu.org (full text, mbox, reply):

Efraim Flashner <efraim@flashner.co.il> writes:

> I used guix time-machine to do a build run on Berlin and everything
> built except for xen-guest-agent (dev86), niri and (python-pytorch).
> With the update to dev86 from master applied on the rust-team branch
> xen-guest-agent built without problems, and niri built locally.  I'm
> sending it through again on berlin to see if I can figure out why it
> didn't work there.
>
> I haven't gotten a chance to try any builds yet on aarch64 or riscv64


For niri, I think setting RAYON_NUM_THREADS[1] would help.

[1]: https://github.com/YaLTeR/niri/wiki/Packaging-niri

Information forwarded to guix-patches@gnu.org:
bug#79004; Package guix-patches. (Mon, 11 Aug 2025 17:38:01 GMT) (full text, mbox, link).

Message #41 received at 79004@debbugs.gnu.org (full text, mbox, reply):

Andreas Enge <andreas@enge.fr> writes:

> Hello,
>
> we expect to merge go-team tomorrow. nss-updates currently has a problem
> that may or may not be fixed till then. Is rust-team ready to jump to
> the front of the queue if necessary?

I see you have addressed the issue :)

Since there won't be major build changes on the branch, both options are
acceptable to me.

> Please rebase in any case on the latest master commit known to the data
> service, see the green badges at
>    https://data.qa.guix.gnu.org/repository/1/branch/master

Thanks, rebased.

Information forwarded to guix-patches@gnu.org:
bug#79004; Package guix-patches. (Mon, 11 Aug 2025 18:12:02 GMT) (full text, mbox, link).

Message #44 received at 79004@debbugs.gnu.org (full text, mbox, reply):

Am Tue, Aug 12, 2025 at 01:36:37AM +0800 schrieb Hilton Chain:
> I see you have addressed the issue :)

Yes, nss-updates should be ready to go.

> Since there won't be major build changes on the branch, both options are
> acceptable to me.
> Thanks, rebased.

Thanks! So in the end, there will be no urgency, and it will be your
turn in hopefully a few days, or maybe only a week.

Thanks for your reactivity,

Andreas

Information forwarded to guix-patches@gnu.org:
bug#79004; Package guix-patches. (Fri, 15 Aug 2025 14:51:02 GMT) (full text, mbox, link).

Message #47 received at 79004@debbugs.gnu.org (full text, mbox, reply):

Hello,

things advance well with nss-updates, and with a bit of luck, we may
even be able to push to master tomorrow. Could you already rebase
rust-team on nss-updates? Then data.qa would already evaluate the new
commit, and building could start immediately. I tried it myself, but
between changed files in cargo-something on nss-updates and the file
having been deleted on rust-team I did not know what to do.

In case something goes wrong, I have backed up the current branch as
rust-team-on-master.

Thanks,

Andreas

Information forwarded to guix-patches@gnu.org:
bug#79004; Package guix-patches. (Sat, 16 Aug 2025 08:30:02 GMT) (full text, mbox, link).

Message #50 received at 79004@debbugs.gnu.org (full text, mbox, reply):

Andreas Enge <andreas@enge.fr> writes:

> Hello,
>
> things advance well with nss-updates, and with a bit of luck, we may
> even be able to push to master tomorrow. Could you already rebase
> rust-team on nss-updates? Then data.qa would already evaluate the new

Rebased!

> commit, and building could start immediately. I tried it myself, but
> between changed files in cargo-something on nss-updates and the file
> having been deleted on rust-team I did not know what to do.
>
> In case something goes wrong, I have backed up the current branch as
> rust-team-on-master.

Information forwarded to guix-patches@gnu.org:
bug#79004; Package guix-patches. (Mon, 18 Aug 2025 09:10:01 GMT) (full text, mbox, link).

Message #53 received at 79004@debbugs.gnu.org (full text, mbox, reply):

Hello,

things have worked out, the rust-team branch has started after nss-updates.
A bit slowly, with only 200 x86_64 packages built overnight, but I hope
the pace will go up. I have rebased it on the master commit
50f65b553d2f5ebccb5f8a0ae41fb99077e362f6 . Now we (hopefully) just need
to wait.

Andreas

Information forwarded to guix-patches@gnu.org:
bug#79004; Package guix-patches. (Wed, 20 Aug 2025 21:40:01 GMT) (full text, mbox, link).

Message #56 received at 79004@debbugs.gnu.org (full text, mbox, reply):

The branch is essentially built, 228 packages missing on x86_64, 1 on i686,
86 on aarch64; nothing peculiar in the numbers.

But I tend to overlook that this may hide important leaf packages that
do not build... In my own home profile, this concerned librewolf, but
this one has been repaired by the first master commit after which we had
rebased. So for good measure, I have rebased once more on commit
   824989b0d47b5cd12dfc6f3d6ffc836319ccf287 .

I have forced a new evaluation by the data service:
   https://data.qa.guix.gnu.org/revision/1d0877d7cde8580df340bb5a01a47880e4dd1a52

Please feel free to push if you deem the branch ready.

Andreas

Information forwarded to guix-patches@gnu.org:
bug#79004; Package guix-patches. (Thu, 21 Aug 2025 10:34:02 GMT) (full text, mbox, link).

Message #59 received at 79004@debbugs.gnu.org (full text, mbox, reply):

Andreas Enge <andreas@enge.fr> writes:

> The branch is essentially built, 228 packages missing on x86_64, 1 on i686,
> 86 on aarch64; nothing peculiar in the numbers.
>
> But I tend to overlook that this may hide important leaf packages that
> do not build... In my own home profile, this concerned librewolf, but
> this one has been repaired by the first master commit after which we had
> rebased. So for good measure, I have rebased once more on commit
>    824989b0d47b5cd12dfc6f3d6ffc836319ccf287 .

Seeing through the logs, the failures seem to be on the QA side.  I have
no issue building these broken packages on x86_64-linux.

I haven't built all of them on aarch64-linux, but at least emacs succeeds.

> I have forced a new evaluation by the data service:
>    https://data.qa.guix.gnu.org/revision/1d0877d7cde8580df340bb5a01a47880e4dd1a52
>
> Please feel free to push if you deem the branch ready.

Thanks, I'm going to merge the branch.

Reply sent to Hilton Chain <hako@ultrarare.space>:
You have taken responsibility. (Thu, 21 Aug 2025 11:44:03 GMT) (full text, mbox, link).

Notification sent to Hilton Chain <hako@ultrarare.space>:
bug acknowledged by developer. (Thu, 21 Aug 2025 11:44:03 GMT) (full text, mbox, link).

Message #64 received at 79004-done@debbugs.gnu.org (full text, mbox, reply):

Hilton Chain <hako@ultrarare.space> writes:

> Andreas Enge <andreas@enge.fr> writes:
>
>> The branch is essentially built, 228 packages missing on x86_64, 1 on i686,
>> 86 on aarch64; nothing peculiar in the numbers.
>>
>> But I tend to overlook that this may hide important leaf packages that
>> do not build... In my own home profile, this concerned librewolf, but
>> this one has been repaired by the first master commit after which we had
>> rebased. So for good measure, I have rebased once more on commit
>>    824989b0d47b5cd12dfc6f3d6ffc836319ccf287 .
>
> Seeing through the logs, the failures seem to be on the QA side.  I have
> no issue building these broken packages on x86_64-linux.
>
> I haven't built all of them on aarch64-linux, but at least emacs succeeds.
>
>> I have forced a new evaluation by the data service:
>>    https://data.qa.guix.gnu.org/revision/1d0877d7cde8580df340bb5a01a47880e4dd1a52
>>
>> Please feel free to push if you deem the branch ready.
>
> Thanks, I'm going to merge the branch.

Merged :)

Display info messages

Send a report that this bug log contains spam.

debbugs.gnu.org maintainers <help-debbugs@gnu.org>. Last modified: Tue Sep 9 03:40:53 2025; Machine Name: wallace-server

GNU bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.