dustymabe added a new comment to an issue you are following:
@dustymabe The reason why I thought inheritance is, you dont need to
add packages multiple times. Once you add the package to coreos-release they will be
available for all other tags. And you can compose either from coreos-release or
Now that I am thinking out loud, coreos-pool will pick all the builds
in coreos-release, which I think might not be desirable. Can you confirm this and I can
remove the inheritance between coreos-pool and coreos-release.
We aren't planning on composing from `coreos-release`. Just from `coreos-pool`. The
rationale for the need for `coreos-release` is in my earlier
comment](https://pagure.io/releng/issue/8294#comment-567284). Yes, please remove the
inheritance. Also note that we only need one distrepo set up and that is against
But I think we should leave the coreos-pool and
fxx-coreos-signing-pending inheritance as it is, since you can add a package to
coreos-pool and it will be available in fxx-core-signing-pending and if they are separate
you need to add the package to both tags and also we need to change koji hub permissions
as well. Since fxx-coreos-signing-pending is just a holding tag, it wont be of a problem.
My understanding is that the package goes to `fxx-coreos-signing-pending` when it is built
and then robosig moves it to `coreos-pool` when the package has been signed. I don't
think we need inheritance there? What would be the benefit?
To reply, visit the link below or just reply to this email