Re: problem with Dependency Resolution

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

 



Hi Michael,


Usually you cannot simply break any package dependencies
and replace a strictly required API with something incompatible.

I think the same that you say..,  but .....

I didn't force the installation of the old dconf-Edit .. , the installation was pretty smooth..


I uninstalled the old version using the command remove...

------
here what you wont know ....

-----------------

[angelo_dev@zorro ~]$ rpm -qa dconf\*
dconf-0.18.0-2.fc20.x86_64
[angelo_dev@zorro ~]$

-----------------

[angelo_dev@zorro ~]$ sudo yum update
[sudo] password for angelo_dev:
Loaded plugins: langpacks, refresh-packagekit
No packages marked for update
[angelo_dev@zorro ~]$

-----------------

I send you, in attachment, the result of command distro-sync

----

I thank you very much for your help


Regards


Angelo







On Tue, Oct 14, 2014 at 6:48 PM, Michael Schwendt <mschwendt@xxxxxxxxx> wrote:
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@xxxxxxxxxxxxxxxxxxxxxxx
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

Attachment: yum
Description: Binary data

-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
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
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux