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

[Gregor Riepl]

> Do you plan to maintain these packages as part of the 3dprinter group?
> If so, the maintainer should be changed from your name to the mailing
> list, to make sure the packages show up on
> <URL: https://qa.debian.org/developer.php?login=3dprinter-general@lists.alioth.debian.org >.

Ok.

> The packages have outdated standards-version.  The current one is 4.1.0,
> if I am not mistaken.

That must have changed in the meantime...
It was still ok when I packaged 2.5.0 AFAIR.

> You mention that you suspect the lintian issue
> hardening-no-fortify-functions might be a bug in lintian or g++.  I am
> quite sure it is not a bug in lintian, and suggest to not hide it until
> you figure out what is going on.

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).

> Did you consider multiarch when structuring the library packages?

I did follow the advice given in the maintainer docs, but I never tested if
building for other archs or parallel installation would actually work.

> The cura-engine package is already in Debian, so a new upload should
> either use a different package name or continue the d/changelog from
> where the last upload left off.

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.

Bas agreed that we shouldn't change the package name, as that would be
confusing to users.

> I suspect you can get a similar effect by importing orig tarballs (with
> pristine-tar, preferably) using the --upstream-vcs-tag=tag_name
> argument.

Ok... I'll look into this.

> Which package do you believe should be uploaded first?

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.