Re: 2 of 4 systems messed up after dnf system-upgrade

On 07/07/2016 05:45 PM, Greg Woods wrote: > > On Thu, Jul 7, 2016 at 5:05 PM, Rick Stevens > wrote: > > The behavior of dnf sure looks like you have some weird > options set in the dnf.conf or repo files (like excludes and such). > > > Boot to the head > >

Re: 2 of 4 systems messed up after dnf system-upgrade

On Thu, Jul 7, 2016 at 5:05 PM, Rick Stevens wrote: > The behavior of dnf sure looks like you have some weird > options set in the dnf.conf or repo files (like excludes and such). > Boot to the head Turns out the two systems that failed were the two that get used a lot. On those, I had been hav

Re: 2 of 4 systems messed up after dnf system-upgrade

On 07/07/2016 03:45 PM, Greg Woods wrote: > > On Wed, Jul 6, 2016 at 1:00 PM, Greg Woods > wrote: > > On 07/04/16 07:23, Greg Woods wrote: > > I have upgraded 4 systems (two laptops and two desktops, all different > hardware) from > > F23 to F24. Two of them a

Re: 2 of 4 systems messed up after dnf system-upgrade

On Wed, Jul 6, 2016 at 1:00 PM, Greg Woods wrote: > On 07/04/16 07:23, Greg Woods wrote: > > I have upgraded 4 systems (two laptops and two desktops, all different > hardware) from > > F23 to F24. Two of them are working fine, and the others seem to be > badly messed up in > > the area of package

Re: 2 of 4 systems messed up after dnf system-upgrade

On Tue, Jul 5, 2016 at 10:35 PM, Ed Greshko wrote: > > > On 07/04/16 07:23, Greg Woods wrote: > > I have upgraded 4 systems (two laptops and two desktops, all different > hardware) from > > F23 to F24. Two of them are working fine, and the others seem to be > badly messed up in > > the area of pa

Re: 2 of 4 systems messed up after dnf system-upgrade

On 07/04/16 07:23, Greg Woods wrote: > I have upgraded 4 systems (two laptops and two desktops, all different > hardware) from > F23 to F24. Two of them are working fine, and the others seem to be badly > messed up in > the area of package management. The main symptom I see is that > google-ch

Re: 2 of 4 systems messed up after dnf system-upgrade

On Tue, Jul 5, 2016 at 6:37 PM, Samuel Sieb wrote > > > > What is the output of "dnf repolist all"? > root@cobweb yum.repos.d]# dnf repolist all > Last metadata expiration check: 1:29:54 ago on Tue Jul 5 19:57:02 2016. > repo id repo > name

Re: 2 of 4 systems messed up after dnf system-upgrade

On 07/05/2016 03:50 PM, Greg Woods wrote: It's not wildcarding on cups*, so that's not it. The repo database just appears to be massively hosed somehow: Just making sure. It did seem very strange to match something like that in the repo directory. [root@cobweb yum.repos.d]# dnf repoquery --

Re: 2 of 4 systems messed up after dnf system-upgrade

Thanks for the responses. Sorry for the delay, July 4 is the Independence Day holiday here in the US, and I have been visiting with family the past couple of days. It's not wildcarding on cups*, so that's not it. The repo database just appears to be massively hosed somehow: [root@cobweb yum.repos

Re: 2 of 4 systems messed up after dnf system-upgrade

On 07/03/2016 04:23 PM, Greg Woods wrote: [root@cobweb yum.repos.d]# dnf install google-chrome-stable --allowerasing Last metadata expiration check: 0:08:42 ago on Sun Jul 3 17:09:12 2016. Error: nothing provides /usr/bin/foomatic-rip needed by redhat-lsb-printing-4.1-32.fc24.x86_64 [root@cobweb

Re: 2 of 4 systems messed up after dnf system-upgrade

2016-07-04 1:23 GMT+02:00, Greg Woods : > I have upgraded 4 systems (two laptops and two desktops, all different > hardware) from F23 to F24. Two of them are working fine, and the others > seem to be badly messed up in the area of package management. The main > symptom I see is that google-chrome-s