From: Thorsten Leemhuis on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3884#note_2549958821 CCing @dzickusrh @scweaver and @agruenba JFYI, @dzickusrh and me yesterday at Flock talked about about how to handle situations like this (spec file changes that depend on upstream changes) more elegantly in the future, as having os-build broken for so long is kinda contrary to the "always" the "a" in "ark" stands for – and also creates problems for developers, as @agruenba's comment https://gitlab.com/cki- project/kernel-ark/-/merge_requests/3898#note_2543917925 shows. I thought about this. There is no elegant solution, but I guess the ifdefery solution briefly outlined above might in the end be the best. So I guess if a similar situation arises in the future I will submit a change that will use that trick. -- _______________________________________________ kernel mailing list -- kernel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kernel-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/kernel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
