On Mon, May 29, 2017 at 10:15 AM, Matthias Runge mrunge@redhat.com wrote:
On Fri, May 26, 2017 at 07:55:32AM -0600, Rich Megginson wrote:
On 05/26/2017 02:59 AM, Sandro Bonazzola wrote:
Hi, I just discovered we have an issue with the package tagging about
fluentd.
fluentd-0.12.26-2.el7
$ cbs list-tags |grep opstool|grep release opstools7-common-release opstools7-elastic-2-release opstools7-elastic-common-release
We should get rid of these elastic tags, or at least ignore them, and if there are any packages that we need in those tags, we should add them to fluentd-012.
opstools7-fluentd-012-release opstools7-perfmon-common-release opstools7-sensu-023-release opstools7-sensu-027-release opstools7-sensu-common-release
can we review the mappings in order to get fluentd packages correctly published? Personally I would be happy if fluentd and collectd can be in their own repo so they won't require openstack as dependency repo.
Packages tagged and not landing somewhere is unfortunate and should be sorted out. Unfortunately, that is nothing we can do, that is something for CentOS infra folks.
Well, we need to tell CentOS infra folks which tags should be published and where :-) So, I can open a ticket for adding the mappings for fluentd-012 tags, where the packages should land?
https://buildlogs.centos.org/centos/7/opstools/$basearch/fluentd/ ? guessed above because on mirrors we have: http://mirror.centos.org/centos/7/opstools/x86_64/fluentd/
I'm fine with getting rid of opstools7-elastic-* tags, we don't use them anymore and afaik, we won't do in the future.
Ok, so if nobody objecting, I'll open a ticket tomorrow morning for removing those tags from cbs.
A while ago, we moved the packages relying on openstack packages to the cloud sig, and cremoved the dependency of openstack from opstools. Unfortunately, the resulting centos-release-opstools build[1] was not tagged and pushed correctly.
now tagged correctly, not yet in http://mirror.centos.org/centos/7/extras/x86_64/Packages/ but should be just a matter of sign and publish which should hopefully happen soon.
-- Matthias Runge mrunge@matthias-runge.de