android-file-transfer-git

Build times (auto-updated)

• x86_64: 3m21s (2026-10-05 23:57 UTC, MAKEFLAGS=-j6)

---

Category: local-install/android-file-transfer-git – plain AUR package maintained by someone else (FabioLolix), not ours to maintain. Built and published to archlinuxaba purely so the cluster has it too, same as any other local-install/ entry (see memory/TOOLING_NOTES.md’s “scripts/install_only_packages” section and [[feedback_local_install_rebuilds]]).

Companion package to the new stable-release [android-file-transfer]: this is the VCS/git build of the same upstream (whoozle/android-file-transfer-linux), tracking master directly. provides=(android-file-transfer) / conflicts=(android-file-transfer ...) on their side, and our stable package conflicts back against android-file-transfer-git – expected, by design (can’t install both at once, pick one).

2026-09-19: initial build

• Fresh clone of https://aur.archlinux.org/android-file-transfer-git.git into /data/INSTALL/android-file-transfer-git (no prior local checkout existed, so no -old backup/restore dance needed).
• repo_release.sh on it as-is, no PKGBUILD edits (this is “build their PKGBUILD unmodified” territory, not ours to patch).
• x86_64: built + published clean (android-file-transfer-git 4.5.r7.g8892693-1 + debug package). namcap warnings are all implicit-library noise (openssl/libgcc/readline/glibc/libstdc++/file), same pattern as the sibling -cli/stable packages – not actionable.
• i686: FAILED, not a package bug: the i686 chroot’s qt6-tools binaries (uic, rcc, lrelease) are linked against libicui18n.so.75, which isn’t present/matching in that chroot’s current ICU install – error while loading shared libraries: libicui18n.so.75: cannot open shared object file. This is an ICU/Qt6 ABI mismatch in the local i686 chroot itself (see the icu74/75/76/77 shim packages this project already maintains for related ICU-version problems), not something to fix by editing this PKGBUILD. Left unbuilt for i686; repo_release.sh published the arch that did succeed and moved on, same handling as the aarch64 board-down case on [[android-file-transfer]].