devel-announce July 2017

devel-announce@lists.fedoraproject.org

7 participants
31 discussions

Outage: HyperKitty database schema change - 2017-08-04 21:00 UTC
by Aurelien Bompard 28 Jul '17

28 Jul '17

There will be an outage starting at 2017-08-04 21:00 UTC, which will last approximately 15 hours. To convert UTC to your local time, take a look at https://fedoraproject.org/wiki/UTCHowto or run: date -d '2017-08-04 21:00 UTC' Reason for outage: important HyperKitty database schema change Affected Services: * HyperKitty, the mailing-list archives and reading interface * Postorius, the mailing-list administration interface Unaffected Services: Mailman will not be affected, emails sent to the lists will continue to be delivered during the outage, but they will not be archived at that time (the archiver will be offline). The emails delivered during the outage will be added to the archives when they are back online. Ticket Link: https://pagure.io/fedora-infrastructure/issue/6184 Contact Information: Please join #fedora-admin in irc.freenode.net or add comments to the ticket for this outage above.

1 0

Change Checkpoint: Proposal submission deadline (Self contained Changes) on Fedora 27 is today
by Jan Kurik 25 Jul '17

25 Jul '17

Hi everyone! Today is the submission deadline for Self contained Changes of Fedora 27 [1]. Please schedule your upcoming Changes (Self contained as well as System wide) for the next (Fedora 28) release. Branch of Fedora 27 from Rawhide is then planned on 2017-Aug-15. [1] https://fedoraproject.org/wiki/Releases/27/Schedule 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

Rawhide Rebase Warning to Package Maintainers
by Jan Kurik 25 Jul '17

25 Jul '17

Greetings, This e-mail is intended to inform you about the upcoming Bugzilla changes happening on 2017-08-15 (Rawhide bug rebase) and what you need to do, if anything. We will be automatically changing the version for most rawhide bugs to Fedora 27. This will result in regular bugs reported against rawhide during the Fedora 27 development cycle being changed to version ‘27' instead of their current assignment, ‘rawhide’. This is to align with the branching of Fedora 27 from rawhide and to more accurately tell where in the lineage of releases the bug was last reported. Note that this procedure does not apply to bugs that are open for the ‘Package Review’ or 'kernel' components or bugs that have the ''FutureFeature'' or ''Tracking'' keywords set. These will stay open as rawhide bugs indefinitely. If you do not want your bugs changed to version ‘27‘, add the ''FutureFeature'' keyword. If you need help changing a large amount of bugs manually, we’d be glad to help. The process was re-approved by FESCo https://pagure.io/fesco/issue/1096 . Jan -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic

1 0

Announcing Boltron!
by langdon 25 Jul '17

25 Jul '17

As you may have seen on Fedora Magazine[1], the Modularity and Server Working Groups are very excited to announce the availability of the Boltron Preview Release[2]! I highly recommend you read the post[1], but you can also jump to getting the container, found in the Fedora Registry: docker run --rm -it registry.fedoraproject.org/f26-modular/boltron Please do check out the Getting Started[3] page and the Known Issues[4] before you get too far. We also built some feedback mechanisms, one is a Walkthrough[5] and one is more General Feedback[6]. If you have time, we would love it if you could try the walkthrough[5]. On behalf of all the people involved, Langdon White Modularity Objective PS: and a massive thanks to all the people involved.. zodbot ++ all the people! [1]: Blog Post: https://fedoramagazine.org/announcing-boltron/ [2]: Docs: https://docs.pagure.org/modularity/boltron/ [3]: Getting Started: http://bit.ly/mod-instruct [4]: Known Issues: https://docs.pagure.org/modularity/prototype/boltron/issues.html [5]: Walkthrough: http://bit.ly/mod-walkthrough [6]: General Feedback: http://bit.ly/mod-feedback

1 0

F27 Self Contained Change: Platform Python Stack
by Jan Kurik 25 Jul '17

25 Jul '17

= Proposed Self Contained Change: Platform Python Stack = https://fedoraproject.org/wiki/Changes/Platform_Python_Stack Change owner(s): * Miro Hrončok<python-maint at redhat dot com> A revisit of the System Python change https://fedoraproject.org/wiki/Changes/System_Python from Fedora 24. It has been renamed from System Python to Platform Python not to collide with upstream PEP 432. Platform Python will be a separate stack fo Python packages aimed to provide all necessary dependencies to run and build dnf. In Fedora 27 this will be Python 3.6 (same version as python3, but this might change in the future with the Modularity effort). == Detailed Description == The changes made during the System Python change from Fedora 24 will be reverted. A new platform-python (source) package will be created as a copy of the python3 package. Unlike python3, it will be changed so that: the location of files will not be /usr/lib/python3.6/ but /usr/lib/platform-python/ the script that generates the python(abi) requirement will be adapted to generate platform-python(abi) requirement for that location the location of the binary will be /usr/libexec/platform-python all the macros will use the platform python binary and will be renamed all subpackages will be named platform-python-* the debug build will be disabled the modules that are (before this change) not part of system-python-libs but rather python3-libs will relocate to platform-python-libs-devel to be available only on build-time platform-python-libs will provide platform-python(abi) instead of python(abi) Several packages (see bellow) will introduce a new platform-python- subpackage. Example specfile of such package: https://fedoraproject.org/wiki/Changes/Platform_Python_Stack#Detailed_Descr… The complete list of affected packages is not final yet. It should be all the Python build dependencies of dnf and their build dependencies as well, excluding packages only needed to build the documentation (normal python3- (or even python2-) packages will be used to build the documentation as it is now). Currently, we have established this as a list of packages: https://fedoraproject.org/wiki/Changes/Platform_Python_Stack#Detailed_Descr… == Scope == * Proposal owners: - identify a list of runtime and build dependencies of dnf - create a platform-python source package - change the script that generates the python(abi) requirements to also generate platform-python(abi) requirements - revert system-python related things from the python3 package (add appropriate provides/obsoletes) - add a platform-python- subpackage to identified list of packages - switch dnf to use that stack * Other developers: N/A (not a System Wide Change) * Release engineering: https://pagure.io/releng/issue/6917 * List of deliverables: N/A (not a System Wide Change) * 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

F27 Self Contained Change: OpenSSH Server Crypto Policy
by Jan Kurik 25 Jul '17

25 Jul '17

= Proposed Self Contained Change: OpenSSH Server Crypto Policy = https://fedoraproject.org/wiki/Changes/OpenSSH_Server_Crypto_Policy Change owner(s): * Jakub Jelen <jjelen AT redhat DOT com> OpenSSH clients follow the system-wide crypto policy since Fedora 26. This F27 change modifies the openssh server configuration to adhere to the system-wide policy. That will allow openssh server configuration to adapt to the multiple security levels offered system-wide. == Detailed Description == Currently, the set of cryptographic algorithms used in OpenSSH is defined by upstream and Fedora just inherits what upstream considers secure. If there are special requirements for the security, manual modifications of the configuration files is required, which also prevents package manager to update the configuration file with future updates and can possibly leave enabled insecure algorithms. Since Fedora 26 OpenSSH clients are following crypto policies defined system-wide using Include configuration option in the main ssh_config. We can not use the same method in the server, because OpenBSD did not accept yet the patch supporting the same in the server configuration (upstream bug) so we will work out other way of doing that without disrupting existing workflows. For more information about Crypto Policy, see the appropriate wiki page Changes/CryptoPolicy describing the concept in whole. == Scope == * Proposal owners: Create a replace script, that will replace predefined comment in the configuration with configuration generated according to current crypto policies. Make systemd trigger this script on restart. * Other developers: N/A (not a System Wide Change) * Release engineering: https://pagure.io/releng/issue/6915 * List of deliverables: N/A (not a System Wide Change) * 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

Elections July/August 2017 to FESCo, Council, FAmSCo - Nomination period is now open
by Jan Kurik 24 Jul '17

24 Jul '17

Greetings, FESCo, Council and FAmSCo elections are now open and we're looking for new candidates: https://fedoraproject.org/wiki/Elections If you are interested in these roles, please add yourself to the lists of nominees before 23:59:59 UTC on July 31st, 2017! If you wish to nominate someone else, please consult with that person ahead of time. If you know someone who would be a good candidate, now is a great time to make sure they're thinking about it. For FESCo we have opened 4 seats: https://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations For Council we have opened 1 seat: https://fedoraproject.org/wiki/Council/Nominations For FAmSCo we have opened 3 seats: https://fedoraproject.org/wiki/FAmSCo_nominations The Elections schedule is as follows: * July 25 - July 31: Nomination period * August 01 - August 07: Campaign period. * August 08 - August 14: Voting Open * August 15: Results announcement Elections Questionnaire needs more questions for email/Community blog interviews! If you have anything you would like to ask candidates to FESCo, FAmSCo or to Council, please add it to the wiki. http://fedoraproject.org/wiki/Elections/Questionnaire Read more about the FESCo, FAMSCo ans Council at: http://fedoraproject.org/wiki/Development/SteeringCommittee https://fedoraproject.org/wiki/Fedora_Ambassadors_Steering_Committee http://fedoraproject.org/wiki/Council 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

Reminder: Fedora 24 End Of Life on 2017-Aug-08
by Jaroslav Reznik 21 Jul '17

21 Jul '17

Fedora 24 support is going to be EOL on Tuesday, August 08th, 2017. At this day we are going to close all the Fedora 24 bugs which will remain open [1]. You have last few weeks to submit your updates to the Fedora 24, if you have any, before the Fedora 24 release becomes unsupported. [1] https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedor… Jaroslav

1 0

F27 Self Contained Change: libpinyin 2.1
by Jaroslav Reznik 19 Jul '17

19 Jul '17

= Proposed Self Contained Change: libpinyin 2.1 = https://fedoraproject.org/wiki/Changes/libpinyin2.1 Change owner(s): * Peng Wu <pwu(a)redhat.com> libpinyin 2.1 will merge libzhuyin code and replace the package == Detailed Description == Actually libzhuyin uses very similar code as libpinyin. After merged libzhuyin into libpinyin, it will bring some libpinyin features to libzhuyin. == Scope == * Proposal owners: merge libzhuyin code into libpinyin. merge libzhuyin data into ibus-libzhuyin. retire libzhuyin package for Fedora 27. * Other developers: N/A (not a System Wide Change) * Release engineering: [1] * Policies and guidelines: N/A (not a System Wide Change) * Trademark approval: N/A (not needed for this Change) [1] https://pagure.io/releng/issue/6912 Jaroslav

1 0

F27 Self Contained Change: Chinese Serif Fonts
by Jaroslav Reznik 19 Jul '17

19 Jul '17

= Proposed Self Contained Change: Chinese Serif Fonts = https://fedoraproject.org/wiki/Changes/ChineseSerifFonts Change owner(s): * Peng Wu <pwu(a)redhat.com> Fedora already provides default Chinese Sans fonts, now Fedora 27 will also provide default Chinese Serif fonts. == Detailed Description == Adobe and Google released good quality Chinese Sans and Serif fonts now. Now Fedora 27 will package the Chinese fonts, and use the fonts as default Chinese fonts. == Scope == * Proposal owners: new packages for adobe-source-han-serif-cn-fonts and adobe-source-han-serif-tw-fonts. update font packages to use both Chinese Sans and Serif fonts update fedora-comps to install the Chinese Sans and Serif fonts by default * Other developers: N/A (not a System Wide Change) * Release engineering: [1] * Policies and guidelines: N/A (not a System Wide Change) * Trademark approval: N/A (not needed for this Change) [1] https://pagure.io/releng/issue/6911 Jaroslav

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

devel-announce July 2017