The non-modular repo files include commented-out baseurl= lines with correct direct URLs, as well as the 'active' metalink= lines pointing to the mirrormanager redirect system. The modular repo files do not have these, though - just the metalink= lines. This isn't really a huge problem, but it happens to make life rather more difficult for openQA, which wants to edit the repo files so they point to the compose it's testing, not to the mirror system and thus in the end (usually) the *previous* compose. We currently do this with a couple of sed commands which comment out the metalink= lines and uncomment and edit the baseurl= lines. It's rather harder to construct correct baseurl= lines for each repo entirely from scratch.
https://pagure.io/fedora-modular-repos/pull-request/13
Proposed as a Freeze Exception for 27-server-beta by Fedora user sgallagh using the blocker tracking app because: Adam requested this change to make running the openqa tests easier. To that end, including it as an FE makes sense so we can accurately test the composes.
+1 FE
Merged and built F27 - fedora-modular-repos-27-7.fc27 - https://koji.fedoraproject.org/koji/buildinfo?buildID=996157 F28/Rawhide - fedora-modular-repos-28-4.fc28 - https://koji.fedoraproject.org/koji/buildinfo?buildID=996154
Marking MODIFIED. It's been queued for the Beta Release Candidate. Will mark as ON_QA once that is completed.
There are enough votes to mark as Accepted.
This was included in the Beta RCs
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.