Postings by =?ISO-8859-1?B?SC4gR3XpbWFy?=

RDO meeting (2018-12-19) minutes

#rdo: RDO meeting - 2018-12-19

Meeting started by number80 at 15:04:15 UTC.

RDO meeting (2018-12-12) minutes

#rdo: RDO meeting - 2018-12-12

Meeting started by number80 at 15:02:11 UTC.

RDO meeting (2018-11-14) minutes

#rdo: RDO meeting - 2018-11-14

Meeting started by number80 at 15:03:29 UTC. The full logs are
available at
<a href="" title=""></a>

Meeting summary
* roll call (number80, 15:03:40)

* heads up on pcmk2 rpms for OOOCI consumption?

RDO meeting (2018-10-24) minutes

#rdo: RDO meeting - 2018-10-24

Meeting started by number80 at 15:01:23 UTC.

Today's meeting cancelled


nobody else showed up so it's cancelled.

Have a great day!

Reminder meeting on Thursday 3pm UTC


kind reminder that we will hold CentOS Cloud SIG meeting on
#centos-devel on Freenode at 3pm UTC


Reboot weekly Cloud SIG meetings


since we have a newer group (CloudStack) joining us, we decided to
reboot our weekly meetings.
In order to find a timeslot that suits everyone, I suggest that we use
a whenisgood poll:
<a href="" title=""></a>

Please don't forget to set your timezone when answering the poll. I'll
publish results asap


New SIG: OpenStack


I'd like to announce the beginning of a new SIG: OpenStack.

During these last years, I've been more or less maintaining OpenStack
clients, and I'd like to pass over
that (burden) to a SIG.
OpenStack clients/libraries are quite tied to each other, so it is
difficult to maintain them without provenpackager
permissions, and it is also a lot of work to sync requirements, do the

Ceph (alt/multi)arch rebuild


I'm currently trying to enable OpenStack on ppc64le architecture and
it requires Ceph on ppc64le.
So I applied to join to the Storage SIG (sponsor needed!) so I can
help with the Ceph bootstrap and maintenance.


RDO meeting (2016-11-02) Minutes

My bad for sending this late!

#rdo: RDO meeting - 2016-10-02

Meeting started by number80 at 15:00:27 UTC.

Aarch64 bootstrap status


Many thanks to Thomas who spent his evening merging aarch64 builds
(and Fabian for enabling the arch in our CBS tags!)
Here's a summary of the bootstrap:
<a href="" title=""></a>

Erlang and texlive are still building, but the biggest remaining chunk
will be building v8 on aarch64 (and node.js) but overall we're good.
Next steps will be fixing broken builds and proper testing on real hardware.


Bootstrapping a new arch


There was various discussions about enabling aarch64 architecture for
Cloud SIG OpenStack repositories.
And likely others are coming, so I'd like to confirm with a wider
audience about the proper course of action.
So we can document it and share that experience with other SIGs.

Arrfab suggested the following:
* scratch builds with archoverride of existing arch-dependent builds
* ask CBS admin to merge the task with existing builds using mergeScratch.

I find this process simple and efficient, but I'm worried about how it scales.
In my case, I have about 250 binary packages (including the

RDO meeting minutes - 2016-08-24

#rdo: RDO meeting - 2016-08-24

Meeting started by number80 at 15:00:18 UTC.

Broken dependencies in CentOS Extras


while running repoclosure on Cloud SIG repositories, I found out that
cockpit had missing dependencies.

Last metadata expiration check: 0:00:02 ago on Wed Jul 6 19:53:59 2016.
package: cockpit-ostree-0.108-1.el7.centos.x86_64 from centos-extras
unresolved deps:
rpm-ostree-client >= 2015.11-1
package: cockpit-selinux-0.108-1.el7.centos.noarch from centos-extras
unresolved deps:
setroubleshoot-server >= 3.3.3

Could be fine, but it's best to check with you guys.


"Summary/Minutes for today's FESCo meeting (2016-06-24)"

#fedora-meeting: FESCO (2016-06-24)

Meeting started by number80 at 16:00:02 UTC.

"Schedule for Friday's FESCo Meeting (2016-06-24)"

Following is the list of topics that will be discussed in the FESCo
meeting Friday at 16:00UTC in #fedora-meeting on

To convert UTC to your local time, take a look at
<a href="" title=""></a>

or run:
date -d '2016-06-24 16:00 UTC'

Links to all tickets below can be found at:
<a href="" title=""></a>

= Followups =

#topic #1587 Policy regarding packaging when upstream has chosen
inappropriate name for package
.fesco 1587
<a href="" title=""></a>

#topic #1576 Evaluate Workstation graphical upgrade Change status
.fesco 157

status of virt7-docker repository?


I'm considering to add virt7-docker repository as a dependency for the
openstack repo from Cloud SIG.
It seems that it's not consumable yet and some packages like
Kubernetes are outdated.

Could you update me with the current status and if there is anything
we can do to help?


Mitaka stable packaged for RDO


the RDO community has packages available for Mitaka Stable in its
testing repositories.
Official RDO release will be announced after we validate this release
with our CI.


Summary/Minutes for today's FESCo meeting (2016-03-04)

#fedora-meeting: FESCO (2016-03-04)

Meeting started by number80 at 17:00:11 UTC.

Schedule for Friday's FESCo Meeting (2016-03-04)

Following is the list of topics that will be discussed in the FESCo
meeting Friday at 17:00UTC in #fedora-meeting on

To convert UTC to your local time, take a look at
<a href="" title=""></a>

or run:
date -d '2016-03-04 17:00 UTC'

Links to all tickets below can be found at:
<a href="" title=""></a>

= Followups =

#topic 1518 Software packaged in Fedora should not be allowed to
implement DRM schemes that cannot be disabled
.fesco 1518
<a href="" title=""></a>

#topic 1552 Review of delayed Changes for F24
.fesco 1552

Ceph/Storage SIG


In order to be truly independent from EPEL, the Cloud SIG/OpenStack is
looking to consume Ceph from Storage SIG repo.
Seems that the only builds are from oVirt and testing build targets,
so I'd like to confirm what are the plans to deliver Ceph if there are


Unresponsive maintainer procedure for nsjae


I'd like to start the unresponsive maintainer procedure for nsaje.
<a href="" title=""></a>

Nec is a former Red Hat intern and Alan tried to contact him more than
one month ago.
He also requested package ACLs for python-kazoo without any answer.

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

If anyone can contact him I would be grateful.


koji client issue with CBS with python >= 2.7.9


I finally found a workaround to fix CBS issues when using python >=
2.7.9 (like Fedora 22 and above)
<a href="" title=""></a>
Though it's dirty, but it's no different from python 2.7.8 and older behavior.

Starting python 2.7.9, python ssl standard module enable certificate
verification by default, hence causing koji client to fail when
interacting with CBS.
What I do not get is why withe the same koki client I have no issues
with Fedora Koji instance, and why it fails with CBS.
People using F21 and older or CentOS, won't experience that issue.

I suspect either

Converge EPEL and CBS


Since the CentOS acquihire, there was a lot of discussion about EPEL's future.
Since the FOSDEM meetup between Fedora/CentOS folks, there was little
progress on that topic

After a discussion with a Smooge, I decided to come with a proposal,
knowing that
1. Fedora wants to keep EPEL within it umbrella
2. That CentOS SIGs are in practice rebuilding a lot of EPEL packages
(or retag them for other SIGs)
leading to poor maintenance as they don't follow EPEL tickets for all
their dependencies.

Switching to SPDX in license tags


I would like to get feedback from Fedora Legal and also my fellow
contributors about considering

SPDX (Software Package Data Exchange) is a specification hosted by the
Linux Foundation defining
a standard format for communicating components, licenses and
copyrights associated with a software package.
<a href="" title=""></a>

It would make it much easier collaborating with other distributions
and upstream projects.

On a more practical side, it would mean standardizing on SPDX short
identifier to design licenses
and exceptions in all our packages.
<a href="" title=""></a>


Juno/EL6 clients


just to notify you that I finished rebuilding Juno clients on EL6.

They are currently available in a (temporary) repository, you could already test
them by executing the following command:

cat << EOF > /etc/yum.repos.d/cloud6-testing.repo

If you find any EL6 specific issues, please either open a ticket in RDO bugzilla
assigned to hguemar AT redhat DOT com or contacting me directly.

Best regards,

separate targets for Cloud SIG.


While the RDO CI deployment is moving forward, here's an (urgent)
topic to deal with.
We will start importing the next OpenStack release (Kilo) packages and
that requires
having separate targets in CBS since we'd maintain multiple releases who may use
common deps but with incompatible versions.
I suspect that the other cloud projects will have the same issues.

I'd suggest that we put this topic into the next meeting.

cloud7-el7-common (common stuff that are currently in EPEL) => shared
by all projects
inherited by cloud7-el7-<project>-<release>


Governance change for Fedora Project

Dear contributors,

Following the current discussion about governance, a proposal to
change the governance model of the project has been made during the
"Governance for Fedora.Next workshop" in Flock Prague 2014.
We request your feedbacks about before considering its adoption or rejection.

* dissolving the current board
* the board will be replaced by a "community council" (final name to be chosen)
* the community council will be the main governance body of the Fedora
Project, its role will be to define a shared vision accross the
project and the highest decision-making power.

semi-away notice


yesterday, I broke my left arm, so my response time will be
significantly slowed down for about 4 weeks.
I kindly ask my co-maintainers and provenpackagers to look after my
I'll still be around, i'll also finish my packages reviews.


Welcome to our GSoC students -- Perfect 10 !


Google just published the list of the accepted GSoC proposals:
<a href="" title=""></a>

We -the GSoC SIG- had a hard time to trim the list of proposals down to
10 slots and we're very pleased to see that all of them got accepted !
Thanks to my co-administrators: Buddhike (bckukera), Kushal (kushaldas),
the mentors: Emily, Kaushal (kshlm), Mikolaj (mizdebsk),Pierre-Yves
(pingou), Ratnadeep (rtntpro), Stanislas (sochotny), Vit Ondruch
who did a great job reviewing and selecting the projects.
It was a pleasure to work with you guys, this is YOUR s