Re: failure of f24 to f25 upgrade

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 12/02/2016 10:34 PM, Kevin Kofler wrote:
Przemek Klosowski wrote:
Right, that's what I thought. Still, completely blocking the upgrade
seems rude. Yum had an option --skip-broken  that would just leave such
packages alone,
I don't think keeping an old version of the filesystem package (because the 
conflict is between google-earth-stable and the new version of filesystem) 
installed instead of the current one is a good idea.
You're right in this case, but the three cases I encountered (see below) were not that serious. The error messages weren't very helpful: they just stated the conflict. I am not sure what is the best recommendation we should give; I could think of four:
 
- report this problem in Bugzilla, wait until the problem is fixed in Fedora repos and try again
- consider ignoring the conflict if appropriate (equivalent of --skip-broken, would require changes in DNF)
- delete the offending packages and try again, and then reinstall
- downgrade the offending  package (to what?) and try again

I did the delete/upgrade/reinstall, and also reported the problems; two are apparently already fixed by packages

https://bugzilla.redhat.com/show_bug.cgi?id=1396848

https://bugzilla.redhat.com/show_bug.cgi?id=1396849

https://bugzilla.redhat.com/show_bug.cgi?id=1396319

_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux