[bug#62252] [PATCH v3 09/19] gnu: python-hatchling: Use upstream homepage.

[Ricardo Wurmus <rekado@elephly.net>]

Liliana Marie Prikler <liliana.prikler@gmail.com> writes:

> Am Sonntag, dem 26.03.2023 um 09:55 +0200 schrieb Ricardo Wurmus:
>> Hi,
>> 
>> I have built python-orjson on wip-rekado-rust-team, which is based on
>> top of the rust-team (but rebased on top of current master).  This
>> lets us build python-fastapi without having to remove orjson.
> Do we have an ETA on wip-rekado-rust-team?  And most importantly, does
> it come with antioxidant? :)

wip-rekado-rust-team is held up by the merge of the rust-team branch;
that one can only be merged once we’ve built rust on aarch64.  This
hasn’t succeeded yet as the builds time out or fail due to lack of
resources.  I’m trying to build it manually on ci.guix.gnu.org (i.e. not
through cuirass), so I have more control over options.

When rust-team has been merged, we’d build the few extra commits added
by wip-rekado-rust-team and merged that too.

> Hmm, 380 rebuilds would be fine if it was just python imho, but since
> it appears to cut into R and Gnome as well, I get your point.  Should
> we do the typical -next dance?

I don’t know.  I thought: rebase a feature branch on top of master,
start building it on ci, merge as soon as it’s done.

>> The starlette update also looks good to me, though you could move it
>> to 0.26.1 (with hash
>> 1gd9pvcfifrlaskqz741n4rbsgljn6jnjgkscvj211paay87knj1).
>> I used the version form pypi which didn’t come with tests, so I don’t
>> know if running the tests of 0.26.1 is more difficult than running
>> those of 0.25.
> I actually haven't tested 0.26.1 – the patch was lying around for some
> while before committing, since I didn't have the other parts running
> back then.  I'll probably send a v4 once I check whether there's an
> issue and what that issue might be.

Good good!

-- 
Ricardo