infrastructure January 2019

infrastructure@lists.fedoraproject.org

37 participants
41 discussions

[release] MirrorManager2: 0.9.0
by Adrian Reber 15 Jan '19

15 Jan '19

A new release of MirrorManager2 is available: 0.9.0 - crawler: Correctly calculate the remaining time https://github.com/fedora-infra/mirrormanager2/pull/244 - repomap: more modular repository detection logic https://github.com/fedora-infra/mirrormanager2/pull/243 - crawler: correctly handle keep-alive for HTTPS https://github.com/fedora-infra/mirrormanager2/pull/245 - crawler: only update directories of the current category https://github.com/fedora-infra/mirrormanager2/pull/250 - python3 compatibility https://github.com/fedora-infra/mirrormanager2/pull/185 - rpmmd: switch from yum.repoMDObject pyrpmmd https://github.com/fedora-infra/mirrormanager2/pull/254 - Migrate to new geoip API https://github.com/fedora-infra/mirrormanager2/pull/253 - Use InputRequired() instead of Required() https://github.com/fedora-infra/mirrormanager2/pull/256 - Enable MirrorManager2 to be built using Python 3 for Fedora https://github.com/fedora-infra/mirrormanager2/pull/260 - Fix tests with python3 https://github.com/fedora-infra/mirrormanager2/pull/261 - Toggle private https://github.com/fedora-infra/mirrormanager2/pull/257 This release includes a few smaller fixes which are already running on Fedora's production systems and it also includes the switch to GeoIP2. Especially the switch to GeoIP2 means that it requires additional changes to Fedora's MirrorManager2 instance to make sure the new GeoIP2 databases are available on the relevant systems. I will look into updating Fedora's staging MirrorManager2 instance in the next days. Thanks to Zbigniew Jędrzejewski-Szmek and Neal Gompa for porting MirrorManager2 to Python3. From now on the Fedora packages will be using Python3. The EPEL7 packages which are used in Fedora's MirrorManager2 instance will still be Python2. Tests are all green with Python3, but as far as I know there is no MirrorManager2 instance running on Python3... yet. Adrian

1 0

Greenwave and WaiverDB releases
by Giulia Naponiello 15 Jan '19

15 Jan '19

Hello, Matt and I are releasing a new version of Greenwave and WaiverDB for Fedora. We are starting in these moments. We are available on IRC. Cheers Giulia

2 2

[Fedocal] Reminder meeting : Infra Office Hours
by cverna＠fedoraproject.org 14 Jan '19

14 Jan '19

Dear all, You are kindly invited to the meeting: Infra Office Hours on 2019-01-15 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

release-monitoring.org is unavailable
by Michal Konecny 14 Jan '19

14 Jan '19

Hi everyone, right now I'm trying to deploy version 0.14.0 of Anitya on release-monitoring.org. Unfortunately there is a creation of new index in database, which is taking longer than expected. So right now release-monitoring.org is unavailable. I will let you know when it will be available again. Regards, mkonecny

1 1

Help! SSL certificate errors for fedora related sites from university network
by Ankur Sinha 14 Jan '19

14 Jan '19

Hello, When I try to access a few fedora related resources from my university network, I tend to get certificate errors. I was getting these from fedoramagazine.org, then from meetbot, and I got one when running `fedpkg build` that really freaked me out: $ fedpkg build Could not execute build: The connection to PDC failed while trying to get the active release branches. The error was: HTTPSConnectionPool(host='pdc.fedoraproject.org', port=443): Max retries exceeded with url: /rest_api/v1/component-branches/?global_component=lifeograph&fields=name&fields=active (Caused by SSLError(SSLCertVerificationError("hostname 'pdc.fedoraproject.org' doesn't match either of 'phishing-alert.herts.ac.uk', 'www.phishing-alert.herts.ac.uk', 'f5-phishing-alert.herts.ac.uk'"))) I tried it again, and it worked (phew!), but I haven't been able to get fedoramagazine to work at all. I've filed a ticket with university IT already. Their initial comment was: "site is report (sic) to be using an invalid certificate. It is not blocked manually by UH", which is probably inaccurate given that we have no issues with these web resources outside the university network. Would anyone have any hints on what they may be doing? I know it's a hard problem to diagnose without knowing what the university IT is upto, but any hints that I could pass on to them would be appreciated. -- Thanks, Regards, Ankur Sinha "FranciscoD" https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London

2 2

Proposal: Add a separate “flatpaks/” namespace.
by Owen Taylor 11 Jan '19

11 Jan '19

Currently, the content for a Flatpak in Fedora can be found in modules/<application>. E.g.: https://src.fedoraproject.org/modules/quadrapassel/tree/master - I’d like to propose creating a separate namespace in src.fedoraproject.org - flatpaks/ Benefits: * Allow automation to easily distinguish Flatpaks from other modules. (https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… ) * Make it easy to browse through the source of available Flatpaks * Reduce some confusion. A Flatpak is a module, but it’s *also* a container, and the dist-git repository will include files for both. Downsides: * We have a few graphical applications that are available as standard loose-rpm macros (gimp, rawtherapee, skychart). While it should work to have flatpaks/gimp and modules/gimp build different streams of the gimp module, it’s going to be more confusing than different branches in the same repository. (There are even possibilities for using the *same* branch using module-stream-expansion, though that’s not something I’d encourage at the moment.) Needed steps: * Remove special casing of flatpak => modules in Bodhi https://github.com/fedora-infra/bodhi/blob/develop/bodhi/server/models.py#L… * Adjust namespace special-casing in fedpkg https://pagure.io/fedpkg/blob/master/f/fedpkg/cli.py * Adjust namespace special-casing in fedscm_admin https://pagure.io/fedscm-admin/blob/master/f/fedscm_admin/utils.py * In fedscm_admin: Map flatpaks namespace to the ‘module’ PDC branch type when storing the SLA into the PDC, to avoid PDC changes, and because the SLA really is a module SLA. * Adjust distgit pagure configuration to add flatpaks to ALLOWED_PREFIX and REQUIRED_GROUPS https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/distgi… * Add flatpaks/ to the kojid allowed_scms configuration https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/koji_b… * Add flatpaks/ to the module-build-service SCMS configuration https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/mbs/co… * Adjust the owner-sync-pagure script to handle flatpaks/ https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/bodhi2… * Move or reimport existing Flatpak repositories (modules/eog, modules/feedreader, modules/flatpak-common, modules/flatpak-runtime, modules/gnome-clocks, modules/gnome-tetravex, modules/quadrapassel) Potential issues: * We should probably move flatpak-common to the flatpaks/ namespace for ease of discovery, but it isn’t in any way a flatpak, it’s just a module that Flatpaks can depend on. * The ability of modules to include other modules won’t work without further adjustments to the MBS config.py (MODULES_ALLOW_REPOSITORY) - I don't see this as useful functionality for Flatpaks.

2 2

[Fedocal] Reminder meeting : Fedora Infrastructure
by smooge＠gmail.com 09 Jan '19

09 Jan '19

Dear all, You are kindly invited to the meeting: Fedora Infrastructure on 2019-01-10 from 15:00:00 to 16:00:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Weekly Fedora Infrastructure meeting. See infrastructure list for agenda a day before or view it at https://infinote.fedoraproject.org/cgit/infinote/tree/fedora-infrastructure… Source: https://apps.fedoraproject.org/calendar/meeting/22/

1 0

Anitya 0.14.0 (stg.release-monitoring.org) deployed on staging
by Michal Konecny 09 Jan '19

09 Jan '19

Hi everybody, I want to announce that the Anitya 0.14.0 was deployed on staging (https://stg.release-monitoring.org/) Feel free to test it. Anitya 0.14.0 will be deployed on production next week if no breaking issue will be found. You can see changelog here https://github.com/release-monitoring/anitya/releases/tag/0.14.0 There are plenty of changes in this version. Here are most noticeable: * Delete cascade added to most db models - No orphaned packages or mappings anymore \o/ * Logs page is reworked - Should be much more simpler * Check is now done for all versions instead of only latest - No version will be lost anymore * Rate limit is now handled more efficiently - No Github project should be skipped anymore * New user management allowing simple promotion of users to admin - No need to change configuration for every new admin * project.version.update fedmsg topic now contains information about ecosystem - This should help when you are looking for projects from Pypi or Rubygems * Support for Python 2.7 is now officially dropped Thanks to everyone who contributed to this new version. Regards, mkonecny _______________________________________________ infrastructure mailing list -- infrastructure(a)lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapr…

2 2

[Fedocal] Reminder meeting : Fedora koji outage
by smooge＠gmail.com 08 Jan '19

08 Jan '19

Dear all, You are kindly invited to the meeting: Fedora koji outage on 2019-01-11 from 00:00:00 to 00:00:00 UTC The meeting will be about: Planned Outage - Koji Services - 2019-01-11 22:00 UTC There will be an koji outage starting at 2019-01-11 22:00 UTC, which will last approximately 4 days. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2019-01-11 22:00UTC' Reason for outage: The facility that houses the Fedora s390 server will have a major power outage starting 2019-01-11 22:00 UTC and ending 2019-01-14 22:00 UTC. During this time the s390 builders will not be available and all builds will be queued up until they are available and will not complete. Affected Services: koji and related services which make composes and builds Ticket Link: https://pagure.io/fedora-infrastructure/issue/7429 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. Source: https://apps.fedoraproject.org/calendar/meeting/9422/

1 0

Re-enable updates-testing ostree for Silverblue
by Dusty Mabe 08 Jan '19

08 Jan '19

Now that pungi has been updated on the bodhi backend machines (https://pagure.io/fedora-infrastructure/issue/7484) I can re-enable updates-testing for silverblue. Also added some removal of code specific to f27. - bodhi-pungi: re-enable testing ostree for silverblue - bodhi-pungi: simplify now that f27 is EOL

2 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure January 2019