On Wed, 2017-04-05 at 07:17 -0700, stan wrote:
On Wed, 05 Apr 2017 12:03:51 +0100
Ankur Sinha <sanjay.ankur(a)gmail.com> wrote:
> Hello,
>
> I was looking to upgrade my machine to F26 using dnf system-upgrade. I
> got a conflict or two and was wondering if this is a known issue and
> whether it is OK to proceed?
>
> > > [asinha@cs-as14aho-2-herts-ac-uk ~]$ sudo dnf system-upgrade
> > > download
> > >
--releasever=26
> >
> > Failed to synchronize cache for repo 'rpmfusion-nonfree-updates',
> > disabling. Failed to synchronize cache for repo
> > 'rpmfusion-free-updates', disabling. Last metadata expiration
> > check: 0:00:18 ago on Wed Apr 5 11:59:31 2017. Error: nothing
> > provides nss(x86-64) >= 3.29.3 needed by
> > java-1.8.0-openjdk-headless-1:1.8.0.121-10.b14.fc26.x86_64. nothing
> > provides nss >= 3.29.3 needed by firefox-52.0-7.fc26.x86_64.
> > problem with installed package lz4-1.7.5-1.fc25.i686. nothing
> > provides nss(x86-32) >= 3.29.3 needed by
> > java-1.8.0-openjdk-headless-1:1.8.0.121-10.b14.fc26.i686. nothing
> > provides nss(x86-64) >= 3.29.3 needed by
> > java-1.8.0-openjdk-headless-1:1.8.0.121-10.b14.fc26.x86_64 (try to
> > add '--allowerasing' to command line to replace conflicting
> > packages)
My interpretation of that output is that package lz4-1.7.5-1.fc25.i686
is blocking the update. It somehow creates a dependency chain that
doesn't allow nss to update, and so the rest follows.
You could try removing that package, and then running the
system-upgrade again. Reinstall it after the system-upgrade completes
if it is still available in F26.
No, that's wrong. An nss update which several other packages had
already rebuilt again was unpushed a couple of days ago, which caused
many dependency issues like this. It's since been re-pushed, and when
the nightly compose that just completed (20170405.n.0) syncs out to
mirrors the problem should be resolved.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net