[3dprinter-general] Bug#706656: ITP: cura -- Controller for 3D printers

Petter Reinholdtsen pere at hungry.com
Thu Sep 28 07:18:28 UTC 2017

[Gregor Riepl]
> That must have changed in the meantime...
> It was still ok when I packaged 2.5.0 AFAIR.

Yes, it changed fairly recently.

> I did quite a bit of research, and I'm almost certain it's a false positive.
> The docs mention posting to
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673112 in such a case.
> I'll remove the override until this has been done (post-release).

I suggest you add the bts ref to the lintian comment to make this clear.
I have fairly high trust in this test in lintian, but have not
investigated your particular case, so see no basis to object to your
findings.  I am glad you have researched it. :)

> This problem has already been resolved. cura-engine will be given a new epoch
> (1:in), which makes it a working upgrade to the "old" CuraEngine. As far as I
> understand, the epoch was introduced for exactly this use case.

Yes, but you should not throw away the old changelog entries.

> libArcus is a dependency of Cura and CuraEngine, and libSavitar is
> needed by Cura. Both should be built first. After that, CuraEngine,
> then Uranium (that's the UI framework) and ultimately
> Cura. fdm-materials is an optional package containing only data files
> and can be built separately.

OK, so lets start with libArcus, then.  Should we coordinate on IRC? I
joined #debian-3dprinting to help out.  If you got the time, I suspect
we can get it uploaded into NEW today.

Happy hacking
Petter Reinholdtsen

More information about the 3dprinter-general mailing list