distrobuilder-git
- Path: arch/maintained/distrobuilder-git
- Build failure during the 2026-07-07 “build all packages for x86_64”
private-repo release pass (see
repo_release_logs/maintained_distrobuilder-git.log).
- Go module build fails via cgo:
../go/pkg/mod/go.podman.io/storage@v1.62.0/drivers/btrfs/version.go:6:10:
fatal error: btrfs/version.h: No such file or directory – a transitive
Go dependency (go.podman.io/storage’s btrfs driver) needs the
btrfs-progs C headers via cgo, and that isn’t declared as a
makedepends entry in this PKGBUILD.
- Likely a one-line fix (add
btrfs-progs to makedepends) similar in
spirit to the missing-git bug (memory/adtpro-git.md,
memory/c2t-git.md, memory/dos33fsprogs-git.md,
memory/dsk2nib-git.md), but not verified/fixed as part of this pass –
distrobuilder-git also pulls a large Go module graph so there could be
other missing cgo deps behind this one once it’s addressed.
- 2026-08-02: confirmed the
btrfs-progs fix above – added it to
makedepends, pkgrel 1 -> 2. It works: the btrfs cgo compile now
succeeds and the build gets much further.
- Hit a second, different failure right after:
go build fails in
go.podman.io/storage@v1.62.0/userns.go with
undefined: securejoin.OpenInRoot / undefined: securejoin.Reopen.
This is a Go module version-skew issue – go.podman.io/storage
expects a newer github.com/cyphar/filepath-securejoin than what
go mod vendor resolved into the vendor tree (those two functions
don’t exist in the older securejoin version pulled in). Not a
packaging bug in this PKGBUILD’s own code; likely needs either a
go get github.com/cyphar/filepath-securejoin@latest (or an
explicit go.mod replace/require bump) added to prepare() before
go mod vendor runs, to force MVS to pick a compatible version.
Not fixed as part of this pass – flagging only, would need someone
familiar with this dependency’s intended version to pin correctly
without breaking something else in the large LXC/LXD/incus module
graph this package vendors.
pkgver/pkgrel note: makepkg’s own VCS pkgver() auto-update
reset pkgrel back to 1 and bumped pkgver to the live HEAD
(v3.3.1.r48.gf2c2434 as of this date) during the failed build
attempt – this is normal -git package behavior (not something to
revert), but means the pkgrel=2 packaging fix above got
overwritten back to a fresh pkgrel=1 in the same run. Since the
package still doesn’t build, this is currently untested at any
pkgrel – re-verify once the securejoin issue is resolved.