Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1584479
WIP PR: https://src.fedoraproject.org/rpms/slic3r/pull-request/1
Status: During the build, it fails the testsuite.
I am very occupied by other things and I don't have the time to finish
this in reasonable time. Help would be greatly appreciated.
Fedora needs to have the latest version of the 3D printing apps to
remain the best distro for 3D printing.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
Hi, I maintain OpenTK as a direct dependency of RepetierHost (a 3D
printing tool using mono).
RepetierHost went closed source, but we maintain an older version which
was free software.
OpenTK FTBFS since F28. I have no resources to solve that, so I'm
looking for someone who has maybe better understanding of mono to take over.
https://bugzilla.redhat.com/show_bug.cgi?id=1555483
If nobody volunteers, I will orphan both packages.
Thanks.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
I'm ready to update the cura-lulzbot stack (and firmware), but in order
to do that, I need to get python-uranium-lulzbot into Fedora. The
package review is here:
https://bugzilla.redhat.com/show_bug.cgi?id=1532837
Thanks,
~tom
Miro Hronok <mhroncok(a)redhat.com> writes:
> I've updated it to 2.0.0rc5.
Fixes the "Ok 0" bugs.
Fixes the print-everything-twice bug.
Still has the OpenGL attribute bug, and the Gtk warning bug (at least,
when opening the "load file" dialog).
Anyone available to review this Pull Request?
https://src.fedoraproject.org/rpms/printrun/pull-request/2
(I want to push this to F28. It's a Release Candidate version, but I
will backport all fixes, we need to get this to boarder audience.)
Thanks,
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
Hi there,
recently, Cura, a 3D printing software by Ultimaker and its community
have been relicensed from AGPLv3+ to LGPLv3+ [0][1].
When updating Cura in Fedora, I forgot to check, and it's still listed
as AGPLv3+. However, I'm not sure whether I can change the tag to
LGPLv3+, because it uses other software with "stronger" licenses.
In fact, there seem to be a problem already with Uranium (python-uranium
SRPM).
Cura uses CuraEngine (AGPLv3+) trough a protobuf interface [2].
I'm unsure whether a protobuf interface makes the AGPLv3+ "infect" Cura.
I'd guess it does.
Cura uses (Python imports) Uranium (currently also listed as LGPLv3+ in
Fedora) that imports PyQt5 (GPLv3).
I'm confident that PyQt5's GPLv3 "infects" both Uranium and Cura to be
GPLv3. It's the PyQt5's authors business model [3].
So I guess Uranium should be GPLv3 and Cura should be either GPLv3 or
AGPLv3 (no +) depending on the protobuf thing.
I wonder if what Ultimaker is doing is even possible, and whether I
should ask them about it, but before I do, I'll ask here.
BTW Our python-qt5 package (PyQt5 upstream) is listed in Fedora as "BSD
and GPLv2+" which I'm confident is not true and I opened [4] while
investigating this.
Thanks for help.
[0]
https://ultimaker.com/en/community/50303-cura-license-update-from-agpl-to-l…
[1]
https://github.com/Ultimaker/Cura/commit/9a193ad5c5ab5324ad1335dd9adf80fef2…
[2]
https://github.com/Ultimaker/Cura/blob/master/plugins/CuraEngineBackend/Cur…
[3] https://www.riverbankcomputing.com/commercial/license-faq
[4] https://bugzilla.redhat.com/show_bug.cgi?id=1520186
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok