Dne 09. 01. 23 v 7:38 Thorsten Leemhuis
napsal(a):
That made me remember the biggest showstopper: I regularly push the results of one build to two different repositories (which ones depends on the phase of the kernel devel cycle and if Fedora is shipping the latest stable series). To explain: currently I build one vanilla mainline package (6.2-rc...) and push it to the kernel-vanilla-mainline and kernel-vanilla-mainline-wo-mergew repos (rpms hardlinked of course). But within the merge window (e.g. after 6.1 was released and before 6.2-rc1 came out) I didn't do that; back then I pushed the latest stable releases to the kernel-vanilla-stable and kernel-vanilla-mainline-wo-mergew repos, as some people want to avoid mainline builds during that phase (even some kernel devs are careful with mainline builds during that time frame). And right now kernel-vanilla-stable and kernel-vanilla-fedora ship different builds (6.1.y and 6.0.y to be precise); but that will change again in a few days, when Fedora will jump to 6.1 in updates-testing, then those repos will start shipping the same packages again. See https://fedoraproject.org/wiki/Kernel_Vanilla_Repositories#Configure_the_repositories to get a brief idea. I assume that's not possible with copr, unless I build everything twice I now simply hardlink. Which would require quite a build of compute time and storage space without a strong reason.
1) Create project "kernel-vanilla-mainline" in Copr
2) Create project "kernel-vanilla-mainline-wo-mergew" in Copr and in settings set:
* external repositories: copr://user/kernel-vanilla-mainline
* : copr://user/kernel-vanilla-mainline
3) When you build into "kernel-vanilla-mainline" then the build will be available in both repositories. Available both as build requires and even as run-time because:
4) when you run 'dnf copr enable kernel-vanilla-mainline-wo-mergew" then it will enable "kernel-vanilla-mainline" too. So all build from both project will be available for users of "kernel-vanilla-mainline-wo-mergew"
Miroslav
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-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/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
