infrastructure October 2018

infrastructure@lists.fedoraproject.org

29 participants
54 discussions

epel7-infra and epel7 conflicts wrt pagure updates (or, can we have an epel7-infra DistTag?)
by Neal Gompa 02 Oct '18

02 Oct '18

Hey all, So as you all know, Pagure 5.0 was released[1]. With 5.0, I've taken over primary maintenance of the package outside of epel7-infra, which means that Fedora and EPEL7 packages are generally maintained by me (with packaging changes generally synced from upstream), since Pierre-Yves doesn't have time to maintain it. We've already received the approval to re-sync pagure's EPEL7 package with Fedora to update to 5.0[2]. However, this presents a bit of a problem. Pierre-Yves updates the pagure package for epel7-infra before making the general release that I can consume and push to Fedora and EPEL7. This wouldn't be an issue, except that the DistTag for epel7-infra is the same as epel7 (.el7). This means I'm locked out of that NEVR for EPEL7 updates, due to the nature of Koji considering NEVR of builds globally unique. This is frustrating because it means that I can't maintain the common spec file for both Fedora and EPEL7 (which is in turn primarily maintained upstream in the pagure git repo). Of course, I can just bump the Release to be above the epel7-infra build, but that means I'm playing NEVR games, and I don't want to do that. And if there needs to be distinct changes for epel7-infra, this is going to be an unpleasant fight. I'd like to propose that we change epel7-infra so that the DistTag defined in %dist is ".el7.infra" instead of ".el7". This will prevent the conflict and have the advantage that the infra tag is higher by default. For this current update round, I'm going to be putting a higher Release value because I need to anyway, as there's a bug in the way pagure is done that breaks packaging in Fedora and openSUSE[3]. But in the future, I'd like to have the freedom to use the correct NEVR everywhere. What do you all think? [1]: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapr… [2]: https://meetbot.fedoraproject.org/teams/epel/epel.2018-09-26-17.01.html [3]: https://pagure.io/pagure/issue/3706 -- 真実はいつも一つ！/ Always, there's only one truth!

4 5

Fedora Infrastructure Planned Outage 2018-10-03
by Stephen John Smoogen 01 Oct '18

01 Oct '18

tl;dr: All Fedora Infrastructure systems will be updated and rebooted over this week. Systems that can be done outside of the planned outage. 2018-10-01 21:00 UTC Staging and downloads 2018-10-02 throughout the 'day' single proxies will be updated/rebooted. 2018-10-03 production systems including all build servers will be rebooted. === Planned Outage - Build/Production - 2018-10-03 21:00 UTC There will be an outage starting at 2018-10-03 21:00 UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2018-10-03 21:00UTC' Reason for outage: Various kernel, library, and general security updates need to be applied to all servers. Due to the kernel, glibc, and other updates.. all systems will be rebooted afterwords Affected Services: All build, production and related services will be affected. Ticket Link: https://pagure.io/fedora-infrastructure/issue/7272 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. Reply -- Stephen J Smoogen.

1 0

a few f29 ostree sync fixups for new-updates-sync
by Dusty Mabe 01 Oct '18

01 Oct '18

[PATCH 1/2] new-updates-sync: it's silverblue now [PATCH 2/2] new-updates-sync: sync the base ref for now until f29

2 4

[Fedocal] Reminder meeting : Infra Office Hours
by cverna＠fedoraproject.org 01 Oct '18

01 Oct '18

Dear all, You are kindly invited to the meeting: Infra Office Hours on 2018-10-02 from 18:00:00 to 19:00:00 UTC At fedora-admin(a)irc.freenode.net The meeting will be about: Weekly hour dedicated to answer questions or help people with fixing tickets or implementing features. Source: https://apps.fedoraproject.org/calendar/meeting/9255/

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure October 2018