To start working on nqp:
* install development packages
  # aptitude install git-buildpackage devscripts cme
* set up your environement to have something like:
  $ cat ~/.devscripts
  DEBCHANGE_RELEASE_HEURISTIC=changelog
  DEBUILD_LINTIAN=yes
  DEBUILD_LINTIAN_OPTS="-i -I --show-overrides"
  USCAN_DESTDIR=../tarballs
  DEBRELEASE_DEBS_DIR=../build-area
  $ cat ~/.gbp.conf
  [DEFAULT]
  pristine-tar = True
  sign-tags = True
  [buildpackage]
  # use a build area relative to the git repository
  export-dir=../build-area/
  tarball-dir = ../tarballs/
  urgency=low
  # to use the same build area for all packages use an absolute path:
  #export-dir=/home/debian-packages/build-area
  [import-orig]
  # run hook after the import:
  postimport = gbp dch -N%(version)s -S -a --debian-branch=$GBP_BRANCH
* clone nqp:
  $ gbp clone git+ssh://git.debian.org/git/pkg-rakudo/nqp.git

To update nqp with upstream tarball:
* import new version:
  $ gbp import-orig --uscan
  - follow the prompts
* push the merge to Alioth
  $ gbp push

To build the package:
  $ gbp build-package -us -uc

To cleanup cruft (dangerous, commit your work before):
  $ git reset --hard
  $ git clean -dxf

Note about the source:
* upstream nqp is deliver with a set of jar files without source.
  These jar files are removed when upstream tarball is imported
  (see Debian/copyright file)
  There's no need to worry about the jar files as long as we don't
  provide nqp/jvm.
  The jar files in stage0 directory can be rebuilt with:
  configure && make && make m-bootstrap-files
