On Tue, May 31, 2022 at 3:12 AM Laszlo Ersek <lersek@xxxxxxxxxx> wrote: > > On 05/31/22 08:58, Dan Horák wrote: > > On Tue, 31 May 2022 08:39:28 +0200 > > Laszlo Ersek <lersek@xxxxxxxxxx> wrote: > > > >> Hi, > >> > >> where can I find the exploded git tree for "kernel-5.17.4-200.fc35"? > >> > >> The tree at > >> <https://git.kernel.org/pub/scm/linux/kernel/git/jwboyer/fedora.git> is > >> no good; it does not have tags beyond .fc33. > > > > Fedora kernels now live in the https://gitlab.com/cki-project/kernel-ark > > project, the particular one should be in > > https://gitlab.com/cki-project/kernel-ark/-/tree/kernel-5.17.4-0 > > Thanks! > > This is a very strange practice -- the RPM NVR is "5.17.4-200.fc35", but > the exploded git tag does not have "200.fc35" in the name anywhere. > Additionally, dist-git commit c8aa1cc125eb ("kernel-5.17.4-0", > 2022-04-20) on the "f35" branch does not imply "200" by any means > either, I need to look into the spec file (in both git repos -- exploded > and dist-git) to see "%define pkgrelease 200". I'd say that's a pretty > cumbersome way for anyone to associate an actual kernel RPM and/or > "uname -r" output with a particular git checkout. > It actually makes sense pretty well because the dist-git are generated by "make dist-git' with some options. In particular, Fedora 34/35/and 36 are all built from the exact same dist-git commit. Typically there is no difference between them at all other than the "release" which is currently 100 for F34, 200 for F35, and 300 for F36. The -0 represents the last digit, so if I did a 5.17.4-201.fc35, it would map to a 5.17.4-1 release tag. In your case here, kernel-5.17.4-0 was the commit used to build kernel-5.17.4-100.fc34, kernel-5.17.4-200.fc35, and kernel-5.17.4-300.fc36. The redhat/release_targets file will say which releases are currently supported by the branch. Now, we are in a slightly odd setup where Fedora 36 has some differences, though they are all in the config. In this case, redhat/patches/0001-Revert-SimpleDRM-changes.patch is applied before generating dist-git for F34 and F35. I should add the script used to convert to dist-git to the tree (and will do so after this response as redhat/fedora-stable-release.sh) It just iterates over redhat/release_targets and runs 'make IS_FEDORA=1 DIST=".fc$release" BUILDID="" BUILD=$build RHDISTGIT_BRANCH=f$release dist-git;' for each one. The build to release mapping happens in script. Justin _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
