Arch Linux User Repository

• gpg-error to 1.59
• removed c-ares

@ulidtko: thanks, bumped zlib to 1.3.2.

Hi Andreas! FYI, https://zlib.net/ gives 404 on zlib-1.3.1.tar.gz -- since very recently, I believe.

So, pacman-static does not install. Trivial patch though:

diff --git i/PKGBUILD w/PKGBUILD
index 52229df..e597534 100644
--- i/PKGBUILD
+++ w/PKGBUILD
@@ -8,7 +8,7 @@ _cares_ver=1.34.6
 _nghttp2_ver=1.68.0
 _curlver=8.18.0
 _sslver=3.6.1
-_zlibver=1.3.1
+_zlibver=1.3.2
 _xzver=5.8.2
 _bzipver=1.0.8
 _zstdver=1.5.7
@@ -102,7 +102,7 @@ sha512sums=('512c5096c82e00730c884e5d4d452928a66d35b42a831a2b4b8b17af9215140d6b2
             'SKIP'
             'b1873dbb7a49460b007255689102062756972de5cc2d38b12cc9f389b6be412da6797579b1acd3717a8cd2ee118fd9801b94e55f063d4328f050f0876a5eb53c'
             'b5887ea77417fae49b6cb1e9fa782d3021f268d5219701d87a092235964f73fa72a31428b630445517f56f2bb69dcbbb24119ef9dbf8b4e40a753369a9f9a16f'
-            '580677aad97093829090d4b605ac81c50327e74a6c2de0b85dd2e8525553f3ddde17556ea46f8f007f89e435493c9a20bc997d1ef1c1c2c23274528e3c46b94f'
+            '70963771ea5d763614278a69b474f09b7d237ef8f53b675a10fe31d9923aeef601504b35d7ebd1b1e7f347e9ebb048e6b3b47fffdf137e7bdc7e8d5eb4ec4692'
             'SKIP'
             '328fe243e5701ac8216d21168a9e17ea9475cc08b27659c18b68230d8ddd0fffa9f831c576b08c160774fe2c4795604f82b64113e7f84db417b4bd26a4dae2c1'
             '083f5e675d73f3233c7930ebe20425a533feedeaaa9d8cc86831312a6581cefbe6ed0d08d2fa89be81082f2a5abdabca8b3c080bf97218a1bd59dc118a30b9f3'

There is a comment in the PKGBUILD, that c-ares is needed for static builds, so let's leave it in, but keep curl using the threaded resolver (as in pkver=4), as this seems to work.

aha, cool. So it is the resolver. What I don't yet understand is, c-ares was used in pacman-static, but has not been used in curl upstream since 2011. I'll remove it next time, every dependeny less is a good dependency. :-)

Thank you, Andreas, pacman-static 7.1.0.r9.g54d9411-4 solves it.

Thank you for your efforts, Andreas. :) Regards, Ralf

Update:

I made a change in the wiki:

https://wiki.archlinux.org/index.php?title=Pacman&oldid=865179

Interestingly, pacman-static --version Pacman v6.0.1 - libalpm v13.0.1 from the link works for me, while aur/pacman-static 7.1.0.r9.g54d9411-3 still does not work. So far, I have not built pacman-static in a clean chroot.

I think I found the problem. c-ares is built with configure, that requires the autoreconf -fi script to be run before to even get the configure from configure.ac. As it is now, configure should bail out in the build, but somehow just is silently ignored? I could build it diretly also with cmake (as the upstream c=cares package is doing it).

I'm currently synching the PKGBUILDs of all packages with the local ones in pacman-static (config options, RISCV64), etc. just to make sure the differences are as small as possible.

I don't want pacman-static to become sick from "feature creep", but maybe those libraries from upstream should also be built into pacman-static (opinions?):

• libidn2 (pacman mirrors don't really use punny-code)
• libngtcp2 (probably not)
• libnghttp3 (if pacman mirrors are on HTTP/3 maybe)
• enable-ktls in openssl, requires newer kernels, so maybe not enable it right
  now
• --enable-ipv6: probably a good idea, might be enabled by default anyway

I ran pacman-static twice in a row, once without and once with "domain localdomain" in /etc/resolv.conf. It works without "domain localdomain". To me, however, it doesn't look like a solution at first glance, but merely a reference to whatever.

Update: This does not actually solve the problem, see https://bbs.archlinux.org/viewtopic.php?pid=2287041#p2287041 .