Arch Linux User Repository

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.

It looks like due to cmake update.

[builder@aa7f539cb45d w]$ tail /home/builder/w/src/vcpkg/buildtrees/giflib/config-x64-linux-out.log

  Update the VERSION argument <min> value.  Or, use the <min>...<max> syntax
  to tell CMake that the project requires at least <min> but has been updated
  to work with policies introduced by <max> or earlier.

  Or, add -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to try configuring anyway.


-- Configuring incomplete, errors occurred!

Adding the flag -DCMAKE_POLICY_VERSION_MINIMUM=3.5 in PKGBUILD does not help. I think it needs to be added to one of the package that is downloaded during build.

Ideally all sources should be added to the sources array instead of downloading during build. That would allow to patch problems like this.

Current version (20250312-1) fails to build for me.

Error:

Downloading giflib-5.2.2.tar.gz, trying https://sourceforge.net/projects/giflib/files///giflib-5.2.2.tar.gz/download
Successfully downloaded giflib-5.2.2.tar.gz
-- Extracting source /home/builder/w/src/vcpkg/downloads/giflib-5.2.2.tar.gz
-- Using source at /home/builder/w/src/vcpkg/buildtrees/giflib/src/-9e90bb84d0.clean
-- Found external ninja('1.12.1').
-- Configuring x64-linux
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:127 (message):
    Command failed: /usr/sbin/ninja -v
    Working Directory: /home/builder/w/src/vcpkg/buildtrees/giflib/x64-linux-rel/vcpkg-parallel-configure
    Error code: 1
    See logs for more information:
      /home/builder/w/src/vcpkg/buildtrees/giflib/config-x64-linux-rel-CMakeCache.txt.log
      /home/builder/w/src/vcpkg/buildtrees/giflib/config-x64-linux-out.log

Call Stack (most recent call first):
  /home/builder/w/src/build/vcpkg_installed/x64-linux/share/vcpkg-cmake/vcpkg_cmake_configure.cmake:269 (vcpkg_execute_required_process)
  buildtrees/versioning_/versions/giflib/3763c06b1c8fce08fe96398c747b343707832d62/portfile.cmake:17 (vcpkg_cmake_configure)
  scripts/ports.cmake:196 (include)


error: building giflib:x64-linux failed with: BUILD_FAILED

Does it really need to download and build openssl 3.4.0 when arch has 3.4.1? I'd prefer not having multiple versions installed. Same thing, but less critical also applies to curl, and others.

Hi. Ladybird 20250312 segfaults for me, and searching AUR comments below it looks like it might be a me-only problem. Any idea why? EDIT ah, a few such reports in sibling AUR pkg https://aur.archlinux.org/packages/ladybird-git .

~ gdb Ladybird
(No debugging symbols found in Ladybird)

(gdb) run
Starting program: /usr/bin/Ladybird
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7ffff130c6c0 (LWP 256378)]
[New Thread 0x7fffeafd46c0 (LWP 256379)]
[New Thread 0x7fffe9fd36c0 (LWP 256380)]
[New Thread 0x7fffe3fff6c0 (LWP 256381)]
[New Thread 0x7fffe2ffe6c0 (LWP 256382)]
[New Thread 0x7fffe1ffd6c0 (LWP 256383)]
[New Thread 0x7fffcffff6c0 (LWP 256384)]

Thread 1 "Ladybird" received signal SIGSEGV, Segmentation fault.
0x000055555e60e120 in ?? ()

The PKGBUILD does not properly disable vcpkg telemetry as described in https://github.com/LadybirdBrowser/ladybird/issues/3816. We should probably take care of this.

@Sateallia alright. There's also the option to build ladybird with a compilation cache, so only the changed files are recompiled if you update git commits.

@RubenKelevra I prefer not to use Chaotic-AUR as I connect to systems that aren't mine and I don't wish to expose them to any danger that comes from third party repositories. If timschumi declines my proposal/request, I will look into setting up a builder of my own so thank you for the idea.

@Sateallia you can install ladybird without the need for compilation via chaotic-aur. The only thing necessary for more up-to-date updates would be, that someone confirms that a git version is building and then move this package here up to this commit.

ladybird-git often breaks because of vcpkg updates. Even when it builds properly, it moves too fast for me since I'm on a low-powered computer and building multiple times in a day takes too much time. Considering Ladybird is planning an alpha release in 2026, it would be nice if this package could be updated at least once a month to an arbitrary random commit. This would also allow people that evaluate Ladybird every month (after the monthly TMiL bulletins) to follow Ladybird's progress.

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.