You are not logged in.
Hi everyone,
first off: I know the right place for this is normally an AUR comment or an out-of-date flag on the package itself. I do not have an AUR account though, and account registration is currently disabled, so I cannot comment or flag right now. I am posting here so the fixes are at least written down somewhere public, in case someone hits the same build errors or the maintainer wants to pick them up.
The package is euro-office-desktopeditors-git (maintainer: FranoGames). It builds Euro-Office DesktopEditors (a FOSS fork of ONLYOFFICE) from git via a Docker buildx bake build. The PKGBUILD has not been updated since it was first pushed (2025-05-31), and since it is a -git package that always builds current upstream, the build commands have drifted out of sync with the current repo layout. As it stands the build fails for everyone.
I worked through it end to end and got a working install. Here is what breaks and how to fix it.
1. build() enters the wrong directory
build() does cd "DesktopEditors/build" and runs bake packages, but the packages target lives in build/linux, not build. Result: "failed to find target packages", the build stops immediately.
2. build() skips the first build stage
Even from the right directory, the build is two stages. The packages target consumes an artifact at ../deploy/common that is produced by the desktop-common target (the default target) in build/. The PKGBUILD only runs the second stage, so it fails with:
ERROR: oci-layout reference "oci-layout://../deploy/common:latest" could not be resolvedThis is exactly the order the upstream build/linux/README.md documents (build desktop-common first, then the linux target), and there is even a build.sh upstream that does both. The PKGBUILD just does not follow it.
3. package() uses the wrong path in three places
package() points at build/deploy/packages, but the artifacts land in build/linux/deploy/packages. The cd and both cp -r lines need the /linux added, otherwise it cannot find the built .tar.xz files.
Here is the corrected build() and package():
build() {
cd "DesktopEditors/build"
BUILDX_BAKE_ENTITLEMENTS_FS=0 BUILDX_BUILDER=euro-office-desktopeditors-git docker buildx bake
cd "linux"
BUILDX_BAKE_ENTITLEMENTS_FS=0 BUILDX_BUILDER=euro-office-desktopeditors-git docker buildx bake packages
rm -rf /tmp/euro-office
}
package() {
cd "$srcdir/DesktopEditors/build/linux/deploy/packages"
bsdtar xvf $(ls | grep "x86_64.tar.xz")
chmod +x "usr/bin/euro-office-desktopeditors"
bsdtar xvf $(ls | grep "any.tar.xz")
cp -r "$srcdir/DesktopEditors/build/linux/deploy/packages/usr" "$pkgdir/"
cp -r "$srcdir/DesktopEditors/build/linux/deploy/packages/opt" "$pkgdir/"
}The first bake with no target builds the default (desktop-common), the second builds packages from build/linux. With that, the build runs through and installs fine.
What I am hoping for
Mostly I just want these fixes on record. If FranoGames sees this and wants to update the PKGBUILD, great, feel free to use any of the above. If not, I am happy to help: I will comment or flag on the AUR the moment registration reopens, and if the package ends up needing a new maintainer I would be glad to adopt it and keep it working. Whatever is easiest for everyone.
Thanks :)
Offline
You had a typo with the date, the package was first submitted in may 2026 , not 2025 .
I looked at upstream build instructions and realised they want people to run a docker image to create another docker image that will run the app.
Most of the dependencies needed are bundled in the created docker image. Qt6 is one of those deps and I think we all know how many issues are caused by differences between system provided qt and bundled qt .
I don't know much about docker images, so it may be possible docker isolation is good enough to prevent those issues .
Personally I don't see advantages of packaging this for archlinux . A wiki page with clear instructions how to create the docker image and run it on archlinux would be a better fit.
Since I may be wrong, I'll add a comment to the aur page for this package to alert the maintainer to this thread.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Hi there,
I'm the maintainer of the AUR package. Thanks for pointing that out. I messed up quite some things when updating the PKGBUILD so the currently published version is a patchwork of different changes I did. I did not catch that on my end for which I take full responsibility. I'll take a look at your changes and update the package ASAP (should definitely be done by Monday). As for the concerns voiced by Lone_Wolf I personally decided to build this in this way as it fit my use-case better. Euro Office still hasn't seen any official releases so I'd say that it's worth waiting until they start providing packages to see if packaging for arch makes sense.
Best regards
Offline