On Wed, Apr 14, 2021 at 1:47 PM Thorsten Leemhuis <fedora@xxxxxxxxxxxxx> wrote: > > > On 14.04.21 10:45, Tomas Tomecek wrote: > > Good morning, I'd like to announce the creation of Fedora Source-git SIG: > > https://fedoraproject.org/wiki/SIGs/Source-git > > > > Our main goal in the SIG right now is to establish a development > > workflow for Fedora Linux packages using repositories with sources and > > upstream history (this is what we call source-git), instead of just > > distribution files with links to tarballs (dist-git). > > Just wondering: will there be some coordination with the Fedora kernel > developers that are relying on a git based workflow since a few > weeks now (for rawhide even longer)? > > To those who don't know: all the stuff in dist-git kernel is > generated from https://gitlab.com/cki-project/kernel-ark these days > afaik, so it might be wise to make sure the solution you work out works > for them as well. Especially as I find find some parts of how they do it > a bit questionable. The main tarball they use as Source0 for example > doesn't match the tarball downloadable from kernel.org(¹); all the > patches are stashed into one(²); patches for fedora specific stuff (like > the configs needed for building the kernel) are in the same branch as > the patches(³). I think that makes things quite confusing, especially > for outsiders. Sometimes I wonder if some of what the kernel people do > violates the Fedora Packaging Guidelines(⁴), but the kernel-ark people > ensured me it's fine. > > CU, knurd > > (¹) > https://src.fedoraproject.org/rpms/kernel/blob/f33/f/sources for example > states: > > SHA512 (linux-5.11.14.tar.xz) = ccf0eaf6df0dacd2984c361621f67a3d16cf7a7174155ebdf646f1acfec43e19ff942e6c17e5bc3b5dc7a300c32bdc6ee37877162c099f5bd9924244f9445467 > But: > $ wget --quiet > https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.11.14.tar.xz > $ sha512sum linux-5.11.14.tar.xz > 8dfc7ff184e5cb33fff74686071f1605f3a834669e201d272f3047aa00657339ec1a3cfd605d8761b8a0f335b8488c02c701e72ed30031856e9c154aa1ff2d88 > linux-5.11.14.tar.xz > likely different compression options used by default, the upstream tarball is just a bit smaller. We create the tarballourselves, but based on greg's tag. If you explode and compare them, they are identical: fedora64:[~/srcchk]>diff -ruNp stable-5.11.14/ ark-5.11.14/ fedora64:[~/srcchk]>ls -l *5.11.14.tar.xz -rw-rw-r--. 1 jforbes jforbes 123313416 Apr 15 12:38 ark-5.11.14.tar.xz -rw-r--r--. 1 jforbes jforbes 117651976 Apr 15 12:42 linux-5.11.14.tar.xz For what it's worth, until they changed compression, we used to recompress the upstream tarball and end up with a similar result. As to your (*) they are tagged in the git tree, you can verify that tag in our clone of the upstream tree, or directly in the upstream tree if you wish, both audit sources are available. As to the single patch vs the broken out, it is a matter of git merge vs git rebase. If we did a rebase with every release, they could be broken out cleanly, but the trade off is any update becomes a forced update, and any pending MR is invalidated. We do rebase the patches on the creation of stable branches, so fedora-5.11 was created by rebasing the rawhide branch over Greg's linux-5.11.y branch. It is merged forward from there, but none of the patches should be too different to quickly figure out. > > (²) > https://src.fedoraproject.org/rpms/kernel/blob/f33/f/patch-5.11-redhat.patch > FWIW, links to the individual patches can be found here: > https://src.fedoraproject.org/rpms/kernel/blob/f33/f/Patchlist.changelog > > (³) for example > https://gitlab.com/cki-project/kernel-ark/-/commits/fedora-5.11 > > (⁴) like this part "sources used to build a package should be the > vanilla sources available from upstream. To help reviewers and QA > scripts verify this, the packager needs to indicate where a reviewer can > find the source that was used to make the rpm". The quote is from here: > https://docs.fedoraproject.org/en-US/packaging-guidelines/SourceURL/ > _______________________________________________ > 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 _______________________________________________ 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
