koji

#4227 koji 1.35: blocking a package from a tag does not seem to cause newRepo tasks
Closed: Dropped by mikem. Opened by decathorpe.

Closed: Dropped
Reopen Issue

As far as I can tell, a package getting blocked from a tag (i.e. package retirement) does not cause a newRepo for that tag.

There's doesn't seem to be a way to actually cause a newRepo to happen for that tag manually for the sole purpose of wanting that package removed from the repository (or any tags that inherit from the tag in which the package was blocked) - since both koji wait-repo <tag> and koji wait-repo <tag> --request don't seem to do anything unless given an explicit --build <build> argument. But in the case of a blocked / removed package, giving that argument is impossible. (see also https://pagure.io/koji/issue/4226)

So as far as I can tell, it's currently not possible to manually trigger newRepo tasks after a package removal.

With on-demand regens, tag changes like this do not automatically trigger a regen. If you have just made a change to a tag, you can request a current updated repo by running koji request-repo --current.

You can also get a build to do this step for you by passing --wait-repo to the build command.

koji wait-repo and koji wait-repo --request don't seem to do anything unless given an explicit --build

Ah, it seems the wait-repo rewrite waits for a valid repo, but not necessarily a current repo. The old one did always wait for a regen even if there was already a repo. I'll get a fix for that. In the meantime, koji request-repo --current --wait should do essentially the same thing.

Metadata Update from @mikem:
- Custom field Size adjusted to None

In the meantime, koji request-repo --current --wait should do essentially the same thing.

Thank you, this seems to be a good workaround for now.

I've filed #4228 to make the wait-repo command work more like it used to. I've also filed issue #4229 for this specific aspect of your issue.

Zooming out, the subject "blocking a package from a tag does not seem to cause newRepo tasks" is not something we can fix without essentially nullifying on-demand repos. That said, blocking a package (or any other tag change) will eventually lead to a regen if there is a demand for it (e.g. a build or direct request).

further reading: https://docs.pagure.org/koji/repo_generation/

I skimmed the new docs last week before 1.35 was deployed on Fedora infra :)

Thank you for filing a separate issue and the quick fix in the linked PR!

Feel free to close this particular issue as "can't / won't fix" then.

Metadata Update from @mikem:
- Issue close_status updated to: Dropped
- Issue status updated to: Closed (was: Open)

Commit 9b08aad4 relates to this ticket

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/koji/koji/issues/4227

Please continue any further discussion there.
Metadata
None
None
None
None
Low
None
Related Pull Requests
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.