<feed xmlns='http://www.w3.org/2005/Atom'>
<title>buildbot/docker/buildmaster/patches, branch v28</title>
<subtitle>LEDE buildbot configuration</subtitle>
<id>https://git.openwrt.org/buildbot/atom?h=v28</id>
<link rel='self' href='https://git.openwrt.org/buildbot/atom?h=v28'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/buildbot/'/>
<updated>2026-11-01T10:06:34Z</updated>
<entry>
<title>buildmaster: build apk 3.0.5 from the OpenWrt sources mirror</title>
<updated>2026-11-01T10:06:34Z</updated>
<author>
<name>Petr Štetiar</name>
</author>
<published>2026-10-28T06:23:05Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/buildbot/commit/?id=a8f4ec77d05f047bf182667415552e6d82eba417'/>
<id>urn:sha1:a8f4ec77d05f047bf182667415552e6d82eba417</id>
<content type='text'>
Bump apk-tools from a 2024 pre-release commit to 3.0.5, the version that
OpenWrt main and openwrt-25.12 pin. scripts/signall.sh signs releases
with this binary (apk adbsign), so it should match what OpenWrt builds.

Fetch the release tarball from sources.openwrt.org and check its sha256,
instead of cloning gitlab.alpinelinux.org, which is not always reachable.
Build it with meson as a static musl binary, because the final image is
Debian (glibc).

Apply OpenWrt's patch "crypto_openssl: use deterministic ECDSA
signatures" (OpenWrt commit e923974fc172). With it, signing the same
data twice gives identical bytes, instead of a different signature each
time from a random ECDSA nonce.

Update the cram test for the new usage line of apk 3.0.5.

Signed-off-by: Petr Štetiar &lt;ynezz@true.cz&gt;
Link: https://github.com/openwrt/buildbot/pull/84
Signed-off-by: Christian Marangi &lt;ansuelsmth@gmail.com&gt;
</content>
</entry>
</feed>
