Translation(s): English - Italiano

svn-buildpackage is a tool which helps in maintenance of packages with Subversion.

Group maintainance HowTo



origUrl specification:

eddy@bounty ~/usr/src/games/trunk/wormux $ svn pl debian/ | grep svn-bp
eddy@bounty ~/usr/src/games/trunk/wormux $ svn pg svn-bp:origUrl debian/

Relative information:


Introduction for a beginner, with debichem

These lines have been written when I began to join the team Debichem.


Everyone has particular habits: I used to manage all of my packages in directories like ${HOME}/development/$PACKAGE

For example the package "units-filter" was managed inside ${HOME}/development/units-filter, and this directory contained files like ${HOME}/development/units-filter/units-filter_3.5.orig.tar.gz

From now on, the particular directory ${HOME}/development will be named ${devroot}.

Getting the team's work into my computer

cd ${devroot}
svn checkout svn+ssh://svn://

cd ${devroot}/debichem
svn update



Working on the package jmol

cd ${devroot}/debichem/unstable/jmol
mkdir ${devroot}/jmol
uscan --force-download --devroot ${devroot}/jmol

jmol: Version (13.2.3) available on remote site:
  (local version is 13.0.15+dfsg, mangled local version number 13.0.15)
jmol: Successfully downloaded updated package Jmol-13.2.3-full.tar.gz
    and symlinked jmol_13.2.3.orig.tar.gz to it
... [ many other lines ] ...
+ exit 0

here are the next hints from Daniel Leidert

- To do some patching or check compilation you can do `svn-do`. In the
  resulting path you can create or modify patches. Do `exit` and all changes
  will be copied to the subversion tree (including changed or added patch
  files). Do `exit 1` or similar and all changes will be dropped.


Just tag, no dependency checks

svn-buildpackage --svn-tag-only -d

Obtaining the unpacked source package without building

svn-buildpackage -d --svn-export


svn-buildpackage -d --svn-builder echo

Modifing easily packages which are partially imported (sources which have the mergeWithUpstream option set)

All of the following commands use the svn-do wrapper script which is present in /usr/bin/svn-do (in older versions svn-do was in /usr/share/svn-buildpackage/contrib/svn-do)

# clean the tree (useful if this requires the full source tree)
% svn-do debclean
I: Exporting source tree via svn-buildpackage...
I: Running command: debclean
I: Copying back the debian/ tree...
`debian/control' ->

# use quilt to refresh a patch
% QUILT_PATCHES=debian/patches svn-do \
     sh -c "quilt push 002_static-linking-dont-build-perf.patch; quilt refresh"
I: Copying back the debian/ tree...
`debian/patches/002_static-linking-dont-build-perf.patch' ->

# start a source editing session and decide later not to copy back the
# debian/ tree
% svn-do $SHELL
I: Running command: /bin/zsh
% exit 1
E: command exited with 1; not copying back the debian/ tree.

# edit a patch in a CDBS' simple-patchsys based package
% svn-do cdbs-edit-patch 02_pmount.patch


svn-buildpackage is currently maintained as part of the collab-maint repository. To join the development team, check it out, join the channel #debian-svn-bp on OFTC, subscribe to PTS on There are some potential improvements that could be made.

Obtaining the current svn-buildpackage can be done via the following command:

debcheckout svn-buildpackage

or, if you want to use authorized access (requires an account on Alioth):

debcheckout -a svn-buildpackage