Starts and slices fine. Will try the new Mini firmaware and homing on Monday.

Resolved the TLS Certificate transparency error.

Fixes https://pagure.io/fedora-infrastructure/issue/5614 for me

Fixes https://github.com/kliment/Printrun/issues/782

Fixes #1397699

I've tested it with tox and it worked.

Requires /usr/bin/python

This update has been unpushed.

Requires /usr/bin/python

This update has been unpushed.

This update has been unpushed.

Seems OK now. However, I have not yet had time to test the actual firmware upload. I hope you have tested that before damaging all the Lulzbots out there :D

No unversioned obsoletes:

[~]$ rpm -q --obsoletes python
PyXML <= 0.8.4-29
python-ctypes < 1.0.1
python-elementtree <= 1.2.6
python-hashlib < 20081120
python-ordereddict <= 1.1-8
python-sqlite < 2.3.2
python-uuid < 1.31
[~]$ rpm -q --obsoletes python-libs
[~]$ rpm -q --obsoletes python-devel 
[~]$ rpm -q --obsoletes python-tools
[~]$ rpm -q --obsoletes tkinter 
[~]$

The rewheel/__init__.py is complete.

Executing python and doing some REPL works fine. Nothing critical in my system depends on it, so system works as well.

Thanks

Seeing how it is "synced" shouldn't cura-lulzbot require the exact same version of the firmware package to prevent errors (i.e. == instead of >=)?

With Lulzbot Mini, it says: I am sorry, but Cura does not ship with a default firmware for your machine configuration.

Creates PepperFlash directory where plugin needs to live if user has it.

It does not happen, see:

%if 0%{?nacl}
...
%dir %{chromium_path}/PepperFlash/
...
%endif

And %{?nacl} is 0 on F23.

Other than that, the package seem to work.

25 karma and 4 months, please do something.