This bugzilla is likely a fallout from the Python 3.11 rebuild.

If your package (or some of the dependencies it has) failed to rebuild during the Python 3.11 rebuild, they now fail to install. To fix this, packages need to be rebuilt in Rawhide.

We will slowly triage the bugzillas, but we'd appreciate your help.

If you know this is blocked by an existing reported build failure or another package not yet rebuilt with Python 3.11, please mark it as such by using the "Depends On"/"Blocks" bugzilla fields. That will help us determine what failures to prioritize.

If this is not Python 3.11 related, please remove the PYTHON3.11 blocking tracker.

Thank you and sorry for the inconvenience. Let me know if you need any help.

Hello,

This is the first reminder (step 3 from https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs).

If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem.

____________________ TestCu2QuPen.test_ignore_single_points ____________________
self = <tests.pens_test.TestCu2QuPen testMethod=test_ignore_single_points>
    def test_ignore_single_points(self):
        pen = DummyPen()
        try:
            logging.captureWarnings(True)
            with CapturingLogHandler("py.warnings", level="WARNING") as log:
                quadpen = Cu2QuPen(pen, MAX_ERR, ignore_single_points=True)
        finally:
            logging.captureWarnings(False)
        quadpen.moveTo((0, 0))
        quadpen.endPath()
        quadpen.moveTo((1, 1))
        quadpen.closePath()
    
        self.assertGreaterEqual(len(log.records), 1)
        self.assertIn("ignore_single_points is deprecated",
>                     log.records[0].args[0])
E       IndexError: tuple index out of range
tests/pens_test.py:248: IndexError



I recall fixing this in another project: https://src.fedoraproject.org/rpms/fonttools/c/56762bce3fbd532389751251f0177c27be1864ce?branch=rawhide  + https://github.com/fonttools/fonttools/pull/2655

https://pypi.org/project/cu2qu/ says:

> This library is now maintained as part of https://github.com/fonttools/fonttools

Should we retire this package? Nothing in Fedora seems to depend on it.

(In reply to Miro Hrončok from comment #4)
> Should we retire this package? Nothing in Fedora seems to depend on it.

Another package awaiting review, also from https://github.com/googlefonts/, does still depend on it:

https://bugzilla.redhat.com/show_bug.cgi?id=2091310
https://github.com/googlefonts/ufo2ft/blob/6c05d0c8cc5395427cee8600f77354dde2c88040/setup.py#L33

(In reply to Ben Beasley from comment #5)
> 
> Another package awaiting review, also from https://github.com/googlefonts/,
> does still depend on it:

Upstream for ufo2ft doesn’t want to switch to the fonttools implementation from the standalone cu2qu because Cython acceleration is disabled in PyPI builds of fonttools[1]. (It looks like it is currently not enabled in Fedora builds either, although we could change that.) However, a straightforward patch for switching to fonttools is available in the linked PR.

Maybe we could retire this package in combination with enabling the Cython acceleration in fonttools, and patch ufo2ft accordingly. Or, we could always fix this package and keep it around a little longer, I guess. It doesn’t seem like upstream’s strategy is workable in the long term.

[1] https://github.com/googlefonts/ufo2ft/pull/461

It would be good to enable Cython acceleration in fonttools and patch ufo2ft.  PyPI will likely need to update their policies since they will also need to accommodate GPU accelerated programs and simd.  Enabling Cython acceleration is not essential, so this could be done at a later stage.

Hello,

This is the second reminder (step 4 from https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs).

If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem.

(In reply to Benson Muite from comment #7)
> It would be good to enable Cython acceleration in fonttools and patch
> ufo2ft.  PyPI will likely need to update their policies since they will also
> need to accommodate GPU accelerated programs and simd.  Enabling Cython
> acceleration is not essential, so this could be done at a later stage.

Forgive me if I am explaining something you already know, but I think there may be a misunderstanding here. Cython transpiles Python (or almost-Python) code to C or C++, allowing it to be compiled ahead of time as an extension. This usually provides a speedup, and for “loopy” numerical code the advantage can be huge. Cython also makes it easier to write bindings to existing C/C++ libraries or hand-written C/C++ code. In fonttools, Cython acceleration means Lib/fontTools/cu2qu/cu2qu.py is transpiled to C and compiled as an extension.

There are no issues with upstreams uploading Python packages with compiled extensions to PyPI, and there are at least hundreds of packages on PyPI already using Cython. It does create a headache for the upstream, because they have to build binary wheels on all supported platforms using something like https://cibuildwheel.readthedocs.io/, instead of just uploading the pure-Python wheel built on any arbitrary platform. That may explain why fonttools doesn’t do it.

I don’t believe GPU acceleration or SIMD extensions (beyond those guaranteed to be part of x86_64) are involved in the matter at all.

PR to enable Cython acceleration of cu2qu in fonttools: https://src.fedoraproject.org/rpms/fonttools/pull-request/7

This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle.
Changing version to 37.

This package has been orphaned.

You can pick it up at https://src.fedoraproject.org/rpms/python-cu2qu by clicking button "Take". If nobody picks it up, it will be retired and removed from a distribution.

Recommendation: allow automatic retirement to occur, and patch any future dependent packages to use fontTools.cu2qu instead—especially now that https://src.fedoraproject.org/rpms/fonttools/pull-request/7 has been merged to enable Cython acceleration there.

ufo2ft seems to work with cu2qu in fontTools.

Automation has figured out the package is retired in Fedora 37.

If you like it to be unretired, please open a ticket at https://pagure.io/releng/new_issue?template=package_unretirement

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days