Package Details: pacman-static 7.0.0.r6.gc685ae6-12

Git Clone URL: https://aur.archlinux.org/pacman-static.git (read-only, click to copy)
Package Base: pacman-static
Description: Statically-compiled pacman (to fix or install systems without libc)
Upstream URL: https://www.archlinux.org/pacman/
Licenses: GPL-2.0-or-later
Submitter: mazieres
Maintainer: Morganamilo (andreas_baumann)
Last Packager: andreas_baumann
Votes: 58
Popularity: 2.43
First Submitted: 2013-01-09 02:17 (UTC)
Last Updated: 2024-12-19 07:58 (UTC)

Dependencies (5)

Required by (0)

Sources (26)

Pinned Comments

Morganamilo commented on 2022-02-20 18:30 (UTC)

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/

Latest Comments

1 2 3 4 5 6 .. 14 Next › Last »

andreas_baumann commented on 2024-12-14 07:28 (UTC) (edited on 2024-12-14 07:31 (UTC) by andreas_baumann)

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?

he_ruoyang commented on 2024-12-14 04:20 (UTC) (edited on 2024-12-14 04:29 (UTC) by he_ruoyang)

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 失败

andreas_baumann commented on 2024-12-05 08:37 (UTC)

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

andreas_baumann commented on 2024-12-05 08:13 (UTC) (edited on 2024-12-05 08:15 (UTC) by andreas_baumann)

@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. ;-)

txtsd commented on 2024-12-03 01:54 (UTC)

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.

andreas_baumann commented on 2024-10-23 14:14 (UTC)

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..

andreas_baumann commented on 2024-10-23 14:07 (UTC)

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..

Ataraxy commented on 2024-10-19 21:57 (UTC)

Any tips on installing libassuan?

% sudo ./pacman-static -S libassuan                                                 129ms | 24-10-19 23:52:56
warning: libassuan-3.0.0-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) libassuan-3.0.0-1

Total Installed Size:  0.23 MiB
Net Upgrade Size:      0.00 MiB

:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring                                                       [################################################] 100%
(1/1) checking package integrity                                                     [################################################] 100%
(1/1) loading package files                                                          [################################################] 100%
(1/1) checking for file conflicts                                                    [################################################] 100%
(1/1) checking available disk space                                                  [################################################] 100%
:: Processing package changes...
(1/1) reinstalling libassuan                                                         [################################################] 100%
:: Running post-transaction hooks...
(1/1) Cleaning pacman cache...
Installed packages:
pacman-conf: error while loading shared libraries: libassuan.so.0: cannot open shared object file: No such file or directory
==> no candidate packages found for pruning
Uninstalled packages:
pacman: error while loading shared libraries: libassuan.so.0: cannot open shared object file: No such file or directory
==> ERROR: failed to retrieve the list of installed packages
error: command failed to execute correctly

Ataraxy commented on 2024-10-19 21:43 (UTC)

make[1]: Entering directory '/tmp/src/openssl-3.3.2'
musl-gcc  -I. -Iinclude -Iapps/include  -pthread -m64 -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -D_LARGEFILE6
4_SOURCE -Wa,--noexecstack -D_FORTIFY_SOURCE=2 -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -D_LARGEFILE64_SOURC
E -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -static -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSLDIR="\"/etc/ssl\"" -DENGINESDIR="\"/t
mp/src/temp/usr/lib/engines-3\"" -DMODULESDIR="\"/tmp/src/temp/usr/lib/ossl-modules\"" -DOPENSSL_BUILDING_OPENSSL -DNDEBUG -D_FORTIFY_SOURCE
=2  -c -o apps/lib/libapps-lib-app_libctx.o apps/lib/app_libctx.c
musl-gcc  -I. -Iinclude -Iapps/include  -pthread -m64 -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -D_LARGEFILE6
4_SOURCE -Wa,--noexecstack -D_FORTIFY_SOURCE=2 -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -D_LARGEFILE64_SOURC
E -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -static -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSLDIR="\"/etc/ssl\"" -DENGINESDIR="\"/t
mp/src/temp/usr/lib/engines-3\"" -DMODULESDIR="\"/tmp/src/temp/usr/lib/ossl-modules\"" -DOPENSSL_BUILDING_OPENSSL -DNDEBUG -D_FORTIFY_SOURCE
=2  -c -o apps/lib/libapps-lib-app_params.o apps/lib/app_params.c
/bin/sh: line 1: musl-gcc: command not found
make[1]: *** [Makefile:3343: apps/lib/libapps-lib-app_libctx.o] Error 127
make[1]: *** Waiting for unfinished jobs....
/bin/sh: line 1: musl-gcc: command not found
make[1]: *** [Makefile:3345: apps/lib/libapps-lib-app_params.o] Error 127
make[1]: Leaving directory '/tmp/src/openssl-3.3.2'
make: *** [Makefile:1702: build_libs] Error 2
==> ERROR: A failure occurred in build().

Thanks for the prebuilt binary -- it saved me. Any chance of an 2024 update for it?