Previously when we run $ koji edit-tag-inheritance f32-updates-candidate f32-updates it will set f32-updates as the parent of f32-updates-candidate but now its failing with
$ koji edit-tag-inheritance f32-updates-candidate f32-updates
f32-updates
f32-updates-candidate
$ koji edit-tag-inheritance f32-updates-candidate f32-updates No inheritance link found to remove. Please check your arguments
I guess the intermittent solution is to remove the current inheritance and add it again with new parent.
But it would be nice to have the functionality back.
edit-tag-inheritance is to edit the existing inheritance config. The error indicates that f32-updates is not the parent tag of f32-updates-candidate
edit-tag-inheritance
So the right command is add-tag-inheritance.
add-tag-inheritance
Does that make sense to combine those 2 commands or make them more tolerant?
@mikem @tkopecek ?
Metadata Update from @julian8628: - Custom field Size adjusted to None
I don't think, it ever worked this way (at least this codepath is not touched for three years). If we want to to behave like this, it means adding new options brew edit-tag-inheritance tag parent --replace new_parent as cuurent parent is only to identify one of the parents on same inheritance level, like in the following example:
brew edit-tag-inheritance tag parent --replace new_parent
parent
$ koji list-tag-inheritance f30-minimal-build-side-150 f30-minimal-build-side-150 (150) .... ├─f30-minimal-build (99) .... └─f30-build (92) # what should be meaning of this? Which parent should be replaced? $ koji edit-tag-inheritance f30-minimal-build-side-150 new_parent
@mohanboddu it can be tricky to set up tag inheritance. Have you seen https://github.com/ktdreyer/koji-ansible ? You can use the koji_tag Ansible module to define your tag inheritance declaratively.
koji_tag
Metadata Update from @mikem: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
This issue has been migrated to Fedora Forge: https://forge.fedoraproject.org/koji/koji/issues/2007
Please continue any further discussion there.