Re: Thoughts about packaging a standalone python-PyQt5-sip?
On Tue, 27 Apr 2021, Kevin Fenzi wrote: I'd be able and willing to assist here too, thanks for working on it! As far as sip6 goes, I'd venture the adjustment from v5 to v6 will be smaller than what v4 to v5 was. Yeah, agreed. Happy to work with you both and get this done. :) Okay, I'll work on dusting off my existing work, refreshing it, and get in touch with you guys. Scott ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Thoughts about packaging a standalone python-PyQt5-sip?
On Mon, Apr 26, 2021 at 02:29:52PM -0400, Scott Talbert wrote: > On Sat, 24 Apr 2021, Kevin Fenzi wrote: > > > On Tue, Jan 12, 2021 at 10:42:28PM -0500, Scott Talbert wrote: > > > > > > OK, I'm going to make an attempt to move python-qt5 (and its friends) to > > > sip5. I'm planning to build everything in a copr first. > > > > Hey Scott. > > > > Did you get any further with this? > > > > Anything I can do to help? I'd really like to be able to update calibre > > again. :) > > Yes, I got fairly far with porting all PyQt5 SIP consumers (including > calibre) to use SIPv5. I think I then got discouraged at the thought of > making a bunch of PRs and having to nag maintainers to merge them in some > sort of coordinated fashion. > > I guess - if I get everything working, would you be willing to merge a bunch > of related PRs as provenpackager and do rebuilds in a side tag? Sure! As long as maintainers are on board... > At this point, it might also make sense to go directly to SIPv6 as that's > out already. I'm not sure how wide support for 6 is, but I suspect it's easier to get to than 4-5 was. ;) On Mon, Apr 26, 2021 at 10:47:43PM -0500, Rex Dieter wrote: > > I'd be able and willing to assist here too, thanks for working on it! > > As far as sip6 goes, I'd venture the adjustment from v5 to v6 will be > smaller than what v4 to v5 was. Yeah, agreed. Happy to work with you both and get this done. :) kevin signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Thoughts about packaging a standalone python-PyQt5-sip?
Scott Talbert wrote: > Yes, I got fairly far with porting all PyQt5 SIP consumers (including > calibre) to use SIPv5. I think I then got discouraged at the thought of > making a bunch of PRs and having to nag maintainers to merge them in some > sort of coordinated fashion. > > I guess - if I get everything working, would you be willing to merge a > bunch of related PRs as provenpackager and do rebuilds in a side tag? I'd be able and willing to assist here too, thanks for working on it! As far as sip6 goes, I'd venture the adjustment from v5 to v6 will be smaller than what v4 to v5 was. -- Rex ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Thoughts about packaging a standalone python-PyQt5-sip?
On Sat, 24 Apr 2021, Kevin Fenzi wrote: On Tue, Jan 12, 2021 at 10:42:28PM -0500, Scott Talbert wrote: OK, I'm going to make an attempt to move python-qt5 (and its friends) to sip5. I'm planning to build everything in a copr first. Hey Scott. Did you get any further with this? Anything I can do to help? I'd really like to be able to update calibre again. :) Yes, I got fairly far with porting all PyQt5 SIP consumers (including calibre) to use SIPv5. I think I then got discouraged at the thought of making a bunch of PRs and having to nag maintainers to merge them in some sort of coordinated fashion. I guess - if I get everything working, would you be willing to merge a bunch of related PRs as provenpackager and do rebuilds in a side tag? At this point, it might also make sense to go directly to SIPv6 as that's out already. Scott ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Thoughts about packaging a standalone python-PyQt5-sip?
On Tue, Jan 12, 2021 at 10:42:28PM -0500, Scott Talbert wrote: > > OK, I'm going to make an attempt to move python-qt5 (and its friends) to > sip5. I'm planning to build everything in a copr first. Hey Scott. Did you get any further with this? Anything I can do to help? I'd really like to be able to update calibre again. :) kevin signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Thoughts about packaging a standalone python-PyQt5-sip?
On Mon, 4 Jan 2021, Rex Dieter wrote: I think fundamentally the version of PyQt5-sip probably needs to match (or be very close to) the version of sip that PyQt5 itself was compiled with. I think for calibre (which is currently failing with): ... /usr/bin/python3 -c import os; os.chdir('/builddir/build/BUILD/calibre-5.8.1/build/pyqt/pictureflow'); from sipbuild.tools.build import main; main(); --verbose --no-make --qmake /usr/bin/qmake-qt5 Querying qmake about your Qt installation... /usr/bin/qmake-qt5 -query These bindings will be built: pictureflow. Generating the pictureflow bindings... -c: Unable to find file "QtWidgets/QtWidgetsmod.sip" ...we need python-qt5 to be using sip5 also. I looked into it a bit, it completely changes from using a configure.py to using sip-build and PyQt-builder. Or can we just add a subpackage there that uses sip5 and keep the sip4 ones for sip4 users? something like python3-qt5-sip5-devel ? Or should we just convert everything to sip5 now? I'd really like to get calibre building again... :) It looks like technically you can still use configure.py to build PyQt5 with sip5, but it does seem more forward looking to switch to sip-build / sip-install. BTW, can you please build PyQt-builder for F33? Thanks. Sure. Also, co-maintainers welcome. :) Thanks! BTW, I starting looking into moving python-qt5 to sip5. It doesn't look like it would be *that* difficult. I thought about doing a PR, but it might be better if the regular pyqt5 maintainer (if interested/available) did it. With my "regular maintainer" hat on, I'll say unfortunately I've not had time to look into this and probably won't for the foreseeable immediate future. I'll also chime in with "co-maintainers" welcome if there are folks interested in able in moving this forward. Just take care to minimize breakage. OK, I'm going to make an attempt to move python-qt5 (and its friends) to sip5. I'm planning to build everything in a copr first. Thanks, Scott ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Thoughts about packaging a standalone python-PyQt5-sip?
On Wed, Jan 06, 2021 at 11:07:24AM -0500, Scott Talbert wrote: > > OK. > > And of course, now sip6 has been released. So perhaps we should just skip > sip5 altogether and just go directly to 6. Ha. Figures. I just want to get back to where I can update calibre again. It updates very often because they are always adding/tweaking support for all the ebook readers out there. Not being able to update it these last few months is getting more and more painful. :( kevin signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Thoughts about packaging a standalone python-PyQt5-sip?
On Mon, 4 Jan 2021, Rex Dieter wrote: I think fundamentally the version of PyQt5-sip probably needs to match (or be very close to) the version of sip that PyQt5 itself was compiled with. I think for calibre (which is currently failing with): ... /usr/bin/python3 -c import os; os.chdir('/builddir/build/BUILD/calibre-5.8.1/build/pyqt/pictureflow'); from sipbuild.tools.build import main; main(); --verbose --no-make --qmake /usr/bin/qmake-qt5 Querying qmake about your Qt installation... /usr/bin/qmake-qt5 -query These bindings will be built: pictureflow. Generating the pictureflow bindings... -c: Unable to find file "QtWidgets/QtWidgetsmod.sip" ...we need python-qt5 to be using sip5 also. I looked into it a bit, it completely changes from using a configure.py to using sip-build and PyQt-builder. Or can we just add a subpackage there that uses sip5 and keep the sip4 ones for sip4 users? something like python3-qt5-sip5-devel ? Or should we just convert everything to sip5 now? I'd really like to get calibre building again... :) It looks like technically you can still use configure.py to build PyQt5 with sip5, but it does seem more forward looking to switch to sip-build / sip-install. BTW, can you please build PyQt-builder for F33? Thanks. Sure. Also, co-maintainers welcome. :) Thanks! BTW, I starting looking into moving python-qt5 to sip5. It doesn't look like it would be *that* difficult. I thought about doing a PR, but it might be better if the regular pyqt5 maintainer (if interested/available) did it. With my "regular maintainer" hat on, I'll say unfortunately I've not had time to look into this and probably won't for the foreseeable immediate future. I'll also chime in with "co-maintainers" welcome if there are folks interested in able in moving this forward. Just take care to minimize breakage. OK. And of course, now sip6 has been released. So perhaps we should just skip sip5 altogether and just go directly to 6. Scott ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Thoughts about packaging a standalone python-PyQt5-sip?
Scott Talbert wrote: > On Sat, 2 Jan 2021, Kevin Fenzi wrote: > > I think fundamentally the version of PyQt5-sip probably needs to match > (or be very close to) the version of sip that PyQt5 itself was > compiled with. I think for calibre (which is currently failing with): ... /usr/bin/python3 -c import os; os.chdir('/builddir/build/BUILD/calibre-5.8.1/build/pyqt/pictureflow'); from sipbuild.tools.build import main; main(); --verbose --no-make --qmake /usr/bin/qmake-qt5 Querying qmake about your Qt installation... /usr/bin/qmake-qt5 -query These bindings will be built: pictureflow. Generating the pictureflow bindings... -c: Unable to find file "QtWidgets/QtWidgetsmod.sip" ...we need python-qt5 to be using sip5 also. I looked into it a bit, it completely changes from using a configure.py to using sip-build and PyQt-builder. Or can we just add a subpackage there that uses sip5 and keep the sip4 ones for sip4 users? something like python3-qt5-sip5-devel ? Or should we just convert everything to sip5 now? I'd really like to get calibre building again... :) >>> >>> It looks like technically you can still use configure.py to build PyQt5 >>> with sip5, but it does seem more forward looking to switch to sip-build >>> / sip-install. >>> >>> BTW, can you please build PyQt-builder for F33? Thanks. >> >> Sure. Also, co-maintainers welcome. :) > > Thanks! BTW, I starting looking into moving python-qt5 to sip5. It > doesn't look like it would be *that* difficult. I thought about doing a > PR, but it might be better if the regular pyqt5 maintainer (if > interested/available) did it. With my "regular maintainer" hat on, I'll say unfortunately I've not had time to look into this and probably won't for the foreseeable immediate future. I'll also chime in with "co-maintainers" welcome if there are folks interested in able in moving this forward. Just take care to minimize breakage. -- Rex ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Thoughts about packaging a standalone python-PyQt5-sip?
On Sat, 2 Jan 2021, Kevin Fenzi wrote: I think fundamentally the version of PyQt5-sip probably needs to match (or be very close to) the version of sip that PyQt5 itself was compiled with. I think for calibre (which is currently failing with): ... /usr/bin/python3 -c import os; os.chdir('/builddir/build/BUILD/calibre-5.8.1/build/pyqt/pictureflow'); from sipbuild.tools.build import main; main(); --verbose --no-make --qmake /usr/bin/qmake-qt5 Querying qmake about your Qt installation... /usr/bin/qmake-qt5 -query These bindings will be built: pictureflow. Generating the pictureflow bindings... -c: Unable to find file "QtWidgets/QtWidgetsmod.sip" ...we need python-qt5 to be using sip5 also. I looked into it a bit, it completely changes from using a configure.py to using sip-build and PyQt-builder. Or can we just add a subpackage there that uses sip5 and keep the sip4 ones for sip4 users? something like python3-qt5-sip5-devel ? Or should we just convert everything to sip5 now? I'd really like to get calibre building again... :) It looks like technically you can still use configure.py to build PyQt5 with sip5, but it does seem more forward looking to switch to sip-build / sip-install. BTW, can you please build PyQt-builder for F33? Thanks. Sure. Also, co-maintainers welcome. :) Thanks! BTW, I starting looking into moving python-qt5 to sip5. It doesn't look like it would be *that* difficult. I thought about doing a PR, but it might be better if the regular pyqt5 maintainer (if interested/available) did it. Scott ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Thoughts about packaging a standalone python-PyQt5-sip?
On Thu, Dec 31, 2020 at 10:02:44PM -0500, Scott Talbert wrote: > On Thu, 31 Dec 2020, Kevin Fenzi wrote: > > > > I think fundamentally the version of PyQt5-sip probably needs to match (or > > > be very close to) the version of sip that PyQt5 itself was compiled with. > > > > I think for calibre (which is currently failing with): > > > > ... > > /usr/bin/python3 -c import os; > > os.chdir('/builddir/build/BUILD/calibre-5.8.1/build/pyqt/pictureflow'); > > from sipbuild.tools.build import main; main(); --verbose --no-make --qmake > > /usr/bin/qmake-qt5 > > Querying qmake about your Qt installation... > > /usr/bin/qmake-qt5 -query > > These bindings will be built: pictureflow. > > Generating the pictureflow bindings... > > -c: Unable to find file "QtWidgets/QtWidgetsmod.sip" > > > > ...we need python-qt5 to be using sip5 also. I looked into it a bit, it > > completely changes from using a configure.py to using sip-build and > > PyQt-builder. > > > > Or can we just add a subpackage there that uses sip5 and keep the sip4 > > ones for sip4 users? something like python3-qt5-sip5-devel ? > > > > Or should we just convert everything to sip5 now? > > > > I'd really like to get calibre building again... :) > > It looks like technically you can still use configure.py to build PyQt5 with > sip5, but it does seem more forward looking to switch to sip-build / > sip-install. > > BTW, can you please build PyQt-builder for F33? Thanks. Sure. Also, co-maintainers welcome. :) kevin signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Thoughts about packaging a standalone python-PyQt5-sip?
On Thu, 31 Dec 2020, Kevin Fenzi wrote: I think fundamentally the version of PyQt5-sip probably needs to match (or be very close to) the version of sip that PyQt5 itself was compiled with. I think for calibre (which is currently failing with): ... /usr/bin/python3 -c import os; os.chdir('/builddir/build/BUILD/calibre-5.8.1/build/pyqt/pictureflow'); from sipbuild.tools.build import main; main(); --verbose --no-make --qmake /usr/bin/qmake-qt5 Querying qmake about your Qt installation... /usr/bin/qmake-qt5 -query These bindings will be built: pictureflow. Generating the pictureflow bindings... -c: Unable to find file "QtWidgets/QtWidgetsmod.sip" ...we need python-qt5 to be using sip5 also. I looked into it a bit, it completely changes from using a configure.py to using sip-build and PyQt-builder. Or can we just add a subpackage there that uses sip5 and keep the sip4 ones for sip4 users? something like python3-qt5-sip5-devel ? Or should we just convert everything to sip5 now? I'd really like to get calibre building again... :) It looks like technically you can still use configure.py to build PyQt5 with sip5, but it does seem more forward looking to switch to sip-build / sip-install. BTW, can you please build PyQt-builder for F33? Thanks. Scott ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Thoughts about packaging a standalone python-PyQt5-sip?
On Wed, 2020-12-30 at 20:40 -0500, Scott Talbert wrote: > On Wed, 30 Dec 2020, Scott Talbert wrote: > > > > Neal and I are looking at getting ButterManager packaged, and it > > > depends on sip and PyQt5-sip: > > > > > > > > > https://github.com/egara/buttermanager/blob/master/requirements.txt > > > > > > [snip] > > > Any idea what's the best way to handle this? and/or why PyQt5- > > > sip's > > > versioning get so far ahead of sip? > > > > I think fundamentally the version of PyQt5-sip probably needs to > > match (or be > > very close to) the version of sip that PyQt5 itself was compiled > > with. > > So it looks like with sip 5, PyQt5-sip is now published separately .. with sip 4, PyQt5-sip has a matching version number, but the package provides an API that is version 12.7. Confusing! > > Also, it seems a bit odd that ButterManager requires PyQt5- > > sip>=12.7.0, but > > only requires sip>=4.19.8 (ie, a MUCH older version of sip). You > > might want > > to just try patching that out and/or inquire with upstream about > > whether that > > version dependency is correct. > > Upstream clarified and it turns out they don't actually depend on sip. And they don't need to depend directly on PyQt5-sip either, PyQt5 automatically pulls it in. > > > Looking at the history...it almost looks like these dependencies were > added due to a packaging bug in PyQt5 in Arch Linux?? [1] > > [1] https://github.com/egara/buttermanager/issues/13 > Yup, thanks! > So it seems like the PyQt5-sip and sip dependencies really shouldn't > be > there as ButterManager doesn't use them itself (that I can tell). > We do need a strategy for how to eventually switch to the standalone PyQt5-sip, but that can wait for when we rebase PyQt5 and KDE to it I guess. Best regards, -- Michel Alexandre Salim profile: https://keyoxide.org/mic...@michel-slm.name chat via email: https://delta.chat/ GPG key: 5DCE 2E7E 9C3B 1CFF D335 C1D7 8B22 9D2F 7CCC 04F2 signature.asc Description: This is a digitally signed message part ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Thoughts about packaging a standalone python-PyQt5-sip?
On Wed, Dec 30, 2020 at 08:26:42PM -0500, Scott Talbert wrote: > > I think fundamentally the version of PyQt5-sip probably needs to match (or > be very close to) the version of sip that PyQt5 itself was compiled with. I think for calibre (which is currently failing with): ... /usr/bin/python3 -c import os; os.chdir('/builddir/build/BUILD/calibre-5.8.1/build/pyqt/pictureflow'); from sipbuild.tools.build import main; main(); --verbose --no-make --qmake /usr/bin/qmake-qt5 Querying qmake about your Qt installation... /usr/bin/qmake-qt5 -query These bindings will be built: pictureflow. Generating the pictureflow bindings... -c: Unable to find file "QtWidgets/QtWidgetsmod.sip" ...we need python-qt5 to be using sip5 also. I looked into it a bit, it completely changes from using a configure.py to using sip-build and PyQt-builder. Or can we just add a subpackage there that uses sip5 and keep the sip4 ones for sip4 users? something like python3-qt5-sip5-devel ? Or should we just convert everything to sip5 now? I'd really like to get calibre building again... :) kevin signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Thoughts about packaging a standalone python-PyQt5-sip?
On Wed, 30 Dec 2020, Scott Talbert wrote: Neal and I are looking at getting ButterManager packaged, and it depends on sip and PyQt5-sip: https://github.com/egara/buttermanager/blob/master/requirements.txt Now, this is where things get a bit odd: - the current sip (4.19.24) does not have autogenerated Python provides, but sip5 does: $ sudo dnf repoquery --provides sip Last metadata expiration check: 1:48:00 ago on Wed 30 Dec 2020 02:50:53 PM PST. sip = 4.19.24-1.fc33 sip(x86-64) = 4.19.24-1.fc33 sip-macros = 4.19.24-1.fc33 $ sudo dnf repoquery --provides sip5 Last metadata expiration check: 1:48:05 ago on Wed 30 Dec 2020 02:50:53 PM PST. python-sip5 = 5.5.0-1.fc33 python3-sip5 = 5.5.0-1.fc33 python3.9-sip5 = 5.5.0-1.fc33 python3.9dist(sip) = 5.5 python3dist(sip) = 5.5 sip5 = 5.5.0-1.fc33 sip5(x86-64) = 5.5.0-1.fc33 - sip ships PyQt5 bindings with matching version, but sip 5 seems to no longer do so $ sudo dnf info python3-pyqt5-sip Last metadata expiration check: 1:51:03 ago on Wed 30 Dec 2020 02:50:53 PM PST. Installed Packages Name : python3-pyqt5-sip Version : 4.19.24 Release : 1.fc33 Architecture : x86_64 Size : 244 k Source : sip-4.19.24-1.fc33.src.rpm Repository : @System From repo: fedora Summary : SIP - Python 3/C++ Bindings Generator for pyqt5 URL : https://riverbankcomputing.com/software/sip/intro License : GPLv2 or GPLv3 and (GPLv3+ with exceptions) Description : This is the Python 3 build of pyqt5-SIP. - https://pypi.org/project/PyQt5-sip/ has PyQt5-sip 12.8.1 but https://pypi.org/project/sip/ has sip 5.5.0 which matches the sip5 in Fedora (available since last month) - there's a lot of packages that depend on python3-pyqt5-sip (though none use the canonical python3dist(pyqt5-sip) unfortunately) $ sudo dnf repoquery --repo rawhide,rawhide-source --whatrequires 'python3dist(pyqt5-sip)' Last metadata expiration check: 0:15:20 ago on Wed 30 Dec 2020 04:28:29 PM PST. $ sudo dnf repoquery --repo rawhide,rawhide-source --whatrequires python3-pyqt5-sip Last metadata expiration check: 0:15:30 ago on Wed 30 Dec 2020 04:28:29 PM PST. calibre-0:4.23.0-3.fc34.x86_64 krita-0:4.4.1-1.fc34.i686 krita-0:4.4.1-1.fc34.x86_64 libarcus-0:4.8.0-1.fc34.src mingw-python-qt5-0:5.15.0-4.fc34.src pyqtwebengine-0:5.15.0-2.fc33.src python-pyface-0:7.1.0-1.fc34.src python-pynest2d-0:4.8.0-1.fc34.src python-qt5-0:5.15.0-5.fc34.src python3-arcus-0:4.8.0-1.fc34.x86_64 python3-arcus-lulzbot-0:3.6.21-8.fc34.x86_64 python3-poppler-qt5-0:0.75.0-6.fc33.x86_64 python3-pyqtchart-0:5.15.2-1.fc34.i686 python3-pyqtchart-0:5.15.2-1.fc34.x86_64 python3-qgis-0:3.16.1-2.fc34.i686 python3-qgis-0:3.16.1-2.fc34.x86_64 python3-qscintilla-qt5-0:2.11.5-1.fc34.x86_64 python3-qt5-base-0:5.15.0-5.fc34.i686 python3-qt5-base-0:5.15.0-5.fc34.x86_64 qhexedit2-0:0.8.9-2.fc33.src scidavis-0:2.3.0-2.fc33.src veusz-0:3.3.1-1.fc34.src veusz-0:3.3.1-1.fc34.x86_64 Any idea what's the best way to handle this? and/or why PyQt5-sip's versioning get so far ahead of sip? I think fundamentally the version of PyQt5-sip probably needs to match (or be very close to) the version of sip that PyQt5 itself was compiled with. Also, it seems a bit odd that ButterManager requires PyQt5-sip>=12.7.0, but only requires sip>=4.19.8 (ie, a MUCH older version of sip). You might want to just try patching that out and/or inquire with upstream about whether that version dependency is correct. (Further details: the PyQt5-sip module consists of generated code that's created by the sip code generator.) Furthermore, I'm a bit confused about why ButterManager requires PyQt5-sip and sip to begin with. I can't see either being used in the current code on GitHub: [talbert@deasil buttermanager]$ grep -rsI sip * requirements.txt:PyQt5-sip>=12.7.0 requirements.txt:sip>=4.19.8 setup.py: 'sip>=4.19.8' snapcraft.yaml: - python3-sip Looking at the history...it almost looks like these dependencies were added due to a packaging bug in PyQt5 in Arch Linux?? [1] [1] https://github.com/egara/buttermanager/issues/13 So it seems like the PyQt5-sip and sip dependencies really shouldn't be there as ButterManager doesn't use them itself (that I can tell). Scott ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Thoughts about packaging a standalone python-PyQt5-sip?
On Wed, 30 Dec 2020, Michel Alexandre Salim wrote: Hi all, Neal and I are looking at getting ButterManager packaged, and it depends on sip and PyQt5-sip: https://github.com/egara/buttermanager/blob/master/requirements.txt Now, this is where things get a bit odd: - the current sip (4.19.24) does not have autogenerated Python provides, but sip5 does: $ sudo dnf repoquery --provides sip Last metadata expiration check: 1:48:00 ago on Wed 30 Dec 2020 02:50:53 PM PST. sip = 4.19.24-1.fc33 sip(x86-64) = 4.19.24-1.fc33 sip-macros = 4.19.24-1.fc33 $ sudo dnf repoquery --provides sip5 Last metadata expiration check: 1:48:05 ago on Wed 30 Dec 2020 02:50:53 PM PST. python-sip5 = 5.5.0-1.fc33 python3-sip5 = 5.5.0-1.fc33 python3.9-sip5 = 5.5.0-1.fc33 python3.9dist(sip) = 5.5 python3dist(sip) = 5.5 sip5 = 5.5.0-1.fc33 sip5(x86-64) = 5.5.0-1.fc33 - sip ships PyQt5 bindings with matching version, but sip 5 seems to no longer do so $ sudo dnf info python3-pyqt5-sip Last metadata expiration check: 1:51:03 ago on Wed 30 Dec 2020 02:50:53 PM PST. Installed Packages Name : python3-pyqt5-sip Version : 4.19.24 Release : 1.fc33 Architecture : x86_64 Size : 244 k Source : sip-4.19.24-1.fc33.src.rpm Repository : @System From repo: fedora Summary : SIP - Python 3/C++ Bindings Generator for pyqt5 URL : https://riverbankcomputing.com/software/sip/intro License : GPLv2 or GPLv3 and (GPLv3+ with exceptions) Description : This is the Python 3 build of pyqt5-SIP. - https://pypi.org/project/PyQt5-sip/ has PyQt5-sip 12.8.1 but https://pypi.org/project/sip/ has sip 5.5.0 which matches the sip5 in Fedora (available since last month) - there's a lot of packages that depend on python3-pyqt5-sip (though none use the canonical python3dist(pyqt5-sip) unfortunately) $ sudo dnf repoquery --repo rawhide,rawhide-source --whatrequires 'python3dist(pyqt5-sip)' Last metadata expiration check: 0:15:20 ago on Wed 30 Dec 2020 04:28:29 PM PST. $ sudo dnf repoquery --repo rawhide,rawhide-source --whatrequires python3-pyqt5-sip Last metadata expiration check: 0:15:30 ago on Wed 30 Dec 2020 04:28:29 PM PST. calibre-0:4.23.0-3.fc34.x86_64 krita-0:4.4.1-1.fc34.i686 krita-0:4.4.1-1.fc34.x86_64 libarcus-0:4.8.0-1.fc34.src mingw-python-qt5-0:5.15.0-4.fc34.src pyqtwebengine-0:5.15.0-2.fc33.src python-pyface-0:7.1.0-1.fc34.src python-pynest2d-0:4.8.0-1.fc34.src python-qt5-0:5.15.0-5.fc34.src python3-arcus-0:4.8.0-1.fc34.x86_64 python3-arcus-lulzbot-0:3.6.21-8.fc34.x86_64 python3-poppler-qt5-0:0.75.0-6.fc33.x86_64 python3-pyqtchart-0:5.15.2-1.fc34.i686 python3-pyqtchart-0:5.15.2-1.fc34.x86_64 python3-qgis-0:3.16.1-2.fc34.i686 python3-qgis-0:3.16.1-2.fc34.x86_64 python3-qscintilla-qt5-0:2.11.5-1.fc34.x86_64 python3-qt5-base-0:5.15.0-5.fc34.i686 python3-qt5-base-0:5.15.0-5.fc34.x86_64 qhexedit2-0:0.8.9-2.fc33.src scidavis-0:2.3.0-2.fc33.src veusz-0:3.3.1-1.fc34.src veusz-0:3.3.1-1.fc34.x86_64 Any idea what's the best way to handle this? and/or why PyQt5-sip's versioning get so far ahead of sip? I think fundamentally the version of PyQt5-sip probably needs to match (or be very close to) the version of sip that PyQt5 itself was compiled with. Also, it seems a bit odd that ButterManager requires PyQt5-sip>=12.7.0, but only requires sip>=4.19.8 (ie, a MUCH older version of sip). You might want to just try patching that out and/or inquire with upstream about whether that version dependency is correct. (Further details: the PyQt5-sip module consists of generated code that's created by the sip code generator.) Scott ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Thoughts about packaging a standalone python-PyQt5-sip?
Hi all, Neal and I are looking at getting ButterManager packaged, and it depends on sip and PyQt5-sip: https://github.com/egara/buttermanager/blob/master/requirements.txt Now, this is where things get a bit odd: - the current sip (4.19.24) does not have autogenerated Python provides, but sip5 does: $ sudo dnf repoquery --provides sip Last metadata expiration check: 1:48:00 ago on Wed 30 Dec 2020 02:50:53 PM PST. sip = 4.19.24-1.fc33 sip(x86-64) = 4.19.24-1.fc33 sip-macros = 4.19.24-1.fc33 $ sudo dnf repoquery --provides sip5 Last metadata expiration check: 1:48:05 ago on Wed 30 Dec 2020 02:50:53 PM PST. python-sip5 = 5.5.0-1.fc33 python3-sip5 = 5.5.0-1.fc33 python3.9-sip5 = 5.5.0-1.fc33 python3.9dist(sip) = 5.5 python3dist(sip) = 5.5 sip5 = 5.5.0-1.fc33 sip5(x86-64) = 5.5.0-1.fc33 - sip ships PyQt5 bindings with matching version, but sip 5 seems to no longer do so $ sudo dnf info python3-pyqt5-sip Last metadata expiration check: 1:51:03 ago on Wed 30 Dec 2020 02:50:53 PM PST. Installed Packages Name : python3-pyqt5-sip Version : 4.19.24 Release : 1.fc33 Architecture : x86_64 Size : 244 k Source : sip-4.19.24-1.fc33.src.rpm Repository : @System From repo: fedora Summary : SIP - Python 3/C++ Bindings Generator for pyqt5 URL : https://riverbankcomputing.com/software/sip/intro License : GPLv2 or GPLv3 and (GPLv3+ with exceptions) Description : This is the Python 3 build of pyqt5-SIP. - https://pypi.org/project/PyQt5-sip/ has PyQt5-sip 12.8.1 but https://pypi.org/project/sip/ has sip 5.5.0 which matches the sip5 in Fedora (available since last month) - there's a lot of packages that depend on python3-pyqt5-sip (though none use the canonical python3dist(pyqt5-sip) unfortunately) $ sudo dnf repoquery --repo rawhide,rawhide-source --whatrequires 'python3dist(pyqt5-sip)' Last metadata expiration check: 0:15:20 ago on Wed 30 Dec 2020 04:28:29 PM PST. $ sudo dnf repoquery --repo rawhide,rawhide-source --whatrequires python3-pyqt5-sip Last metadata expiration check: 0:15:30 ago on Wed 30 Dec 2020 04:28:29 PM PST. calibre-0:4.23.0-3.fc34.x86_64 krita-0:4.4.1-1.fc34.i686 krita-0:4.4.1-1.fc34.x86_64 libarcus-0:4.8.0-1.fc34.src mingw-python-qt5-0:5.15.0-4.fc34.src pyqtwebengine-0:5.15.0-2.fc33.src python-pyface-0:7.1.0-1.fc34.src python-pynest2d-0:4.8.0-1.fc34.src python-qt5-0:5.15.0-5.fc34.src python3-arcus-0:4.8.0-1.fc34.x86_64 python3-arcus-lulzbot-0:3.6.21-8.fc34.x86_64 python3-poppler-qt5-0:0.75.0-6.fc33.x86_64 python3-pyqtchart-0:5.15.2-1.fc34.i686 python3-pyqtchart-0:5.15.2-1.fc34.x86_64 python3-qgis-0:3.16.1-2.fc34.i686 python3-qgis-0:3.16.1-2.fc34.x86_64 python3-qscintilla-qt5-0:2.11.5-1.fc34.x86_64 python3-qt5-base-0:5.15.0-5.fc34.i686 python3-qt5-base-0:5.15.0-5.fc34.x86_64 qhexedit2-0:0.8.9-2.fc33.src scidavis-0:2.3.0-2.fc33.src veusz-0:3.3.1-1.fc34.src veusz-0:3.3.1-1.fc34.x86_64 Any idea what's the best way to handle this? and/or why PyQt5-sip's versioning get so far ahead of sip? Thanks, -- Michel Alexandre Salim profile: https://keyoxide.org/mic...@michel-slm.name chat via email: https://delta.chat/ GPG key: 5DCE 2E7E 9C3B 1CFF D335 C1D7 8B22 9D2F 7CCC 04F2 signature.asc Description: This is a digitally signed message part ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org