Daniel Richard G.

Note that the current xtradeb-convert release will generally require a current Chromium package in order to work. In this case, the `bookworm/libxml-parseerr.patch` file was newly added to 125.0.6422.141. You'll need...

Understood that time is tight. Looking forward to hearing your thoughts when you have the opportunity. There's a lot of moving parts, to be sure! I try to aim for...

I've updated the cache expiration logic to avoid a corner case where an orig-source tarball may be deleted prematurely. And I also added the `remote-check.sh` script, which I had forgotten...

Yeah, bash was the natural choice since most of the work amounted to running other programs. I take it you'd have preferred Python? :-) > Do you have part of...

An update: I've developed some [tooling](https://github.com/iskunk/cr-ghci-build) that is able to adapt the Chromium build so that it can build on GitHub runners in a mostly-parallel way. I recently updated it,...

> Overall I think this looks good, my only nit is that the remote-check script has a lot of moving parts and it would be better to have a github...

@implicitfield wrote: > Regarding release monitoring, the main repository has an existing [workflow](https://github.com/ungoogled-software/ungoogled-chromium/blob/master/.github/workflows/new_version_check.yml) for checking for upstream chromium releases. It runs every hour, and doesn't install any packages at runtime,...

@implicitfield wrote: > > Oof, that's a perfect scenario to get a cross-compilation build going. I've done it for Windows, but don't know what would be involved for macOS. >...

> I guess macOS itself should work fine under QEMU, but that seems like a relatively heavy solution. There's also the [Darling project](https://github.com/darlinghq/darling) (which is essentially the macOS equivalent to...

> I've used those runners actually, they're just in public beta, but it sounds like they [don't support nested virtualization](https://github.com/orgs/community/discussions/19197#discussioncomment-11863501), so emulation would still be where it's at. I guess...