DevHeads.net

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

Intent to replace bzr (bazaar) with brz (breezy)

Hello,
bzr (bazaar) FTBFS and is orphaned.

I have a Python 3 replacement called breezy (brz) ready, but it has some
problems with remote repositories on Python 3.8, so I was not ready to build it,
obsolete bzr and have a broken alternative.

However, bzr now also fails to install, so it cannot be any more broken than it
already is.

This update's test gating status has been changed to, 'greenwave_failed'.

Couple of my updates have e-mailed me $subj. Is it something to worry about?

Example: <a href="https://bodhi.fedoraproject.org/updates/FEDORA-2019-f2ffe568a1" title="https://bodhi.fedoraproject.org/updates/FEDORA-2019-f2ffe568a1">https://bodhi.fedoraproject.org/updates/FEDORA-2019-f2ffe568a1</a>

Intent to orphan python-unittest2

Hello mostly Bcced maintainers of packages impacted by this.

I maintain python-unittest2, a backport of the standard library unittest module
from Python 3 to Python 2 (mostly) [1].

We are removing python2-unittest2 soon, as nothing depends on it any more [2].

I'd retire the package, as it makes no sense on Python 3, however there are
packages that use python3-unittest2 for various invalid reasons.

The proper action is to fix the packages to use unittest from the standard
library, but I lack the energy to coordinate that, so i just decided to just
orphan it.

That said, if you want my h

HEADS UP: Rawhide rebuild of Python packages with old bytecode version

Hello,
Python packages built with Python < 3.8.0b4 have invalid bytecode version,
because the version was updated in 3.8.0b4.

To see why this is a problem, follow the bugreport:

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

We were waiting for 3.8.0rc1 to see if the version is not updated once more.
It was not.

After rc1 hits the f32 buildroot we will mass bump and rebuild all Python
packages that still have the old bytecode.

The list of packages based on data from Monday (to be updated):

2ping
5minute
APLpy
ATpy
Cython
GitPython
Mayavi
NLopt
OpenIPMI
OpenLP
ProDy
PyDrive
PyGreSQ

Orphaned packages looking for new maintainers

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.

Schedule for Thursday's FPC Meeting (2019-09-26 16:00 UTC)

Following is the list of topics that will be discussed in the FPC
meeting Thursday at 2019-09-26 16:00 UTC in #fedora-meeting-1 on irc.freenode.net.

Local time information (via.

Join the package collection maintainers: Visit src.fp.o to request rights?

I was recently contacted by a fellow Fedora contributor about this.

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

I think this is not true, but what to say instead?

Orphaned tagsoup

tagsoup was maintained byt he Stewardship SIG and is no longer required by any
of our packages. I have orphaned it.

I don't know much about the package, but several other Java stuff requires it:

icedtea-web-0:1.8.2-3.fc31.src
icedtea-web-0:1.8.2-3.fc31.x86_64
javadocofflinesearch-0:2.2-9.fc31.noarch
javadocofflinesearch-0:2.2-9.fc31.src
xom-0:1.2.10-13.fc31.src

It was updated to the current 1.2.1 version in 2012 and upstream has either
moved or died.

Orphaned packages looking for new maintainers

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.

python-asgiref license change

The license of python-asgiref has been changed from "BSD" to "BSD and ASL 2.0"
(due to bundling).

<a href="https://src.fedoraproject.org/rpms/python-asgiref/c/cb241f277fdc2f3042dfade0b942df8c6a7acd0f?branch=master" title="https://src.fedoraproject.org/rpms/python-asgiref/c/cb241f277fdc2f3042dfade0b942df8c6a7acd0f?branch=master">https://src.fedoraproject.org/rpms/python-asgiref/c/cb241f277fdc2f3042df...</a>

Orphaned packages looking for new maintainers

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.

Orphaning python-MultipartPostHandler2

Hi.
I've orphaned python-MultipartPostHandler2.

It seems to be a leaf package and I have absolutely zero use case for it.

Let me know if you want it (I can still assign it to you), or open a releng ticket.

Orphaned packages to be retired (~400 during this 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.

How to contact hno (Henrik Nordström)?

Hey,

anybody knows how to properly contact hno (Henrik Nordström) and whether they
are still interested in maintaining bzr?

<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1749118" title="https://bugzilla.redhat.com/show_bug.cgi?id=1749118">https://bugzilla.redhat.com/show_bug.cgi?id=1749118</a>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1486686" title="https://bugzilla.redhat.com/show_bug.cgi?id=1486686">https://bugzilla.redhat.com/show_bug.cgi?id=1486686</a>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1734995" title="https://bugzilla.redhat.com/show_bug.cgi?id=1734995">https://bugzilla.redhat.com/show_bug.cgi?id=1734995</a>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1737937" title="https://bugzilla.redhat.com/show_bug.cgi?id=1737937">https://bugzilla.redhat.com/show_bug.cgi?id=1737937</a>

See also
<a href="https://lists.fedoraproject.org/archives/list/ ... at lists dot fedoraproject.org/message/OUMBR2LWRMWWXRWU4S4DREVHNVKYQGJV/" title="https://lists.fedoraproject.org/archives/list/ ... at lists dot fedoraproject.org/message/OUMBR2LWRMWWXRWU4S4DREVHNVKYQGJV/">https://lists.fedoraproject.org/archives/list/ ... at lists dot fedoraproject....</a>

Packages with broken dependencies on Python 3.7

Hello packagers!

The following packages failed to build on Fedora 32 with Python 3.8 and they
still require Python 3.7 on runtime.

If the packages won't build with Python 3.8, they won't be installable, along
with all their dependent packages, in Fedora 32.

If there is an "actual" build failure, you should have already received a bug
report blocking the tracking bug:

<a href="https://bugzilla.redhat.com/showdependencytree.cgi?id=PYTHON38&amp;hide_resolved=1" title="https://bugzilla.redhat.com/showdependencytree.cgi?id=PYTHON38&amp;hide_resolved=1">https://bugzilla.redhat.com/showdependencytree.cgi?id=PYTHON38&amp;hide_reso...</a>

If it is a dependency failure caused by an external factor (retired package,
etc.) there should be a bugreport as well.

However, if the packa

Looking for maintainers of Bazaar / Breeze (bzr / brz)

Hello,

it seems that the current maintainers of Bazaar (bzr) are not likely interested
anymore in the package.

It is mostyl dead upstream, depends on Python 2 and brings a quite a stack of
required packages.

There is s Python 3 compatible fork called Breeze (brz).
I've prepared the spec file for Breeze, but I don't have interest in maintaining
it. Is there any volunteer to maintain Bazaar / Breeze?

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

Thanks,

Orphaned itext, plan is to retire it in ~2 weeks

I've just orphaned itext, previously owned the Stewardship SIG.

The package wasn't updated for over a decade and has an open CVE from Fedora 26
era. The Stewardship SIG took it for maven-doxia, but we've luckily managed to
get rid of the dependency.

Since this package is dangerous, I'd like to retire it right away, but
flyingsaucer requires it. Hence I plan to retire it once flyingsaucer is retired
(it is already orphaned for 5 weeks).

Orphaned packages looking for new maintainers

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 jsch-agent-proxy

I've orphaned jsch-agent-proxy, previously maintained by the Stewardship SIG.

Retiring python2 and introducing python27 later this week

We are retiring python2 and introducing python27 later this week. Rawhide only.

As for now, nothing should break, except python2-debug will exist no more.

Packages (build)requiring python2 or python2-devel should continue to work for
now.

Rawhide gating: What shell be done with failed updates?

If updates in rawhide gating fail the tests, what is the procedure? Should they
be unpuhsed, or left to rot forever?

See for example <a href="https://bodhi.fedoraproject.org/updates/?packages=podman" title="https://bodhi.fedoraproject.org/updates/?packages=podman">https://bodhi.fedoraproject.org/updates/?packages=podman</a>

Fedora 31: Noninstallable Python 2 packages to be retired just before the beta freeze

In line with the approved Fedora 31 change, packages that fail to install due to
missing Python 2 dependencies are to be removed.

Orphaned packages looking for new maintainers

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.

nothing provides pkgconfig(egl) needed by qt5-qtbase-devel

I'm hit by the above error in rawhide.

Is this expected or unexpected failure?

Modular packages requiring Python 3.7

The following Fedora 30 modular packages require python(abi) = 3.7:

$ repoquery --repo=updates-modular --whatrequires 'python(abi) = 3.7'
meson-0:0.50.1-1.module_f30+3966+49c83da1.noarch
python3-aexpect-0:1.5.1-5.module_f30+4307+91f2a6b8.noarch
python3-pygit2-0:0.27.4-1.module_f30+2959+693db98d.x86_64
stratis-cli-0:1.0.2-1.module_f30+4065+aaaad0b9.x86_64

$ repoquery --repo=updates-modular --whatrequires 'python(abi) = 3.7' --source
meson-0.50.0-1.module_f30+3586+7354b37a.src.rpm
python-aexpect-1.5.1-4.module_f30+2883+7f6a800a.src.rpm
python-pygit2-0.27.4-1.module_f30+2959+693db98d.src.rpm
st

Package commit right, how to remove youself?

I wonder, how does a packager remove themselves from a package, if they have
commit rights only. The obvious way (going trough Settings), is not possible (no
Settings).

Thanks,

Rebase option suddenly missing from src.fo.o PRs?

I've recently noticed that src.fo.o PRs no longer let me click "Rebase" under
the "Merge" button.

Am I the only one impacted?

Is that deliberate or some bug worth reporting?

Orphaned packages looking for new maintainers

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.

Fedora 32 Python 3.8 rebuilds have started in a side tag

Hello, in order to deliver Python 3.8, we are running a coordinated rebuild in a
side tag.

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

If you see a "Rebuild for Python 3.8" commit in your package, please don't
rebuild it in regular rawhide.
If you need to, please let me know, so we can coordinate.

If you'd like to update the package, you should be able to build it in the side
tag via:

    on branch master:
    $ fedpkg build --target=f32-python

Note that it will take a while before the essential packages are rebuilt, so
don't except all your dependencies to be available ri