If we're plugging tools we use to make Debian packages without dealing with the insanity of Debian tooling, I use debbuild[1] with OBS[2] for the bulk of my pac

If we're plugging tools we use to make Debian packages without dealing with the insanity of Debian tooling, I use debbuild[1] with OBS[2] for the bulk of my packaging at work for Debian/Ubuntu systems. As it turns out, it doesn't take that much effort to make packages that comply with Fedora/openSUSE Packaging Guidelines and Debian Policy with this tool, and it has drastically simplified my ability to maintain software across distributions in a way that still cleanly integrates with the distribution platform. This is how the Spacewalk Debian/Ubuntu client packages are built[3][4], among many other things. There's also a few other examples out in the wild[5][6][7]. At least for the stuff I make for myself, I haven't made packages that fully pass lintian, but it's not terribly difficult to do if you want to. [1]: https://github.com/ascherer/debbuild https://github.com/ascherer/debbuild [2]: https://openbuildservice.org/ https://openbuildservice.org/ [3]: https://gitlab.com/datto/engineering/spacewalk-debian-client-packages https://gitlab.com/datto/engineering/spacewalk-debian-client... [4]: https://build.opensuse.org/project/show/systemsmanagement:spacewalk:2.9:debclients https://build.opensuse.org/project/show/systemsmanagement:sp... [5]: https://pagure.io/python36-flatpkg-deb https://pagure.io/python36-flatpkg-deb [6]: https://pagure.io/rpmdevtools-deb https://pagure.io/rpmdevtools-deb [7]: https://build.opensuse.org/package/view_file/Virtualization:Appliances:Builder/python-kiwi/python-kiwi.spec?expand=1 https://build.opensuse.org/package/view_file/Virtualization:...