DevHeads.net

Postings by Kevin Fenzi

Schedule for Mondays's FESCo Meeting (2019-09-09)

Following is the list of topics that will be discussed in the
FESCo meeting Monday at 15:00UTC in #fedora-meeting-1 on
irc.freenode.net.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/UTCHowto" title="http://fedoraproject.org/wiki/UTCHowto">http://fedoraproject.org/wiki/UTCHowto</a>

or run:

date -d '2019-09-09 15:00 UTC'

Links to all issues to be discussed can be found at:
<a href="https://pagure.io/fesco/report/meeting_agenda" title="https://pagure.io/fesco/report/meeting_agenda">https://pagure.io/fesco/report/meeting_agenda</a>

= Discussed and Voted in the Ticket =

chromium : exception to continue using python2 to build
<a href="https://pagure.io/fesco/issue/2214" title="https://pagure.io/fesco/issue/2214">https://pagure.io/fesco/issue/2214</a>
APPROVED (+3,0,-0).

Nonresponsive maintainer: Gaël Chamoulaud gchamoul
<a href="https://pagure.io/fesco/i" title="https://pagure.io/fesco/i">https://pagure.io/fesco/i</a>

round up of failing f31 (branched) images

Hey folks.

Looking at the latest incomplete composes (remember: incomplete means at
least one non blocking image/thing failed to compose, but all blocking
items did compose) at <a href="https://pagure.io/releng/failed-composes/issues" title="https://pagure.io/releng/failed-composes/issues">https://pagure.io/releng/failed-composes/issues</a>

If you want your spin/image in the beta, you will need to propose a fix
in packages or fedora-comps or fedora-kickstart pr and then make sure
there is a bugzilla bug for the issue and propose that as a FE.

Scientific KDE

Bunch of deps issues:

a f31 branched compose is syncing...

Finally.

Sorry for the long delay in this, but it kept hitting problem after
problem. ;(

It is syncing now, and expect it to sync out past the master mirror
tonight.

kevin

koji build archiving

Koji.fedoraproject.org currently stores every rpm ever shipped to users
since the Fedora 7 days, along with a lot of information about every
build it’s ever made, even if not distributed. We have continued to grow
the storage backing koji over time, but it is close to reaching a size
we can no longer expand (75TB).

We are going to start moving builds off our main storage volume on to
slower (but still accessible) volumes in order to shrink our main volume
of active releases and make it easier to move and expand.

friday roundup of failing images in rawhide

hey folks, here is a list of currently failing images in rawhide.
Please fix if you can.

1.

python-oauthlib update

Greetings.
(I am posting this to the devel list and also Bccing the maintainers of
the involved packages below).

A bit back I updated python-requests-oauthlib to 1.2.0.

I didn't realize at the time that this version needs python-oauthlib
3.0.0 or newer.

3.0.0 is a api breaking major version:
<a href="https://github.com/oauthlib/oauthlib/releases/tag/v3.0.0" title="https://github.com/oauthlib/oauthlib/releases/tag/v3.0.0">https://github.com/oauthlib/oauthlib/releases/tag/v3.0.0</a>

The following packages depend on python-oauthlib:

cloud-init
python-apprise
python-jira
python-requests-oauthlib
python-social-auth-core

From what I can tell:

python-requests-oauthlib is already set for the update.
python-social-auth-core - us

Planned Outage -pagure.io - 2019-07-12 21:00 UTC

Planned Outage -pagure.io - 2019-07-12 21:00 UTC

There will be an outage starting at 2019-07-12 21:00 UTC ,
which will last approximately 4 hours.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="http://fedoraproject.org/wiki/Infrastructure/UTCHowto">http://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>
or run:

date -d '2019-07-12 21:00UTC'

Reason for outage:

We will be moving pagure.io from one datacenter to another. The time to
sync the data is expected to be around an hour, but we are leaving time
for configuration issues or network problems. We will try and minimize
the downtime as much as possible.

roundup of failing images for 2019-07-07

So, what better way to relax on a sunday than to look at image compose
failures? :)

1. The armv7 workstation compose:
<a href="https://koji.fedoraproject.org/koji/taskinfo?taskID=36106518" title="https://koji.fedoraproject.org/koji/taskinfo?taskID=36106518">https://koji.fedoraproject.org/koji/taskinfo?taskID=36106518</a>

This is failing because it cannot find 'epiphany'.
This is because it's using the Workstation repo instead of the
"Everything" repo to compose from. So, we either need to fix that or
remove epiphany from it's kickstart. Who "owns" this image? The arm SIG?
Workstation sig?

2.

Planned Outage - fedoraproject.org/wiki - 2019-06-27 21:00 UTC

Planned Outage - fedoraproject.org/wiki - 2019-06-27 21:00 UTC

There will be an outage starting at 2019-06-27 21:00 UTC ,
which will last approximately 2 hours.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="http://fedoraproject.org/wiki/Infrastructure/UTCHowto">http://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>
or run:

date -d '2019-06-27 21:00UTC'

Reason for outage:

We will be updating the nodes running mediawiki to Fedora 30 and thus
also upgrading mediawiki to a newer version. The last scheduled upgrade
was aborted due to some issues found in staging.

rawhide status - 2019-06-19

Greetings everyone.

I thought I would send out a rawhide status email to catch everyone up
to whats going on there. I should have sent it sooner, but I was on
vacation, then in a set of meetings, etc.

The last rawhide compose that completed was 2019-06-09 (10 days ago now).

There's been a number of reasons for this. In order to accommodate some
fedora 31 changes ( dynamic build requires ) and epel8 work we needed a
koji with some backported patches as well as newer mock and createrepo_c.

So, first step was to get armv7 builders off Fedora 27 where they have
been stuck due to a kernel bug.

Planned Outage - fedoraproject.org/wiki - 2019-06-19 21:00 UTC

Planned Outage - fedoraproject.org/wiki - 2019-06-19 21:00 UTC

There will be an outage starting at 2019-06-19 21:00 UTC ,
which will last approximately 1 hour.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="http://fedoraproject.org/wiki/Infrastructure/UTCHowto">http://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>
or run:

date -d '2019-06-19 21:00UTC'

Reason for outage:

We will be updating the nodes running mediawiki to Fedora 30 and thus
also upgrading mediawiki to a newer version.

Affected Services:

<a href="https://fedoraproject.org/wiki" title="https://fedoraproject.org/wiki">https://fedoraproject.org/wiki</a>

Ticket Link:

<a href="https://pagure.io/fedora-infrastructure/issue/7914" title="https://pagure.io/fedora-infrastructure/issue/7914">https://pagure.io/fedora-infrastructure/issue/7914</a>

Please join #fedora-admin or #fedora-noc

Attempting to contact unresponsive maintainers: dkaspar flaper87

I'd like to appologize for the delay in this email.

The notices I get were being filtered and I didn't realize I wasn't
seeing them for a while. ;(

We've been told that the email addresses for these package maintainers
are no longer valid.

Planned Outage - src.fedoraproject.org - 2019-05-03 19:00 UTC

Planned Outage - src.fedoraproject.org - 2019-05-03 19:00 UTC

There will be an outage starting at 2019-05-03 19:00 UTC ,
which will last approximately 1 hour.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="http://fedoraproject.org/wiki/Infrastructure/UTCHowto">http://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>
or run:

date -d '2019-05-03 19:00UTC'

Reason for outage:

We will be adding additional disk space to src.fedoraproject.org.

Retirement of cgit access to src.fedoraproject.org

Greetings,

In the past, src.fedoraproject.org git repositories have been accessable
via the pagure[1] interface or via the cgit web interface.

We have been planning some changes to the way the backend git
repositories are stored on src.fedoraproject.org: from local bare repos
to repoSpanner[2] clustered and distributed repositories. This will
allow multiple frontends for that data, including sharing them with
git.centos.org.

This change however meant that cgit could no longer have access to
the bare git repositories and thus would no longer work.

announcing HTTPS pushing to dist-git/src.fedoraproject.org for packagers and non-packagers

Greetings.

I'm happy to announce that you can now use https to push commits

to src.fedoraproject.org.

Maintainer test instances

Greetings.

This is a periodic reminder that we have some test instances setup for
package maintainers. Please see:

<a href="https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers" title="https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers">https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Mainta...</a>

for more information.

Additionally, I have just added 2 aarch64 instances (running Fedora 29).

I hope folks will find them useful.

kevin

mxml license change

The mxml package ( Minature XML devel library )

has changed it's license from LGPLv2+ to ASL 2.0 with exception with the
3.0 release (I am just about to push out).

( exception is locateed at
<a href="https://github.com/michaelrsweet/mxml/blob/master/NOTICE" title="https://github.com/michaelrsweet/mxml/blob/master/NOTICE">https://github.com/michaelrsweet/mxml/blob/master/NOTICE</a> )

kevin

signing status

Just wanted to update everyone on our current status.

As you know from the other thread:

* The mass rebuild happened and finished.
* The mass rebuild side tag was merged into the f30-pending tag
(to make sure everything was signed).
* In the middle of the night our autosign box stopped processing.
* The next morning this was noticed and a request for a replacement
motherboard was sent.
* Since that was going to take a day, we setup another machine to do
autosigning.
* That machine started processing the backlog, but also stopped
processing a few times (waiting on koji).
* Finally we set back

A smart cache-y proposal for composes

So, I had an idea of one method of attack for composes and lifecycles
that I thought I would toss out there to see what others thought of it.

Instead of redesigning and reimplementing our current build/compose/test
pipeline we improve it by making the current process cache as much of
everything as it possibly can and listening and operating on any changes
in inputs.

Attempting to contact unresponsive maintainers: sross, ryansb, mpreisle

Greetings, we've been told that the email addresses for these package
maintainers are no longer valid. I'm starting the unresponsive
maintainer policy to find out if they are still interested in
maintaining their packages (and if so, have them update their email
addresses in FAS).

If they're not interested in maintaining or we can't locate them in 1
week, I'll have FESCo orphan the packages so that others can take them
over.

If you have a way to contact these maintainers, please let them know
that we'd appreciate knowing what to do with their packages.

Planned Outage - System Updates/reboots - 2018-11-07 21:00 UTC

Planned Outage - System Updates/reboots - 2018-11-07 21:00 UTC

There will be an outage starting at 2018-11-07 21:00 UTC,
which will last approximately 6 hours.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="http://fedoraproject.org/wiki/Infrastructure/UTCHowto">http://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>
or run:

date -d '2018-11-07 21:00UTC'

Reason for outage:

We will be applying updates and rebooting servers as well as doing some
hardware maint tasks (disk replacement, etc).

Affected Services:

Most fedoraproject.org services will be affected some in the outage
window.

Attempting to contact unresponsive maintainers:

Greetings, we've been told that the email addresses for these package
maintainers are no longer valid. I'm starting the unresponsive
maintainer policy to find out if they are still interested in
maintaining their packages (and if so, have them update their email
addresses in FAS).

If they're not interested in maintaining or we can't locate them in 1
week, I'll have FESCo orphan the packages so that others can take them
over.

If you have a way to contact these maintainers, please let them know
that we'd appreciate knowing what to do with their packages.

Planned Outage - Fedora Production Openshift - 2018-09-27 21:00 UTC

Planned Outage - Fedora Production Openshift - 2018-09-27 21:00 UTC

There will be an outage starting at 2018-09-27 21:00 UTC,
which will last approximately 4 hours.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="http://fedoraproject.org/wiki/Infrastructure/UTCHowto">http://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>
or run:

date -d '2018-09-27 21:00 UTC'

Reason for outage:

We will be redeploying our production openshift with more compute nodes,
and a number of new features enabled.

Affected Services:

<a href="https://bodhi.fedoraproject.org" title="https://bodhi.fedoraproject.org">https://bodhi.fedoraproject.org</a>
<a href="https://coreos.fedoraproject.org" title="https://coreos.fedoraproject.org">https://coreos.fedoraproject.org</a>
<a href="https://greenwave.fedoraproject.org" title="https://greenwave.fedoraproject.org">https://greenwave.fedoraproject.org</a>
<a href="https://waiverdb.fedoraproject.org" title="https://waiverdb.fedoraproject.org">https://waiverdb.fedoraproject.org</a>

some trac plugins looking for point of contacts

Hey all.

I have:

trac-bazaar-plugin
trac-git-plugin
trac-iniadmin-plugin
trac-mercurial-plugin
trac-ticketdelete-plugin

Which are all FTBFS (likely due to unversioned python2 use).

I don't use trac anymore, so I am going to orphan these, unless anyone
would like to take them on, in which case I'd be happy to transfer them
to you.

I'll keep them until saturday, then orphan and folks can file releng
tickets after that to get them.

kevin

Schedule for Monday's FESCo Meeting (2018-07-09)

Following is the list of topics that will be discussed in the
FESCo meeting Monday at 15:00UTC in #fedora-meeting-1 on
irc.freenode.net.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/UTCHowto" title="http://fedoraproject.org/wiki/UTCHowto">http://fedoraproject.org/wiki/UTCHowto</a>

or run:
date -d '2018-07-09 15:00 UTC'

Links to all issues to be discussed can be found at:
<a href="https://pagure.io/fesco/report/meeting_agenda" title="https://pagure.io/fesco/report/meeting_agenda">https://pagure.io/fesco/report/meeting_agenda</a>

= Discussed and Voted in the Ticket =

<a href="https://pagure.io/fesco/issue/1920" title="https://pagure.io/fesco/issue/1920">https://pagure.io/fesco/issue/1920</a>
F29 System Wide Change: Build non-RELRO ELF binaries with .plt.got isolation
APPROVED

<a href="https://pagure.io/fesco/issue/1923" title="https://pagure.io/fesco/issue/1923">https://pagure.io/fesco/issue/1923</a>
F29 Self Contained Change: glib

Schedule for Monday's FESCo Meeting (2018-07-02)

Following is the list of topics that will be discussed in the
FESCo meeting Monday at 15:00UTC in #fedora-meeting-1 on
irc.freenode.net.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/UTCHowto" title="http://fedoraproject.org/wiki/UTCHowto">http://fedoraproject.org/wiki/UTCHowto</a>

or run:
date -d '2018-07-02 15:00 UTC'

Links to all issues to be discussed can be found at:
<a href="https://pagure.io/fesco/report/meeting_agenda" title="https://pagure.io/fesco/report/meeting_agenda">https://pagure.io/fesco/report/meeting_agenda</a>

= Discussed and Voted in the Ticket =

None have reached 7 days yet.

= Followups =

None

= New business =

#topic #1917 F29 System Wide Change: Make BootLoaderSpec-style
configuration files the default
.fesco 1917
<a href="https://pag" title="https://pag">https://pag</a>

Planned Outage - Fedora Production Openshift - 2018-05-31 21:00 UTC

Planned Outage - Fedora Production Openshift - 2018-05-31 21:00 UTC

There will be an outage starting at 2018-05-31 21:00UTC,
which will last approximately 3 hours.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="http://fedoraproject.org/wiki/Infrastructure/UTCHowto">http://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>
or run:

date -d '2018-05-31 21:00 UTC'

Reason for outage:

We will be re-installing our production openshift cluster.

Planned Outage - Server updates - 2018-05-08 21:00 UTC

Planned Outage - Server updates - 2018-05-08 21:00 UTC

There will be an outage starting at 2018-05-08 21:00 UTC,
which will last approximately 6 hours.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="http://fedoraproject.org/wiki/Infrastructure/UTCHowto">http://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>
or run:

date -d '2018-05-08 21:00UTC'

Reason for outage:

We will be updating servers and rebooting them into the latest kernels.
While we will try and keep disruption to a minimum, services may be up
and down during the outage window.

Affected Services:

All services may be impacted for short times in the outage window.

Ticket Link:

h

Attempting to contact unresponsive maintainers - ddomingo, yruseva, cspicer, kheib

Greetings, we've been told that the email addresses for these package
maintainers are no longer valid. I'm starting the unresponsive
maintainer policy to find out if they are still interested in
maintaining their packages (and if so, have them update their email
addresses in FAS).

If they're not interested in maintaining or we can't locate them in 1
week, I'll have FESCo orphan the packages so that others can take them
over.

If you have a way to contact these maintainers, please let them know
that we'd appreciate knowing what to do with their packages.

Planned outage: All Services - 2018-04-04 21:00 UTC

There will be an outage starting at 2018-04-04 21:00UTC, which will last
approximately 6 hours.

To convert UTC to your local time, take a look at

<a href="http://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="http://fedoraproject.org/wiki/Infrastructure/UTCHowto">http://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>

or run:

date -d '2018-04-04 21:00UTC'

Reason for outage:

We will be applying critical security updates and rebooting all
servers.

Affected Services:

All services may be affected.