DevHeads.net

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

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

Can we please stop enforcing Signed-off-by commits?

It happened to me almost dozen times now, so here's my rage :D

I want to send a pull request to a Fedora project*, I clone it, fork it, push to
the fork, open a PR and there it goes:

! This repo requires all commits to have the Signed-off-by whatnot in them !

So I have to go again, amend with -s, push force. That is tedious and at least I
know how to do that. I assume there are people who don't.

Can we stop this nonsense? I usually smuggle something like:

Signed-off-by: Stop This < ... at plea dot se>

And nobody ever cares!

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.

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>

I plan to retire packages that were already announced 3 times next Monday.

Unorphan/unretire packages at <a href="https://pagure.io/releng/issues" title="https://pagure.io/releng/issues">https://pagure.io/releng/issues</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 need new maintainers (will be retired 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.

Orphaned python-dropbox

JFYI I have just orphaned python-dropbox. I no longer use it for several
years and I don't really care about it.

python2-dropbox is required by duplicity.

Orphaned packages need new maintainers (will be retired 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.

Orphaned packages need new maintainers (will be retired 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.

How do I "release" a spin/lab?

When Fedora 29 was released, the Python Classroom Lab wasn't built.

The problem is now fixed:

<a href="https://koji.fedoraproject.org/koji/packageinfo?packageID=23847" title="https://koji.fedoraproject.org/koji/packageinfo?packageID=23847">https://koji.fedoraproject.org/koji/packageinfo?packageID=23847</a>

However how do i build and release it, so it is listed on:

<a href="https://labs.fedoraproject.org/" title="https://labs.fedoraproject.org/">https://labs.fedoraproject.org/</a>

And so that

<a href="https://labs.fedoraproject.org/python-classroom/download/index.html" title="https://labs.fedoraproject.org/python-classroom/download/index.html">https://labs.fedoraproject.org/python-classroom/download/index.html</a>

Doesn't list 404 links?

Thanks,

Upstream tip wanted: CI service for Big Endian acrhes

Recently I've reported some Big Endian related test failures to an
upstream project [0].

I was asked by an upstream project maintainer, whether I know some free
Continuous Integration services where they can easily run their
testsuite on Big Endian.

Any tips?

* Upstream uses Travis CI to test on x86_64 Linux (Ubuntu)
* Upstream uses AppVeyor to test on Microsoft Windows
* It's a pure Python project, noarch, but some changes need to be done
when loading/saving binary data (LE) with NumPy on BE system.

What I've considered:

* COPR (but there is no big endian arch)
* (Ab)using

Retired long orphaned Python 2 only packages

We have a policy for long orphaned packages that says if they are
orphaned for 6+ weeks, they are retired.

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

Since the policy was not happening and is blocking our removal of Python
2 packages, I've just retired the following packages:

ambari
arm-none-eabi-gdb
enemies-of-carlotta
fedmsg-notify
gnome-hearts
metamorphose2
mMass
ntop
phatch
pyrasite
python-decoratortools
python-kid
python-myghty
python-pycallgraph
python-turbocheetah
python-turbokid
python-4Suite-XML
qmforge
recoverjpeg
rpm-ostree-toolbox
spacewalk-koan

GNOME/Icon themes expert help needed: Trash icon stopped showing up with "my" icon theme

Hi.

I got a bugzilla that says gnome-color-icon-theme fails to show empty
Trash icon.

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

However apparently nothing changed in the package, hence I guess
something must have changed in GNOME. Is there anyone who can help me
understand and debug this?

Thanks,

Orphaned python2-astroid and python2-pylint

Hi,

I've just orphaned python2-astroid and python2-pylint.

I don't need them and I don't want to maintain legacy python2 packages.

Those are needed for python2-spyder, python2-asttokens,
python2-flake8-import-order. Please consider removing those, so we can
retire python2-astroid and python2-pylint. If you need to keep them,
please consider maintaining python2-astroid and/or python2-pylint.

Thanks,

Intent to drop python2-SecretStorage and python2-keyring in a week

Hi.

We are planning to update python-SecretStorage to a version that does
not support python2 [0][1].

Whoever needs python2-SecretStorage can add it as a separate package,
the spec is ready at [2].

Nobody from the current maintainers of dependent packages responded to a
request of maintainership (some said they don't need it).

python2-SecretStorage is needed by python-keyring and transitively for:

* supernova
* python-keystoneclient
* python-msrestazure
* python-oauth2client

I decided I won't package python2-SecretStorage just to orphan it
immediately.

Could not execute new_sources: Fail to upload files. Server returns status 403

Got this when I run `fedpkg new-sources`.

$ fedpkg --release master new-sources wheel-0.32.0.tar.gz
Could not execute new_sources: Fail to upload files. Server returns
status 403

What do i need to do?

I've rekinited, I've rerun `fedora-packager-setup`, `fedora-cert` tells
me it's not needed any more.

Is there something more I should do?

<a href="https://status.fedoraproject.org/" title="https://status.fedoraproject.org/">https://status.fedoraproject.org/</a> is all green.

Thanks,

Orphaned python2-matplotlib

I've orphaned python2-matplotlib.
Nobody replied to my previous heads up e-mails.

Heads Up: matplotlib 3 (no Python 2 support) in rawhide

We updated python-matplotlib to 3.0.0. It only supports Python 3. This
was done in Rawhide only.

The python2-matplotlib* subpackages were moved to a new SRPM,
python2-matplotlib (remains at 2.2.x), as plenty of cruft still needs
them :(

If you experience some relevant trouble (conflicts between packages,
blocked updates, unresolved deps, matplotlib not working, your plots
exploding...) please file bugs or let me know.

python2-matplotlib needs a maintainer. Volunteer at your local animal
shelter (e-mail me).

Heads Up: python2 is marked as deprecated

In line with the "Mass Python 2 Package Removal" Fedora 30 Change [0],
we've just marked python2 and all it's subpackages as deprecated in
rawhide [1].

No new packages can depend on python2 except renames and FESCo/FPC
exceptions. See more info in the Guidelines for Deprecating Fedora
Packages [2].

[0] <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>
[1]
<a href="https://src.fedoraproject.org/rpms/python2/c/0052c9fa9d76e1706d96a17460ad26f331a4e0fe?branch=master" title="https://src.fedoraproject.org/rpms/python2/c/0052c9fa9d76e1706d96a17460ad26f331a4e0fe?branch=master">https://src.fedoraproject.org/rpms/python2/c/0052c9fa9d76e1706d96a17460a...</a>
[2] <a href="https://fedoraproject.org/wiki/Packaging:Deprecating_Packages" title="https://fedoraproject.org/wiki/Packaging:Deprecating_Packages">https://fedoraproject.org/wiki/Packaging:Deprecating_Packages</a>