devel-announce November 2017

devel-announce@lists.fedoraproject.org

4 participants
18 discussions

F28 System Wide Change: time-1.8
by Jan Kurik 10 Nov '17

10 Nov '17

= System Wide Change: time-1.8 = https://fedoraproject.org/wiki/Changes/time-1.8 Change owner(s): * Petr <ppisar AT redhat DOT com> A new time tool version 1.8 has changed output format. == Detailed Description == After many years a new 1.8 version of time tool was released. This version brings some noticeable changes: License changed from (GPLv2+) to (GPLv3+ and GFDL). Additional exit codes are used to report measured command failures and failures to execute the command. A measured command failure is reported by default. See the first line in this output: $ time /usr/bin/false Command exited with non-zero status 1 0.00user 0.00system 0:00.00elapsed 100%CPU (0avgtext+0avgdata 1196maxresident)k 0inputs+0outputs (0major+55minor)pagefaults 0swaps In previous Fedora versions, the first line was printed only if -v option was specified. This is not true anymore and the line is printed by default. You can disable it with a new -q option: $ time -q /usr/bin/false 0.00user 0.00system 0:00.00elapsed 100%CPU (0avgtext+0avgdata 1268maxresident)k 0inputs+0outputs (0major+55minor)pagefaults 0swaps Because this violated POSIX mode, Fedora changed time-1.8 not to print the first line when invoked with -p option and upstream accepted the change so that future time versions will behave like Fedora. For Fedora users, there is no change in the POSIX mode output: $ time -p /usr/bin/false real 0.00 user 0.00 sys 0.00 If you use time tool in your script without the -p option, then either adjust your script to expect different output, or add -q option. Be ware of portability across distributions using different time versions. == Scope == * Proposal owners: The time package will be upgraded and patched to preserve output format in the POSIX mode. * Other developers: Review their scripts and packages whether they use time' in non-POSIX mode and parse time's output. If they are affected, they should add -q option to the time command, or adjust their code do deal with the new first line. * Release engineering: https://pagure.io/releng/issue/7153 * List of deliverables: Not affected * Policies and guidelines: No change is needed. * Trademark approval: No approval is needed. -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic

1 0

Fedora 27 Modular Server Beta status is GO
by Jan Kurik 09 Nov '17

09 Nov '17

The Fedora-Modular-27-20171108.2 RC compose [1][2] is considered as GOLD and is going to be shipped on 2017-Nov-14 as F27 Modular Server Beta release. For more information please check the meeting minutes [3] from the Go/No-Go meeting. [1] http://kojipkgs.fedoraproject.org/compose/27/Fedora-Modular-27-20171108.2 [2] http://dl.fedoraproject.org/pub/alt/stage/27_Modular_Beta-1.5 [3] https://meetbot.fedoraproject.org/fedora-meeting-1/2017-11-09/f27-final-and… Jan -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic

1 0

Fedora 27 Final status is GO
by Jan Kurik 09 Nov '17

09 Nov '17

The Fedora-27-20171105.0 (Fedora_27_RC_1.6 ) compose [1][2] is considered as GOLD and is going to be shipped on 2017-Nov-14 as Fedora 27 Final release. For more information please check the meeting minutes [3] from the Go/No-Go meeting. [1] https://kojipkgs.fedoraproject.org/compose/27/Fedora-27-20171105.0/compose/ [2] http://dl.fedoraproject.org/pub/alt/stage/27_RC-1.6/ [3] https://meetbot.fedoraproject.org/fedora-meeting-1/2017-11-09/f27-final-and… Regards, Jan -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic

1 0

Fedora 27 Final status is NO-GO
by Jan Kurik 06 Nov '17

06 Nov '17

Release status of the Fedora 27 Final is NO-GO. The next Go/No-Go meeting is planned on Thursday, November 9th. The GA date for the F27 Final release moves 2017-Nov-14. For more details please check the Go/No-Go meeting minutes[1]. [1] https://meetbot.fedoraproject.org/teams/f27-final-and-server-beta-go-no-go-… Regards, Jan -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic

1 0

F28 System Wide Change: Ruby 2.5
by Jan Kurik 06 Nov '17

06 Nov '17

= System Wide Change:Ruby 2.5 = https://fedoraproject.org/wiki/Changes/Ruby_2.5 Change owner(s): * Vít Ondruch <vondruch AT redhat DOT com> Ruby 2.5 is the latest stable version of Ruby. Many new features and improvements are included for the increasingly diverse and expanding demands for Ruby. With this major update from Ruby 2.4 in Fedora 26 to Ruby 2.5 in Fedora 28, Fedora becomes the superior Ruby development platform. == Detailed Description == Ruby 2.5 is upstream's new major release of Ruby. Many new features and improvements are included. === New Features === * Top-level constant look-up is removed. * rescue/else/ensure are allowed inside do/end blocks. * refinements take place in string interpolations. * yield_self === Other notable changes since 2.4 === * Merge Onigmo to 6.1.1. It adds absent operator Note that Ruby 2.4.1 also includes this change. * Merge bundler to standard libraries. * Merge rubygems-2.6.13. * Merge rdoc-6.0.0.beta2. Change lexer IRB based one to Ripper. It much improves the speed of generating document. / Update supported Unicode version to 10.0.0. == Scope == * Proposal owners: - Finish packaging of Ruby 2.5. Current changes available in private-ruby-2.5 branch of ruby package in dist-git. - Rebuilding of Ruby packages providing native extensions (i.e. packages which depends on libruby). * Other developers: - Rebuild of packages with binary extensions (i.e. packages which depends on libruby) will be handled automatically, but some packages might need fixes/updates to support Ruby 2.5 properly. * Release engineering: - https://pagure.io/releng/issue/7142 - Separate Koji tag for package rebuild will be needed. * List of deliverables: N/A (not needed for this Change) * Policies and guidelines: N/A (not needed for this Change) * Trademark approval: N/A (not needed for this Change) -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic

1 0

F28 Self Contained Change: Sugar 0.112
by Jan Kurik 06 Nov '17

06 Nov '17

= Proposed Self Contained Change: Sugar 0.112 = https://fedoraproject.org/wiki/Changes/Sugar-112 Change owner(s): * Peter Robinson <pbrobinson at fedoraproject dot org > Update Sugar to the new upstream 0.112 stable feature release. == Detailed Description == We want to provide the new version of the Sugar desktop environment as well as more activities to allow further building upon the collaborative environment. Users curious about the Sugar interface can test out Sugar on an existing Fedora system by selecting the Sugar environment from their display manager. Developers interested in working on the Sugar interface or writing activities can have a development platform without needing an XO laptop. == Scope == * Proposal owners: Update to the latest Sugar UX, update and test Activities and other integration with the distro. * Other developers: N/A (not a System Wide Change) * Release engineering: Ticket #7134: https://pagure.io/releng/issue/7134 * Policies and guidelines: N/A (not a System Wide Change) * Trademark approval: N/A (not needed for this Change) -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic

1 0

Fedora 27 Server Beta status (4th round) is NO-GO
by Jan Kurik 02 Nov '17

02 Nov '17

Due to missing RC for the F27 Server Beta release the release status of the Fedora 27 Server Beta is NO-GO. The next Go/No-Go meeting is planned on Thursday, November 9th. The F27 Server Beta release slips for one week on 2017-Nov-14. The slip also affects the F27 Server GA and it moves to 2018-Jan-09, having Go/No-Go meeting on 2018-Jan-04. Regards, Jan -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic

1 0

long waiting times for COPR jobs
by Michal Novotny 01 Nov '17

01 Nov '17

Hello, lately, COPR pending job queues are holding jobs for pretty long time (even hours). This is a buggy behaviour and we will be doing our best to fix this issue in the following days. Thank your for your patience COPR team

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

devel-announce November 2017