Hi Fellowship of Fedora,

as we have not reach the minimal number of nominees to FESCo required
by FESCo election policy [1], to get ready for voting, FESCo has
decided to prolong the nomination period for one week.
As such, the Nomination period has been re-opened until May 31st @
23:59:59 UTC. Till this deadline you can nominate your self or you can
nominate someone else, who might be, from your perspective, a valuable
member of FESCo.

Announcing the creation of a new nightly release validation test event
for Fedora 29 Rawhide 20180524.n.0. Please help run some tests for this
nightly compose if you have time.

I installed the latest batch of updates for F28 tonight. Since that
included a new kernel (4.16.10-300.fc28), I rebooted. The system came up
with the GDM panic screen [1]. I rebooted into the previous kernel
thinking that something might be wrong with the new one. Same result. I
rebooted again and added enforcing=0 to the kernel boot line. That
worked. I did a full SELinux relabel immediately afterwards. Nothing
relevant changed labels.

The SELinux Alert Browser says there are no alerts.

= Proposed System Wide Change: The tzdata transition to 'vanguard' format =
<a href="https://fedoraproject.org/wiki/Changes/TZDATA-VANGUARD" title="https://fedoraproject.org/wiki/Changes/TZDATA-VANGUARD">https://fedoraproject.org/wiki/Changes/TZDATA-VANGUARD</a>

Owner(s):
* Patsy Franklin <pfrankli at redhat dot com>

As of tzdata-2018e, the upstream will now default to using the
'vanguard' data format including negative DST offsets. As a
fall-back, the 'rearguard' data format is still available on F28, F27
and F26.

== Detailed description ==
tzdata-2018e defaults to the 'vanguard' data format.

This is the last reminder that today, on 2018-May-22, at 23:59:59 UTC
we will close the Nomination window of May-2018 Elections.
Please check the nomination pages [1][2][3] and apply, if you are
interested to work in FESCo, Council or Mindshare teams.

[1] <a href="https://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations" title="https://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations">https://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations</a>
[2] <a href="https://fedoraproject.org/wiki/Council/Nominations" title="https://fedoraproject.org/wiki/Council/Nominations">https://fedoraproject.org/wiki/Council/Nominations</a>
[3] <a href="https://fedoraproject.org/wiki/Mindshare/Nominations" title="https://fedoraproject.org/wiki/Mindshare/Nominations">https://fedoraproject.org/wiki/Mindshare/Nominations</a>

Regards,
Jan

On Wed, May 16, 2018 at 2:05 AM, Jan Kurik < ... at redhat dot com> wrote:

Hi all,

I am trying to use the package "fossil", but I am having problems
because its version is too old.

Fedora 28 (and thus the fossil package) contains version 2.2, while the
current version of fossil is 2.6 (released 15 days ago).

Version 2.2 included in Fedora, was released on April 2017.

What is the process of triggering an update to fossil package to version
2.6?

George

This is just a reminder that on 2018-May-22 at 23:59:59 UTC we will
close the Nomination window of May-2018 Elections.
Please check the nomination pages [1][2][3] and apply, if you are
interested to work in FESCo, Council or Mindshare teams.

[1] <a href="https://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations" title="https://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations">https://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations</a>
[2] <a href="https://fedoraproject.org/wiki/Council/Nominations" title="https://fedoraproject.org/wiki/Council/Nominations">https://fedoraproject.org/wiki/Council/Nominations</a>
[3] <a href="https://fedoraproject.org/wiki/Mindshare/Nominations" title="https://fedoraproject.org/wiki/Mindshare/Nominations">https://fedoraproject.org/wiki/Mindshare/Nominations</a>

Regards,
Jan

On Wed, May 16, 2018 at 2:05 AM, Jan Kurik < ... at redhat dot com> wrote:

As per step 4 of Policy for nonresponsive package maintainers [1], I'm asking here whether anyone knows cwickert (Christoph Wickert), who is maintainer of the different packages including gtkhash, and has a way of contacting him/her. This package is quite outdated as it has not seen an update in >4 years. There are 5 open bug reports by 5 different people filed against this package and some of them are requesting an update [2]. None of those bug reports have any comment from the maintainer. One of those bug reports is open since 2013-12-03 [3].

No missing expected images.

Failed openQA tests: 10/137 (x86_64), 3/24 (i386), 1/2 (arm)

New failures (same test did not fail in Rawhide-20180517.n.1):

ID: 239248 Test: x86_64 Workstation-live-iso desktop_update_graphical
URL: <a href="https://openqa.fedoraproject.org/tests/239248" title="https://openqa.fedoraproject.org/tests/239248">https://openqa.fedoraproject.org/tests/239248</a>
ID: 239254 Test: x86_64 Workstation-boot-iso memory_check@uefi
URL: <a href="https://openqa.fedoraproject.org/tests/239254" title="https://openqa.fedoraproject.org/tests/239254">https://openqa.fedoraproject.org/tests/239254</a>
ID: 239268 Test: x86_64 KDE-live-iso desktop_update_graphical
URL: <a href="https://openqa.fedoraproject.org/tests/239268" title="https://openqa.fedoraproject.org/tests/239268">https://openqa.fedoraproject.org/tests/239268</a>
ID: 239295 Test: x86_64 universal install_kickstart_user_creation
URL: <a href="https://openqa.fedoraproje" title="https://openqa.fedoraproje">https://openqa.fedoraproje</a>

Announcing the creation of a new nightly release validation test event
for Fedora 29 Rawhide 20180519.n.0. Please help run some tests for this
nightly compose if you have time.

What macro(s) should I use in an RPM spec to refer to a directory like
/usr/lib/modules-load.d, which is under /usr/lib even if libdir is
/usr/lib64? Is there something better than %{_usr}/lib/modules-load.d?

No missing expected images.

Failed openQA tests: 8/137 (x86_64), 2/24 (i386), 1/2 (arm)

New failures (same test did not fail in Rawhide-20180516.n.0):

ID: 238718 Test: x86_64 Server-dvd-iso server_cockpit_basic
URL: <a href="https://openqa.fedoraproject.org/tests/238718" title="https://openqa.fedoraproject.org/tests/238718">https://openqa.fedoraproject.org/tests/238718</a>
ID: 238743 Test: x86_64 Workstation-boot-iso install_default@uefi
URL: <a href="https://openqa.fedoraproject.org/tests/238743" title="https://openqa.fedoraproject.org/tests/238743">https://openqa.fedoraproject.org/tests/238743</a>

Old failures (same test failed in Rawhide-20180516.n.0):

ID: 238716 Test: x86_64 Server-dvd-iso server_role_deploy_domain_controller
URL: <a href="https://openqa.fedoraproject.org/tests/238716" title="https://openqa.fedoraproject.org/tests/238716">https://openqa.fedoraproject.org/tests/238716</a>
ID: 238734 Test: x86_64 Workstat

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
<a href="http://fedoraproject.org/wiki/UTCHowto" title="http://fedoraproject.org/wiki/UTCHowto">http://fedoraproject.org/wiki/UTCHowto</a>

or run:
date -d '2018-05-18 15:00 UTC'

Links to all issues below can be found at:
<a href="https://pagure.io/fesco/report/meeting_agenda" title="https://pagure.io/fesco/report/meeting_agenda">https://pagure.io/fesco/report/meeting_agenda</a>

= Followups =

#topic #1892 F29 Self Contained Change: MySQL 8
.fesco 1892
<a href="https://pagure.io/fesco/issue/1892" title="https://pagure.io/fesco/issue/1892">https://pagure.io/fesco/issue/1892</a>

#topic #1890 updating the FTBFS cleanup policy
.fesco 1890
<a href="https://pagure.io/fesco/issue/1890" title="https://pagure.io/fesco/issue/1890">https://pagure.io/fesco/issue/1890</a>

#topic #1877 large number of pac

=================================================================================
#fedora-meeting-3: Meeting of the Modularity Working Group (once every two weeks)
=================================================================================

Meeting started by nils at 14:00:54 UTC.

Minutes: <a href="https://meetbot.fedoraproject.org/fedora-meeting-3/2018-05-15/modularity_wg.2018-05-15-14.00.html" title="https://meetbot.fedoraproject.org/fedora-meeting-3/2018-05-15/modularity_wg.2018-05-15-14.00.html">https://meetbot.fedoraproject.org/fedora-meeting-3/2018-05-15/modularity...</a>
Minutes (text): <a href="https://meetbot.fedoraproject.org/fedora-meeting-3/2018-05-15/modularity_wg.2018-05-15-14.00.txt" title="https://meetbot.fedoraproject.org/fedora-meeting-3/2018-05-15/modularity_wg.2018-05-15-14.00.txt">https://meetbot.fedoraproject.org/fedora-meeting-3/2018-05-15/modularity...</a>
Log: <a href="https://meetbot.fedoraproject.org/fedora-meeting-3/2018-05-15/modularity_wg.2018-05-1" title="https://meetbot.fedoraproject.org/fedora-meeting-3/2018-05-15/modularity_wg.2018-05-1">https://meetbot.fedoraproject.org/fedora-meeting-3/2018-05-15/modularity...</a>

Hi all,

A new version fedpkg-1.33 is released.

Changelog

- Allow running tests against specified rpkg (cqi)
- Fix test due to rpkg uses getpass.getuser (cqi)
- Getting bodhi version works with Python 3 - #213 (cqi)
- Detect Bodhi client by major version - #204 (cqi)
- Allow requesting modular repositories without bug ID - #197
(rdossant)
- Fix test test_verify_sls_invalid_date - #209 (cqi)
- Copy pip-pycurl to ensure pycurl is installed correctly (cqi)
- Fix unicode issue for update command in Python 3 - #206 (cqi)
- Fix a few E722 code styles errors (cqi)
- Fix fake PDC URL in test (cqi)

Hi All,
I wanted to re-introduce myself as well as ask for a sponsor for my package PrestoPalette.

Here's the link to the (approved) review request:
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1570047" title="https://bugzilla.redhat.com/show_bug.cgi?id=1570047">https://bugzilla.redhat.com/show_bug.cgi?id=1570047</a>

My original introduction email can be found here:
<a href="https://lists.fedoraproject.org/archives/list/ ... at lists dot fedoraproject.org/message/X57D5ZGVACRKZ3RHHRJYUQW4FO56JG5J/" title="https://lists.fedoraproject.org/archives/list/ ... at lists dot fedoraproject.org/message/X57D5ZGVACRKZ3RHHRJYUQW4FO56JG5J/">https://lists.fedoraproject.org/archives/list/ ... at lists dot fedoraproject....</a>

PrestoPalette is a new package that I'm trying to publish into the package repo and become its maintainer.

I'm asking for a sponsor so that I can publish PrestoPalette.

- Darryl T.

A new Fedora Atomic Host update is available via an OSTree update:

Version: 28.20180515.1
Commit(x86_64): a29367c58417c28e2bd8306c1f438b934df79eba13706e078fe8564d9e0eb32b
Commit(aarch64): ec501e5a6833e6117632c3a7fc90ef17530399b6411ad9ba2c5c85f22cabe8dd
Commit(ppc64le): dfe24e5d495ec16fbe2d61e6b494def2b119301f6565b8b6ecd542d79b02df89

We are releasing images from multiple architectures but please note
that x86_64 architecture is the only one that undergoes automated
testing at this time.

Existing systems can be upgraded in place via e.g.

Hello people,

I would like to know if you know about any service / tool / application
that still relies on NIS domain to be set in Fedora?

So far, I know only about SSSD/FreeIPA relying on it. Does anybody know
anything else? All replies are welcome. :)

Best regards,

David Kaspar [Dee'Kej]
*Associate Software Engineer*
*Brno, Czech Republic*

RED HAT | TRIED. TESTED. TRUSTED.
Every airline in the Fortune 500 relies on Red Hat.
Find out why at Trusted | Red Hat <http://www.redhat.com/en/about/trusted>.

In Fedora, for historic reasons, we run “/sbin/telinit u” after
installing a new glibc RPM package version.

Does this still make sense? Should we remove the code which invokes
telinit from the glibc package?

Thanks,
Florian

Hello People!

So we are working on revamping the Fedora Community App
<https://play.google.com/store/apps/details?id=com.fedoraqa.fedora&hl=en>,
and after an initial feedback and user testing session, we have an improved
wireframe ready for another round of testing.

I was wondering if some of you can test this wireframe and provide some
valuable feedback. In the process, you will be asked to do very simple
tasks (which will hardly take 2 minutes) on a clickable prototype. We can
learn from the insights of testing to iterate on the design of the
application.

No missing expected images.

Failed openQA tests: 23/137 (x86_64), 8/24 (i386), 1/2 (arm)

New failures (same test did not fail in Rawhide-20180513.n.1):

ID: 237471 Test: x86_64 Server-boot-iso install_default@uefi
URL: <a href="https://openqa.fedoraproject.org/tests/237471" title="https://openqa.fedoraproject.org/tests/237471">https://openqa.fedoraproject.org/tests/237471</a>
ID: 237492 Test: x86_64 Server-dvd-iso server_cockpit_basic
URL: <a href="https://openqa.fedoraproject.org/tests/237492" title="https://openqa.fedoraproject.org/tests/237492">https://openqa.fedoraproject.org/tests/237492</a>
ID: 237496 Test: x86_64 Everything-boot-iso install_default@uefi
URL: <a href="https://openqa.fedoraproject.org/tests/237496" title="https://openqa.fedoraproject.org/tests/237496">https://openqa.fedoraproject.org/tests/237496</a>
ID: 237534 Test: x86_64 AtomicHost-dvd_ostree-iso install_default@uefi
URL: <a href="https://openqa.fedoraproject.o" title="https://openqa.fedoraproject.o">https://openqa.fedoraproject.o</a>

Lately, I've seen quite a few spurious build failures.

Dear all,

You are kindly invited to the meeting:
Modularity WG (once every two weeks) on 2018-05-15 from 10:00:00 to 11:00:00 US/Eastern
At <a href="mailto:fedora-meeting- ... at irc dot freenode.net">fedora-meeting- ... at irc dot freenode.net</a>

The meeting will be about:
Meeting of the Modularity Working Group.

More information available at: [Modularity Working Group wiki page](<a href="https://fedoraproject.org/wiki/Modularity_Working_Group" title="https://fedoraproject.org/wiki/Modularity_Working_Group">https://fedoraproject.org/wiki/Modularity_Working_Group</a>)

The agenda for the meeting is available at [modularity-wg-agendas pad](<a href="https://board.net/p/modularity-wg-agendas" title="https://board.net/p/modularity-wg-agendas">https://board.net/p/modularity-wg-agendas</a>).

Source: <a href="https://apps.fedoraproject.org/calendar/meeting/5249/" title="https://apps.fedoraproject.org/calendar/meeting/5249/">https://apps.fedoraproject.org/calendar/meeting/5249/</a>

Hello, please take someone this Window Manager

Hello,

I've just submitted an update to cmpfit[0] for f28. The automated tests
show errors and warnings only on x86_64 and armv7hl[1] and the errors have
to do with the omission of ldconfig scriptlets. Aren't we supposed to get
rid of these for f28+?

The warnings are:
cmpfit-devel.armv7hl: W: no-documentation
cmpfit-devel.x86_64: W: only-non-binary-in-usr-lib
cmpfit-devel.x86_64: W: no-documentation
Is there any merit to them?

Hi,

The Fedora Media Writer for macOS at getfedora.org is not signed. I
filed this bug a couple weeks ago but somehow lost track of it, and
also it's possibly not the right location for the bug report as it
relates to what's offered on getfedora.org

As I mention in the bug, it's not a big deal to use the work around
for unsigned binaries when testing.

The libidn upstream has released 1.35, which increments the soname.
I'm planning to update the package on the next Tuesday.

The following packages will need to be rebuilt. I don't see anything
critical that should break the buildroot.