I’m trying to perform an upgrade from Fedora 30 to 31 like described in the docs: DNF System Upgrade :: Fedora Docs
I tested it with a machine with Internet access, where it worked fine, but I have to do this with our local repositories from the RedHat Satellite.
So the first question/step is: How can I configure/tell dnf to use the local repositories also for the system-upgrade download step?
Or another formulation for the question: How does the --releasever=31 switch knows where it has to look for the files?
Or another formulation for the question: How does the --releasever=31 switch knows where it has to look for the files?
releasever is just a variable used by dnf in the repo definition. It is used in the repo URL definition or in the metalink definition. Here is the metalink definition from my machine:
So if I am not mistaken, you need to provide the repository of release 31 via your Satellite, and make sure that the repo URL definition on your machines is not hardcoded to the current release.
thank you very much for your post. In my opinion your idea does make sense - the Fedora version is hardcoded in the .repo-files on my machines, I have to look how I can change that the correct way. In any way this this a good place to start.
Thanks once more, I will report if I can tell something new.
i marked your answer as solution for my second question-formulation. As i said, the URL to the repositories are “hardcoded” in my case and a test with the added $releasever variable resulted in the expected outcome like you described it.
However, the solution to get the upgrade to work was even easier. I simply added the fedora31 repositories additionally to my .repo-files (via new RedHat-Satellite-Activation-key and subscription-manager) and “dnf system-upgrade download --releasever=31” worked as expected.