New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cura 4.9.1 #21150
Cura 4.9.1 #21150
Conversation
Pull Request assignmentSubmitter: @MathyV dev-libs/libarcus: @gentoo/3dprint, @alexxy, @gentoo/proxy-maint, @MathyV, @Perlovka Linked bugsIn order to force reassignment and/or bug reference scan, please append Docs: Code of Conduct ● Copyright policy (expl.) ● Devmanual ● GitHub PRs ● Proxy-maint guide |
Pull request CI reportReport generated at: 2021-06-07 16:24 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
Looks like I jumped the gun a bit and missed a new python dependency keyring, checking if I missed any else |
I added keyring, importlib_metadata and PyQt5-sip since they were added to requirements.txt in Ultimaker/Cura@8bc2c71 I left the other dependencies alone since they only got an update. |
Pull request CI reportReport generated at: 2021-06-07 18:39 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for your contribution. Could you have a look at my review comments?
@@ -0,0 +1,30 @@ | |||
--- a/src/Socket_p.h |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This file has the same content as libarcus-4.8.0-deprecated-protobuf-calls.patch please reference this instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My reasoning was that I expect 4.8.0 to disappear soon because of no Python 3.9 in the ebuilds, yet I didn't want to touch the ebuild contents, but okay, I'll adapt it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@expeditioneer is it okay if I rename the file to be versionless and update 4.8.0 also without a revbump?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MathyV i would like to have the version number when this patch was first introduced so it is IMHO better to keep track when this patch was first introduced. This is not a strong opinion i could also be happy with a versionless patch.
@@ -0,0 +1,11 @@ | |||
--- a/CMakeLists.txt |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This file has the same content as pynest2d-4.8.0-fix-cpp-version.patch please reference this instead.
@@ -0,0 +1,24 @@ | |||
See https://github.com/Ultimaker/pynest2d/pull/3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This file has the same content as pynest2d-4.8.0-required-flags-from-Libnest2D-target.patch please reference this instead.
~dev-python/uranium-${PV}[${PYTHON_SINGLE_USEDEP}] | ||
~media-gfx/curaengine-${PV} | ||
~media-gfx/fdm-materials-${PV} | ||
dev-qt/qtquickcontrols[widgets] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should it not be dev-qt/qtquickcontrols2 ? Could you also add the slot to this dependency?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tbh I just copied these verbatim from the bug https://bugs.gentoo.org/731274 I will ask the original submitter to comment here
media-gfx/cura/cura-4.9.1.ebuild
Outdated
~media-gfx/curaengine-${PV} | ||
~media-gfx/fdm-materials-${PV} | ||
dev-qt/qtquickcontrols[widgets] | ||
dev-python/PyQt5[-debug] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
dev-python/PyQt5 already listed on Line37
Sorry, that could have been me who did not keep track on the ebuilds in my local repository when patching. I have not been able to start cura for the past year due to qtquickcontrols not being build with the widgets USE flag (only qtquickcontrols, qtquickcontrols2 does not seem to matter when I tested). While troubleshooting and enabling the debug USE flag for a number of packages I came across the following bug: I have tested that and it's happens for cura-4.9.1 as well. So sorry for the mistake with having multiple PyQt5s in the ebuild but USE="-debug" has to be used for PyQt5 in order for cura to start. |
Another comment; I also changed the sip dependency in the libarcus ebuild to use <dev-python/sip-5.5.0 in my local repository since dev-python/sip-5.5.0 seems to break it (ModuleNotFoundError: No module named 'sip' when emerging). |
@hrnick the dependency should be <dev-python/sip-5[${PYTHON_MULTI_USEDEP}] because libarcus is no SIP 5 compatible, see Ultimaker/libArcus#114 |
Closes: https://bugs.gentoo.org/793803 Package-Manager: Portage-3.0.19, Repoman-3.0.3 Signed-off-by: Mathy Vanvoorden <mathy@vanvoorden.be>
Closes: https://bugs.gentoo.org/793803 Package-Manager: Portage-3.0.19, Repoman-3.0.3 Signed-off-by: Mathy Vanvoorden <mathy@vanvoorden.be>
Closes: https://bugs.gentoo.org/793803 Package-Manager: Portage-3.0.19, Repoman-3.0.3 Signed-off-by: Mathy Vanvoorden <mathy@vanvoorden.be>
Closes: https://bugs.gentoo.org/793803 Package-Manager: Portage-3.0.19, Repoman-3.0.3 Signed-off-by: Mathy Vanvoorden <mathy@vanvoorden.be>
Closes: https://bugs.gentoo.org/793803 Package-Manager: Portage-3.0.19, Repoman-3.0.3 Signed-off-by: Mathy Vanvoorden <mathy@vanvoorden.be>
Closes: https://bugs.gentoo.org/793803 Package-Manager: Portage-3.0.19, Repoman-3.0.3 Signed-off-by: Mathy Vanvoorden <mathy@vanvoorden.be>
Closes: https://bugs.gentoo.org/793803 Package-Manager: Portage-3.0.19, Repoman-3.0.3 Signed-off-by: Mathy Vanvoorden <mathy@vanvoorden.be>
Closes: https://bugs.gentoo.org/793803 Closes: https://bugs.gentoo.org/731274 Package-Manager: Portage-3.0.19, Repoman-3.0.3 Signed-off-by: Mathy Vanvoorden <mathy@vanvoorden.be>
I updated the ebuilds:
As I also commented in https://bugs.gentoo.org/795072 there is already a hard dependency on < sip-5 in libarcus so not sure why you are seeing this @hrnick , my best bet is that you are building with ebuild or emerging with --nodeps, on my system portage respects the blocker and downgrades sip. |
Pull request CI reportReport generated at: 2021-06-10 07:15 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
@MathyV Thank you for your contribution! I'll merge this in a few seconds. |
Version bump (https://bugs.gentoo.org/793803)
This PR also adds python 3.9 to the ebuilds and fixes a potential dependency issue (https://bugs.gentoo.org/731274)