July 2017 - devel - Fedora Mailing-Lists

Fedora 26 status is GO, release on July 11, 2017

by Jaroslav Reznik

The Fedora 26 Final 1.5 compose [1] is considered as GOLD and is going to be shipped live on Tuesday, July 11th, 2017. For more information please check the Go/No-Go meeting minutes [2] or logs [3]. I'd like to thank everyone for the hard work on this release and great job Jan! [1] https://kojipkgs.fedoraproject.org/compose/26/Fedora-26-20170705.0/compose/ [2] https://meetbot.fedoraproject.org/fedora-meeting-2/2017-07-06/f26_final_g... [3] https://meetbot.fedoraproject.org/fedora-meeting-2/2017-07-06/f26_final_g... Thanks, Jaroslav

6 years, 9 months

1
0
0 / 0

Another Fedora 26 test request: VMware

by Adam Williamson

Hi folks! Got another request for Fedora 26 Final testing: can folks please try booting RC-1.4 in VMware? For me, the Workstation live fails to boot properly, in various configurations; in comparison the F25 Final Workstation live boots fine. That worried me a bit, so it'd be good to hear results from other testers... -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

6 years, 9 months

1
1
0 / 0

Re: F27 Self Contained Change: VirtualBox Guest Integration

by Zbigniew Jędrzejewski-Szmek

On Thu, Jul 06, 2017 at 06:17:53PM +0200, Reindl Harald wrote: > > > Am 06.07.2017 um 17:18 schrieb Zbigniew Jędrzejewski-Szmek: > >On Thu, Jul 06, 2017 at 04:10:29PM +0200, Jaroslav Reznik wrote: > >>= Proposed Self Contained Change: VirtualBox Guest Integration = > >>https://fedoraproject.org/wiki/Changes/VirtualBox_Guest_Integration > >> > >>Change owner(s): > >>* Hans de Goede <hdegoede(a)redhat.com> > >> > >>VirtualBox is popular, easy to use virtual-machine software. The > >>purpose of this change is to ship the VirtualBox guest-drivers and > >>-tools by default in the Fedora workstation product. > > > >Please make sure when running on non-VirtualBox machines the > >drivers and services are not loaded and there are no warnings emitted. > >(I know we've had similar problems before — e.g. > >https://bugzilla.redhat.com/show_bug.cgi?id=999804, and some other > >bugs I cannot find now, so I'm just saying that this is something > >worth checking for from the start.) > >Probably the right solution is to use a udev rule to trigger starting > >of various services only if the "devices" are found. Something like > >/usr/lib/udev/rules.d/70-spice-vdagentd.rules in spice-vdagent.rpm > > this needs to be done like for VMware and if systemd don't detect > vbox systemd needs to be fixed instead dirty udev workarounds > > [Unit] > Description=VMware Tools > ConditionVirtualization=vmware I don't know how exactly how VirtualBox (or VMWare) implement guest additions, but using an udev rule in general is a better solution: 1. Using ConditionVirtualization=xxx assumes that the guest additions are *always* enabled when ConditionVirtualization=xxx is true. From what I have seen, that's generally not true, and you need to configure a specific "channel" in virtualization configuration. That means that ConditionVirtualization is just not specific enough. 2. Using ConditionVirtualization means that the service start is always enqueued (and skipped on the majority of systems). This appears in the logs, and it's just nicer not to have that. 3. If the "channel" is "hot pluggable", the device can appear any time after bootup. With the udev rule, that'll just work. ConditionVirtualization would only be checked once at bootup. The way that the configuration for spice-vdagent.service is done is pretty nice: 1. /usr/lib/udev/rules.d/70-spice-vdagentd.rules contains the rule that pulls in spice-vdagentd.target 2. spice-vdagentd.service has [Install] WantedBy=spice-vdagentd.target 3. /usr/lib/systemd/system-preset/90-default.preset has "enable spice-vdagentd.service" 4. spice-vdagent.rpm has "systemctl preset spice-vdagentd.service" This means that things work out of the box, are completely silent if not virtualized or the channel is not configured, and the admin can enable/disable the service at will, and it's possible to configure different or additional stuff to start if the channel is available. Flexible, but without any hacks. Zbyszek

6 years, 9 months

1
0
0 / 0

F27 System Wide Change: NSS signtool deprecation

by Jaroslav Reznik

= System Wide Change: NSS signtool deprecation = https://fedoraproject.org/wiki/Changes/NSSSigntoolDeprecation Change owner(s): * Kai Engert <kaie(a)redhat.com> Deprecate the NSS tool named signtool, currently shipped as part of the nss-tools package, and available in the default search path at /usr/bin/signtool. Move it to /usr/lib*/nss/unsupported-tools/signtool. == Detailed Description == The NSS signtool is hardcoded to use SHA1 for signatures, however, SHA1 is no longer considered secure. Because it seems difficult to change the signtool default to make use of a more secure hash algorithm in a backwards and forwards compatible way, and because signtool might no longer be required for common uses, the suggestion is to deprecate it. See also [1] and [2] == Scope == * Proposal owners: The work required to implement this change is a simple packaging change. * Other developers: Users who used signtool for signing Jar/Zip/etc. files must use a different tool. A possible alternative is the jarsigner tool, which is shipped as part of the java-*-openjdk-devel package. * Release engineering: [1] * List of deliverables: N/A * Policies and guidelines: N/A, no changes should be necessary. * Trademark approval: N/A (not needed for this Change) [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1345528 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1444136 [3] https://pagure.io/releng/issue/6882 Thanks, Jaroslav

6 years, 9 months

1
0
0 / 0

F27 System Wide Change: The GNU C Library version 2.26

by Jaroslav Reznik

= System Wide Change: The GNU C Library version 2.26 = https://fedoraproject.org/wiki/Changes/GLIBC226 Change owner(s): * Carlos O'Donell <carlos(a)redhat.com> Switch glibc in Fedora 27 to glibc version 2.26. == Detailed Description == The GNU C Library version 2.26 will be released at the beginning of August 2017; we have started closely tracking the glibc 2.26 development code in Fedora Rawhide and are addressing any issues as they arise. Given the present schedule Fedora 27 will branch after the GLIBC 2.26 upstream release. However, the mass rebuild schedule means Fedora 27 will mass rebuild just after GLIBC 2.26 upstream freezes ABI for release, so careful attention must be paid to any last minute ABI changes. == Scope == * Proposal owners: Update glibc to 2.26 from tested upstream release. * Other developers: Developers need to ensure that rawhide is stable and ready for the Fedora 27 branch. Given that glibc is backwards compatible and we have been testing the new glibc in rawhide it should make very little impact when updated. * Release engineering: [1] All Fedora releases must be released using a released version of glibc. The Fedora glibc team is responsible for ensuring that Fedora Rawhide stabilizes ABI before a Fedora release, or that after the branch that the Fedora release is rebased (a very small rebase) to the final released version. This is a requirement for Fedora to inherit the ABI and API guarantees provided by upstream. If a mass rebuild is required by glibc or other components, the Fedora glibc team will ensure coordination with release engineering such that a mass rebuild uses the released version of glibc to fix any last minute ABI changes. The GNU C Library (glibc) does not require a mass rebuild for this release. * List of deliverables: all * Policies and guidelines: The policies and guidelines do not need to be updated. * Trademark approval: N/A (not needed for this Change) [1] https://pagure.io/releng/issue/6890 Thanks, Jaroslav

6 years, 9 months

1
0
0 / 0

some help needed with requires issue in spec file for pyproj

by Jos de Kloe

something strange happened in my recent pyproj build on rawhide which causes all relevant requires to be lost, see: https://bugzilla.redhat.com/show_bug.cgi?id=1467366 I tried to find a solution or workaround, but without succes. When I do a local mock build the same problem arises. I tried to activate some debug options on mock, but even adding " --verbose --rpmbuild-opts='-vv' " did not give me anymore details on the process used to find the requires. This is the only output I see for the python3 sub-package in my local mock build when all these debug options are active: ... Finding Requires(interp): Finding Requires(rpmlib): Finding Requires(verify): Finding Requires(pre): Finding Requires(post): Finding Requires(preun): Finding Requires(postun): Finding Requires(pretrans): Finding Requires(posttrans): Finding Requires: /bin/sh -c " while read FILE; do echo "${FILE}" | /usr/lib/rpm/rpmdeps -R; done | /bin/sort -u " Finding Conflicts: Finding Obsoletes: Finding Recommends: Finding Suggests: Finding Supplements: Finding Enhances: Provides: python3-pyproj = 1.9.5.1-7.fc27 python3-pyproj(x86-64) = 1.9.5.1-7.fc27 Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Processing files: pyproj-debuginfo-1.9.5.1-7.fc27.x86_64 Provides: pyproj-debuginfo = 1.9.5.1-7.fc27 pyproj-debuginfo(x86-64) = 1.9.5.1-7.fc27 Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 ... While it should have requires on python3, proj-nad and proj-epsg rpm confirms the problem: rpm -q --requires -p /var/lib/mock/fedora-rawhide-x86_64/result/python3-pyproj-1.9.5.1-7.fc27.x86_64.rpm rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(PayloadIsXz) <= 5.2-1 [end of output] Adding explicit requires to python2 and python3 in the general definitions in the top of the spec file or in the sub-package definitions does not help. Basically I have no clue what else I code do to debug this. If anyone has an idea I would much appreciate to hear it. Best regards, Jos

6 years, 9 months

3
7
0 / 0

Review swap

by Gwyn Ciesla

I just submitted python-slackclient: https://bugzilla.redhat.com/show_bug.cgi?id=1467995 Willing to do one of yours. Thanks! -G -- http://cecinestpasunefromage.wordpress.com/ ------------------------------------------------ in your fear, seek only peace in your fear, seek only love -d. bowie

6 years, 9 months

2
2
0 / 0

Schedule for Thursday's FPC Meeting (YYYY-MM-DD 16:00 UTC)

by James Antill

Following is the list of topics that will be discussed in the FPC meeting Thursday at 2017-07-06 16:00 UTC in #fedora-meeting-1 on irc.freenode.net. Local time information (via. uitime): ================= Day: Thursday ================== 2017-07-06 09:00 PDT US/Pacific 2017-07-06 12:00 EDT --> US/Eastern <-- 2017-07-06 16:00 UTC UTC 2017-07-06 17:00 BST Europe/London 2017-07-06 18:00 CEST Europe/Berlin 2017-07-06 18:00 CEST Europe/Paris 2017-07-06 21:30 IST Asia/Calcutta ---------------- New Day: Friday ----------------- 2017-07-07 00:00 HKT Asia/Hong_Kong 2017-07-07 00:00 +08 Asia/Singapore 2017-07-07 01:00 JST Asia/Tokyo 2017-07-07 02:00 AEST Australia/Brisbane Links to all tickets below can be found at: https://pagure.io/packaging-committee/issues?status=Open&tags=meeting = Followups = #topic #691 noarch *sub*packages with arch-specific dependencies .fpc 691 https://pagure.io/packaging-committee/issue/691 #topic #693 Wiki:Packaging:RPMMacros .fpc 693 https://pagure.io/packaging-committee/issue/693 = Open Floor = For more complete details, please visit each individual ticket. The report of the agenda items can be found at: https://pagure.io/packaging-committee/issues?status=Open&tags=meeting 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/fpc, 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.

6 years, 9 months

2
1
0 / 0

[Test-Announce] Fedora 26 Candidate RC-1.5 Available Now!

by Adam Williamson

** NOTE ** RC-1.5 is a kind of 'conditional' compose. The sole difference to RC-1.4 (bar anything that went odd in the compose process) is the qemu update for https://bodhi.fedoraproject.org/updates/FEDORA-2017-db0ad12bde . So aside from virt guest tests, most other results should be transferable from RC-1.4. Still, at least smoke testing each image would be great. We may wind up shipping RC-1.4, shipping RC-1.5, or not shipping either; it'll be decided at the Go/No-Go meeting in the morning. According to the schedule [1], Fedora 26 Candidate RC-1.5 is now available for testing. Please help us complete all the validation testing! For more information on release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Test coverage information for the current release can be seen at: https://www.happyassassin.net/testcase_stats/26 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_26_RC_1.5_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_26_RC_1.5_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_26_RC_1.5_Base https://fedoraproject.org/wiki/Test_Results:Fedora_26_RC_1.5_Server https://fedoraproject.org/wiki/Test_Results:Fedora_26_RC_1.5_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_26_RC_1.5_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_26_RC_1.5_Security_Lab All Final priority test cases for each of these test pages [2] must pass in order to meet the RC Release Criteria [3]. Help is available on #fedora-qa on irc.freenode.net [4], or on the test list [5]. Current Blocker and Freeze Exception bugs: http://qa.fedoraproject.org/blockerbugs/current [1] http://fedorapeople.org/groups/schedule/f-26/f-26-quality-tasks.html [2] https://fedoraproject.org/wiki/QA:Release_validation_test_plan [3] https://fedoraproject.org/wiki/Fedora_26_RC_Release_Criteria [4] irc://irc.freenode.net/fedora-qa [5] https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/ -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ test-announce mailing list -- test-announce(a)lists.fedoraproject.org To unsubscribe send an email to test-announce-leave(a)lists.fedoraproject.org

6 years, 9 months

1
0
0 / 0

[Fedocal] Reminder meeting : Fedora 26 Final Release Readiness Meeting

by jkurik＠redhat.com

Dear all, You are kindly invited to the meeting: Fedora 26 Final Release Readiness Meeting on 2017-07-06 from 19:00:00 to 21:00:00 UTC At fedora-meeting-2(a)irc.freenode.net The meeting will be about: Join us on irc.freenode.net in #fedora-meeting-2 for the Fedora 26 Final Release Readiness Meeting meeting. We will meet to make sure we are coordinated and ready for the Final release of Fedora 26. 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. [FedoCal] https://apps.fedoraproject.org/calendar/meeting/6285/ More information available at: https://fedoraproject.org/wiki/Release_Readiness_Meetings Thank you for your support and Regards, Jan Source: https://apps.fedoraproject.org/calendar/meeting/6285/

6 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel July 2017