Arch Linux User Repository

@bhuvan The error output points out an error log, please read it.

@bhuvan have you enabled to chroot build option in paru?

I get the same error that @RubenKelevra got while trying to install ladybird using paru. I am not sure what am i doing wrong here. I tried installing it few days back I got the same error.

Call Stack (most recent call first):
  scripts/cmake/vcpkg_download_distfile.cmake:270 (z_vcpkg_download_distfile_show_proxy_and_fail)
  scripts/cmake/vcpkg_from_gitlab.cmake:113 (vcpkg_download_distfile)
  buildtrees/versioning_/versions/dav1d/0349d1196602b2983b1171647b30b5a9379920c6/portfile.cmake:1 (vcpkg_from_gitlab)
  scripts/ports.cmake:191 (include)


error: building dav1d:x64-linux failed with: BUILD_FAILED
Elapsed time to handle dav1d:x64-linux: 37.4 ms
Please ensure you're using the latest port files with `git pull` and `vcpkg update`.
Then check for known issues at:
  https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+dav1d
You can submit a new issue at:
  https://github.com/microsoft/vcpkg/issues/new?title=[dav1d]+Build+error+on+x64-linux&body=Copy+issue+body+from+%2Fhome%2Fbhuvan%2F.cache%2Fparu%2Fclone%2Fladybird%2Fsrc%2Fbuild%2Fvcpkg_installed%2Fvcpkg%2Fissue_body.md

-- Running vcpkg install - failed
CMake Error at /home/bhuvan/.cache/paru/clone/ladybird/src/vcpkg/scripts/buildsystems/vcpkg.cmake:899 (message):
  vcpkg install failed.  See logs for more information:
  /home/bhuvan/.cache/paru/clone/ladybird/src/build/vcpkg-manifest-install.log
Call Stack (most recent call first):
  /usr/share/cmake/Modules/CMakeDetermineSystem.cmake:146 (include)
  CMakeLists.txt:10 (project)


CMake Error: CMake was unable to find a build program corresponding to "Ninja".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.
CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage
CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage
-- Configuring incomplete, errors occurred!
==> ERROR: A failure occurred in build().
    Aborting...
error: failed to build 'ladybird-20240716-1': 
error: packages failed to build: ladybird-20240716-1

I am not sure if it is the same error or a different one. I have ninja installed in my system too. I am installing it on my laptop which I use daily.

@timschumi

I can't tell you why it fixed the issue for me, but I build it several times now with the new version, and it worked every time.

While it failed 3 times before.

So was it a local issue, or do you need to fix it upstream? I'm confused now. :)

@RubenKelevra Again, this was unrelated, as evidenced by somebody apparently having the same issue even on the 20240716 version of the package.

@bionade24 I have the option to either fix the actual issue upstream or to paper over it within the PKGBUILD. If you don't mind, I'd rather do it properly.

@timschumi if upstream build violates namcap or some other Archlinux packaging guidelines are there isn't a specific exception for this (e.g. go software), this is still the packagers responsibility. As a pkg maintainer you should patch upstream if it is necessary for the user experience, even if Archlinux tends to follow upstream closer than most distros.

@timschumi sure you did:

-source=("git+$url#commit=d07cf26894bcaa5791ed3b7715b94e25227b2bda" # 2024-07-11
+source=("git+$url#commit=bfc9dc447f42eb9d7d0927721291d1b528b3125d" # 2024-07-16

This fixed the build issue.

@bionade24 Thanks for the pointer about namcap, I haven't heard about that before. That said, most of the issues would be attributed to upstream packaging bugs (since most of it boils down to test files and empty test directories being installed) instead of something that this particular PKGBUILD is doing wrong.

@RubenKelevra I have changed precisely nothing related to this issue. It has always been a local problem.

AUR helpers are not supported by Arch Linux.

even if it's not an officially supported way

The whole AUR is not "officially supported", so spare us that crap.

Package should build fine in a chroot, regardless if it's a docker container or a systemd-nspawn. There should be no difference.

The updated version now builds fine in chroot again. So thanks for the fix @timschumi. :)

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.