Matěj Cepl

Hmm, cannot reproduce here with `0.9+git.1743662388.48639f5a`.

It may be worthy to study the development of this solution in the threads https://lists.sr.ht/~martanne/devel/patches/49637, https://lists.sr.ht/~martanne/devel/patches/49527 and https://lists.sr.ht/~martanne/devel/ I have been personally uneasy with this solution and I would be...

That test is known not to be 100% reliable.

Many people use annotated git tags for storing release notes, when we want to keep our repositories as independent of GitHub as possible. See for example https://git.sr.ht/~mcepl/m2crypto/refs/0.46.0

Another consideration about the heavyweight tags is that they could be GPG signed, which many use as part of their securing repositiry (see that tag I linked above).

> Thanks for starting on this! When you think it's ready, request a review and I'll have a look. Also, please give a link to Typst documentation. This is probably...

I wonder whether we shouldn’t have some library of testing documents. I have converted my last sermon slides to Typst (and I am not completely persuaded that it is easier...

Wouldn't it be possible to talk QuickJS maintainers to separate `libregexp` into separate repo and use it then as a git submodule?

+1 from this openSUSE packager, the same happens here. [Complete build log](https://github.com/user-attachments/files/17596495/_log.txt) lists all packages used and steps taken to reproduce.

Actually, I have this even on the regular x86_64 (openSUSE/Tumbleweed, psutil 5.7.0), when building python-psutil package for the distribution: ``` [ 7s] ====================================================================== [ 7s] FAIL: psutil.tests.test_linux.TestSensorsBattery.test_emulate_energy_full_0 [ 7s] ----------------------------------------------------------------------...