Fedora 20 updates-testing report

2014-07-11 Thread updates
The following Fedora 20 Security updates need testing: Age URL 71 https://admin.fedoraproject.org/updates/FEDORA-2014-5897/nrpe-2.15-2.fc20 51 https://admin.fedoraproject.org/updates/FEDORA-2014-6551/chicken-4.8.0.6-2.fc20 49 https://admin.fedoraproject.org/updates/FEDORA-2014-6615/dru

Fedora 19 updates-testing report

2014-07-11 Thread updates
The following Fedora 19 Security updates need testing: Age URL 259 https://admin.fedoraproject.org/updates/FEDORA-2013-19963/openstack-glance-2013.1.4-1.fc19 71 https://admin.fedoraproject.org/updates/FEDORA-2014-5896/nrpe-2.15-2.fc19 60 https://admin.fedoraproject.org/updates/FEDORA-20

Re: Blocker bug process proposal: make FESCo blockers automatic

2014-07-11 Thread Kevin Fenzi
On Fri, 11 Jul 2014 13:50:25 -0700 Adam Williamson wrote: > On Thu, 2014-07-10 at 23:53 -0500, Dan Mossor wrote: > > On 07/10/2014 03:54 PM, Adam Williamson wrote: > > > Hi folks! So, we have this Alpha release criterion: > > > > > > https://fedoraproject.org/wiki/Fedora_21_Alpha_Release_Criteria

Re: F21 Debug Kernels

2014-07-11 Thread Adam Williamson
On Fri, 2014-07-11 at 12:51 -0400, Shawn Starr wrote: > On July 11, 2014 08:39:55 AM Mike Chambers wrote: > > I forget, but isn't there a parameter to turn off debugging on kernels > > if so desired? Maint F21, not rawhide (cause I know about the rawhide > > debug kernels). > > > > > > Yes the o

Re: Blocker bug process proposal: make FESCo blockers automatic

2014-07-11 Thread Adam Williamson
On Thu, 2014-07-10 at 23:53 -0500, Dan Mossor wrote: > On 07/10/2014 03:54 PM, Adam Williamson wrote: > > Hi folks! So, we have this Alpha release criterion: > > > > https://fedoraproject.org/wiki/Fedora_21_Alpha_Release_Criteria#FESCo_blocker_bugs > > > > it was added back in 2013 - > > https://li

Re: F21 Debug Kernels

2014-07-11 Thread Shawn Starr
On July 11, 2014 08:39:55 AM Mike Chambers wrote: > I forget, but isn't there a parameter to turn off debugging on kernels > if so desired? Maint F21, not rawhide (cause I know about the rawhide > debug kernels). > > > Yes the one I have (that came installed on F21) does have it on. I seem to u

Re: why is "journalctl" suddenly running rampant on my system?

2014-07-11 Thread Matthias Clasen
On Fri, 2014-07-11 at 07:45 -0400, Robert P. J. Day wrote: > On Fri, 11 Jul 2014, Robert P. J. Day wrote: > > > from out of nowhere last night, i suddenly had six journalctl > > processes running on my quad core, each one running at 99% CPU, > > causing the cooling fans to be running full speed.

F21 Debug Kernels

2014-07-11 Thread Mike Chambers
I forget, but isn't there a parameter to turn off debugging on kernels if so desired? Maint F21, not rawhide (cause I know about the rawhide debug kernels). Yes the one I have (that came installed on F21) does have it on. -- Mike Chambers Madisonville, KY "Best little town on Earth!" -- tes

F-21 Branched report: 20140711 changes

2014-07-11 Thread Fedora Branched Report
Compose started at Fri Jul 11 07:15:02 UTC 2014 Broken deps for armhfp -- [APLpy] APLpy-0.9.8-5.fc21.noarch requires pywcs [PyKDE] PyKDE-3.16.6-14.fc20.armv7hl requires sip-api(10) >= 0:10.0 [audtty] audtty-0.1.12-9.fc

Re: why is "journalctl" suddenly running rampant on my system?

2014-07-11 Thread Robert P. J. Day
On Fri, 11 Jul 2014, Robert P. J. Day wrote: > from out of nowhere last night, i suddenly had six journalctl > processes running on my quad core, each one running at 99% CPU, > causing the cooling fans to be running full speed. > > and now this morning, the fans suddenly kick in again, i check

why is "journalctl" suddenly running rampant on my system?

2014-07-11 Thread Robert P. J. Day
from out of nowhere last night, i suddenly had six journalctl processes running on my quad core, each one running at 99% CPU, causing the cooling fans to be running full speed. and now this morning, the fans suddenly kick in again, i check, there's two journalctl processes, again each one run

rawhide report: 20140711 changes

2014-07-11 Thread Fedora Rawhide Report
Broken deps for i386 -- [APLpy] APLpy-0.9.8-5.fc21.noarch requires pywcs [PyKDE] PyKDE-3.16.6-14.fc20.i686 requires sip-api(10) >= 0:10.0 [audtty] audtty-0.1.12-9.fc20.i686 requires libaudclient.so.2 [aws] aws-d

Re: Re: empty .bash_history

2014-07-11 Thread José Matos
On Thursday 10 July 2014 17:26:07 Adam Williamson wrote: > It happened to me once for my root account, but doesn't seem to be > happening every reboot, no. Using F20 sometimes that happens to me on the both the personal and the root accounts. The point here is sometimes. I don't have any clear p