debian 11 bullseye has had its 5th birthday, meaning we should switch away.
Migrating to debian 12 bookworm is most likely trivial, however it is a user-facing breaking-change as it bumps the minimum supported target system. (e.g. the required glibc version needed at runtime)
|
# Note: we deliberately use an old Debian stable as base image. |
|
# from https://docs.appimage.org/introduction/concepts.html : |
|
# "[AppImages] should be built on the oldest possible system, allowing them to run on newer system[s]" |
|
|
|
FROM debian:bullseye@sha256:cf48c31af360e1c0a0aedd33aae4d928b68c2cdf093f1612650eb1ff434d1c34 |
This is the reason why the CI builds are failing:
https://github.com/spesmilo/electrum/actions/runs/34180978591/job/101919865769#step:5:68
1.607 E: Release file for http://deb.debian.org/debian-security/dists/bullseye-security/InRelease is expired (invalid since 5h 29min 42s). Updates for this repository will not be applied.
We can probably apply a quick fix for the build script as workaround for the time being.
debian 11 bullseye has had its 5th birthday, meaning we should switch away.
Migrating to debian 12 bookworm is most likely trivial, however it is a user-facing breaking-change as it bumps the minimum supported target system. (e.g. the required glibc version needed at runtime)
electrum/contrib/build-linux/appimage/Dockerfile
Lines 1 to 5 in 722f702
This is the reason why the CI builds are failing:
https://github.com/spesmilo/electrum/actions/runs/34180978591/job/101919865769#step:5:68
We can probably apply a quick fix for the build script as workaround for the time being.