Repository navigation
Bump Alpine version 3.24.3 → 3.24.4 - #151
Conversation
|
New aports tag does not exist yet. Note that none of this really matters as the build pulls everything from the apk repos. So it will have the new version, if it has been released to apk, regardless of which version of the build script from apk is being used. We are not rebuilding the kernel or the packages. |
|
What can we do now to pull in the "*sshole" (https://sshhole.com) fix? |
|
The tag exists on their gitlab https://gitlab.alpinelinux.org/alpine/aports/-/tags/v3.24.4 , but apparently not synced to github yet |
|
We should probably just wait a couple of hours to see if the tag has synced by then. It is still very new. We can also just create a new tag on the repo, which will trigger a new build. It will have the updated package, but still be named 3.24.3, which is not ideal. So this should only be a fallback if the tag doesn't appear soon. Or we could switch the aports submodule to gitlab? |
|
The mirroring from GitLab seems to be stuck. Normally each push is mirrored directly, but GitHub hasn't been updated in 8 days now, so unless somebody unblocks it, nothing will happen. So we should pick one of the fallbacks: (a) rebuild with the fixed package, but a 3.24.3 name, or (b) move the submodule to GitLab. |
Done |
Switch from the mirror https://github.com/alpinelinux/aports.git to the upstream https://git.alpinelinux.org/aports.git as the GitHub mirror is out of sync. Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
What This PR Changes
The title explains
Linked Issue (Required in most cases)
https://alpinelinux.org/posts/alpine-3.21.10-3.22.8-3.23.8-3.24.4-released/
How I Tested This
CI will test this
AI Usage
NONE