Curl released a new version, which fixed a high-severity vulnerability. Is there a need to upgrade the curl version in this package?
Search Criteria
Package Details: pacman-static 7.0.0.r3.g7736133-9
Package Actions
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: | 57 |
Popularity: | 2.77 |
First Submitted: | 2013-01-09 02:17 (UTC) |
Last Updated: | 2024-11-23 08:26 (UTC) |
Dependencies (5)
- pacman (pacman-gitAUR)
- git (git-gitAUR, git-glAUR) (make)
- kernel-headers-musl (make)
- meson (meson-gitAUR) (make)
- musl (musl-gitAUR) (make)
Required by (0)
Sources (26)
- ca-dir.patch
- git+https://github.com/tukaani-project/xz#tag=v5.6.3
- git+https://gitlab.archlinux.org/pacman/pacman.git#tag=v7.0.0?signed
- https://curl.haxx.se/download/curl-8.11.0.tar.gz
- https://curl.haxx.se/download/curl-8.11.0.tar.gz.asc
- https://github.com/c-ares/c-ares/releases/download/v1.34.2/c-ares-1.34.2.tar.gz
- https://github.com/c-ares/c-ares/releases/download/v1.34.2/c-ares-1.34.2.tar.gz.asc
- https://github.com/facebook/zstd/releases/download/v1.5.6/zstd-1.5.6.tar.zst
- https://github.com/facebook/zstd/releases/download/v1.5.6/zstd-1.5.6.tar.zst.sig
- https://github.com/libarchive/libarchive/releases/download/v3.7.7/libarchive-3.7.7.tar.xz
- https://github.com/libarchive/libarchive/releases/download/v3.7.7/libarchive-3.7.7.tar.xz.asc
- https://github.com/nghttp2/nghttp2/releases/download/v1.64.0/nghttp2-1.64.0.tar.xz
- https://github.com/openssl/openssl/releases/download/openssl-3.4.0/openssl-3.4.0.tar.gz
- https://github.com/openssl/openssl/releases/download/openssl-3.4.0/openssl-3.4.0.tar.gz.asc
- https://gnupg.org/ftp/gcrypt/libassuan/libassuan-3.0.0.tar.bz2
- https://gnupg.org/ftp/gcrypt/libassuan/libassuan-3.0.0.tar.bz2.sig
- https://gnupg.org/ftp/gcrypt/libgpg-error/libgpg-error-1.51.tar.bz2
- https://gnupg.org/ftp/gcrypt/libgpg-error/libgpg-error-1.51.tar.bz2.sig
- https://sourceware.org/pub/bzip2/bzip2-1.0.8.tar.gz
- https://sourceware.org/pub/bzip2/bzip2-1.0.8.tar.gz.sig
- https://www.gnupg.org/ftp/gcrypt/gpgme/gpgme-1.24.0.tar.bz2
- https://www.gnupg.org/ftp/gcrypt/gpgme/gpgme-1.24.0.tar.bz2.sig
- https://zlib.net/zlib-1.3.1.tar.gz
- https://zlib.net/zlib-1.3.1.tar.gz.asc
- openssl-3.0.7-no-atomic.patch
- pacman-revertme-makepkg-remove-libdepends-and-libprovides.patch
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 13 Next › Last »
BryanLiang commented on 2023-10-13 09:44 (UTC)
andreas_baumann commented on 2023-09-21 13:34 (UTC)
The backported patches of pacman are most likely unnecessary as they affect shell stuff in makepkg and some python tests, not pacman itself. Will check and remove them again (or strip them down) in the next build..
andreas_baumann commented on 2023-09-21 08:19 (UTC) (edited on 2023-09-21 10:30 (UTC) by andreas_baumann)
Using zlib 1.3 now.
Also integrated the "patch in prepare", thanks for that, good idea.
6.0.2-4 is a version with minimal updates of 3rd party packages.
6.0.2-5 is a version with all 3rd party packages updated as well as integrated backports from upstream for pacman itself.
BrainDamage commented on 2023-09-17 07:07 (UTC)
here's a small patch to move source patching to a separate prepare() function, this way one can use --noextract with makepkg to resume a partial build ( I've had to do this a few times since it takes a while to build the whole thing )
diff --git a/PKGBUILD b/PKGBUILD
index 1650390..9b4efde 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -146,13 +146,23 @@ export CXXFLAGS+=' -D_LARGEFILE64_SOURCE'
# recover on systems with broken zstd support in libarchive
[[ $PKGEXT = .pkg.tar.zst ]] && PKGEXT=.pkg.tar.xz
+prepare() {
+ # openssl
+ cd "${srcdir}"/openssl-${_sslver}
+ patch -Np1 -i "${srcdir}/ca-dir.patch"
+ case ${CARCH} in
+ arm|armv6h|armv7h)
+ # special patch to omit -latomic when installing pkgconfig files
+ patch -Np1 -i "${srcdir}/openssl-3.0.7-no-atomic.patch"
+ esac
+}
+
build() {
export PKG_CONFIG_PATH="${srcdir}"/temp/usr/lib/pkgconfig
export PATH="${srcdir}/temp/usr/bin:${PATH}"
# openssl
cd "${srcdir}"/openssl-${_sslver}
- patch -Np1 -i "${srcdir}/ca-dir.patch"
case ${CARCH} in
x86_64)
openssltarget='linux-x86_64'
@@ -173,8 +183,6 @@ build() {
arm|armv6h|armv7h)
openssltarget='linux-armv4'
optflags=''
- # special patch to ommit -latomic when installing pkgconfig files
- patch -Np1 -i "${srcdir}/openssl-3.0.7-no-atomic.patch"
;;
aarch64)
openssltarget='linux-aarch64'
--
yochananmarqos commented on 2023-09-08 19:17 (UTC)
@Morganamilo: PKGBUILD, please? Did you update any dependencies?
user_58180 commented on 2023-09-08 19:08 (UTC)
curl: (22) The requested URL returned error: 404
==> ERROR: Failure while downloading https://zlib.net/zlib-1.2.13.tar.gz
Should probably be replaced with https://www.zlib.net/fossils/zlib-1.2.13.tar.gz
.
andreas_baumann commented on 2023-06-01 08:43 (UTC)
I added the _LARGEFILE64_SOURCE define. I cannot reproduce the ARFLAGS issues in libassuan though.
arglebargle commented on 2023-05-30 04:51 (UTC)
As of 2023-05 you now need to specify ar flags too, here's the patch I'm using to build:
commit 8d66b546d4ed08a5250bd2964ee2883982e148ec
Author: Arglebargle <arglebargle@arglebargle.dev>
Date: Mon May 29 21:13:14 2023 -0700
patched to build as of 2023-05-21
diff --git a/PKGBUILD b/PKGBUILD
index 4454724..fc1ae94 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -16,7 +16,7 @@ _libarchive_ver=3.6.1
_gpgerrorver=1.46
_libassuanver=2.5.5
_gpgmever=1.18.0
-pkgrel=2
+pkgrel=2.1
pkgdesc="Statically-compiled pacman (to fix or install systems without libc)"
arch=('i486' 'i686' 'pentium4' 'x86_64' 'arm' 'armv6h' 'armv7h' 'aarch64')
url="https://www.archlinux.org/pacman/"
@@ -137,6 +137,7 @@ if [[ $CARCH = i686 || $CARCH = pentium4 || $CARCH = i486 ]]; then
export CFLAGS="${CFLAGS/-fstack-protector-strong/}"
export CXXFLAGS="${CXXFLAGS/-fstack-protector-strong/}"
fi
+export CFLAGS+=' -D_LARGEFILE64_SOURCE'
# keep using xz-compressed packages, because one use of the package is to
# recover on systems with broken zstd support in libarchive
@@ -272,7 +273,8 @@ build() {
# libassuan
cd "${srcdir}"/libassuan-${_libassuanver}
- ./configure --prefix="${srcdir}"/temp/usr \
+ # libassuan needs ARFLAGS specified or a warning from -u kills the build
+ AR_FLAGS=cr ARFLAGS=cr ./configure --prefix="${srcdir}"/temp/usr \
--disable-shared
make -C src
make -C src install-{binSCRIPTS,libLTLIBRARIES,nodist_includeHEADERS,pkgconfigDATA}
ericwoud commented on 2023-05-24 19:27 (UTC) (edited on 2023-05-25 06:07 (UTC) by ericwoud)
I need the following patch to build (aarch64). gpgme complains about undefined ino64_t and off64_t.
diff -Naur a/PKGBUILD b/PKGBUILD
--- a/PKGBUILD 2023-05-23 14:21:17.569868489 +0200
+++ b/PKGBUILD 2023-05-23 14:18:54.134365754 +0200
@@ -137,6 +137,7 @@
export CFLAGS="${CFLAGS/-fstack-protector-strong/}"
export CXXFLAGS="${CXXFLAGS/-fstack-protector-strong/}"
fi
+export CFLAGS+=' -D_LARGEFILE64_SOURCE'
# keep using xz-compressed packages, because one use of the package is to
# recover on systems with broken zstd support in libarchive
Same as gpgme: Fix with with largefile support
Also see Q: Do I need to define _LARGEFILE64_SOURCE to get 64bit off_t?
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
Pre compiled binaries
https://pkgbuild.com/~morganamilo/pacman-static/x86_64/bin/