Adam Jackson | 20 May 14:41 2015
Picon

Schedule for Wednesday's FESCo Meeting (2015-05-20)

Following is the list of topics that will be discussed in the FESCo
meeting Wednesday at 18:00UTC in #fedora-meeting on irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2015-05-20 18:00 UTC'

Links to all tickets below can be found at: 
https://fedorahosted.org/fesco/report/9

= Followups =

#topic #1441  Packaging: Practices for Migration of cron jobs to
systemd timer units 
.fesco 1441
https://fedorahosted.org/fesco/ticket/1441

= New business =

= Open Floor = 

For more complete details, please visit each individual ticket.  The
report of the agenda items can be found at
https://fedorahosted.org/fesco/report/9

If you would like to add something to this agenda, you can reply to
this e-mail, file a new ticket at https://fedorahosted.org/fesco,
e-mail me directly, or bring it up at the end of the meeting, during
(Continue reading)

Miroslav Suchý | 20 May 12:44 2015
Face
Picon

Building rawhide packages using Mock on EL{6,7} machines

If your workstation is EL{6,7} and you have recent Mock, you may find that building packages for Fedora
rawhide ends up
with failure.
You can read about this situation in my blogpost:

http://miroslav.suchy.cz/blog/archives/2015/05/20/why_mock_does_not_work_on_el_6_and_el7_and_how_to_fix_it/index.html

-- 
Miroslav Suchy, RHCA
Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys
--

-- 
devel mailing list
devel <at> lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Fedora Rawhide Report | 20 May 12:40 2015

rawhide report: 20150520 changes

Compose started at Wed May 20 05:15:04 UTC 2015
Broken deps for i386
----------------------------------------------------------
[InsightToolkit]
	InsightToolkit-4.7.1-4.fc23.i686 requires libhdf5_cpp.so.9
	InsightToolkit-4.7.1-4.fc23.i686 requires libhdf5.so.9
[OpenTK]
	OpenTK-1.1-1.4c.fc22.noarch requires mono(mscorlib) = 0:2.0.0.0
	OpenTK-1.1-1.4c.fc22.noarch requires mono(System.Xml) = 0:2.0.0.0
	OpenTK-1.1-1.4c.fc22.noarch requires mono(System.Windows.Forms) = 0:2.0.0.0
	OpenTK-1.1-1.4c.fc22.noarch requires mono(System.Drawing) = 0:2.0.0.0
	OpenTK-1.1-1.4c.fc22.noarch requires mono(System) = 0:2.0.0.0
[RepetierHost]
	RepetierHost-0.90D-2.fc21.noarch requires mono(mscorlib) = 0:2.0.0.0
	RepetierHost-0.90D-2.fc21.noarch requires mono(System.Xml) = 0:2.0.0.0
	RepetierHost-0.90D-2.fc21.noarch requires mono(System.Windows.Forms) = 0:2.0.0.0
	RepetierHost-0.90D-2.fc21.noarch requires mono(System.Drawing) = 0:2.0.0.0
	RepetierHost-0.90D-2.fc21.noarch requires mono(System.Core) = 0:3.5.0.0
	RepetierHost-0.90D-2.fc21.noarch requires mono(System) = 0:2.0.0.0
[banshee]
	banshee-2.6.2-9.fc23.i686 requires mono(mscorlib) = 0:2.0.0.0
	banshee-2.6.2-9.fc23.i686 requires mono(System.Xml) = 0:2.0.0.0
	banshee-2.6.2-9.fc23.i686 requires mono(System.Core) = 0:3.5.0.0
	banshee-2.6.2-9.fc23.i686 requires mono(System) = 0:2.0.0.0
	banshee-2.6.2-9.fc23.i686 requires mono(Mono.Posix) = 0:2.0.0.0
	banshee-2.6.2-9.fc23.i686 requires mono(Mono.Cairo) = 0:2.0.0.0
	banshee-2.6.2-9.fc23.i686 requires mono(ICSharpCode.SharpZipLib) = 0:2.84.0.0
[bless]
	bless-0.6.0-14.fc22.i686 requires mono(mscorlib) = 0:2.0.0.0
	bless-0.6.0-14.fc22.i686 requires mono(System.Xml) = 0:2.0.0.0
(Continue reading)

Jens Petersen | 20 May 11:50 2015
Picon

updating f22 llvm to 3.5.2 release?

Hi,

I opened https://bugzilla.redhat.com/show_bug.cgi?id=1221923
about this too but thought it would be good to ask here.

F22 currently has llvm-3.5.0 (F23 is now on 3.6.0):
I believe there is a newer 3.5.2 bugfix release -
would it make sense to make a F22 update for that?
Is there any expected risk with doing that?

Anyway for F23 I probably have to make a llvm35 package
again for building ghc-7.10 on armv7 (and ideally aarch64).
3.5.0 has a critical bug that breaks ghc, so it would
be based on 3.5.2 anyway.

Jens
--

-- 
devel mailing list
devel <at> lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Petr Schindler | 20 May 10:44 2015
Picon

[Test-Announce] Fedora 22 Final Release Compose 1 (RC1) Available Now!

Fedora 22 Final Release Compose 1 (RC1) is now available for testing.
Please help us complete as much of the validation testing as we can!

This is first release compose so everything should be tested properly.

Content information, including changes, can be found at 
https://fedorahosted.org/rel-eng/ticket/6166#comment:9 . Please see the
following pages for
download links and testing instructions. Normally dl.fedoraproject.org 
should provide the fastest download, but download-
ib01.fedoraproject.org is available as a mirror (with an approximately 
1 hour lag) in case of trouble. To use it, just replace "dl" with 
"download-ib01" in the download URL.

Installation:

https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test

Base:

https://fedoraproject.org/wiki/Test_Results:Current_Base_Test

Workstation and Desktop:

https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test

Server:

https://fedoraproject.org/wiki/Test_Results:Current_Server_Test

(Continue reading)

opensource | 19 May 22:09 2015

Orphaned Packages in rawhide (2015-05-19)

The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life

Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one. Please adopt the affected package or
retire your depending package to avoid broken dependencies, otherwise your
package will be retired when the affected package gets retired.

      Package                    (co)maintainers              Status Change 
===========================================================================
blahtexml              orphan                                 2 weeks ago   
gvrpcd                 orphan                                 2 weeks ago   
mozilla-noscript       orphan, ixs, tomspur                   0 weeks ago   
nss_compat_ossl        orphan, kdudka, mharmsen, rcritten,    2 weeks ago   
                       rrelyea                                              
obexftp                orphan, itamarjp                       6 weeks ago   
ovirt-node             orphan, apevec, fabiand, jboggs,       2 weeks ago   
                       mburns72h, pmyers                                    
python-sqlalchemy0.5   orphan                                 7 weeks ago   
python-sqlamp          orphan                                 7 weeks ago   

The following packages require above mentioned packages:
Depending on: nss_compat_ossl (1), status change: 2015-04-29 (2 weeks ago)
	centerim (maintained by: lkundrak, awjb)
		centerim-4.22.10-17.fc23.i686 requires libnss_compat_ossl.so.0
		centerim-4.22.10-17.fc23.src requires nss_compat_ossl-devel = 0.9.6-9.fc22

Depending on: python-sqlalchemy0.5 (1), status change: 2015-03-31 (7 weeks ago)
(Continue reading)

Jaroslav Reznik | 19 May 12:26 2015
Picon

Fedora 22 Final Release Readiness Meeting :: Thursday, May 21, 19:00 UTC

Fedora 22 Final Release Readiness Meeting.

date: 2015-05-21 place: irc.freenode.net in #fedora-meeting-2
time: 19:00 UTC (3 PM EDT, 12 noon PDT, 21:00 CEST)

This Thursday, May 21, we will meet to make sure we are coordinated
and ready for the Final release of Fedora 22 on Tuesday, May 26, 2015.
Please note that this meeting will occur on May 21 even if the
release is delayed at the Go/No-Go meeting on the same day two hours
earlier.

You may received this message several times, but I was asked to open this
meeting to the teams and I'll also hope this will raise awareness and more
team representatives will come to this meeting. This meeting works best
when we have representatives from all of the teams. We also have a badge!

Jaroslav
_______________________________________________
devel-announce mailing list
devel-announce <at> lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce
--

-- 
devel mailing list
devel <at> lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Jaroslav Reznik | 19 May 12:35 2015
Picon

[Test-Announce] Fedora 22 Final Go/No-Go Meeting, Thursday, May 21 <at> 17:00 UTC

Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 22.

Thursday, May 21, 2015 17:00 UTC (1 PM EDT, 10 AM PDT, 19:00 CEST)

"Before each public release Development, QA and Release Engineering meet
to determine if the release criteria are met for a particular release.
This meeting is called the Go/No-Go Meeting."

"Verifying that the Release criteria are met is the responsibility of
the QA Team."

For more details about this meeting see:
https://fedoraproject.org/wiki/Go_No_Go_Meeting

In the meantime, keep an eye on the Fedora 22 Final Blocker list:
http://qa.fedoraproject.org/blockerbugs/milestone/22/final/buglist

We don't have RC yet but seem like we're very close to it - testing
heroes will be needed to cover all required tests by this meeting.

Jaroslav

_______________________________________________
test-announce mailing list
test-announce <at> lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
--

-- 
devel mailing list
devel <at> lists.fedoraproject.org
(Continue reading)

Jaroslav Reznik | 19 May 12:35 2015
Picon

Fedora 22 Final Go/No-Go Meeting, Thursday, May 21 <at> 17:00 UTC

Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 22.

Thursday, May 21, 2015 17:00 UTC (1 PM EDT, 10 AM PDT, 19:00 CEST)

"Before each public release Development, QA and Release Engineering meet
to determine if the release criteria are met for a particular release.
This meeting is called the Go/No-Go Meeting."

"Verifying that the Release criteria are met is the responsibility of
the QA Team."

For more details about this meeting see:
https://fedoraproject.org/wiki/Go_No_Go_Meeting

In the meantime, keep an eye on the Fedora 22 Final Blocker list:
http://qa.fedoraproject.org/blockerbugs/milestone/22/final/buglist

We don't have RC yet but seem like we're very close to it - testing
heroes will be needed to cover all required tests by this meeting.

Jaroslav

_______________________________________________
devel-announce mailing list
devel-announce <at> lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce
--

-- 
devel mailing list
devel <at> lists.fedoraproject.org
(Continue reading)

Martin Stransky | 19 May 10:38 2015
Picon

Rapid release for security updates

Hi guys,

is there any mechanism how to speed up release of critical security 
fixes by Fedora update system?

For instance Firefox packages are released *week* after official Mozilla 
release which is really bad.

Any idea here?

ma.
--

-- 
devel mailing list
devel <at> lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Matthew Miller | 19 May 01:44 2015

simplestreams json or index.asc for deliverables in the new list-of-deliverables?

FESCo Ticket #1427 <https://fedorahosted.org/fesco/ticket/1427>
formalizes the list of deliverables for each Fedora release. Cool.

Let's go a step beyond this and make a machine-readable list, at least
of image-based deliverables. One approach would be to use using Ubuntu's simplestreams
format, documented at
<http://bazaar.launchpad.net/~smoser/simplestreams/trunk/view/head:/doc/README.>

A second option would be the index.asc as used by virt-builder:
<https://fedorahosted.org/rel-eng/ticket/5805>

That way, we'd have a standardized way for applications to find and
download/launch/whatever various Fedora images. This is a definite need
(see https://fedorahosted.org/cloud/ticket/93) and rather than
inventing a new wheel, maybe we could see if we could pound one of
these into shape.

-- 
Matthew Miller
<mattdm <at> fedoraproject.org>
Fedora Project Leader
--

-- 
devel mailing list
devel <at> lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Gmane