Bug#706656: ITP: cura -- Controller for 3D printers
- To: Petter Reinholdtsen <firstname.lastname@example.org>, email@example.com
- Cc: firstname.lastname@example.org, Bas Wijnen <email@example.com>
- Subject: Bug#706656: ITP: cura -- Controller for 3D printers
- From: Gregor Riepl <firstname.lastname@example.org>
- Date: Fri, 6 Oct 2017 08:53:16 +0200
- Message-id: <[🔎] email@example.com>
- Reply-to: Gregor Riepl <firstname.lastname@example.org>, email@example.com
- In-reply-to: <[🔎] firstname.lastname@example.org>
- References: <email@example.com> <20170329202756.GF25093@spark.dtdns.net> <firstname.lastname@example.org> <email@example.com> <20170404103445.GB29341@spark.dtdns.net> <firstname.lastname@example.org> <20170405064017.GD29341@spark.dtdns.net> <email@example.com> <20170504055905.GG16366@spark.dtdns.net> <firstname.lastname@example.org> <email@example.com> <20170927114908.GA5704@diskless.uio.no> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com> <[🔎] firstname.lastname@example.org> <email@example.com>
> So, libarcus is uploaded and in NEW, and cura-engine is ready to be
> uploaded but held off until its build dependency libarcus is in
> unstable (what about uploading without arcus support for now?)
CuraEngine is not of much use without libArcus, I'm afraid...
I'm not sure if it even works.
> I'm reluctant to touch the git repository of the remaining packages,
> given that their structure is going to change. Please let me know when
> you complete a transition.
I'm on it, it's just taking a bit longer because I'm still struggling with
git-buildpackage and the standard Debian repo layout.
But it's coming.
libSavitar 2.6.0-1 is ready for review and Cura is under way.
2.6.0 is not a mistake: it contains a critical patch that was causing a
dependency problem. I changed Cura's dependencies accordingly.
> Bernd Zeimetz had a few comments on IRC regarding libSavitar:
> <bzed> I don't know about 2.5/2.6, but mixing the versions sounds wring as they usually are released together
As mentioned above, libSavitar 2.6.0 has a critical fix.
I can turn it into a Debian patch for 2.5.0, but I don't really see the point
since it will be updated to 2.7.0 soon anyway.
> <bzed> https://github.com/thopiekar/Cura-packaging/blob/master/libSavitar/rules
> <bzed> thats the upstream debian/rules file
> <bzed> which looks much more sane. the short one from onitake might do the same, but I doubt it builds for all python versions as it should.
> <bzed> pere: uranium should remove the update checker plugin
> <bzed> https://github.com/thopiekar/Cura-packaging/blob/master/Uranium/rules - again, see upstream
> <bzed> pere: also there are some dependencies/recommends missing.
> <bzed> numpy and blas on the first look
> <bzed> (blas is really recommended to have!)
Thanks for the note, I'll look into it ASAP.
Haven't looked at thopiekar's repo in a while, he didn't show much interest in
addressing Debian policy problems. So I moved away from his work.
But he's working a bit more closely with the Cura project, so it might still