On Thu, Jul 11, 2024 at 03:45:35PM -0700, Kevin Fenzi wrote: > On Thu, Jul 11, 2024 at 10:55:03PM GMT, Jan Pazdziora wrote: > > > > But when I run the scratch build, I still get the latest greatest > > build from f40-updates. So it seems tagging into my child tag (target) > > does not "override" the build seen, I still get newer build from the > > parent tags. > > Did you wait for the next newrepo? > It's not instant. You have to tag the package and wait-repo for the next > newrepo for that sidetag.
I thought I did but apparently I did not. When I tried the same scratch-build now, it got the dependency package in the desired version. > > How can I stop any newer build of that package to propagate from > > f40 (or f40-updates) to my side tag and force the old build I need > > to take precedence? > > You shouldn't need to, koji doesn't know anything about 'versions'. It > only knows what is the most recently tagged in build of that package. Great, that's how I remembered it from my past. Thanks for the confirmation and for your help. -- Jan Pazdziora | OpenShift AI | Red Hat -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
