On Wed Oct 31 I would like to do some maintenance on staging Koji. For more details see https://pagure.io/fedora-infrastructure/issue/7326
Does anyone have any objections? Also please let me know if there is any staging-specific Koji configuration that should be preserved but it is not ansiblized, otherwise it will be lost during sync.
This shared document is for the next fedora infrastructure meeting.
= Preamble =
The infrastructure team will be having its weekly meeting tomorrow,
2018-10-24 at 14:00 UTC in #fedora-meeting-1 on the freenode network.
We have a gobby document
(see: https://fedoraproject.org/wiki/Gobby )
fedora-infrastructure-meeting-next is the document.
Please try and review and edit that document before the meeting and we
will use it to have our agenda of things to discuss. A copy as of today
is included in this email.
If you have something to discuss, add the topic to the discussion area
with your name. If you would like to teach other folks about some
application or setup in our infrastructure, please add that topic and
your name to the learn about section.
= Introduction =
We will use it over the week before the meeting to gather status and info and
discussion items and so forth, then use it in the irc meeting to transfer
information to the meetbot logs.
= Meeting start stuff =
#startmeeting Infrastructure (2018-10-24)
#chair nirik pingou puiterwijk relrod smooge tflink threebean cverna mkonecny
= Let new people say hello =
#topic New folks introductions
#info This is a place where people who are interested in Fedora
Infrastructure can introduce themselves
#info Getting Started Guide:
= Status / Information / Trivia / Announcements =
(We put things here we want others on the team to know, but don't need
(Please use #info <the thing> - your name)
#topic announcements and information
#info tflink is on extended PTO
#info nirik is on PTO til 2018-10-29?
#info Final Freeze has started 2018-10-09
= Things we should discuss =
We use this section to bring up discussion topics. Things we want to talk about
as a group and come up with some consensus /suor decision or just brainstorm a
problem or issue. If there are none of these we skip this section.
(Use #topic your discussion topic - your username)
#info relrod is on call from 2018-10-18 -> 2018-10-25
#info smooge is on call from 2018-10-25 -> 2018-11-01
#info nirik is on call from 2018-11-01 -> 2018-11-08
#info ??? is on call from 2018-11-08->2018-11-15
#info ??? is on call from 2018-11-15->2018-11-22
#info Summary of last week: (from smooge )
#topic Tickets discussion
Go thru each ticket one by one
= Apprentice office hours =
#topic Apprentice Open office minutes
#info A time where apprentices may ask for help or look at problems.
Here we will discuss any apprentice questions, try and match up people looking
for things to do with things to do, progress, testing anything like that.
= Learn about some application or setup in infrastructure =
(This section, each week we get 1 person to talk about an application or setup
that we have. Just going over what it is, how to contribute, ideas for
etc. Whoever would like to do this, just add the i/nfo in this section. In the
event we don't find someone to teach about something, we skip this section
and just move on to open floor.)
= Meeting end stuff =
#topic Open Floor
Stephen J Smoogen.
FYI - We are running out of space on copr-be.cloud.fedoraproject.org:
/dev/vdc1 6.4T 6.4T 75G 99% /var/lib/copr/public_html
This is where repositories are stored. We likely run out of space till Monday. Therefore I will add some space to this
volume from openstack - I plan to add 500 GB.
We have been working on a task which should results in smaller footprint - to delete EOLed chroots with build artifacts
(with opt-out option).
You are kindly invited to the meeting:
Infra Office Hours on 2018-10-23 from 18:00:00 to 19:00:00 UTC
The meeting will be about:
Weekly hour dedicated to answer questions or help people with fixing tickets or implementing features.
From: Kevin Fenzi <kevin(a)scrye.com>
This doesn't actually change anything for sshd (only proto 2 is default),
However, rkhunter complains about it not setting that explicitly.
So, this is just to get rkhunter to shut up about it.
Signed-off-by: Kevin Fenzi <kevin(a)scrye.com>
roles/basessh/files/ssh/sshd_config.pagure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/roles/basessh/files/ssh/sshd_config.pagure b/roles/basessh/files/ssh/sshd_config.pagure
index 8fca2d4..0425ccb 100644
@@ -20,7 +20,7 @@
# The default requires explicit activation of protocol 1
# HostKey for protocol version 1
Hi all, I've received these emails approximately every day this week about the Community Blog. Is everything okay? I only have my phone with me and no access to IRC or I'd ask in channel.
The site is currently offline for me.
-------- Original Message --------
From: Jetpack Support <no-reply(a)jetpack.com>
Sent: October 17, 2018 7:44:07 PM UTC
Subject: [Jetpack Monitor] communityblog.fedoraproject.org is not loading!
Hi Justin W. Flory,
https://communityblog.fedoraproject.org did not load when we checked on Wednesday, October 17, 7:43 pm.
Your server is not responding to our monitoring requests. Your site may have PHP fatal errors, database connectivity issues, or other server-level problems. You might be abel to figure out what is causing the problem using this information https://codex.wordpress.org/Common_WordPress_Errors#The_White_Screen_of_D...
If you continue seeing downtime, you should get in touch with your hosting provider for help. You will receive another alert when your site is online again.
More about Monitor: https://jetpack.com/support/monitor/
Why am I receiving this email?
You are receiving this email because you have activated Jetpack Monitor on your site. If you need to contact support, please include this reference: <strong>[101475771/server]</strong>.<br/><br/><a href="https://wordpress.com/settings/security/communityblog.fedoraproject.org">Manage your email settings</a>
Sent from my Android device with K-9 Mail. Please excuse my brevity.
I want to announce that the Anitya 0.13.2 was deployed on
You can see changelog here
Here is the list of main changes:
- User ID is now visible for user on Settings page - this ID is needed
when user wants to be promoted to admin (just ask on #fedora-apps how to
become an admin of Anitya)
- Most of the github projects has now correct setup
- Documentation links are working again
- UI changes in Project page (versions are now displayed at side, so you
can see whole setting of the project without scrolling down)
- You can now choose how versions of the project will be sorted using
version scheme. Currently you can choose from sorting by Date or by RPM
versioning (NOTE: This could cause some issues in already existing
projects, because every version retrieved before this update is missing