Robin Laing wrote:
But why cannot there be a group of updates based on the new python or
the new X? How do others manage these changes? Not all packages depend
on python or X so not all packages need to be updated. There must be
some support for python2.4 in 2.5 or that would require a major change
and I would expect the numbering to change to 3.0.
In some instances, the entire distribution is rebuild against a new
version of glibc which would result in a new version of some package
pulling in a new glibc forcing you to move to newer versions of every
package. While a staging area like a testing repository can be used to
prevent major problems it is still very much disruptive.
Don't get me wrong, I do understand this reasoning. I have tried the
upgrade via yum path with headaches and will stick with the clean
install from that point on.
I would appreciate if you continue to yum upgrade and report problems
especially during test releases so that we can avoid those issues in the
general release. Most of these issues are packaging problems which can
be fixed.
Rahul
--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
