On 05/13/2018 01:09 PM, ToddAndMargo wrote:
On 05/12/2018 01:12 PM, Samuel Sieb wrote:
Yes, I saw your earlier email. This was just an explanation of what
the problem was and why downgrading worked. You downgraded to a much
older version that matched the obsolete requirement and also
webkit2gtk3 provided a newer version of webkitgtk4.
64,000 dollar question: why did DNF not just leave it alone?
The webkit2gtk3-jsc was required by packages in F28. The webkitgtk4-jsc
had a newer version so was not obsoleted or upgraded by anything so
would not be removed. The file conflict was not detected until after
all the resolving was finished and the file checks were running.
Lesson learned: stay off the Testing repo, unless there is
something specific I need.
That depends on your tolerance for risk. I usually keep testing enabled
to get the latest packages when I update. It's very rare that there is
a problem in testing normally. There can definitely be upgrade path
issues if you use testing, but a situation like this only happens when
you have a package rename with a difficult obsoleting situation.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
