kparal added a new comment to an issue you are following:
``
I tested Rawhide system and standard dnf operation on Fedora and third-party repositories
(COPR and fully third-party) work fine. Gnome Software is broken as always, but I managed
to install some packages, so the plumbing is fine (the problems are not related to this
change).
I identified a problem in rpmfusion subrepositories that get shipped officially in our
`fedora-workstation-repositories` package (steam, nvidia). Their mirrormanager still
doesn't support 31/32/rawhide as `$releasever`, so those repos are not accessible. The
full rpmfusion repos support these versions, so this is somewhat related, but not a fault
of the proposed change. I'll file a bug.
I realized that the command to switch from Rawhide to Branched is a bit more complicated
than originally claimed in *Proposed solution 1*. It is:
```
sudo dnf distrosync --refresh fedora-release\* --releasever=31 --repo=fedora
--repo=updates
sudo dnf distrosync --refresh
```
The reason is that `fedora-rawhide.repo` uses `rawhide` hardcoded instead of
`$releasever`. I can change that as part of my patch, but that would cover just the base
`fedora` repo and you'd still have to enable `updates` manually. I think repo
definitions can get a proper overhaul once the proposed change is in place (as mentioned
in *Possible future steps for Fedora Releng* in comment 0).
Those commands above work fine in general, but on my particular system some package
downgrade seriously messed up the whole system (shouldn't be relevant to this
proposal).
When going from Branched to Rawhide, I had to use this command:
```
sudo dnf distrosync --refresh fedora-release\* --releasever=rawhide --repo=fedora
sudo dnf distrosync --refresh
```
(and optionally `--repo=copr-kparal-rawhide-releasever` to have my patches applied
immediately). Ideally that `--repo=fedora` shouldn't be needed, but I discovered an
issue in Fedora's mirrormanager - it knows the `rawhide == 32` alias for standard
repos, but doesn't recognize it for modular repos. That's something we need to
fix, I'll file a separate infra ticket about it. Apart from that, it again seemed to
work fine in general.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7445