I agree with @timschumi. "Doesn't build in my dirty build environment" because you don't use extra-x86_64-build
, makechrootpkg
or an AUR helper that supports building in a clean build environment is not the responsibility of the maintainer to fix. The issue with building in a clean chroot provided by paru should be reproducable, though and I personally would fix such issues, even if it's not an officially supported way (Idk if it's already fixed). FWIW, ladybird builds fine in my CI/CD (build log) and if you don't want to have an effort building it yourself, you can download the built pkg from my user repo https://wiki.archlinux.org/title/Unofficial_user_repositories#oscloud
@timschumi The latest version contains paths that I guess aren't belonging into the pkg:
pacman -Fyl ladybird
<omitted>
ladybird usr/usr/
ladybird usr/usr/Tests/
ladybird usr/usr/Tests/LibMedia/
ladybird usr/usr/Tests/LibMedia/avc_in_matroska.mkv
ladybird usr/usr/Tests/LibMedia/master_elements_containing_crc32.mkv
ladybird usr/usr/Tests/LibMedia/vp9_4k.webm
ladybird usr/usr/Tests/LibMedia/vp9_clamp_reference_mvs.webm
ladybird usr/usr/Tests/LibMedia/vp9_in_webm.webm
ladybird usr/usr/Tests/LibMedia/vp9_oob_blocks.webm
In case you don't already do so, please always check the built pkgs with namcap
for packaging errors before uploading the updated PKGBUILD
.
Pinned Comments
timschumi commented on 2025-02-14 07:21 (UTC)
There is no new tagged (or otherwise differentiable) version to update to. Existing bumps to arbitrary revisions have been done whenever I get around to it to avoid the package falling into complete disrepair (which would cause it to be deleted and most likely recreated by some third party) and to make sure that people who don't pay attention don't get a version that is years out of date. The actual package has always been ladybird-git, and that will remain the case for the foreseeable future as well.