Bug 2271325 - Please branch for F40
Summary: Please branch for F40
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: python-pyside6
Version: 40
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: loise@kde.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-03-24 21:05 UTC by Sandro
Modified: 2024-07-15 01:28 UTC (History)
8 users (show)

Fixed In Version: python-pyside6-6.7.2-1.fc40
Clone Of:
Environment:
Last Closed: 2024-07-15 01:28:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Sandro 2024-03-24 21:05:13 UTC
Please branch python-pyside6 for Fedora 40.

I have a package pending for F40 which depends on pyside6 and which is itself a dependency for another package I'm looking to update in F40.

After branching please build python-pyside6 into side tag f40-build-side-85905.

I'm happy to help where I can.

Reproducible: Always




I'm not sure why you ignored my request in bug 2271188 and silently closed it without responding to bug 2271188 comment 5.

Be that as it may. Here's the official request.

Comment 1 loise@kde.org 2024-03-26 03:02:01 UTC
As much as I can understand your needs, we ( @kde-sig.org ) have a coordination process. I'm not doing things alone and not doing things because I don't know how to do them or not wanting to do them.

To keep you informed, we're waiting for the release of Qt 6.7 and ironing out packaging issues around the pyside tools so the package allows using pyside6 as intended with qt-creator, having docs and the tools being tested (like uic).

Further details about the timing can be found here:

https://wiki.qt.io/Qt_6.7_Release

following the release we're updating Qt first, then kde plasma 6 and pyside is only a currently minor part at the far end of the chain.

Feel free helping to fix the issues around the tools and qch docs generation and submit PRs to speed up the process.

Comment 2 Ben Beasley 2024-03-26 05:05:43 UTC
The “Updated Plan” from https://wiki.qt.io/Qt_6.7_Release has a final release date of 2024-04-02, which is the same day as the F40 Final Freeze based on https://fedorapeople.org/groups/schedule/f-40/f-40-devel-tasks.html.

Unless I’m missing something, it doesn’t seem like this plan is viable.

Comment 3 Sandro 2024-03-26 09:15:34 UTC
(In reply to loise from comment #1)
> As much as I can understand your needs, we (
> @kde-sig.org ) have a coordination process. I'm not
> doing things alone and not doing things because I don't know how to do them
> or not wanting to do them.

Where can I find the details of that coordination process wrt Fedora?

> To keep you informed, we're waiting for the release of Qt 6.7 and ironing
> out packaging issues around the pyside tools so the package allows using
> pyside6 as intended with qt-creator, having docs and the tools being tested
> (like uic).

As things stand now, python-pyside6 is using Qt 6.6 in rawhide. Why not make it available to F40 _before_ the arrival of Qt 6.7. For my part it can stay as is using Qt 6.6 until most things Qt 6.7 have been sorted out in rawhide. I mean it doesn't harm your work in rawhide branching the package, upon request, for F40.

> Further details about the timing can be found here:
> 
> https://wiki.qt.io/Qt_6.7_Release

I agree with Ben here. This looks more like Qt 6.7 will be in F41 rather than F40.
 
> following the release we're updating Qt first, then kde plasma 6 and pyside
> is only a currently minor part at the far end of the chain.

As I mentioned above, I think that doesn't block the branching of pyside6.

> Feel free helping to fix the issues around the tools and qch docs generation
> and submit PRs to speed up the process.

I think I've heard that mentioned before. Yet, I don't see any bugs filed. So, I'm guessing this list of issues is tracked elsewhere. I'm happy to take a look. But I'm not making any promises.

Comment 4 Neal Gompa 2024-03-26 11:55:02 UTC
It will not be exclusive to F41. It will be backported to all Fedora stable releases and EPEL 9. We regularly upgrade Qt in this way.

Comment 5 Sandro 2024-03-26 12:15:15 UTC
(In reply to Neal Gompa from comment #4)
> It will not be exclusive to F41. It will be backported to all Fedora stable
> releases and EPEL 9. We regularly upgrade Qt in this way.

Fair enough. Yet, I still fail to understand why `python-pyside6` cannot be branched now.

In order to give some more background, I need this for Spyder 6. It's still in alpha. But I'd like to track the latest alpha release and ship that in F40. There might even be a chance of 6 final being released before F40 is shipped. But all that is currently blocked by `python-pyside6` not being branched. And `pyside6`, afaics, does not need to wait for the arrival of Qt 6.7.

Comment 6 Neal Gompa 2024-03-26 12:37:03 UTC
The reason is that the pyside6 package is still broken, which we discovered after bringing it into Rawhide. We're trying to fix it up from a functionality and FHS compliance perspective still.

Comment 7 Sandro 2024-03-26 17:40:26 UTC
Okay. I was able to eliminate the dependency on `pyside6` for `python-pytest-qt` in F40. It was needed for the tests, but I switched it to testing only with pyqt6 on Fedora < 41.

So, from where I stand, this is now a much less urgent request. But I believe others may still need it. I saw Ben asking about the branching (bug 2265554 comment 16) even before I submitted bug 2271188 (FTBFS).

Comment 8 Ben Beasley 2024-03-26 17:45:33 UTC
(In reply to Sandro from comment #7)
> So, from where I stand, this is now a much less urgent request. But I
> believe others may still need it. I saw Ben asking about the branching (bug
> 2265554 comment 16) even before I submitted bug 2271188 (FTBFS).

For the packages I have that use pyside6, it’s an optional dependency that I can leave patched out as long as I need to. If a pyside6 package shows up after F40 final release, I can restore the missing functionality or skipped tests. I’d rather have no pyside6 in F40 than one with packaging issues.

Comment 9 Alex Pyrgiotis 2024-05-13 08:37:43 UTC
Heads up, there's now a Python3 bug (or a Shiboken bug, not clear yet) that breaks importing Shiboken6 from PyPI:
* https://bugzilla.redhat.com/show_bug.cgi?id=2279088
* https://bugreports.qt.io/browse/PYSIDE-2747

This means that Fedora users cannot use PySide6, unless they compile it from source.
Now that PySide6 6.7.0 has been released, and the corresponding package (https://packages.fedoraproject.org/pkgs/python-pyside6/python3-pyside6/fedora-rawhide.html) is available in Rawhide, what's remaining for stabilization?

Comment 10 Sandro 2024-05-26 22:19:32 UTC
Gentle nudge...

Is there any forecast when this may be branched for F40. I just finished with a package that depends on PySide6 and it would be nice to make that available in at least one stable branch.

The issue above appears to be solved in version 6.7.1. The upstream issue has been closed.

Comment 11 Fedora Update System 2024-07-06 13:48:50 UTC
FEDORA-2024-032e4839e0 (python-pyside6-6.7.2-1.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-032e4839e0

Comment 12 Fedora Update System 2024-07-07 02:09:55 UTC
FEDORA-2024-032e4839e0 has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf install --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-032e4839e0 \*`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-032e4839e0

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 13 Fedora Update System 2024-07-15 01:28:41 UTC
FEDORA-2024-032e4839e0 (python-pyside6-6.7.2-1.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.


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