Bug 1896806 - gst-editing-services fails to build with Python 3.10
Summary: gst-editing-services fails to build with Python 3.10
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gst-editing-services
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: PYTHON3.10
TreeView+ depends on / blocked
 
Reported: 2020-11-11 15:19 UTC by Tomáš Hrnčiar
Modified: 2020-11-11 19:12 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-11 19:12:42 UTC
Type: Bug


Attachments (Terms of Use)

Description Tomáš Hrnčiar 2020-11-11 15:19:18 UTC
gst-editing-services fails to build with Python 3.10.0a2.

error: File not found: /builddir/build/BUILDROOT/gst-editing-services-1.18.1-1.fc34.x86_64/usr/lib64/python3.10/site-packages/gi/overrides/*

This seems like a conflict between lib64 and lib. The path should probably contain the latter one. 

For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.10/fedora-rawhide-x86_64/01757075-gst-editing-services/

For all our attempts to build gst-editing-services with Python 3.10, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.10/package/gst-editing-services/

Testing and mass rebuild of packages is happening in copr. You can follow these instructions to test locally in mock if your package builds with Python 3.10:
https://copr.fedorainfracloud.org/coprs/g/python/python3.10/

Let us know here if you have any questions.

Python 3.10 will be included in Fedora 35. To make that update smoother, we're building Fedora packages with early pre-releases of Python 3.10.
A build failure prevents us from testing all dependent packages (transitive [Build]Requires), so if this package is required a lot, it's important for us to get it fixed soon.
We'd appreciate help from the people who know this package best, but if you don't want to work on this now, let us know so we can try to work around it on our side.


Note You need to log in before you can comment on or make changes to this bug.