On Tue, 14 Oct 2014 17:41:48 +0300, Angelo Moreschini wrote: > Doing this mistake I have now on my computer some old API(s) that don't > allow me to install the new package.
How so? It sounds more like you are confused by something. Usually you cannot simply break any package dependencies and replace a strictly required API with something incompatible. And even if you did manage to break some "API", that should not break low-level RPM, so as a last resort you could still revert to previously installed good packages. > The output of the program that failed the new installation suggest me: > You could try using --skip-broken to work around the problem > You could try running: rpm -Va --nofiles --nodigest Irrelevant. Please show the full output of the command "yum distro-sync" or "yum update". Also be detailed about your theories, and show what the current state is (e.g. "rpm -qa dconf\*"). Earlier you've been unable to install an old dconf. What have you done to force-install those old packages? Don't draw false conclusions. Consult the list before messing with things based on reading arbitrary web pages. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
