How to get a new CLI/Mono package into Debian
This is a quick rundown of the steps required to get a new package sponsored by the Debian CLI team. The most important step is the first one. If you get onto IRC then you can ask questions and we'll be able to help you out.
Join #debian-cli @ OFTC
The Debian policy, New Maintainers' guide and CLI policy are all key reference documents
Package your app using git-buildpackage (see file:///usr/share/doc/git-buildpackage/manual-html/gbp.import.html#GBP.IMPORT.FROMSCRATCH)
Usually short form dh (see dh(1) for more)
cli-common-dev (--with cli) (using cli-common-dev is essential; refer to the CLI policy to find out how this works)
Set the Maintainer in debian/control to the appropriate team. One of:
Debian CLI Applications Team <pkg-cli-apps-team@lists.alioth.debian.org>
Debian CLI Libraries Team <pkg-cli-libs-team@lists.alioth.debian.org>
Sign up on alioth.debian.org
- Request to join the pkg-cli-apps / pkg-cli-libs projects on alioth.
When approved, ssh to git.debian.org and cd /git/pkg-cli-{apps,libs}; ./setup-repository mypkgname 'packaging for mypkg'
Prepare your git repository for pushing to git.debian.org: git remote set-url origin git+ssh://yourusername@git.debian.org/git/pkg-cli-{apps,libs}/packages/mypkgname.git
- push all branches
Ask for sponsorship: (on IRC) %learn rfs mypkgname <NS>
Stay on IRC to receive feedback, also check %rfs-feedback
- Get uploaded by a DD
When the package is accepted, subscribe to bugs on PTS — mail "subscribe mypkgname" to pts@qa.debian.org. This step is very important. As a Debian maintainer, you need to be responsive when bugs are filed against your package.