3

While the tools are the same, the sections and distribution names are notably different between Ubuntu & Debian (and presumably other Debian-based distros).

For example, a Lua library's debian/control file for Debian might use

 Section: contrib/libdevel

while Ubuntu would use

 Section: universe/interpreters

What is the best way to make deb files for each when "universe" doesn't exist in Debian and "contrib" doesn't exist in Ubuntu given that the tools seem to all act upon a single source/config directory: debian? How does one reconcile this?

Note: this question also applies to changelog entries.

closed as off-topic by Tero Kilkanen, kasperd, mdpc, rnxrx, gWaldo Jan 19 '17 at 13:49

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions on Server Fault must be about managing information technology systems in a business environment. Home and end-user computing questions may be asked on Super User, and questions about development, testing and development tools may be asked on Stack Overflow." – mdpc, gWaldo
If this question can be reworded to fit the rules in the help center, please edit the question.

1

Usually when I need to do this, I create separate debian/* directories for each system I'm supporting. You could store them in lots of different ways: perhaps a dedicated source code repository called "packaging" that contains the directories for each system. You can then use a build or CI system (like Jenkins, Travis CI, or similar) to download your application's source code, download the packaging code for the system you are building the package for, and start the build process.

A tool you may want to take a look at to help make this easier is pbuilder which makes it easy to build a package for many different versions of Debian or Ubuntu by making use of chroots.

I also wrote a walk through of how to use pbuilder that you may find helpful.

Not the answer you're looking for? Browse other questions tagged or ask your own question.