Bug 255630

Summary: cad/cura: update to 4.11.0
Product: Ports & Packages Reporter: Greg V <greg>
Component: Individual Port(s)Assignee: Diane Bruce <db>
Status: Open ---    
Severity: Affects Only Me CC: mazhe, swills, trombik1973
Priority: --- Keywords: patch
Version: LatestFlags: bugzilla: maintainer-feedback? (db)
Hardware: Any   
OS: Any   
Bug Depends on: 255237    
Bug Blocks:    
Attachments:
Description Flags
cura-490.patch
none
cura-490.patch
none
cura-4110.patch
none
revised patch with the latest ports tree none

Description Greg V 2021-05-05 19:26:46 UTC
Relnotes: https://github.com/Ultimaker/Cura/releases/tag/4.9.0

Fix not even exactly mentioned in relnotes: Bridge Fan Speed actually works now, instead of always disabling the fan on detected bridges :D

Port changes: removed git hashes where tags exist; commented out systemd unit.

Weirdness note: pynest2d doesn't have a 4.9.0, so the current commit on the 4.9-beta branch is used.

New dependency: py-keyring. Hopefully didn't miss any others.
Comment 1 Greg V 2021-05-05 19:28:20 UTC
Created attachment 224702 [details]
cura-490.patch

actual patch lol
Comment 2 Diane Bruce freebsd_committer 2021-05-14 15:03:32 UTC
Working on this this weekend.
Comment 3 Matthieu Volat 2021-07-03 06:07:08 UTC
Hi, any progress on reviewing this upgrade? I tried it without seeing any issue, and it's really cool to have Cura in ports!
Comment 4 Greg V 2021-07-29 12:12:54 UTC
Created attachment 226775 [details]
cura-490.patch

Regenerated patch after various portrevision bumps.
Comment 5 Steve Wills freebsd_committer 2021-08-16 14:27:24 UTC
It seems the new cura won't run properly with old py-keyring
Comment 6 Matthieu Volat 2021-09-29 06:18:46 UTC
Created attachment 228237 [details]
cura-4110.patch

Hi, it is a bit sad to see this PR going stale while two other Cura version have been released, I was happy to be able to use Cura in FreeBSD :)

Since the original reporter did not push updates, I would like to propose mine which brings cura to 4.11.0.

Nothing really special to report there, it basically touch the same ports as the 4.9.0 update(cad/cura-engine cad/fdm_materials cad/uranium devel/py-pynest2d net/libarcus net/libcharon) and most of the job was to update the pkg-plist files based on makeplist.

Here some check-plist testing:

gramr:/usr/ports# for port in cad/cura-engine cad/fdm_materials cad/uranium devel/py-pynest2d net/libarcus net/libcharon; do echo "=========== $port ==========="; make -C $port check-plist; done
=========== cad/cura-engine ===========
====> Checking for pkg-plist issues (check-plist)
===> Parsing plist
===> Checking for items in STAGEDIR missing from pkg-plist
===> Checking for items in pkg-plist which are not in STAGEDIR
===> No pkg-plist issues found (check-plist)
=========== cad/fdm_materials ===========
====> Checking for pkg-plist issues (check-plist)
===> Parsing plist
===> Checking for items in STAGEDIR missing from pkg-plist
===> Checking for items in pkg-plist which are not in STAGEDIR
===> No pkg-plist issues found (check-plist)
=========== cad/uranium ===========
====> Checking for pkg-plist issues (check-plist)
===> Parsing plist
===> Checking for items in STAGEDIR missing from pkg-plist
===> Checking for items in pkg-plist which are not in STAGEDIR
===> No pkg-plist issues found (check-plist)
=========== devel/py-pynest2d ===========
====> Checking for pkg-plist issues (check-plist)
===> Parsing plist
===> Checking for items in STAGEDIR missing from pkg-plist
===> Checking for items in pkg-plist which are not in STAGEDIR
===> No pkg-plist issues found (check-plist)
=========== net/libarcus ===========
====> Checking for pkg-plist issues (check-plist)
===> Parsing plist
===> Checking for items in STAGEDIR missing from pkg-plist
===> Checking for items in pkg-plist which are not in STAGEDIR
===> No pkg-plist issues found (check-plist)
=========== net/libcharon ===========
====> Checking for pkg-plist issues (check-plist)
===> Parsing plist
===> Checking for items in STAGEDIR missing from pkg-plist
===> Checking for items in pkg-plist which are not in STAGEDIR
===> No pkg-plist issues found (check-plist)

As for actually using the port, I've tried some splicing and octoprint-based printing without any issue.

Thanks if somebody can have a look and feedback on this.

Regards
Comment 7 Diane Bruce freebsd_committer 2021-10-02 23:44:45 UTC
I'll start work on this tonight.
Comment 8 Diane Bruce freebsd_committer 2021-10-03 14:25:48 UTC
Looks like I got interrupted with real life during test of the Cura 4.9 update as I was sure I had committed that.  Sorry :-(

Looking at 4.11 diffs they work great but py-pynest2d Maintainer is y@trombik.org so he'll also have to approve.
Comment 9 Tomoyuki Sakurai 2021-10-12 01:56:15 UTC
(In reply to Diane Bruce from comment #8)

the maintainer of py-pynest2d here. the port was introduced as a new dependency while updating cura. IMO, all these cura-related ports, such as libarcus, should be managed by a single maintainer because they must be updated at the same time. in theory, other applications may depend on them, but i don't know other consumers.

please reset my MAINTAINER in py-pynest2d. thanks.
Comment 10 Greg V 2021-10-15 20:26:04 UTC
I've had to delete patch-CMakeLists.txt in pynest2d in addition to applying the patch, but 4.11 is working great :)
Comment 11 Tomoyuki Sakurai 2021-10-18 01:45:38 UTC
the patches, `cura-490.patch` and `cura-4110.patch`, are stale. also, errors and warnings are logged in `poudriere` build.
Comment 12 Tomoyuki Sakurai 2021-10-18 01:48:09 UTC
Created attachment 228794 [details]
revised patch with the latest ports tree

also fixes missing `gettext-runtime` dependency.
Comment 13 Tomoyuki Sakurai 2021-10-18 02:03:13 UTC
I would like to call for help and contributions from those who want up-to-date `cura`. as I see it, the maintainer has been busy, and maintaining `cura` and its dependencies is not a trivial task. the traditional workflow in bugzilla is not very suitable for collaboration. here is my partial ports tree to maintain `cura`.

https://github.com/trombik/freebsd-ports-cura

If you want to help, read "Maintaining cura ports" in the Wiki, follow the steps, and report the result in `Issues`.

https://github.com/trombik/freebsd-ports-cura/wiki/Maintaining-cura-ports

If you don't have a working `poudriere`, then, merge the partial ports tree into your own ports tree, and built by hand. Install and use `cura`, print something, and report the result in `Issues`.

In a typical workflow, a PR is made when the partial ports tree has been tested.

This way, the MAINTAINER just need to approve the PR. some other ports, like `drm-current-kmod`, also use a workflow like this.