Anyone understands why this is not being pushed in recent days?

Just wanted to update everyone on our current status.

As you know from the other thread:

* The mass rebuild happened and finished.
* The mass rebuild side tag was merged into the f30-pending tag
(to make sure everything was signed).
* In the middle of the night our autosign box stopped processing.
* The next morning this was noticed and a request for a replacement
motherboard was sent.
* Since that was going to take a day, we setup another machine to do
autosigning.
* That machine started processing the backlog, but also stopped
processing a few times (waiting on koji).
* Finally we set back

Hi,

the compilation of mellowplayer-3.5.1 with gcc-9.0.1 fails on Fedora 30, see the build.log [1]

Fedora Bugzilla [2] - -Wredundant-move gives false positives in C++11 mode

[1] <a href="https://kojipkgs.fedoraproject.org//work/tasks/2212/32602212/build.log" title="https://kojipkgs.fedoraproject.org//work/tasks/2212/32602212/build.log">https://kojipkgs.fedoraproject.org//work/tasks/2212/32602212/build.log</a>

[2] <a href="https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87300" title="https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87300">https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87300</a>

How can this be solved ?

Regards Martin

One of my packages failed the mass rebuild, but only on ppc64le and
aarch64.

Hi,

due to <a href="https://fedoraproject.org/wiki/Changes/Python_Extension_Flags" title="https://fedoraproject.org/wiki/Changes/Python_Extension_Flags">https://fedoraproject.org/wiki/Changes/Python_Extension_Flags</a> it is no
longer correct to just call `python3 setup.py build` or `python3 setup.py
build_ext` in spec without setting the proper flags (for arched builds with
Python extension modules at least).

That is without setting both CFLAGS **and** LDFLAGS.

I've grepped the usage and skimmed trough specs, destining the following list of
packages that fail to properly set both flags.

I intend to fix the packages using my provenpackager rights during next week. I
plan to push directly.

<a href="https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault" title="https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault">https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault</a>

I want this change to succeed but I'm experiencing a regression, and
while trying to troubleshoot it I'm finding it difficult to understand
the myriad differences:

- I can't find the code. I assume all of it is in grub as blscfg.mod
and grub2-mkconfig and its associated scripts in /etc/grub.d but I'm
not seeing code or code reference in the change or here
<a href="https://apps.fedoraproject.org/packages/grub2-efi-x64-modules/" title="https://apps.fedoraproject.org/packages/grub2-efi-x64-modules/">https://apps.fedoraproject.org/packages/grub2-efi-x64-modules/</a>

- I can't find any documentation.

Hi,

While packaging up votca-csg-1.5, I ran into some tests failing:
<a href="https://github.com/votca/csg/issues/326" title="https://github.com/votca/csg/issues/326">https://github.com/votca/csg/issues/326</a>
but this only happens on ppc64le under epel7. (So I expect boost-1.53
being the culprit!)

Is there a good way (qemu or something) to debug this interactively?

Cheers,

Christoph

Libiptcdata was removed due to
<a href="https://fedoraproject.org/wiki/Changes/Mass_Python_2_Package_Removal" title="https://fedoraproject.org/wiki/Changes/Mass_Python_2_Package_Removal">https://fedoraproject.org/wiki/Changes/Mass_Python_2_Package_Removal</a>

Unfortunately, Rawtherapee needs it and is now broken:
<a href="https://koji.fedoraproject.org/koji/buildinfo?buildID=1201565" title="https://koji.fedoraproject.org/koji/buildinfo?buildID=1201565">https://koji.fedoraproject.org/koji/buildinfo?buildID=1201565</a>

I would have expected that only the Python2 subpackage was removed, not
the entire package!

I've been maintaining this for several years since the main admin
(ravenoak) vanished from Fedora. I don't use it anymore (and most of
the world has long since switched to git...) and it has yet again
failed to rebuild during the mass rebuild.

I'm initiating the Non-Responsive Maintainer process for ravenoak so
the main admin will be cleared.

Anyone knows how to contact Stefan?

<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1627400" title="https://bugzilla.redhat.com/show_bug.cgi?id=1627400">https://bugzilla.redhat.com/show_bug.cgi?id=1627400</a>

Hi all,

This package used to be part of Ruby on Rails, later it was removed from
the framework and extracted into independent gem mainly for backward
compatibility. This package is FTBFS ATM, presumably since Ruby on Rails
5.2 were imported into F29, because there is one test failure. Upstream
does not bother to fix this issue and because I don't have any use for
this package, I just orphaned it.

Just a couple of minutes ago, version 2.0 of Lazarus, the Pascal IDE / GUI toolkit was released.

Here's the link to the changelog; there are a few compatibility-breaking changes:
<a href="http://wiki.lazarus.freepascal.org/Lazarus_2.0.0_release_notes" title="http://wiki.lazarus.freepascal.org/Lazarus_2.0.0_release_notes">http://wiki.lazarus.freepascal.org/Lazarus_2.0.0_release_notes</a>

Lazarus is used to compile a few other Fedora packages, thus I'd want to avoid just upgrading it to v.2.0 and calling it a day without checking how it affects the dependent packages. I could submit an F30 change proposal, though that would be way past the deadline.

I've just orphaned 259 packages listed below.

Dear all,

You are kindly invited to the meeting:
Modularity WG (weekly) on 2019-02-05 from 15:00:00 to 16:00:00 UTC
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 as flagged tickets [in the Modularity repository](<a href="https://pagure.io/modularity/issues?status=Open&amp;tags=Meeting" title="https://pagure.io/modularity/issues?status=Open&amp;tags=Meeting">https://pagure.io/modularity/issues?status=Open&amp;tags=Meeting</a>).

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

Python packages can specify extras dependencies, which are sets of dependencies not required for core functionality, and which generally correspond to some feature. These can then be specified by downstream consumers of the package. For example, requests has an entry in extras called security[1], which currently adds requirements of python packages pyOpenSSL >= 0.14, cryptography >= 1.3.4, and idna >= 2.0.0. A downstream consumer that wants to use this would add a dependency on requests[security].

From what I can tell, the current practice in Fedora packaging is to ignore these.

The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them.

Find below a list of topics which are planned to be discussed in the
Fedora Modularity Team meeting on Tuesday at 15:00 UTC in
#fedora-meeting-3 on irc.freenode.net.

To find out when this is in your local time zone, check the Fedora
Calendar (if you've set it and are logged in):
<a href="https://apps.fedoraproject.org/calendar/modularity/#m5249" title="https://apps.fedoraproject.org/calendar/modularity/#m5249">https://apps.fedoraproject.org/calendar/modularity/#m5249</a>

Alternatively, to convert UTC to your local time zone, 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 'Tuesday 15:00 UTC'

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

= Discusse

Hi,

It seems that since CMake 3.13, it is required to invoke the cmake
command explicitly with path to source, which was not required
previously.

No missing expected images.

Compose FAILS proposed Rawhide gating check!
8 of 47 required tests failed, 8 results missing
openQA tests matching unsatisfied gating requirements shown with **GATING** below

Failed openQA tests: 30/132 (x86_64), 3/24 (i386), 1/2 (arm)

New failures (same test not failed in Rawhide-20190201.n.0):

ID: 349095 Test: x86_64 Server-dvd-iso install_repository_nfs_graphical
URL: <a href="https://openqa.fedoraproject.org/tests/349095" title="https://openqa.fedoraproject.org/tests/349095">https://openqa.fedoraproject.org/tests/349095</a>
ID: 349104 Test: x86_64 Server-dvd-iso install_updates_nfs
URL: <a href="https://openqa.fedoraproject.org/tests/349104" title="https://openqa.fedoraproject.org/tests/349104">https://openqa.fedoraproject.org/tests/349104</a>
ID: 349105 Test: x86_64 Server-dvd-is

Hi,
I'm trying to debug a FTBFS in rawhide:

<a href="https://koji.fedoraproject.org/koji/taskinfo?taskID=32412101" title="https://koji.fedoraproject.org/koji/taskinfo?taskID=32412101">https://koji.fedoraproject.org/koji/taskinfo?taskID=32412101</a>

Apparently it fails because of library ordering, but it works in f29.
g_object_unref is defined in gobject-2.0 and it gets surely added by
the 'pkgconf --libs cairo pangocairo pango' command.

Did anything about gobject or glib change in rawhide recently?

Thank you for any help.

Guido

FAS account: tartina

I noticed a warning on one of my packages that the appdata file was marked
as executable. The source file is not, its 644, but I use the install
command to install it to the metainfo directory.

Does "install" install files as executable by default or is something else
going on here?

Adding -m 0644 fixed it but it shouldn't be necessary.

Thanks,
Richard

Hi,

it seems system-config-users is broken [1],
and appears to have no upstream [2].

Do we maintain it at this point at all? Should it be retired "for safety"?

[1] <a href="https://bugz.fedoraproject.org/system-config-users" title="https://bugz.fedoraproject.org/system-config-users">https://bugz.fedoraproject.org/system-config-users</a>
[2]
<a href="https://src.fedoraproject.org/rpms/system-config-users/blob/master/f/system-config-users.spec#_44" title="https://src.fedoraproject.org/rpms/system-config-users/blob/master/f/system-config-users.spec#_44">https://src.fedoraproject.org/rpms/system-config-users/blob/master/f/sys...</a>

Hi all,

One of my package builds (fwupd) in F30 is failing in the unit tests,
with this failure comparing the expected output of a to_string()
function:

- Size: 1.0 kB
+ Size: 1.0?kB

I assume it's due to the removal of glibc-langpacks-all from the
buildroot. I'ts not immediately obvious from reading
<a href="https://fedoraproject.org/wiki/Changes/Remove_glibc-langpacks-all_from_buildroot" title="https://fedoraproject.org/wiki/Changes/Remove_glibc-langpacks-all_from_buildroot">https://fedoraproject.org/wiki/Changes/Remove_glibc-langpacks-all_from_b...</a>
and <a href="https://fedoraproject.org/w/index.php?title=Changes/Remove_glibc-langpacks-all_from_buildroot" title="https://fedoraproject.org/w/index.php?title=Changes/Remove_glibc-langpacks-all_from_buildroot">https://fedoraproject.org/w/index.php?title=Changes/Remove_glibc-langpac...</a>
what I'm supposed to do.

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

Hi,

As some of you know, I've been involved with the OpenVPN packages for some
time as well as being an upstream OpenVPN developer and maintainer. Now we
have released the third beta release of OpenVPN 3 Linux.

This new client shares the same code base the OpenVPN Connect (proprietary)
clients uses as well as the OpenVPN for Android when switching to use the
OpenVPN 3 backend. The OpenVPN 3 code base is a rewrite in C++ and makes use
of the more modern features of C++11.

The Linux version is also very different from the OpenVPN 2.x generation, as
it is now D-Bus based.

Hi,

I've noticed that someone created a flatpak build for one of my packages (feedreader), but it's horribly out of date: flatpak has 2.5.1 vs rpm has 2.7.0. I've been trying to update the flatpak build, but not much luck here.

MayBe I …(can do something useful)?

Hello,

We've been discussing some (hopefully) nice idea with Mikolaj, Neal and
Jakub how we could improve packager (and user) experience and we have some
proposal which will be described below.

We would like to ask you to read it, understand it and ask us any questions
you have.