next steps


it looks like the OpsTools SIG was approved[1]. *yay*!

So, the next steps should be to create a build target, tags.
I would like to rebuild or to retag builds already built
under a tag of the cloud SIG.

What would be the preferred way here? Rebuild? Just tag?


[1] <a href="" title=""></a>


Re: [opstools] next steps

By =?ISO-8859-1?B?... at 06/29/2016 - 10:34

2016-06-29 14:15 GMT+02:00 Matthias Runge <>:

I'd recommend to mass-retag existing builds, no need to rebuild everything.
As for common, I'd be ok to discuss moving it into a more neutral namespace.

Re: [opstools] next steps

By Rich Megginson at 06/29/2016 - 09:10

On 06/29/2016 06:15 AM, Matthias Runge wrote:
We probably need to rebuild. That means starting with the lowest level
dependencies and working our way up.

Is there some way to track down a top level package and all of its
dependencies? For example, if we want to copy fluentd into the opstools
channel/target/buildroot/whatever, is there some way to identify all of
its dependencies, and all of the dependencies' dependencies, etc.?

Re: [opstools] next steps

By =?ISO-8859-1?B?... at 06/29/2016 - 10:35

2016-06-29 15:10 GMT+02:00 Rich Megginson < ... at redhat dot com>:
You can also use repoclosure from yum-utils to check if the CBS
generated repo contains all its runtime dependencies.

Re: [opstools] next steps

By Troy Dawson at 06/29/2016 - 09:20

fluentd-0.12.20 requires

As for their dependants, I'll let ya'll figure it out.

On Wed, Jun 29, 2016 at 8:10 AM, Rich Megginson < ... at redhat dot com> wrote:

Re: [opstools] next steps

By Rich Megginson at 06/29/2016 - 09:37

On 06/29/2016 07:20 AM, Troy Dawson wrote:
I'm assuming we already have all of these packages in the cloud sig
opstools tag/target?