[releng] Issue #6847: Splitting fedora-repos into edition-specific variants (F27 timeframe)

[Matthew Miller]

mattdm reported a new issue against the project: `releng` that you are following:
``
I'd like the different editions to hit the mirrors differently, so I can get a better
sense of the usage of each.  The DNF team proposes [this
solution](https://bugzilla.redhat.com/show_bug.cgi?id=1156007#c18):

>  Dear Matthew, I would like to explain the solution little bit in
> more
>  detail. We propose following:
>  
>  The package fedora-repos will be splitted into 3 packages
>  (fedora-server-repos, fedora-workstations-repos, and fedora-cloud-repos).
>  Each of them will have /etc/yum.repos.d/fedora.repo with modification in
>  metalink, where you can use something like for fedora-workstations-repos:
>  
>  metalink=https://mirrors.fedoraproject.org/metalink?repo=fedora-debug-
>  $releasever&arch=$basearch&releasevariant=workstation 
>  
>  or for fedora-server-repos: 
>  
>  metalink=https://mirrors.fedoraproject.org/metalink?repo=fedora-debug-
>  $releasever&arch=$basearch&releasevariant=server 
>  
>  That means that there will be no additional variable or requirement from dnf
>  site, but only infrastructure solution. And this is exactly what you need,
>  because your request is Fedora specific (cannot be applied for RHEL),
>  therefore it has to be solved by Fedora delivery approach of distro variant.
>  Hope that it helps.
>  
What do you think?
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6847

[Colin Walters]

walters added a new comment to an issue you are following:
``
Can't we autoinject the value of `ID` from `/etc/os-release` as a variable like
`osrelease_id`?  Then we wouldn't need separate files.

``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6847

[Matthew Miller]

mattdm added a new comment to an issue you are following:
``
>  Can't we autoinject the value of ID from /etc/os-release as a
> variable like osrelease_id?  Then we wouldn't need separate files.
>  
That's what I originally asked for (Specifically "What I'd like is ID,
VERSION_ID, and VARIANT_ID from /etc/os-release.") Yum had a feature for adding
arbitrary variables; DNF does not. See https://bugzilla.redhat.com/show_bug.cgi?id=1251774
and upstream https://github.com/rpm-software-management/libdnf/issues/170.

>  The downside is remixes that want to reuse the repos would need to
> carry overrides, perhaps we also autoinject osrelease_idlike and the metalink server would
> respond to either osrelease_id=fedora or osrelease_idlike=fedora.
>  
It seems valuable for these to be categorized separately, too.

>  Also, what value would be used for the container base image?
>  
At present, it'd be `fedora-NN`, with no variant. It would be lovely to have the
container base image use a different variant ID too, though.
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6847

[Mohan Boddu]

mohanboddu added a new comment to an issue you are following:
``
Adding "meeting" keyword, we will discuss it in our next Rel-Eng meeting on next
Monday, June 26th 2017.
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6847

[Dennis Gilmore]

ausil added a new comment to an issue you are following:
``
14:40 < dgilmore> #agreed releng feels that the most appropriate way forward is with
the injection of a variable into the url
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6847

[Dennis Gilmore]

The issue: `Splitting fedora-repos into edition-specific variants (F27 timeframe)` of
project: `releng` has been assigned to `mohanboddu` by ausil.

https://pagure.io/releng/issue/6847