Getting opstools content to mirror.c.o


what's the process to get the opstools content released for testing
purpose on buildlogs.c.o over to a more "official" location on
the mirrors? What do we need to do to get rpms signed there?



Re: [opstools] Getting opstools content to mirror

By Brian Stinson at 01/25/2017 - 06:00

On Jan 25 10:17, Matthias Runge wrote:
Make sure you build a release package with the corresponding repo files,
and open a bug for us, the directory on mirror.c.o corresponds to your
SIG shortname (e.g.: opstools). Details here:

<a href="" title=""></a>


Re: [opstools] Getting opstools content to mirror

By Matthias Runge at 01/25/2017 - 06:18

On Wed, Jan 25, 2017 at 04:00:47AM -0600, Brian Stinson wrote:
Thank you!

Building a centos-release-* package is something like a
hen-and-egg-problem: You need to know the location where it's going
to be distributed to be able to build a config for it, providing that
exact unknown location.

What should I put in for opstools in this case?

There is a centos-release-opstools package currently included in the
testing repo on buildlogs.c.o. Upstream source is here[1].

<a href="" title=""></a>
be an appropriate (and available) location?

Who would take care of signing those rpms? Who would create the key?
Do we sign content from SIGs at all?


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

Re: [opstools] Getting opstools content to mirror

By Fabian Arrotin at 01/25/2017 - 06:39

On 25/01/17 11:18, Matthias Runge wrote:
Yes, and aligned with the other SIGs

Nope, key and signing isn't done by SIGs at all.
The process is to create that bug report (assigned to KBsingh), then
from his side a key will be created (it it doesn't exist yet) and used
to pull/sign/push packages to