Bug 2036371
| Summary: | Please build cura 4.12.1 for Fedora | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jan Pazdziora <jpazdziora> |
| Component: | cura | Assignee: | Miro Hrončok <mhroncok> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 35 | CC: | bernhard.furtmueller, g, jpazdziora, mhroncok, python-sig |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | cura-4.13.1-2.fc34 cura-4.13.1-2.fc35 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-03-14 22:25:25 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Jan Pazdziora
2021-12-31 13:26:43 UTC
I've also noticed that the current cura-4.11.0-1.fc35.noarch installation suffers from https://github.com/Ultimaker/Cura/issues/10785 -- when support blocker is used, clicking on the model results in the same traceback as in the GitHub issue. Thanks, the update PR is waiting for a final review now: https://src.fedoraproject.org/rpms/cura/pull-request/13 Gabriel, isn't there a PR missing for libarcus? Or will that one be created if everything else is ready for final? Good point, I just forgot to open the PR from the branch I pushed a while ago: https://src.fedoraproject.org/rpms/libarcus/pull-request/19 FEDORA-2022-b5207bc9c2 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-b5207bc9c2 FEDORA-2022-d894a07b78 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-d894a07b78 FEDORA-2022-162f70a9db has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-d894a07b78 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-d894a07b78` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-d894a07b78 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-b5207bc9c2 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-b5207bc9c2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-b5207bc9c2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. Thanks for the builds. I confirm that on Fedora 35, cura 4.12.1 seems to work reasonably well. The https://github.com/Ultimaker/Cura/issues/10785 is still present though. Since in the comments of that issues it was pointed out that it might be due to Qt being too new, is that something that Fedora builds might want to carry as a compatibility patch, before 4.13 is out? If you open a PR with the patch, I'll gladly review and merge. Otherwise, I will eventually get to it. Opened PR https://src.fedoraproject.org/rpms/cura/pull-request/14 with the relevant patch. FEDORA-2022-b5207bc9c2 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-b5207bc9c2 (In reply to Gabriel Féron from comment #12) > Opened PR https://src.fedoraproject.org/rpms/cura/pull-request/14 with the > relevant patch. Added to rawhide and the F35 update https://bodhi.fedoraproject.org/updates/FEDORA-2022-b5207bc9c2 FEDORA-2022-b5207bc9c2 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-b5207bc9c2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-b5207bc9c2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-b32cb71cc2 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-b32cb71cc2 FEDORA-2022-252d889047 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-252d889047 FEDORA-2022-252d889047 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-252d889047` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-252d889047 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-b32cb71cc2 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-b32cb71cc2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-b32cb71cc2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-252d889047 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-b32cb71cc2 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report. |