Not only when you use stuff from experimental. It is always a good idea to use 
sbuild or pbuilder/cowbuilder to build your packages before uploading. This is 
even the case when the binary packages will be stripped from uploads in the 
future, because you easily see missing dependencies locally.

Just install cowbuilder, run `sudo cowbuilder --create` and then start a build 
with a script similar to

#! /bin/sh
set -e
ID="`/usr/bin/id -nu`"
GROUP="`/usr/bin/id -ng`"
/bin/rm -rf "$HOME/to_upload/"
sudo /usr/sbin/cowbuilder --update
sudo /usr/sbin/cowbuilder --build --buildresult "$HOME/to_upload" "$@"
sudo /bin/chown "$ID:$GROUP" -R "$HOME/to_upload"
cd "$HOME/to_upload"
/usr/bin/debsign *.changes

(don't forget to change the key-id in debsign). You should add your key id to 
~/.devscripts:

DEBSIGN_KEYID=12345678

And you may speedup cowbuilder startup using following entries in 
~/.pbuilderrc (it will share the apt archives with the host rootfs):

BINDMOUNTS="/var/cache/apt/archives"
APTCACHE=""

Adding debuild options will still work. For example if you have a -2 version 
and want to add the source to the tarball then call the script the following 
way (I just say that it is called buildme and can be found in your $PATH):

build-sponsor mypackage_1.0-2.dsc --debbuildopts -sa



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to