Describe the issue Presence of rawhide-repo-holder build target in Koji makes kojira generate repos for rawhide tag, which according to @puiterwijk is not used any longer.
When do you need this? (YYYY/MM/DD) earliest convenience
When is this no longer needed or useful? (YYYY/MM/DD)
If we cannot complete your request, what is the impact? Koji resources are wasted generating unneeded repos.
Well, this was setup long ago to allow people to use 'rawhide' as a target without having to figure out what number it currently is.
I'm not opposed to dropping it, but we should announce that we are doing so.
@kevin This request is not related to rawhide build target.
rawhide target builds from f29-build to f29-pending. It can be used by packagers. Its purpose is allowing packagers building against rawhide without knowing its release number. rawhide build target is not related to rawhide tag.
rawhide-repo-holder is a dummy target. Its source tag is rawhide, which makes kojira keep repos for rawhide tag up-to-date, which is the reason of existence of this build target. AFAIK these repos are not used and @puiterwijk confirmed that on IRC.
rawhide-repo-holder target could theoretically be used by packagers, but only for scratch builds or with --skip-tag, as normal real builds are not possible because dest tag is locked.
--skip-tag
Moreover, existence of repos for rawhide tag confuses some users - they issue commands like koji wait-repo rawhide when they mean koji wait-repo f29-build and then are wondering and asking around why their builds fail.
koji wait-repo rawhide
koji wait-repo f29-build
@kevin ping? I would love to see number of useless jobs to go away so that we can spend resources on something better (like creating an src repo).
ok, I removed it.
Lets see what breaks. ;)
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)