DevHeads.net

Postings by =?UTF-8?B?TWlybyBIcm9uxI1vaw==?=

Orphaned packages to be retired

The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
<a href="https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life" title="https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life">https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life</a>

Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one.

HEADS UP: Pytest 4 in rawhide

Pytest has been updated to 4.3.1 and most likely will get updated to 4.4 soon.

We had pytest 3.9 before. This is backward incompatible update. See removed
things at:

<a href="https://docs.pytest.org/en/latest/deprecations.html#removed-features" title="https://docs.pytest.org/en/latest/deprecations.html#removed-features">https://docs.pytest.org/en/latest/deprecations.html#removed-features</a>
<a href="https://docs.pytest.org/en/latest/changelog.html" title="https://docs.pytest.org/en/latest/changelog.html">https://docs.pytest.org/en/latest/changelog.html</a>

If you get git by [pytest] section in setup.cfg files, this sed in %prep will
do, but please communicate with your upstreams:

sed -i 's/\[pytest\]/\[tool:pytest\]/' setup.cfg

Should you hit any trouble, please report bugs and block

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

Thanks,

Orphaned packages to be retired

The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
<a href="https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life" title="https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life">https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life</a>

Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one.

ACTION NEEDED: Orphaned packages to be retired (Java packages in 1 week)

The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
<a href="https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life" title="https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life">https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life</a>

Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one.

HEADS UP: PyYAML 5.1 in all Fedoras

PyYAML was updated to 5.1 in all Fedoras (rawhide, branched and stable).

Most significant change is a new warning that can bit you is you treat warnings
as errors.

Please read <a href="https://msg.pyyaml.org/load" title="https://msg.pyyaml.org/load">https://msg.pyyaml.org/load</a> for full details about this.

tl;dr: Use of yaml.load() without specifying the Loader parameter has been
deprecated. It raises a custom warning that is not a subclass of DeprecationWarning.

Very late Fedora 30 change considered: Mono 5

There is a discussion in a FESCo ticket whether we should update to Mono 5 in
Fedora 30. This is absurdly late considering out change process, but the
argument is that it cannot be any worse than it currently is.

<a href="https://fedoraproject.org/wiki/Changes/Mono_5" title="https://fedoraproject.org/wiki/Changes/Mono_5">https://fedoraproject.org/wiki/Changes/Mono_5</a>
<a href="https://pagure.io/fesco/issue/2105" title="https://pagure.io/fesco/issue/2105">https://pagure.io/fesco/issue/2105</a>

Please participate in the discussion in the ticket if you have relevant
arguments for either doing this or not.

Thanks,

Orphaned packages to be retired (Java packages in 2 weeks)

The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
<a href="https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life" title="https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life">https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life</a>

Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one.

I've orphaned spec2scl

It's most probably dead upstream anyway.

Orphaned packages to be retired (Java packages in 3 weeks)

The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
<a href="https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life" title="https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life">https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life</a>

Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one.

Non-responsive maintainer Chris Lalancette (clalance)

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

Anyone knows how to contact the maintainer?

Bugzilla has (very) outdated information on package maintainers

Hi,

I'm doing nonresponsive maintainer (Chris Lalancette) in

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

Yet src.fp.o says the package belongs to Ian McLeod.

This is not the first time I've noticed that the bugzilla info is quite wrong,
most likely very outdated.

Is this a know issue? Where do I report it if not?

HEADS UP: python2-sphinx is going away on Monday (2019-03-11)

Due to <a href="https://fedoraproject.org/wiki/Changes/Sphinx2" title="https://fedoraproject.org/wiki/Changes/Sphinx2">https://fedoraproject.org/wiki/Changes/Sphinx2</a> we will be removing
python2-sphinx and other related packages on Monday (2019-03-11).

If you are Bcc'ed, your package still uses python2-sphinx on build time and will
start to FTBFS. A fix is to stop BuildRequiring it.

Help us test FedoraReview on Python 3

There is a FedoraReview port to Python 3 that needs real word testing by packagers.

When you use FedoraReview, please use the Python 3 port instead to help us find
bugs.

Instructions are at <a href="https://pagure.io/FedoraReview/pull-request/312" title="https://pagure.io/FedoraReview/pull-request/312">https://pagure.io/FedoraReview/pull-request/312</a> -> the first
comment of my Pull Request is updated with up to date instructions.

Thanks,

Orphaned packages looking for new packagers

The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
<a href="https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life" title="https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life">https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life</a>

Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one.

Orphaned packages that will be retired

The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
<a href="https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life" title="https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life">https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life</a>

Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one.

RFE: logrotate for fedpkg mockbuild -N

Hi, I'm writing to devel to see if others would find this useful or not, before
I dig into finding whether it is mock or rpkg to bother about this :D

I build packages with `fedpkg mockbuild -N`. i iterate with spec changes and try
to build the package until it passes.

Orphaned packages that will be retired (and everything will most likely burn)

The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
<a href="https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life" title="https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life">https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life</a>

Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one.

HEADS UP: I plan to correct "python3 setup.py build" calls without proper flags

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.

rpmlint: library-not-linked-against-libc (parts of Python stdlib, after gcc 9)

I've just spotted these when working on Python 3.8.0a1.

Nonrepsonsive maintainer Stefan Seefeld

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>

Nonrepsonsive maintainer Ryan H. Lewis

Anyone knows how to contact Ryan?

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

Orphaned packages to be retired

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

Schedule for Monday's FESCo Meeting (2019-02-04)

(Sorry for the late announcment.)

Following is the list of topics that will be discussed in the
FESCo meeting Monday at 15:00UTC in #fedora-meeting-1 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 '2019-02-04 15:00 UTC'

Links to all issues to be discussed 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>

= Discussed and Voted in the Ticket =

#1820 Drop batched updates policy
<a href="https://pagure.io/fesco/issue/1820" title="https://pagure.io/fesco/issue/1820">https://pagure.io/fesco/issue/1820</a>
AGREED (+5, 0, 0)

#2003 Ursa Major (modules in buildroot) enablement
<a href="https://pagu" title="https://pagu">https://pagu</a>

Is system-config-users maintained or not?

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>

lmfit soname bump 7.0 -> 8.2

lmfit will be bumped. dependent packages build fine.

<a href="https://src.fedoraproject.org/rpms/lmfit/pull-request/3" title="https://src.fedoraproject.org/rpms/lmfit/pull-request/3">https://src.fedoraproject.org/rpms/lmfit/pull-request/3</a>

Orphaned packages to be retired

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

Nonresponsive maintainer Matthias Saou

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

Anyone knows how to reach Matthias?

Nonresponsive maintainer David Timms

Anyone knows how to reach David?

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

Orphaned packages to be retired

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

Schedule for Monday's FESCo Meeting (2019-01-21)

Following is the list of topics that will be discussed in the
FESCo meeting Monday at 15:00UTC in #fedora-meeting-1 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 '2019-01-21 15:00 UTC'

Links to all issues to be discussed 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>

= Discussed and Voted in the Ticket =

Give Bodhi automation to push based on time in testing
<a href="https://pagure.io/fesco/issue/2048" title="https://pagure.io/fesco/issue/2048">https://pagure.io/fesco/issue/2048</a>
APPROVED (+5, 0, -0)

F30 System-Wide Change: Fully remove deprecated and unsafe functions from