https://fedoraproject.org/wiki/Infrastructure/Mirroring/Tiering lists mirror.gtlib.gatech.edu as a Tier 1 mirror (for enchilada and epel), but going by their web view at least - http://www.gtlib.gatech.edu/pub/fedora.redhat/linux/releases/ - it has not been synced since Fedora 33(!) I can't check the rsync module as it's ACL limited, but I'd be surprised if it was up to date.
Their EPEL mirror at http://www.gtlib.gatech.edu/pub/fedora-epel/ does seem to be current.
I guess we should get in touch and find out if the broken Fedora mirroring is inadvertent or intentional?
I removed the out of date "Fedora Linux" category.
sorry, what? I don't understand how that relates to the report.
oh, does that mean MM will no longer consider it a viable Fedora mirror, but will still consider it a viable EPEL mirror?
if so, great. If we're not going to try and get the mirror to fix it, we should also take it out of the wiki page, but I didn't just want to do that right away.
Metadata Update from @james: - Issue tagged with: low-gain, low-trouble, ops
Was this mirrored proposed in the mirrorlist?
Yes.
Have you already reached out to the mirror admin? I was just looking for a quick fix.
I have sent an email to the mirror-admins mailing list and referred to this ticket.
@abompard I'm not sure, off hand, but the wiki page is the canonical reference for people who want to set up a mirror - it tells them to mirror from one of the tier 1 mirrors in the list. So if this one isn't going to be fixed, we should remove it from that list, so no new mirror tries to use it as their source.
Metadata Update from @phsmoura: - Issue priority set to: Waiting on Assignee (was: Needs Review)
So, the admin listed in mirrormanager exists, but their email is set to a @fedoraproject.org one... which... isn't going to work. No idea how they set that. ;(
gtlib@gtlib.gatech.edu seems to be a likely contact, I have mailed them.
Metadata Update from @kevin: - Issue priority set to: Needs Review (was: Waiting on Assignee)
Metadata Update from @kevin: - Issue priority set to: Waiting on Assignee (was: Needs Review)
I hunted around and mailed another address there... will see if it gets any answer.
That got an answer, they are fixing syncing and hope to have everything in place by monday.
This is still early Monday (2025-03-24), esp. for them.
Saying that it looks like they did a sync. late 2025-03-17 / early 2025-03-18 and haven't done one since (last Monday night / Tuesday morning).
It seems to be updating, but still not daily. As of now the last update is from early 4 days ago (2025-03-27, a Thursday).
Metadata Update from @kevin: - Issue assigned to kevin
I think this is done? A quick glance shows it updated today... it has today's rawhide at least.
Metadata Update from @kevin: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.