Re: Non-image blocker process change proposal

2015-12-02 Thread Stephen Gallagher
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/02/2015 06:42 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>> pushed

Fedora Rawhide 20151202 compose check report

2015-12-02 Thread Fedora compose checker
Missing expected images: Cloud disk raw i386 Cloud disk raw x86_64 Cloud_atomic disk raw x86_64 Images in this compose but not Rawhide 20151201: Cloud docker x86_64 No images in Rawhide 20151201 but not this. -- Mail generated by check-compose:

Fedora 22 updates-testing report

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

[Test-Announce]Fedora 21 End Of Life

2015-12-02 Thread Dennis Gilmore
As of the 1st of December 2015, Fedora 21 has reached its end of life for updates and support. No further updates, including security updates, will be available for Fedora 21. A previous reminder was sent on 27th of May [0]. Fedora 22 will continue to receive updates until approximately one month

Fedora 22 updates-testing report

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

rawhide report: 20151202 changes

2015-12-02 Thread Fedora Rawhide Report
Compose started at Wed Dec 2 05:15:04 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

Re: Non-image blocker process change proposal

2015-12-02 Thread Kamil Paral
> > 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 the case and it's the last blocking issue, selected tasks > > (like