bindfs
- Path:
local-install/bindfs (not tracked in arch/; see scripts/install_only_packages)
- 2026-09-10: rebuilt at the user’s request after seeing
error: failed
to prepare transaction... installing fuse3 (3.18.3-1) breaks
dependency 'fuse3=3.18.2' required by bindfs on some machine’s
pacman -Su. Followed the standard local-install rebuild workflow:
backed up /data/INSTALL/bindfs to -old, fresh git clone
https://aur.archlinux.org/bindfs.git, pkgrel 1 -> 1.1 (plain
upstream PKGBUILD, no local diff, so the local-install/adapted
X.Y scheme applies). Built and published cleanly on i686/x86_64.
- Couldn’t confirm the exact root cause of the reported conflict:
neither this fresh build’s own
.PKGINFO nor the previously-
installed 1.18.4-1 build’s .PKGINFO (inspected directly) shows
any version-pinned fuse3 dependency – both just say plain
depend = fuse3, no =3.18.2. The PKGBUILD’s own depends=('glibc'
'fuse3') has never been pinned either. So whatever pinned
fuse3=3.18.2 on the reporting machine isn’t coming from this
project’s published bindfs metadata – possibly an older/different
bindfs build installed there, or something unrelated. This rebuild
(1.18.4-1.1) is still the right move regardless (fresh build,
unpinned dep, pacman -Syu picking it up should resolve any stale
local pin either way), but flag this for whoever verifies it: if the
conflict recurs after upgrading to 1.18.4-1.1, the fuse3-pin
mechanism needs more investigation, not another blind rebuild.
- This build host’s own
fuse3 was still 3.18.2-1 (via extra) at
the time of this rebuild, not yet 3.18.3 – so this was built
against the same fuse3 the host already had, not verified against
3.18.3 specifically.