Re: Updating to F26 using dnf system-upgrade - conflicts

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 2017-04-05 at 18:30 +0100, Ankur Sinha wrote: > Ah - thanks, Adam! I'll wait a bit, retry it and report back. The upgrade went well on two of my systems. I checked up to see if there were any duplicate packages and so on, but nothing there

Re: Updating to F26 using dnf system-upgrade - conflicts

On Wed, 2017-04-05 at 10:01 -0700, Adam Williamson wrote: > 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

Re: Updating to F26 using dnf system-upgrade - conflicts

On Wed, 2017-04-05 at 07:17 -0700, stan wrote: > On Wed, 05 Apr 2017 12:03:51 +0100 > Ankur Sinha 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 >

Re: Updating to F26 using dnf system-upgrade - conflicts

On Wed, 05 Apr 2017 12:03:51 +0100 Ankur Sinha 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? > > > >

Updating to F26 using dnf system-upgrade - conflicts

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