-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
non-tito builds don't contain %{dist} and %{foremandis} macros in SRPM name #318
Comments
The design idea with build SRPM is that it only needs to build the SRPM once and then send that up to Koji or mock. There are two approaches we can take:
|
I think 2 is the cleaner solution given the (now explained and found good) design :) |
@ehelms another interesting side-effect: nightly builds don't have their nightly tag when built from a PR: http://koji.katello.org/koji/buildinfo?buildID=72915 (cc @ekohl ) |
@evgeni This was created back when we used Koji and was primarily a CI issue where the individual jobs per dist were not clear, now with Copr we display it as:
Where the chroot is used for each one from Copr. This would not include the foremandist aspect however. The builds as listed (https://copr.fedorainfracloud.org/coprs/g/theforeman/plugins-nightly-staging/builds/) lack the dist and foremandist because that represents the SRPM that was uploaded. If you think we should still tackle this and ensure it includes dist/foremandist in the SRPM then I'll tackle making this change:
|
I think the display with Copr is sufficiently distinct now, so I'd close this as "not needed anymore". |
theforeman/foreman-packaging#8364 (3.3 tito-based build) links in checks to "koji/rubygem-foreman_webhooks-3.0.4-1.fm3_3.el8.src.rpm"
theforeman/foreman-packaging#8362 (nightly, non-tito) links to "koji/rubygem-foreman_webhooks-3.0.4-1.src.rpm"
This is confusing :)
The text was updated successfully, but these errors were encountered: