devel-announce October 2017

devel-announce@lists.fedoraproject.org

6 participants
17 discussions

[Guidelines change] Changes to the packaging guidelines
by Jason L Tibbitts III 27 Oct '17

27 Oct '17

Here are the recent changes to the packaging guidelines. ----- Following releng approval, the restrictions on the use of rich/Boolean dependencies have been lifted. * https://fedoraproject.org/wiki/Packaging:Guidelines#Rich.2FBoolean_dependen… * https://pagure.io/packaging-committee/issue/559 ----- Packaging guidelines for Rust have been added. * https://fedoraproject.org/wiki/Packaging:Rust * https://pagure.io/packaging-committee/issue/705 ----- A new section was added to the packaging guidelines regarding shebang lines. It forbids the use of 'env' and codifies the longstanding rpmlint rule that non-executable files should not have shebang lines. * https://fedoraproject.org/wiki/Packaging:Guidelines#Shebang_lines * https://pagure.io/packaging-committee/issue/700 ----- Appstream metadata guidelines were updated to reflect the new location into which appdata files should be placed. * https://fedoraproject.org/wiki/Packaging:AppData * https://pagure.io/packaging-committee/issue/704 ----- The python guidelines were modified to forbid the use of /usr/bin/python in shebang lines or as a dependency of a package. * https://fedoraproject.org/wiki/Packaging:Python#Multiple_Python_Runtimes * https://pagure.io/packaging-committee/issue/698 ----- The SourceURL guideliens were altered to Use a simplified form for github URLs. * https://fedoraproject.org/wiki/Packaging:SourceURL#Git_Hosting_Services * https://pagure.io/packaging-committee/issue/697 ----- The section on bundled libraries was expanded with more explicit instructions on constructing the Provides: line which indicates the bundling. * https://fedoraproject.org/wiki/Packaging:Guidelines#Bundling_and_Duplicatio… * https://pagure.io/packaging-committee/issue/696 ----- The section on statically linking executables has been completely revamped to remove the need for committee intervention and to make it more obvious that there is no prohibition on statically linking to build artifacts within a single package. * https://fedoraproject.org/wiki/Packaging:Guidelines#Statically_Linking_Exec… * https://pagure.io/packaging-committee/issue/692

1 0

Autumn Elections 2017: Mindshare elections
by Jan Kurik 27 Oct '17

27 Oct '17

Hi everybody, as approved by Fedora Council [1] we are replacing the FAmSCo elections with elections to a brand new body "Mindshare". You can fine more information about the Mindshare on its wiki page [2]. For this election cycle we have opened 2 seats into this body. At the moment we are collecting questions for candidates in election's Questionnaire [3]. Please have a look at it and contribute with your questions you would like to see answered by candidates to these seats. The Questionnaire [3] is open for new questions till November 6th. [1] https://pagure.io/Fedora-Council/tickets/issue/142 [2] https://fedoraproject.org/wiki/Mindshare [3] https://fedoraproject.org/wiki/Elections/Questionnaire Thanks for your support 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 26 Oct '17

26 Oct '17

Release status of the Fedora 27 Final is NO-GO. The next Go/No-Go meeting is planned on Thursday, November 2nd. The GA date for the F27 Final release moves from Target date to Rain date, which is 2017-Nov-07. For more details please check the Go/No-Go meeting minutes[1]. [1] https://meetbot.fedoraproject.org/fedora-meeting-1/2017-10-26/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 Server Beta status (3rd round) is NO-GO
by Jan Kurik 26 Oct '17

26 Oct '17

Release status of the Fedora 27 Server Beta is NO-GO. The next Go/No-Go meeting is planned on Thursday, November 2nd together with second round of F27 Final Go/No-Go meeting. The F27 Server Beta release slips for one week. The slip also affects the F27 Server GA, it moves to 2017-Dec-19 having Go/No-Go meeting on 2017-Dec-14. For more information please check the F27 Server Beta Go/No-Go meeting minutes [1]. [1] https://meetbot.fedoraproject.org/fedora-meeting-1/2017-10-26/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

F28 System Wide Change: NSS Default File Format SQL
by Jan Kurik 26 Oct '17

26 Oct '17

= System Wide Change: NSS Default File Format SQL = https://fedoraproject.org/wiki/Changes/NSSDefaultFileFormatSql Change owner(s): * Kai Engert <kaie(a)redhat.com> Change the NSS library default to use the sqlite based data storage, when applications don't specify their preferred storage file format. == Detailed Description == Applications that use the NSS library often use a database for storage of keys, certificates and trust. NSS supports two different file formats, one called DBM (based on berkeley DB files) and another one called SQL (based on sqlite DB files). Today's default file format used by NSS, used when applications omit the type parameter, is the older DBM file format, which forbids parallel access to the storage. The suggestion is to change the default file format to SQL, which allows parallel access to the storage. Applications, or users using the NSS command line utilities, often provide the database storage location using a simple directory path parameter. Some might not be aware, or forget, that the parameter can be prefixed with a type modifier, either "dbm:" or "sql:". As a result, when not providing this parameter, the file format used will be the fragile DBM file format. This is particuarly problematic, if a user attempts to modify the NSS storage using command line tools, while another process, such as a daemon, is running concurrently, which also accesses the same database in the DBM file format. This often results in corrupted database storage, which cannot be recovered. By changing the default, all applications that currently use the DBM file format, will automatically be migrated to the SQL file format. NSS has the ability to discover if a storage location (a directory) contains the DBM file format. If configured to use the modern SQL format, NSS will automatically perform a one-time conversion from the DBM to the SQL format. The same applies to the NSS command line utilities. If the NSS library default is changed to SQL, the NSS tools will also trigger the one-time conversion, or access the already converted files. == Scope == * Proposal owners: A small downstream patch needs to be applied to the NSS library package, which changes the library default. * Other developers: It's up to developers of NSS applications, if they accept the new default and an automatic conversion, or if they prefer to continue to use the classic DBM storage format. Although not recommended, developers can easily do so, by adding a "dbm:" prefix to the storage parameter they provide to NSS at NSS library initialization time. * Release engineering: [1] No help should be necessary. No mass rebuild necessary. * Policies and guidelines: N/A * Trademark approval: N/A [1] https://pagure.io/releng/issue/6883 -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic

1 0

Heads Up - openssl makefile and scripts for creating self signed certificates
by Tomas Mraz 24 Oct '17

24 Oct '17

I was asked here to merge pull request that moves the openssl makefile and scripts for creating self signed certificates to /usr/share/doc. I am not sure this is the right thing to do as these are definitely still used currently. Although it is much easier now to set up proper certificates for your servers with Let's Encrypt, it is still not fully automatable process (it needs at least some set up at the beginning for the first issued certificate). Thus it cannot be included for example in rpm packages %post scripts, etc. At least I would like to know from maintainers of packages that depend on openssl whether they currently use the makefile or the scripts to create self signed certificate for the service. Tomas Mraz

1 0

Fedora 27 Final Release Readiness Meeting on Thursday, October 26 @ 19:00 UTC
by Jan Kurik 24 Oct '17

24 Oct '17

Join us on irc.freenode.net in #fedora-meeting-1 for the Fedora 27 Final Release Readiness Meeting meeting. The meeting is going to be held on Thursday, Oct 26, 2017 at 19:00 UTC. Please check the [1] link for your time zone. We will meet to make sure we are coordinated and ready for the Final release of Fedora 27. Please note that this meeting is going to be held 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 it is by purpose to open this meeting to the teams and to raise awareness, so hopefully more team representatives will come to this meeting. This meeting works best when we have representatives from all of the teams. For more information please check the [2] link. [1] https://apps.fedoraproject.org/calendar/meeting/7385/ [2] https://fedoraproject.org/wiki/Release_Readiness_Meetings Thank you for your support, 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

F27 Server Beta & F27 Final Go/No-Go Meeting on Thursday, October 26th @ 17:00 UTC
by Jan Kurik 24 Oct '17

24 Oct '17

Join us on irc.freenode.net in #fedora-meeting-1 for this important meeting, wherein we shall determine the readiness of the Fedora 27 Server Beta [1] as well as Fedora 27 Final [2] releases. The meeting is going to be held on Thursday, October 26th, 2017 at 17:00 UTC. Please check the links [1] and [2] for your time zone. [1] https://apps.fedoraproject.org/calendar/meeting/7520/ [2] https://apps.fedoraproject.org/calendar/meeting/7386/ [3] https://qa.fedoraproject.org/blockerbugs/milestone/27/server-beta/buglist [4] https://qa.fedoraproject.org/blockerbugs/milestone/27/final/buglist Thank you in advance for your support. 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

Autumn Elections 2017: Collection of questions for Questionnaire has been started
by Jan Kurik 23 Oct '17

23 Oct '17

For this Election cycle [1] we are going to follow a new way how Elections are organized. It is an outcome of a discussion on Council level [2] trying to improve participation of the Fedora Community in the election process. Today we are starting collection of questions for Election Questionnaire [3]. The collection period ends one week after the F27 Final GA date, which means there is a time at least to November 6th to collect these questions. For the beginning I have copied the questions from previous Election cycle. Feel free to add more questions or modify the current questions of the Questionnaire [3]. The full schedule of the Autumn Elections 2017 is available on the Elections wiki page [4] and on the detailed schedule for F27 [5]. [1] https://fedoraproject.org/wiki/Elections [2] https://pagure.io/Fedora-Council/tickets/issue/135#comment-467523 [3] https://fedoraproject.org/wiki/Elections/Questionnaire [4] https://fedoraproject.org/wiki/Elections [5] https://fedorapeople.org/groups/schedule/f-27/f-27-elections.html 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 Server Beta status (2nd round) is NO-GO
by Jan Kurik 19 Oct '17

19 Oct '17

Release status of the Fedora 27 Server Beta is NO-GO. The next Go/No-Go meeting is planned on Thursday, October 26th together with F27 Final Go/No-Go meeting. The F27 Server Beta release slips for one week. The slip also affects the F27 Server GA, it moves to 2017-Dec-12 having Go/No-Go meeting on 2017-Nov-30. The rain date for the F27 Server GA moves to 2017-Dec-19 having the Go/No-Go on 2017-Dec-14. For more information please check the F27 Server Beta Go/No-Go meeting minutes [1][2]. [1] https://meetbot.fedoraproject.org/fedora-meeting-1/2017-10-19/f27-server-be… [2] https://meetbot.fedoraproject.org/fedora-meeting-1/2017-10-19/f27-server-be… 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

devel-announce October 2017