Dne 18. 06. 20 v 21:40 Stephen Gallagher napsal(a):
On Thu, Jun 18, 2020 at 3:34 PM John M. Harris Jr
> 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
Sorry, but I don't remember this as "their default streams being
broken". AFAIR, there were multiple applications trying to use different
version of libgit2 at the same time which is not possible. That is
problem of modules design, not problem of the specific default stream as
you put it.
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.)
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines