Re: Update on the KDE KF5 build boondoggle,Message-ID:

2015-11-04 Thread R. G. Newbury
On 11/04/2015 01:40 PM, users-requ...@lists.fedoraproject.org wrote: > >"I don't have to be faster than the bear--I only have to be faster than >YOU!" > And after undergoing 6 surgeries on my feet and looking at having one to repair a damaged knee, I do believe most corpses could outrun me, I

Update on the KDE KF5 build boondoggle

2015-11-04 Thread Mark Haney
I was all prepared to upgrade my F22 KDE laptop to F23 when I got the kf5-filesystem warning when trying to download the upgrade files. I did some digging and found a couple of previous posts (and the bug report) about the issue, but wasn't able to get a complete, current status of this. Can

Re: Update on the KDE KF5 build boondoggle

2015-11-04 Thread Rex Dieter
Mark Haney wrote: > I was all prepared to upgrade my F22 KDE laptop to F23 when I got the > kf5-filesystem warning when trying to download the upgrade files. I did > some digging and found a couple of previous posts (and the bug report) > about the issue, but wasn't able to get a complete,

Re: Update on the KDE KF5 build boondoggle

2015-11-04 Thread Rick Stevens
On 11/04/2015 10:10 AM, Mark Haney wrote: On Wed, Nov 4, 2015 at 12:44 PM, Rex Dieter > wrote: > Can someone bring me up to speed on where we are with this? I've got a > dozen or so similar systems I would like to upgrade but am

Re: Update on the KDE KF5 build boondoggle

2015-11-04 Thread Mark Haney
On Wed, Nov 4, 2015 at 1:23 PM, Rick Stevens wrote: > On 11/04/2015 10:10 AM, Mark Haney wrote: > >> >> So, I should be able to upgrade in the next few hours or so? >> > > I'm going to chime in here...I wouldn't upgrade for a week or so at > least if you have that many

Re: Update on the KDE KF5 build boondoggle

2015-11-04 Thread Mark Haney
On Wed, Nov 4, 2015 at 12:44 PM, Rex Dieter wrote: > > > Can someone bring me up to speed on where we are with this? I've got a > > dozen or so similar systems I would like to upgrade but am hesitant to do > > so until I get some idea of state of this issue. > > Sorry