Date: Sat, 3 Feb 2018 15:27:49 +0000 (UTC) From: notifications@fedoraproject.org To: robert@fedoraproject.org Subject: ignatenkobrain pushed to lame (master). "Switch to %ldconfig_scriptlets (..more)" Message-Id: <20180203152749.286B56087EF3@bastion01.phx2.fedoraproject.org> From notifications@fedoraproject.org Sat Feb 3 16:27:55 2018 ignatenkobrain pushed to lame (master). "Switch to %ldconfig_scriptlets (..more)" https://src.fedoraproject.org/rpms/lame/c/fe2336b6c35255687a511d8592ee42f5cda99eb6?branch=master
In former times, there was a unified diff inline of the e-mail. I would like to see that again to review changes easier, especially as some provenpackagers are introducing larger package changes blindly and without testing etc. (this is an example, the reasoning is not specifically applicable to this commit above).
Is anyone working on this? scm-commits is not showing actual diffs for more than 4 days.
It seems that the issue began to happen around here?
https://lists.fedoraproject.org/archives/list/scm-commits@lists.fedoraproject.org/thread/RSZW26ZXAY6GESGIW3QPOWZSHOSTHRTN/ https://lists.fedoraproject.org/archives/list/scm-commits@lists.fedoraproject.org/thread/3GBDDTY7YK5R2PBZ4W5QPVI5KJU4M3Z7/
@jcline does that ring a bell to you?
@pingou nope, I've been on PTO since January 30th. Maybe there was a package update that broke something, but I don't appear to have SSH access to anything so I don't know.
On that day I see a master playbook run and pkgs02 had to be rebooted... but I am not sure how those would affect this.
Ping?
@pingou or @puiterwijk Could perhaps one of you dig into this?
Fixed. Turns out we had a Denial of service attack on 2018-02-02 and some blocks were put in place to block sites that were hitting src.fedoraproject.org hard. Unfortunately, one of those sites was the notification backend server. ;(
We have cleaned up the blocks so things should be working again and also will be looking at changing the way the notification server accesses src so it doesn't cause much load.
Thanks everyone for your patience on this issue and sorry about it happening in the first place.
:person_frowning:
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.