Schedule for Friday's FESCo Meeting (2019-05-24)
Following is the list of topics that will be discussed in the FESCo meeting Friday at 15: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 '2019-05-24 15:00 UTC' Links to all issues to be discussed can be found at: https://pagure.io/fesco/report/meeting_agenda = Discussed and Voted in the Ticket = knot / knot-resolver package rebase exception request https://pagure.io/fesco/issue/2129 DECISION (+3, 0, -1) = Followups = No open tickets = New business = No open tickets = Open Floor = Meeting will be held for Open Floor For more complete details, please visit each individual issue. The report of the agenda items can be found at https://pagure.io/fesco/report/meeting_agenda If you would like to add something to this agenda, you can reply to this e-mail, file a new issue at https://pagure.io/fesco, e-mail me directly, or bring it up at the end of the meeting, during the open floor topic. Note that added topics may be deferred until the following meeting. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora 31 System-Wide Change proposal: RPM 4.15
https://fedoraproject.org/wiki/Changes/RPM-4.15 == Summary == Update RPM to the 4.15.0 release. == Owner == * Name: User:pmatilai, User:ffesti * Email: pmati...@redhat.com,ffe...@redhat.com == Detailed Description == RPM 4.15 contains numerous improvements over previous versions * Faster builds due to increased parallelism * Dynamic build dependency generator (planned) * Caret version operator (the opposite of tilde) * String data is returned as surrogate-escaped utf-8 in Python 3 bindings * %patchlist and %sourcelist spec sections for minimal boilerplate patch and source declarations * Experimental chroot operations for non-root users * Many error and warning report improvements * A new plugin for issuing audit log events on package install/update/erase * Native support for Lua 5.2-5.3 without compat defines in Lua * Numerous other improvements and bugfixes: https://rpm.org/wiki/Releases/4.15.0 Rawhide rpm will be updated to 4.15 alpha once released and updated through beta and rc cycles, 5.15.0 final release is expected prior to F31 final freeze. == Benefit to Fedora == See above. == Scope == * Proposal owners: ** Rebase RPM ** help Python binding users adjust to the string change ** help coordinate for macro + helper script removals * Other developers: ** Test new release, report issues and bugs. ** Fix Python 3 string/bytes usages in API users (https://bugzilla.redhat.com/show_bug.cgi?id=1693751 already in progress in rawhide) * Release engineering: [https://pagure.io/releng/issue/8380 #8380] * Policies and guidelines: As always, utilizing new rpm features is subject to packaging guidelines, but the time for this is after the new version has properly landed. There is no need to change guidelines, any new features are optional. * Trademark approval: N/A (not needed for this Change) == Upgrade/compatibility impact == * Python 3 bindings see a dramatic change as all string data is now returned as utf-8 encoded string instead of bytes, but this is already being test-driven in rawhide and at least anaconda, dnf and mock are already compatible: https://bugzilla.redhat.com/show_bug.cgi?id=1631292 * Similar to compiler updates, some previously working specs might fail to build due to stricter error checking and the like. * Some long-standing perl and python macros and helpers have been removed from rpm and might need either changes to packages or redhat-rpm-config == How To Test == Rpm receives a thorough and constant testing via every single package build, system installs and updates. New features can be tested specifically as per their documentation. == User Experience == There are no significant user experience changes, but some more minor ones include: * faster package builds on SMP systems * improved diagnostics from macro errors/warnings and spec constrcuts == Dependencies == * There is a soname bump involved so all API-dependent packages will need a rebuild. * The Python 3 string change has impact on several packages but this is already in process == Contingency Plan == * Contingency mechanism: Roll back to rpm 4.14, but under no circumstances should such a thing be necessary. * Contingency deadline: Beta freeze. * Blocks release? No == Documentation == Draft release notes available at https://rpm.org/wiki/Releases/4.15.0 -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Schedule for Friday's FESCo Meeting (2019-05-24)
On Fri, May 24, 2019 at 08:33:06AM -0400, Stephen Gallagher wrote: > Following is the list of topics that will be discussed in the > FESCo meeting Friday at 15: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 '2019-05-24 15:00 UTC' > > > Links to all issues to be discussed can be found at: > https://pagure.io/fesco/report/meeting_agenda > > = Discussed and Voted in the Ticket = > knot / knot-resolver package rebase exception request > https://pagure.io/fesco/issue/2129 > DECISION (+3, 0, -1) I think this is a typo, nobody voted against. Zbyszek ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Schedule for Friday's FESCo Meeting (2019-05-24)
On Fri, May 24, 2019 at 9:15 AM Zbigniew Jędrzejewski-Szmek wrote: > > On Fri, May 24, 2019 at 08:33:06AM -0400, Stephen Gallagher wrote: > > Following is the list of topics that will be discussed in the > > FESCo meeting Friday at 15: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 '2019-05-24 15:00 UTC' > > > > > > Links to all issues to be discussed can be found at: > > https://pagure.io/fesco/report/meeting_agenda > > > > = Discussed and Voted in the Ticket = > > knot / knot-resolver package rebase exception request > > https://pagure.io/fesco/issue/2129 > > DECISION (+3, 0, -1) > > I think this is a typo, nobody voted against. > Yup, definitely a typo, sorry about that. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora testing-20190523.0 compose check report
On Thu, 2019-05-23 at 20:32 -0400, Christopher wrote: > Do these compose reports need to spam devel@ ? > I don't think most packagers are involved in composes, Yes, they are. All packagers are involved in composes. Composes are made from the packages built by packagers. :P Most of the bugs in composes are caused by...bugs in packages. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
rpmlint warning: crypto-policy-non-compliance-gnutls-1
> libnbd.x86_64: W: crypto-policy-non-compliance-gnutls-1 > /usr/lib64/libnbd.so.0.0.0 gnutls_priority_set_direct > This application package calls a function to explicitly set crypto ciphers for > SSL/TLS. That may cause the application not to use the system-wide set > cryptographic policy and should be modified in accordance to: > https://fedoraproject.org/wiki/Packaging:CryptoPolicies The library does call gnutls_priority_set_direct, but in a way which I believe still uses the system policies: %prep ./configure --with-tls-priority=@LIBNBD,SYSTEM sets ... #define TLS_PRIORITY "@LIBNBD,SYSTEM" which calls ... err = gnutls_priority_set_direct (session, TLS_PRIORITY, NULL); So we're good and we can ignore this warning, right? I should note that I copied this coding pattern from libvirt. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora testing-20190523.0 compose check report
On Fri, May 24, 2019 at 11:11 AM Adam Williamson wrote: > > On Thu, 2019-05-23 at 20:32 -0400, Christopher wrote: > > Do these compose reports need to spam devel@ ? > > I don't think most packagers are involved in composes, > > Yes, they are. All packagers are involved in composes. Composes are > made from the packages built by packagers. :P Most of the bugs in > composes are caused by...bugs in packages. What I mean is that most packagers wouldn't know what to do with these. These emails don't have any useful information for a packager to follow up with. If there's a composition failure attributable to a package, then those directly involved with composes, could easily pass that information down to the relevant packager. I just think that more automated notices that don't apply to *everyone* on the list, make it harder for packagers to stay subscribed to the list. This kind of information can easily be presented in a more friendly manner by doing something like: 1. Provide a status webpage, 2. Publish to a subscribable service, like an RSS feed, 3. Put the automated emails to a separate composes@ or notifications@ list to allow opt-in. It's nice to be able to keep the human-to-human conversations separate from the bots. It's not critical... it's just nicer, and I think it would help. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora testing-20190523.0 compose check report
On Thu, May 23, 2019 at 8:42 PM Chris Murphy wrote: > > On Thu, May 23, 2019 at 6:33 PM Christopher > wrote: > > > > Do these compose reports need to spam devel@ ? > > I don't think most packagers are involved in composes, and it's hard > > to follow devel@ when it's so busy. It's already cross-posting to > > test@, that should be enough... perhaps there can be a composes@ list > > for these? Then folks can opt in. > > Matches: from:(rawh...@fedoraproject.org) > Do this: Mark as read, Delete it > Are these are the only messages coming from that address? I'm reluctant to do overly aggressive filtering, in case I miss important things. I'm actually trying to be involved as much as I can. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Node.js 12.x Plans for F31+
On Tue, Apr 23, 2019 at 5:40 PM Stephen Gallagher wrote: > > Today, the Node.js upstream released 12.0.0, the next in its line of > long-term support releases. I plan to make this the default version of > Node.js in Fedora 31+, but not immediately. I'm currently working on > getting a modular version of 12.x built for F29, F30 and Rawhide. I'll > get that out to updates-testing this week. I'll send out an update > once it's pushed to updates-testing. > > Once that's available, I encourage all NPM packagers in Fedora to > start testing their build and runtime with the 12.x module. I will be > filing a Change Proposal and plan to switch the system interpreter for > Rawhide over to 12.x around the end of May or beginning of June. > > The exact timing may depend on the current status of the > modules-in-the-non-modular-buildroot work in Fedora. If that's > available by this time, I will retire the non-modular Node.js > interpreter package and make the 12.x module the default stream for > F31+. If it's not available, I'll continue to do what I've been doing > in F29 and F30; building both the modular and non-modular packages. > > If you discover that you own NPM packages that are critical and do not > work with Node.js 12.x, please inform me immediately. We'll talk with > upstream and see what we can do about it. I plan to make this switch on Friday, May 31st, so if you have packages that may break, now would be a good time to let me know. Since the buildroot work isn't yet completely ready, I'm going to take the stop-gap approach and merge the '12' branch to master and do a non-modular build of Node.js 12.x in Rawhide on that day. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora testing-20190523.0 compose check report
On Fri, 2019-05-24 at 14:51 -0400, Christopher wrote: > On Thu, May 23, 2019 at 8:42 PM Chris Murphy wrote: > > On Thu, May 23, 2019 at 6:33 PM Christopher > > wrote: > > > Do these compose reports need to spam devel@ ? > > > I don't think most packagers are involved in composes, and it's hard > > > to follow devel@ when it's so busy. It's already cross-posting to > > > test@, that should be enough... perhaps there can be a composes@ list > > > for these? Then folks can opt in. > > > > Matches: from:(rawh...@fedoraproject.org) > > Do this: Mark as read, Delete it > > > > Are these are the only messages coming from that address? > I'm reluctant to do overly aggressive filtering, in case I miss > important things. I'm actually trying to be involved as much as I can. Only automated report-type things are sent from that address. The 'compose report' emails (different from 'compose check report' emails) and 'updates-testing report' mails also come from the same address. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Review swap: libnbd - a small C library with Python 3 binding
https://bugzilla.redhat.com/show_bug.cgi?id=1713767 libnbd is a library we're planning to use in a few places where we need a client library to access NBD servers. It's a small C library that also builds Python bindings as a subpackage. Will take a review in exchange for something of similar complexity. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
[Test-Announce] Fedora 31 Rawhide 20190524.n.1 nightly compose nominated for testing
Announcing the creation of a new nightly release validation test event for Fedora 31 Rawhide 20190524.n.1. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Notable package version changes: pungi - 20190517.n.0: pungi-4.1.36-4.fc31.src, 20190524.n.1: pungi-4.1.36-5.fc31.src Test coverage information for the current release can be seen at: https://www.happyassassin.net/testcase_stats/31 You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora_31_Rawhide_20190524.n.1_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_31_Rawhide_20190524.n.1_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_31_Rawhide_20190524.n.1_Base https://fedoraproject.org/wiki/Test_Results:Fedora_31_Rawhide_20190524.n.1_Server https://fedoraproject.org/wiki/Test_Results:Fedora_31_Rawhide_20190524.n.1_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_31_Rawhide_20190524.n.1_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_31_Rawhide_20190524.n.1_Security_Lab Thank you for testing! -- Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
