Ask Your Question
1

DNF unable to resolve dependencies for critical packages?

asked 2015-05-29 06:46:18 -0600

trepetti gravatar image

updated 2015-06-01 14:55:41 -0600

mether gravatar image

As an example,

# dnf install java
Last metadata expiration check performed 2:55:30 ago on Fri May 29 04:43:12 2015.
Error: package java-1.8.0-openjdk-1:1.8.0.45-36.b13.fc22.i686 requires java-1.8.0-openjdk-headless = 1:1.8.0.45-36.b13.fc22, but none of the providers can be installed

This is on a fresh install, too. Are there known issues with DNF and the underlying hawkey in dependency resolution and packages with multiple architectures? I'm gonna wait to update my work systems as a result. Just curious how reproducible similar problems are for other F22 users.

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
1

answered 2015-05-29 09:47:06 -0600

baoboa gravatar image

did you add some additional repo or did you use some beta version ?

try this first dnf distro-sync --disablerepo=* --enablerepo=fedora --enablerepo=updates

dnf info java-1.8.0-openjdk.i686 give me this

Version : 1.8.0.45 Release : 38.b14.fc22

edit flag offensive delete link more

Comments

Right you are. Wasn't related to outside repos, but apparently in my haste and autocompleted arguments to dd, I started out with the beta. Dunno how I missed all the warnings in anaconda, but that is what's on my thumb drive. Thank you for pointing it out!

trepetti gravatar imagetrepetti ( 2015-05-29 14:42:40 -0600 )edit

Question Tools

Stats

Asked: 2015-05-29 06:46:18 -0600

Seen: 955 times

Last updated: May 29 '15