Package Details: pacman-static 2015-5

Git Clone URL: (read-only)
Package Base: pacman-static
Description: Statically-compiled pacman (to fix or install systems without libc)
Upstream URL:
Licenses: GPL
Submitter: mazieres
Maintainer: mazieres
Last Packager: mazieres
Votes: 7
Popularity: 0.000000
First Submitted: 2013-01-09 02:17
Last Updated: 2015-06-11 06:26

Required by (0)

Sources (1)

Latest Comments

zashi commented on 2017-04-26 19:23

Ugh... and drop the stupid dependencies that gpgme wants like python and qt5... know what? I'll just keep working on this until I get it working and then list all the changes I had to make.

zashi commented on 2017-04-26 19:12

Also, please add the --without-openssl option to libarchive.

zashi commented on 2017-04-26 18:21

Can you drop the --pkg argument from makepkg? That will make this work again.

mazieres commented on 2013-12-03 05:31

The new version now builds as a regular package, without root privileges. However, since it needs to recompile so many packages, it just grabs the latest arch patches from ABS and is not tied to any particular version. Hence, this is effectively "devel" package--the fact that you compiled version 2013 doesn't mean anything about the versions of pacman or the libraries it is linked against.

mazieres commented on 2013-11-11 06:18

Sadly, static libraries are being removed from almost all packages, making it very difficult to build a static version of pacman on arch itself. I've had to create a shell script that does the build in a chroot environment, which means this package a) requires root for the build phase, and b) isn't really tied to pacman 4.1.2, but builds whatever the latest version it can get out of abs is.

mazieres commented on 2013-10-23 00:18

Good point, Nowaker. I've just changed the package so that most of the dependencies are now makedepends instead of depends. I left gpg2 in there for now, since it does call the executable. Maybe gpg shoudl be an optdepend, since you can actually use pacman without gpg, though it's a bad idea except in an emergency.

Nowaker commented on 2013-10-21 19:52

@mazieres, why does it depend on glibc or whatever if it's statically compiled? I wanted to install this package before performing the glibc and /usr/lib update, and it doesn't let me go. If it's intended "for fixing systems with corrupt libc" it shouldn't depend on anything.

mazieres commented on 2013-08-07 06:11

If you are running this on another system such as debian, you will need to create /var/lib/pacman/{local,sync} and possibly /var/cache/pacman/pkg, same as if you were "pacstrapping" an arch system. Alternatively you can edit your pacman.conf file to put these directories somewhere else.

Anonymous comment on 2013-08-01 14:10

I've try to run pacman-static under debian wheezy.
I can run "help" (-h) but if i use "pacman-static -Syy" it says:
error: failed to initialize alpm library (could not find or read directory)

axlrose commented on 2013-03-23 10:16

nice work

mazieres commented on 2013-01-09 02:35

If you are totally hosed, to the point that even gpg cannot run to verify signatures, but you still have a root shell, you must do the following:

# cat > /tmp/conf <<EOF
Architecture = auto
SigLevel = Never
Include = /etc/pacman.d/mirrorlist
# pacman-static --config /tmp/conf -S glibc