On Thu, Jun 18, 2020 at 3:34 PM John M. Harris Jr <johnmh(a)splentity.com> wrote:
The issues I've seen so far affect both Fedora and RHEL, but have gotten a bit
better in Fedora. For example, a major concern that has been much worse in
Fedora than RHEL, for obvious reasons:
One month you can do a fresh install, install a package that, as it turns out,
is a module for some reason.
Then you install a fresh system the next month, install the same package.
Perform a dnf update on the previous system, and you'll find that you have a
different version of the package installed, because you're tracking a
different version of a default stream.
Can you give an example of where you've seen this? Because our
policies in Fedora forbid changing a default stream in a released
Fedora. There were a couple exceptions around Java/Maven and libgit2
in the past due to their default streams being broken and causing
issues, but other than those extreme cases, this should never happen
in a stable release. (On Rawhide, that's a different story and if
that's what you're describing, that's a known issue and is being
tracked as part of the upgrade path work.)