Arch Linux User Repository

There's now a custom repo and binaries again. Though only for x86_64 currently.

Custom Repo

[pacman-static]
SigLevel = Required
Server = https://pkgbuild.com/~morganamilo/$repo/$arch

Pre compiled binaries

https://pkgbuild.com/~morganamilo/pacman-static/x86_64/bin/

• updated curl to 8.13.0
• updated gpgerror to 1.53
• updated c-ares to 1.34.5
• updated openssl to 3.5.0
• updated xz to 5.8.1

third party software update:

updated libnghttp2 to 1.65.0

updated xz to 5.8.0

updated zstd to 1.5.7

updated libarchive to 3.7.9

This is due to some newer bash constructs (you might have to update bash first).

    # apply patch level commits on top of annotated tag for pacman
    if [[ -n ${_git_patch_level_commit} ]]; then
        if [[ v${_git_tag} != $(git describe --tags --abbrev=0 "${_git_patch_lev
            error "patch level commit ${_git_patch_level_commit} is not a descen
            exit 1
        fi
        git rebase "${_git_patch_level_commit}"
    fi

I took over the patching code from upstream: https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/blob/main/PKGBUILD?ref_type=heads#L69

I had a similar issue on some ARMv6 Archlinux ARM systems. You can just comment out everything but the git rebase "${_git_patch_level_commit}".

Which bash version do you have?

Is there a syntax error in line 141 of PKGBUILD?

makepkg report:

/home/user/aur/pacman-static/PKGBUILD:行141: 未预期的符号“then”附近有语法错误
/home/user/aur/pacman-static/PKGBUILD:行141: `        if [[ v${_git_tag} != $(git describe --tags --abbrev=0 "${_git_patch_level_commit}") ]] then'
==> 错误： 载入 /home/user/aur/pacman-static/PKGBUILD 失败

PKGBUILD的141行是否有语法错误？

makepkg 提示：

/home/user/aur/pacman-static/PKGBUILD:行141: 未预期的符号“then”附近有语法错误
/home/user/aur/pacman-static/PKGBUILD:行141: `        if [[ v${_git_tag} != $(git describe --tags --abbrev=0 "${_git_patch_level_commit}") ]] then'
==> 错误： 载入 /home/user/aur/pacman-static/PKGBUILD 失败

updated pacman to 7.0.0.r6.gc685ae6 and gpgme to 1.24.1

@txtsd: that's not up to me to decide (I'm just co-maintainer), you can ask Morganamilo directly (or eschwartz? He is still in the PKGBUILD as maintainer).

Sometimes updates take longer, because I want to make sure they also work on ARM or IA32. ;-)

Could I have co-maintainer on this please? I'd like to help keep it up-to-speed. I {,co-}maintain a ton of packages on the AUR.

found a candidate which should probably be patched:

./scripts/pacman-key.sh.in:PACMAN_KEYRING_DIR=${PACMAN_KEYRING_DIR:-$(pacman-conf --config="$CONFIG" gpgdir)}

But I doubt a hook calls pacman-key..

strange. musl-gcc is part of the musl package which is a makedepend of the package.

There is a /usr/bin/pacman-conf-static, maybe copying that to /usr/bin/pacman-conf temporarily is an option to install libassuan. To me it's not clear which hook is calling pacman-conf..