Hi Gregor. [Gregor Riepl] > sorry about the delay. I was waiting for a review from Bas (or another > DD). The package is also currently stuck at version 2.5.0, due to a > lack of time on my side, but I'll try to prepare and push an update > ASAP.
No worries. > The package is on mentors.debian.net, but you also need to get all the > dependencies if you want to build it yourself: > https://mentors.debian.net/packages/uploader/onitake%40gmail.com Is this the same code as on git.debian.org? > Thanks, I'll consider it. > But I'd really prefer another review of the package before releasing > it into the wild. OK. The most important part to review before uploading is debian/copyright. Errors there will block the package from entering Debian. All other errors can be fixed when the package is in unstable. :) > I could also use some help with common usage of Debian git. > My current build/release procedure for Cura is slightly complicated: > https://anonscm.debian.org/cgit/3dprinter/packages/cura.git/tree/debian/README.source > The same has to be repeated for all dependencies. It did seem quite complicated. Some of it could be made easier by adding a debian/gpb.conf file, and some of it could perhaps be made easier by using gbp import-orig. Why do you use release branches? I normally do not. Btw, you might find this look useful to include in your README: while quilt push ; do quilt refresh; done It will refresh all patches unless one of them cause a problem. -- Happy hacking Petter Reinholdtsen