Hello! Thanks for the help! I managed to get a package built for stormpot. The tests and javadoc are not built. My experiments are at https://github.com/gehel/stormpot/tree/debian. I added the debian config files to the original source tree. I'm not sure if that is the way things are usually done, or if a separate repo, just for the debian stuff is better.
There are probably tons of things that are wrong in this package. I'll be happy to fix them if you point them out. Any idea what I should do next? Thanks! On Mon, Jul 11, 2016 at 10:40 AM, Emmanuel Bourg <[email protected]> wrote: > Le 8/07/2016 à 17:54, Guillaume Lederrey a écrit : > >> I'm probably missing something obvious. Could anyone point me in the >> right direction? > > Hi Guillaume, > > Once the debian/* files are generated by mh_make you can build the > package with 'debuild'. mvn-debian is never used, you can forget about > this command. > > To build the package you'll also need the upstream tarball. This is a > compressed tar file containing the sources files of the upstream > project. For a GitHub project like stormpot you generate this tarball by > creating the debian/watch file containing: > > version=3 > https://github.com/chrisvest/stormpot/tags \ > .*/archive/stormpot-([\d\.]+).tar.gz > > and then invoking uscan: > > uscan --download-version 2.4.1 --rename --repack --compression xz > > The tarball is created in the parent directory. At this point you can > run debuild to build the package (or even better, pdebuild to build the > package in a clean environment, but you can learn about this later). > > Emmanuel Bourg > -- Guillaume Lederrey Operations Engineer, Discovery Wikimedia Foundation
