ELN Extras metalink lists only one repo, repo's metadata does not match metalink's requirements #13381
Labels
No labels
after freeze
automation
backlog
blocked
change-ack
change-nak
change-noreleng
changes
Closed As
Can't Fix
Closed As
Duplicate
Closed As
Fixed
Closed As
Fixed with Explanation
Closed As
Get back later
Closed As
Grooming
Closed As
Insufficient data
Closed As
Invalid
Closed As
It's all good
Closed As
taiga
Closed As
upstream
day-to-day
dev
docs
easyfix
epel
f26
f27
f28
f29
f30
f31
f32
f33
f34
f35
f36
f37
f38
f39
f40
f41
f42
f43
f44
f45
fedora
groomed
high-gain
high-trouble
in-progress
in-review
investigation
legal
low-gain
low-trouble
mass rebuild
medium-gain
medium-trouble
meeting
mini-initiative
new_artifact
ops
pdc_retirement
rawhide
RCA
review
script
sidetarget
sprint-0
sprint-1
sprint-2
sprint-3
sprint-4
sprint-5
unfrozen
waiting on external
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
releng/tickets#13381
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Describe the issue
As of right now, this is the content of https://mirrors.fedoraproject.org/metalink?repo=eln-extras-1&arch=x86_64 when hit from my system:
Note only one repo is listed. As of right now, the repomd.xml in that repo does not match the requirements:
This makes ELN installs fail. From packaging.log:
Sometimes this kinda thing happens temporarily as mirrors sync, but this seems deeper. The same issue happened on the previous ELN compose 18 hours ago. And ELN update tests have been hitting it consistently since this run almost exactly a day ago.
When do you need this? (YYYY/MM/DD)
ASAP
When is this no longer needed or useful? (YYYY/MM/DD)
N/A
If we cannot complete this, what is the impact? [Dependencies/Blocker]
ELN installs are broken, probably updates on installed ELN systems are too.
Note the repomd.xml on dl.fp.o currently appears to be the one from the most recent compose, 20260606.n.0. That file's md5sum is bc723735deec7cad24aed4e81e91b9e0 . So it's not simply that dl.fp.o does not have the most recent compose; it does. I don't know yet what it is the metalink is expecting...
Duplicate of infra/tickets#13398 lets track there.
I think it should be fixed now, but we need to make sure it's updating correctly next compose.