From: Justin Forbes on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/issues/41#note_550913432
There are a couple of things here:
> Fedora RPM tagging in the ARK kernel began in May 2020 for fc33.
This line is not entirely accurate, as ARK was only used for Rawhide
from May of 2020 until the 5.11 rebases happened last month. At that
point, ARK was used for all 5.11.* releases.
They are not tagged differently because they are not different in any
way. The script to do stable releases literally sits on the same commit
(currently in the fedora-5.11 branch) and does:
```
for release in `cat redhat/release_targets`; do
case "$release" in
34) build=300
;;
33) build=200
;;
32) build=100
;;
esac
make IS_FEDORA=1 DIST=".fc$release" BUILDID="" BUILD=$build
RHDISTGIT_BRANCH=f$release dist-git;
done
```
There have been cases where the configs differ across versions, but that
is not currently the case Any time that case does pop up, it will be
notated in redhat/rebase-notes.txt. The source tarball and patch set are
identical as they are built from the same script based on the same
commit on the same branch. The 15 mentioned there is somewhat relevant
in that it is the 15th tagged build of 5.11, but given that we very
rarely do more than one build of a given upstream release, just
searching for 5.11.13 will likely find you the tag you are looking for.
I suppose we could reset that number with every version bump so that it
would match the last digit of BUILD always.
_______________________________________________
kernel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
