rawhide report: 20151204 changes

2015-12-04 Thread Fedora Rawhide Report
Compose started at Fri Dec 4 05:15:03 UTC 2015 Broken deps for i386 -- [IQmol] IQmol-2.3.0-9.fc24.i686 requires libboost_serialization.so.1.58.0 IQmol-2.3.0-9.fc24.i686 requires libboost_iostreams.so.1.58.0

[Test-Announce]Fedora 24 Rawhide 20151204 nightly compose nominated for testing

2015-12-04 Thread adamwill
Announcing the creation of a new nightly release validation test event for Fedora 24 Rawhide 20151204. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki

[Test-Announce]Fedora 24 Rawhide 20151204 nightly compose nominated for testing

2015-12-04 Thread adamwill
Announcing the creation of a new nightly release validation test event for Fedora 24 Rawhide 20151204. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki

Fedora Rawhide 20151204 compose check report

2015-12-04 Thread Fedora compose checker
Missing expected images: Cloud disk raw i386 Cloud disk raw x86_64 Cloud_atomic disk raw x86_64 Kde live i386 Images in this compose but not Rawhide 20151203: Xfce live i386 Images in Rawhide 20151203 but not this: Kde live i386 Lxde live i386 Scientific_kde live i386 Scientific_kde live

Fedora 22 updates-testing report

2015-12-04 Thread updates
The following Fedora 22 Security updates need testing: Age URL 239 https://bodhi.fedoraproject.org/updates/FEDORA-2015-5878 echoping-6.1-0.beta.r434svn.1.fc22 188 https://bodhi.fedoraproject.org/updates/FEDORA-2015-9185 ceph-deploy-1.5.25-1.fc22 120

Re: Non-image blocker process change proposal

2015-12-04 Thread Kevin Fenzi
On Wed, 2 Dec 2015 06:42:09 -0500 (EST) Kamil Paral wrote: > If the update is pending stable and just not pushed, it might sense > to move it one day, yes (most probably skipping weekends, though). If > it needs more testing, we might decide to postpone it a several days. > If

Re: Non-image blocker process change proposal

2015-12-04 Thread Adam Williamson
On Fri, 2015-12-04 at 12:20 -0600, Dennis Gilmore wrote: > there is the potential always of hitting issues. with upgrades. an older > release gets a higher nvr and things get messy. It is not an issue just at > release time. This is true, but release time is important, because we're very

Re: Fedora Rawhide 20151204 compose check report

2015-12-04 Thread Adam Williamson
On Fri, 2015-12-04 at 10:03 -0500, Fedora compose checker wrote: > > Failed openQA tests: 43 of 47 freetype 2.6.2 landed in Rawhide, and completely changed font rendering, so I got to spend another fun morning re-taking screenshots. In more exciting news, the public deployments of openqa -

Re: Fedora Rawhide 20151204 compose check report

2015-12-04 Thread Adam Williamson
On Sat, 2015-12-05 at 03:23 +, Fedora compose checker wrote: > Missing expected images: > > Cloud disk raw i386 > Cloud disk raw x86_64 > Cloud_atomic disk raw x86_64 > Kde live i386 > > Images in this compose but not Rawhide 20151203: > > Xfce live i386 > > Images in Rawhide 20151203 but

Fedora Rawhide 20151204 compose check report

2015-12-04 Thread Fedora compose checker
Missing expected images: Cloud disk raw i386 Cloud disk raw x86_64 Cloud_atomic disk raw x86_64 Kde live i386 Images in this compose but not Rawhide 20151203: Xfce live i386 Images in Rawhide 20151203 but not this: Kde live i386 Lxde live i386 Scientific_kde live i386 Scientific_kde live

[Test-Announce]2015-12-07 @ 16:00 UTC - Fedora QA Meeting

2015-12-04 Thread Adam Williamson
# Fedora Quality Assurance Meeting # Date: 2015-12-07 # Time: 16:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: #fedora-meeting on irc.freenode.net Greetings testers! It's QA meeting time again! Let's try again for the meeting that got cancelled last week because of

Re: Non-image blocker process change proposal

2015-12-04 Thread Dennis Gilmore
On Wednesday, December 02, 2015 06:42:09 AM Kamil Paral wrote: > > > Taking all of this into account, would this be a reasonable idea? > > > 1. At Go/No-Go voting time, all updates which block F-N release but > > > belong to F-M (M > > is not