Changelog
svn-buildpackage (0.6.26) unstable; urgency=low
[ Ryan Niebur ]
* if the tarball was downloaded by svn-upgrade's invocation of uscan,
remove it on exit (Closes: #531197)
* if the svn repository is being accessed over ssh, set up a single
ssh connection with an ssh control socket to use throughout the
entire run. This has several advantages. If you are using password
authentication, you will now only need to enter your password once,
instead of many times. This also makes things a *lot* faster.
* allow setting paths relative to the repository root in svn-bp props
(Closes: #415258)
* if they try to svn-upgrade on the tarball that's already in the
tarballs directory, don't error because it already exists
* move the override stuff into SDCommon (Closes: #532239)
* fix --svn-savecfg with --svn-verbose
* allow --svn-savecfg to be used with --svn-override, obviously that's
something that people want to do (based on bug #532239)
* fix downloading the tarball during build
* svn-upgrade: svn up before doing anything
* don't allow svn-upgrading to something that has already been tagged
(Closes: #532832)
* add a setprops option (Closes: #534909)
* Debian Policy 3.8.2
* fix detecting of source builds (Closes: #535614)
* check that the opened changes file is actually a file, and not a
directory (in the event it failed to detect). don't run lintian if
a .changes file wasn't sucessfully found.
* don't die if the tarball can't be found with --svn-download-orig
* don't mention binaries if there aren't any
[ Neil Williams ]
* SDCommon.pm (readLayoutProps): only use repo_root for a Url property
(like tagsUrl).
-- ???? ???????? (Ahmed El-Mahmoudy) <email address hidden> Mon, 20 Jul 2009 19:33:31 +0100
