On 11/9/19 7:16 PM, ToddAndMargo via users wrote:
On 11/9/19 2:44 AM, Patrick O'Callaghan wrote:
A good place to start, but I have found it does not cover
things that go wrong. To me they are rather incomplete
but a good starting point. I reference them in my
full upgrade write up.
I'm with Ed on this. Use the official instructions. Only*after* the
upgrade has succeeded, enable the testing repos if you wish.
poc
They are indeed a good place to start, but they
only work under ideal conditions.
No, the upgrade plugin and the procedures are designed to work under "normal"
or "ordinary" conditions.
So far I've upgraded 9 systems. Aside from 2 issues, one BZ that was fixed during
the beta phase the another an issue with an malformed rpmfusion package, they all
upgraded without issue and without having to use any additional parameters.
When you start always updating from "testing" repos you are doing things which
aren't "normally" done. You should expect to have issues which others won't have.
The set of instructions you've given are unique to your way of doing things. In particular,
enabling *all* repos. The majority of people won't do that. Some less informed folks
may just blindly do it without regards to what may happen.
Frankly, if you're always updating from testing you should enable those repos in their
respective repo files. That way they will be used on updates as well as upgrades.
--
The key to getting good answers is to ask good questions.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
