owncloud-client-6

Category: local-install (rebuilt only so archlinuxaba/the cluster gets it too; not maintained/adapted/owned by us — see arch/scripts/install_only_packages). AUR maintainer is iyanmv, not us.

“ownCloud client based on mirall (Legacy 6.x version with support for ownCloud Server)” — a distinct AUR package from the owncloud-client in [extra], which no longer supports the legacy ownCloud Server protocol. conflicts=(owncloud-client) / provides=(owncloud-client=$pkgver). arch=(x86_64) only (Qt6/KDE ECM/CMake build), validpgpkeys set (ownCloud Client Team signing key) — ran update_pgp_key_dir.sh from inside the checkout before building.

Build notes (2026-08-24, initial add)

• Added via the standard local-install workflow: fresh git clone https://aur.archlinux.org/owncloud-client-6.git /data/INSTALL/owncloud-client-6, then repo_release.sh.
• Build itself (cmake configure + full Qt6/KDE C++ compile) is slow — took ~48 minutes wall clock for a first build (doxygen/sphinx docs + large libsync/gui/cmd targets). Don’t assume a stuck-looking ps snapshot mid-build means it’s hung; check the real build log under /var/lib/archbuild/archlinuxaba-x86_64/build/logdest/ for actual progress instead of trusting a single ps sample.
• makechrootpkg -C (namcap QA pass) failed/aborted on the owncloud-client-6-debug package specifically — the debug package is huge (~37 MB compressed, mostly debug symbols for a large C++/Qt codebase) and namcap either hung or crashed analyzing it, producing an empty owncloud-client-6-debug-*.pkg.tar.zst-namcap.log and an ==> ERROR: Aborting... from archbuild. The main package’s namcap pass completed fine (2 harmless warnings: implicit hicolor-icon-theme dependency, possibly-unneeded qt6-svg).
• Because archbuild reported failure, repo_build.sh counted 0 successful archs and repo_release.sh exited before signing/publishing — even though the actual packages had already been built successfully and were sitting untouched in /var/lib/archbuild/archlinuxaba-x86_64/build/pkgdest/. Recovered by copying both .pkg.tar.zst files out to the pkgdir by hand, then running repo_sign.sh + repo_publish.sh directly (skipping repo_release.sh’s orchestration, since the build step was already done) — successfully published both owncloud-client-6 and owncloud-client-6-debug to os/x86_64/ on the repo host. Manually removed the local .pkg.tar.zst/.sig afterward, matching what repo_release.sh normally does on success.
• If this happens again on a future version bump: check /var/lib/archbuild/archlinuxaba-x86_64/build/pkgdest/ for already-built packages before assuming a real build failure and re-running the (very slow) compile.
• A timeout wrapped around repo_release.sh does not reliably bound this build — the deep sudo/systemd-nspawn/makechrootpkg process tree does not appear to honor timeout’s SIGTERM, so the real build kept running to completion well past the wrapper’s nominal timeout. Don’t rely on timeout to bound a chroot build; if it needs killing, use the machinectl terminate + process-tree kill -9 approach documented for stuck builds instead.