Bug#706656: ITP: cura -- Controller for 3D printers
- To: Gregor Riepl <email@example.com>, firstname.lastname@example.org
- Cc: email@example.com, Bas Wijnen <firstname.lastname@example.org>
- Subject: Bug#706656: ITP: cura -- Controller for 3D printers
- From: Petter Reinholdtsen <email@example.com>
- Date: Fri, 06 Oct 2017 04:57:21 +0200
- Message-id: <[🔎] firstname.lastname@example.org>
- Reply-to: Petter Reinholdtsen <email@example.com>, firstname.lastname@example.org
- In-reply-to: <email@example.com>
- References: <firstname.lastname@example.org> <20170329202756.GF25093@spark.dtdns.net> <email@example.com> <firstname.lastname@example.org> <20170404103445.GB29341@spark.dtdns.net> <email@example.com> <20170405064017.GD29341@spark.dtdns.net> <firstname.lastname@example.org> <20170504055905.GG16366@spark.dtdns.net> <email@example.com> <firstname.lastname@example.org> <20170927114908.GA5704@diskless.uio.no> <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?)
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.
Bernd Zeimetz had a few comments on IRC regarding libSavitar:
<bzed> pere: the mentors link points to a mix of 2.5.0 and 2.6.0 versions
<bzed> ah 3dprinter git, found it
<pere> bzed: yes, <URL: https://anonscm.debian.org/git/3dprinter/packages/ >
<bzed> I don't know about 2.5/2.6, but mixing the versions sounds wring as they usually are released together
<pere> some of them are in some debian-* branches.
<bzed> and cura 2.7.0 is out since a month or so
<pere> my focus so far have not been on versions, but on packaging, but as I said, most work is done by onitake.
<bzed> pere: the c++ library parts seem to be fine.
<bzed> pere: what I think might be broken is th epython part.
<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!)
<bzed> I think there is a lot of stuff to merge from upstream
<pere> bzed: sound like git write access would be very useful for you to get.
<bzed> pere: I'm not really keen on maintaining more packages
<bzed> I need to get rid of some others first
<pere> neither am I, which is why onitake is doing most of the work. :)