musl 1.2
[ci skip]
- I tested the changes in this PR: yes
- I built this PR locally for my native architecture, (x86_64-musl)
- keeping the large-file patch, for now
- requires changes to xbps, along the lines of https://github.com/void-linux/xbps/pull/331 (or some other solution)
- remove configure args for 2038 for 32bit in coreutils, tar, dnsdist
abiwordopencolladaneed updated patches
ref for self:
for a in cross-aarch64-linux-musl cross-arm-linux-musleabi cross-arm-linux-musleabihf cross-armv7l-linux-musleabihf cross-i686-linux-musl cross-mipsel-linux-musl cross-mipsel-linux-muslhf cross-mips-linux-musl cross-mips-linux-muslhf cross-powerpc64le-linux-musl cross-powerpc64-linux-musl cross-powerpcle-linux-musl cross-powerpc-linux-musl cross-x86_64-linux-musl cross-riscv64-linux-musl; do
sed -i s/1.1.24/1.2.4/ srcpkgs/$a/template
sed -i s/1370c9a812b2cf2a7d92802510cca0058cc37e66a7bedd70051f0a34015022a3/7a35eae33d5372a7c0da1188de798726f68825513b7ae3ebe97aaaa52114f039/ srcpkgs/$a/template
xrevbump "bump musl version" $a
done
Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.
Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.
Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.
Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.
Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.