Learn more about these different git repos.
Other Git URLs
When users run koji list-tagged --inherit --latest <tag> <package> on a tag with many parents, it is not immediately obvious how Koji chose the "latest" ​build. It can be confusing to understand what is going on when one parent with a high priority has an older NVR than a parent with a lower priority.
koji list-tagged --inherit --latest <tag> <package>
Please consider adding a --explain flag to list-tagged that would give a human readable description, like:
--explain
list-tagged
Build X is tagged in Y tag because <user> tagged it into into Z tag on <timestamp>
Maybe with pointers to koji list-history and koji list-tag-inheritance as well.
koji list-history
koji list-tag-inheritance
While I'm all for helping users understand what Koji is doing, I'm not sure the proposed output will help much. It might be better to provide a clear doc and link it in the usage text.
Metadata Update from @mikem: - Custom field Size adjusted to None
Metadata Update from @tkopecek: - Issue set to the milestone: 1.28 - Issue tagged with: doc
This user suggestion came from another user actually.
I suspect that person was thinking of how kubectl explain provides some built-in help for the various resources in a cluster.
kubectl explain
Metadata Update from @tkopecek: - Issue set to the milestone: 1.29 (was: 1.28)
Metadata Update from @tkopecek: - Issue set to the milestone: None (was: 1.29)
Login to comment on this ticket.