Mer/Documentation/Getting your package included

Getting your package included in the Repository

 * Make sure it compiles after getting your build dependancies, dpkg-buildpackage.
 * Ideally test both dpkg-buildpackage -S -us -uc, dpkg-buildpackage -b -us -uc, dpkg-buildpackage -B (some packages may not build any arch-dep packages, so that's ok. Microdocument it on Jaiku.)
 * bzr export lp:~yourusername/m-r/ (gives you a checked out version, without metadata)
 * cd
 * dpkg-buildpackage -S -us -uc, to generate a source package
 * Upload the resulting source package (*.changes, *.tar.gz, possibly *.diff.gz) to your ~/incoming on trac.tspre.org.
 * ssh yourlogin@trac.tspre.org /import-new-packages

(This will add the source package to repository, and complain otherwise)


 * You need access to merbuilder & repository upload for the following, ask Stskeeps on Jaiku/IRC for this. Or refer on Jaiku to the source package and some may pick it up
 * On http://jaiku.com/channel/merbuilder, write "build = "
 * You can also save the builder some resources if it's an arch-indep package and do "build-x86 = "
 * You can make a specific rebuild using build-armel-sb (build in scratchbox),
 * Monitor progress at same page (RSS: http://jaiku.com/channel/merbuilder/feed/rss )
 * An LP player notes that it has picked up a package for building at a certain builder
 * A toast means it baked properly on this architecture. And is uploaded to repository.
 * A heart means it built properly on all architectures. And is uploaded to the repository
 * A bomb means it failed to build on an architecture.
 * A shopping wagon means it has noticed your build request and queued it.
 * A straightjacket means that it failed to build on Scratchbox and needed to be built natively. Note this in "Straightjacket packages" when this happens. means there's a bug in SDK.)