Arch Linux User Repository

Hi FixedWing

We unfortunately still cannot reproduce your issue on our side.

Please tell us if there remains any direction we might reasonable pursue. Otherwise, we will sadly be unable to help you.

cheers project-repo

Sorry for taking so long to respond.

I looked for other indicators before I commented but there really was nothing else more specific, which is why I asked.

Same error with 2.1.1. I removed the check function and it built successfully.

Nothing special about the build other than BUILDENV=(!distcc color ccache check !sign) BUILDDIR=/tmp/makepkg Which I would think pretty common.

Thanx.

Hi FixedWing

I am unable to reproduce this issue by calling makepkg in the directory of the PKGBUILD. Is there anything specific I ought to know about your setup?

Regardless of reproducibility, from the output you posted I can gather that there seems to have been a test suite failure. Can you see anything else in the output or in the log files that might be of use for debugging?

In the meantime you can try removing the check() function from the PKGBUILD as a workaround.

cheers project-repo

I'm not able to build 2.1.0. How can I fix this?

==================================== 1/2 ===================================== test: cagebreak:basic / Environment Variables start time: 03:35:55 duration: 0.42s result: exit status 1 command: MALLOC_PERTURB_=34 MESONCURRENTCONFIGDIR=/tmp/makepkg/cagebreak/src/cagebreak /bin/bash /tmp/makepkg/cagebreak/src/cagebreak/test/environment-variables ----------------------------------- stdout ----------------------------------- Cagebreak 2.1.0 is running on Wayland display wayland-1 Cagebreak 2.1.0 is running on Wayland display wayland-1 Cagebreak 2.1.0 is running on Wayland display wayland-1 ----------------------------------- stderr ----------------------------------- cat: /tmp/makepkg/cagebreak/src/cagebreak/_build-envvars/socket: No such file or directory ==============================================================================

Nice work. Thank you!

Cagebreak is now updated to 2.0.0 and everything should work nicely with wlroots 0.16.1.

BTW: We're sorry about the formatting of the PKGBUILD we pasted earlier. It looked much cleaner in the editor.

cheers project-repo

Hi FixedWing,

we are on it. Cagebreak has already been updated to wlroots 0.16.1 but only on the development branch. Not all the QA has been completed. If you want to check out an interim version you can use the PKGBUILD below.

cheers project-repo

Maintainer: project-repo archlinux-aur@project-repo.co

pkgname=cagebreak pkgver=2.0.0 pkgrel=1 pkgdesc='Tiling wayland compositor based on cage inspired by ratpoison' arch=('x86_64') url='https://github.com/project-repo/cagebreak' license=('MIT') depends=('wayland' 'libxkbcommon' 'wlroots<0.17.0' 'pango') makedepends=('meson' 'ninja' 'scdoc' 'wayland-protocols') optdepends=('wl-clipboard: clipboard support' 'xorg-xwayland: x application support') options=('!buildflags' '!strip') conflicts=('cagebreak-bin') source=("cagebreak::git+https://github.com/project-repo/cagebreak") sha512sums=('SKIP') build() { cd "$pkgname" git checkout development meson setup build --buildtype=release -Dxwayland=true -Dman-pages=true ninja -C build } package() { cd "$pkgname" mkdir -p "$pkgdir/usr/bin/" cp 'build/cagebreak' "$pkgdir/usr/bin/" }

There is a conflict between PKGBUILD which requires 'wlroots<0.16.0' and the recently upgraded wlroots which is now at version 16.1.

We are still having some trouble testing the aarch64 build. However, you may use our PKGBUILD at https://github.com/project-repo/cagebreak-pkgbuild/tree/development/cagebreak-arm until we have figured this out.

This PKGBUILD will be merged into master with the next release but not uploaded into the AUR until testing works. Versions and hashes will be automatically adjusted with every future cagebreak release. Nevertheless, aarch64 is still not officially supported at the moment.

cheers project-repo

Thank you for your suggestion. We are looking at compilation and testing for arm and will post here within the next two weeks.

cheers project-repo