Indeed. Unless…
**Ignoring repositories: updates, updates-testing**
Installed Packages
gcc.x86_64 12.2.1-4.fc37 @updates
Available Packages
gcc.x86_64 10.0.1-0.11.fc32 fedora
Sometimes I mean very often, basic knowledge is far from enough.
As you already know, this doesn’t work for us using cacher because older releases are moved to archive, whose URL differs from baseURL manually set in repo.
So, it has to be somehow occurred this could be found in fc32 updates repository when automatic checking is not possible, hence the subject of this topic.
But that’s not all. Even when I set specific archive repo for the baseURL, this is what is gotten
Installed Packages
gcc.x86_64 12.2.1-4.fc37 @updates
Available Packages
gcc.x86_64 10.0.1-0.11.fc32 fedora
gcc.x86_64 10.0.1-0.11.fc32 updates
Which means, there is no way to get info that this package exists when using cacher even if it occurred to me it could be there.
At the end I had the choice to manually browse it, find and download it there, or to set http metalink, and change dom0 RPC policy for this specific template to update out of cacher.
But even that is not all. What if updates repo is disabled?
There’s more…
Now when I know where the package is, it was actually needed to get its source at
https://archives.fedoraproject.org/pub/archive/fedora/linux/updates/32/Everything/SRPMS/Packages/g/
because neither automatically or when downloading it manually it is likely that it will agree to install it with dnf or rpm, due to version conflicts. It’s possible that someone will suggest using --force to force-install an incompatible version of gcc. Such advice is fairly likely to result in an unbootable brick.
So the only practical answer is to download and build gcc yourself with a custom configuration that installs gcc into a non-default location, in order to avoid issues with libstdc++ and libsanitizer. Not a trivial task, which at the end makes the basic knowledge so non-basic.
I am compiling at the moment and it will last, so let’s see if this is the right version.
Thank you for the hint @unman, although I just realized you don’t use cacher for Fedora, hahah.