Without pyside6-uic, pyside6-rcc, and pyside6-designer (especially the first two), many potential dependent packages will be unable to use PySide6. For example, re-enabling the "usdview" application in usd with PySide6 (instead of PySide2) would requires re-generating Python code from .ui files using pyside6-uic. Reproducible: Always This package is a little too complicated for me to offer a PR with a reasonable amount of study and effort.
Hi, you nailed a known problem :) I've currently only found the solution to call uic and rcc with parameters for generating python output. So as far as I understood other linux distros, those tools are only wrapper scripts but up until now I wasn't able to find what is missing so they get generated during the build process and installed. Can you have a look into the build during a copr build and try to fetch this ? I've tried literally for month to find that out. Please let me know if there is any progress to report. BR, Loise
I uploaded my approach to this issue here https://src.fedoraproject.org/fork/luk1337/rpms/python-pyside6/tree/rawhide, this also covers BZ#2301713. Let me know if there's something could be improved etc.
(In reply to Łukasz Patron from comment #2) > I uploaded my approach to this issue here > https://src.fedoraproject.org/fork/luk1337/rpms/python-pyside6/tree/rawhide, > this also covers BZ#2301713. Let me know if there's something could be > improved etc. Also, you can find scratch build here https://koji.fedoraproject.org/koji/taskinfo?taskID=121265953
(In reply to Łukasz Patron from comment #3) > (In reply to Łukasz Patron from comment #2) > > I uploaded my approach to this issue here > > https://src.fedoraproject.org/fork/luk1337/rpms/python-pyside6/tree/rawhide, > > this also covers BZ#2301713. Let me know if there's something could be > > improved etc. > > Also, you can find scratch build here > https://koji.fedoraproject.org/koji/taskinfo?taskID=121265953 I found out that using setup.py install_scripts instead of egg_info creates pyside6-* scripts automatically, I force pushed my branch with that change and started a new scratch build at https://koji.fedoraproject.org/koji/taskinfo?taskID=121278807
(In reply to Łukasz Patron from comment #4) > (In reply to Łukasz Patron from comment #3) > > (In reply to Łukasz Patron from comment #2) > > > I uploaded my approach to this issue here > > > https://src.fedoraproject.org/fork/luk1337/rpms/python-pyside6/tree/rawhide, > > > this also covers BZ#2301713. Let me know if there's something could be > > > improved etc. > > > > Also, you can find scratch build here > > https://koji.fedoraproject.org/koji/taskinfo?taskID=121265953 > > I found out that using setup.py install_scripts instead of egg_info creates > pyside6-* scripts automatically, I force pushed my branch with that change > and started a new scratch build at > https://koji.fedoraproject.org/koji/taskinfo?taskID=121278807 Force pushed again and now shiboken6-genpyi works properly too - https://koji.fedoraproject.org/koji/taskinfo?taskID=121279463
Thanks for investigating this! I didn’t have time to do a detailed review (and I probably won’t), but https://src.fedoraproject.org/fork/luk1337/rpms/python-pyside6/c/f226f8a5a287d82b935693a47ecf86752cbb6b51?branch=rawhide *looks* basically reasonable. I also tried re-enabling the Qt application in usd with https://src.fedoraproject.org/rpms/usd/pull-request/23, and this at least compiled locally. I would like to test it interactively, but I probably won’t have a chance today.
(In reply to Ben Beasley from comment #6) > Thanks for investigating this! > > I didn’t have time to do a detailed review (and I probably won’t), but > https://src.fedoraproject.org/fork/luk1337/rpms/python-pyside6/c/ > f226f8a5a287d82b935693a47ecf86752cbb6b51?branch=rawhide *looks* basically > reasonable. > > I also tried re-enabling the Qt application in usd with > https://src.fedoraproject.org/rpms/usd/pull-request/23, and this at least > compiled locally. I would like to test it interactively, but I probably > won’t have a chance today. I posted this prematurely. The USD build actually failed with [2883/3431] cd /builddir/build/BUILD/usd-24.03-build/OpenUSD-24.03/redhat-linux-build/pxr/usdImaging/usdviewq && /builddir/build/BUILD/usd-24.03-build/OpenUSD-24.03/uic-wrapper -o /builddir/build/BUILD/usd-24.03-build/OpenUSD-24.03/redhat-linux-build/pxr/usdImaging/usdviewq/adjustDefaultMaterialUI.py /builddir/build/BUILD/usd-24.03-build/OpenUSD-24.03/pxr/usdImaging/usdviewq/adjustDefaultMaterialUI.ui FAILED: pxr/usdImaging/usdviewq/adjustDefaultMaterialUI.py /builddir/build/BUILD/usd-24.03-build/OpenUSD-24.03/redhat-linux-build/pxr/usdImaging/usdviewq/adjustDefaultMaterialUI.py cd /builddir/build/BUILD/usd-24.03-build/OpenUSD-24.03/redhat-linux-build/pxr/usdImaging/usdviewq && /builddir/build/BUILD/usd-24.03-build/OpenUSD-24.03/uic-wrapper -o /builddir/build/BUILD/usd-24.03-build/OpenUSD-24.03/redhat-linux-build/pxr/usdImaging/usdviewq/adjustDefaultMaterialUI.py /builddir/build/BUILD/usd-24.03-build/OpenUSD-24.03/pxr/usdImaging/usdviewq/adjustDefaultMaterialUI.ui Traceback (most recent call last): File "/usr/bin/pyside6-uic", line 33, in <module> sys.exit(load_entry_point('PySide6==6.7.2', 'console_scripts', 'pyside6-uic')()) ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/bin/pyside6-uic", line 25, in importlib_load_entry_point return next(matches).load() ~~~~^^^^^^^^^ StopIteration I will look into this further when I have a chance. "pyside6-uic --help" seems to work fine in a mock chroot.
I think my problems are due to the scratch build’s EVR being lower than the one in Rawhide. I’m ending up with mixed versions in my local mock build (downgrades are happening). Let me fiddle with it a bit more.
(In reply to Ben Beasley from comment #7) > (In reply to Ben Beasley from comment #6) > > Thanks for investigating this! > > > > I didn’t have time to do a detailed review (and I probably won’t), but > > https://src.fedoraproject.org/fork/luk1337/rpms/python-pyside6/c/ > > f226f8a5a287d82b935693a47ecf86752cbb6b51?branch=rawhide *looks* basically > > reasonable. > > > > I also tried re-enabling the Qt application in usd with > > https://src.fedoraproject.org/rpms/usd/pull-request/23, and this at least > > compiled locally. I would like to test it interactively, but I probably > > won’t have a chance today. > > I posted this prematurely. The USD build actually failed with > > [2883/3431] cd > /builddir/build/BUILD/usd-24.03-build/OpenUSD-24.03/redhat-linux-build/pxr/ > usdImaging/usdviewq && > /builddir/build/BUILD/usd-24.03-build/OpenUSD-24.03/uic-wrapper -o > /builddir/build/BUILD/usd-24.03-build/OpenUSD-24.03/redhat-linux-build/pxr/ > usdImaging/usdviewq/adjustDefaultMaterialUI.py > /builddir/build/BUILD/usd-24.03-build/OpenUSD-24.03/pxr/usdImaging/usdviewq/ > adjustDefaultMaterialUI.ui > FAILED: pxr/usdImaging/usdviewq/adjustDefaultMaterialUI.py > /builddir/build/BUILD/usd-24.03-build/OpenUSD-24.03/redhat-linux-build/pxr/ > usdImaging/usdviewq/adjustDefaultMaterialUI.py > cd > /builddir/build/BUILD/usd-24.03-build/OpenUSD-24.03/redhat-linux-build/pxr/ > usdImaging/usdviewq && > /builddir/build/BUILD/usd-24.03-build/OpenUSD-24.03/uic-wrapper -o > /builddir/build/BUILD/usd-24.03-build/OpenUSD-24.03/redhat-linux-build/pxr/ > usdImaging/usdviewq/adjustDefaultMaterialUI.py > /builddir/build/BUILD/usd-24.03-build/OpenUSD-24.03/pxr/usdImaging/usdviewq/ > adjustDefaultMaterialUI.ui > Traceback (most recent call last): > File "/usr/bin/pyside6-uic", line 33, in <module> > sys.exit(load_entry_point('PySide6==6.7.2', 'console_scripts', > 'pyside6-uic')()) > > ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/bin/pyside6-uic", line 25, in importlib_load_entry_point > return next(matches).load() > ~~~~^^^^^^^^^ > StopIteration > > I will look into this further when I have a chance. "pyside6-uic --help" > seems to work fine in a mock chroot. Install debel package and it should work.
(In reply to Ben Beasley from comment #7) > > I also tried re-enabling the Qt application in usd with > > https://src.fedoraproject.org/rpms/usd/pull-request/23, and this at least > > compiled locally. I would like to test it interactively, but I probably > > won’t have a chance today. With a few tweaks to the PR, and with workarounds (commenting out the pyside6-related BR’s) to prevent “pre-installed” pyside6 packages from the scratch build from being “upgraded” to the versions currently in Rawhide, the USD build really does work now. Still haven’t had a chance to see if the resulting application actually runs, but it’s a start!
(In reply to Łukasz Patron from comment #9) > (In reply to Ben Beasley from comment #7) > > (In reply to Ben Beasley from comment #6) > > > Thanks for investigating this! > > > > > > I didn’t have time to do a detailed review (and I probably won’t), but > > > https://src.fedoraproject.org/fork/luk1337/rpms/python-pyside6/c/ > > > f226f8a5a287d82b935693a47ecf86752cbb6b51?branch=rawhide *looks* basically > > > reasonable. > > > > > > I also tried re-enabling the Qt application in usd with > > > https://src.fedoraproject.org/rpms/usd/pull-request/23, and this at least > > > compiled locally. I would like to test it interactively, but I probably > > > won’t have a chance today. > > > > I posted this prematurely. The USD build actually failed with > > > > [2883/3431] cd > > /builddir/build/BUILD/usd-24.03-build/OpenUSD-24.03/redhat-linux-build/pxr/ > > usdImaging/usdviewq && > > /builddir/build/BUILD/usd-24.03-build/OpenUSD-24.03/uic-wrapper -o > > /builddir/build/BUILD/usd-24.03-build/OpenUSD-24.03/redhat-linux-build/pxr/ > > usdImaging/usdviewq/adjustDefaultMaterialUI.py > > /builddir/build/BUILD/usd-24.03-build/OpenUSD-24.03/pxr/usdImaging/usdviewq/ > > adjustDefaultMaterialUI.ui > > FAILED: pxr/usdImaging/usdviewq/adjustDefaultMaterialUI.py > > /builddir/build/BUILD/usd-24.03-build/OpenUSD-24.03/redhat-linux-build/pxr/ > > usdImaging/usdviewq/adjustDefaultMaterialUI.py > > cd > > /builddir/build/BUILD/usd-24.03-build/OpenUSD-24.03/redhat-linux-build/pxr/ > > usdImaging/usdviewq && > > /builddir/build/BUILD/usd-24.03-build/OpenUSD-24.03/uic-wrapper -o > > /builddir/build/BUILD/usd-24.03-build/OpenUSD-24.03/redhat-linux-build/pxr/ > > usdImaging/usdviewq/adjustDefaultMaterialUI.py > > /builddir/build/BUILD/usd-24.03-build/OpenUSD-24.03/pxr/usdImaging/usdviewq/ > > adjustDefaultMaterialUI.ui > > Traceback (most recent call last): > > File "/usr/bin/pyside6-uic", line 33, in <module> > > sys.exit(load_entry_point('PySide6==6.7.2', 'console_scripts', > > 'pyside6-uic')()) > > > > ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > File "/usr/bin/pyside6-uic", line 25, in importlib_load_entry_point > > return next(matches).load() > > ~~~~^^^^^^^^^ > > StopIteration > > > > I will look into this further when I have a chance. "pyside6-uic --help" > > seems to work fine in a mock chroot. > > Install debel package and it should work. nvm, it was shiboken6-genpyi that needed that workaround, I fixed it buy moving %{_bindir}/shiboken6-genpyi to the correct package.
I was able to rebuild the source rpm from https://koji.fedoraproject.org/koji/taskinfo?taskID=121279463 for F40, then use it to build USD, and then test the usdview application interactively, and it looks like everything worked! So at least for my use case, it looks like your approach works.
FEDORA-2024-1e2816743b (python-pyside6-6.7.2-3.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-1e2816743b
Thanks again! This is really helpful.
FEDORA-2024-1e2816743b has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-1e2816743b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-1e2816743b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-1e2816743b (python-pyside6-6.7.2-3.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.