Question on Upgrading Alpine
I asked this question here already (sort of) and then closed the issue after @kdaudt replied, but its been bugging me so I figured I would ask again because I feel like I'm missing something.
The question is on the timing between a new Alpine release version being tagged, the install media being generated and posted, the release announcement going out, and the package versions available in the repo mirrors. If you are upgrading with apk from a package mirror, should you wait until the APKINDEX version matches the release version you are upgrading to or does it not matter?
For the 3.16.2 release, I upgraded fairly quickly after the announcement was made. I haven't looked at all the timestamps involved but I think several hours had passed since the release announcement was posted and install media was already available for download. When I ran apk update
though I saw:
v3.16.1-127-gf8694ded81 [http://dl-cdn.alpinelinux.org/alpine/latest-stable/main]
v3.16.1-124-gf7c5296ed8 [http://dl-cdn.alpinelinux.org/alpine/latest-stable/community]
The APKINDEX files were still showing a prefix of 3.16.1. This was the first time I'd upgraded so soon after a release so I'd never seen that before.
A bit later the main version bumped but community was still behind:
v3.16.2-1-g8ffafa0894 [https://dl-cdn.alpinelinux.org/alpine/latest-stable/main]
v3.16.1-124-gf7c5296ed8 [https://dl-cdn.alpinelinux.org/alpine/latest-stable/community]
They now report:
v3.16.2-12-g0a9ad186b5 [https://dl-cdn.alpinelinux.org/alpine/latest-stable/main]
v3.16.2-15-g12d312ed6e [https://dl-cdn.alpinelinux.org/alpine/latest-stable/community]
So should you apk update
first, make sure the repo index versions match the release number and only then apk upgrade --available
? If so, I haven't seen that documented anywhere?