Hello,
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?
Best, Matthias
[1] https://wiki.centos.org/SpecialInterestGroup/OpsTools
On 06/29/2016 06:15 AM, Matthias Runge wrote:
Hello,
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?
Best, Matthias
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.?
fluentd-0.12.20 requires
rubygem-cool.io rubygem-http_parser.rb rubygem-msgpack rubygem-sigdump rubygem-string-scrub rubygem-thread_safe rubygem-tzinfo rubygem-tzinfo-data rubygem-yajl-ruby systemd
As for their dependants, I'll let ya'll figure it out.
On Wed, Jun 29, 2016 at 8:10 AM, Rich Megginson rmeggins@redhat.com wrote:
On 06/29/2016 06:15 AM, Matthias Runge wrote:
Hello,
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?
Best, Matthias
[1] https://wiki.centos.org/SpecialInterestGroup/OpsTools
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.?
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 06/29/2016 07:20 AM, Troy Dawson wrote:
fluentd-0.12.20 requires
rubygem-cool.io rubygem-http_parser.rb rubygem-msgpack rubygem-sigdump rubygem-string-scrub rubygem-thread_safe rubygem-tzinfo rubygem-tzinfo-data rubygem-yajl-ruby systemd
As for their dependants, I'll let ya'll figure it out.
I'm assuming we already have all of these packages in the cloud sig opstools tag/target?
On Wed, Jun 29, 2016 at 8:10 AM, Rich Megginson rmeggins@redhat.com wrote:
On 06/29/2016 06:15 AM, Matthias Runge wrote:
Hello,
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?
Best, Matthias
[1] https://wiki.centos.org/SpecialInterestGroup/OpsTools
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.?
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
2016-06-29 15:10 GMT+02:00 Rich Megginson rmeggins@redhat.com:
On 06/29/2016 06:15 AM, Matthias Runge wrote:
Hello,
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?
Best, Matthias
[1] https://wiki.centos.org/SpecialInterestGroup/OpsTools
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.?
You can also use repoclosure from yum-utils to check if the CBS generated repo contains all its runtime dependencies.
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
2016-06-29 14:15 GMT+02:00 Matthias Runge mrunge@matthias-runge.de:
Hello,
it looks like the OpsTools SIG was approved[1]. *yay*!
Congratulations
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?
Best, Matthias
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.
[1] https://wiki.centos.org/SpecialInterestGroup/OpsTools
Matthias Runge mrunge@matthias-runge.de _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
-
Haïkel -
Matthias Runge -
Rich Megginson -
Troy Dawson