Package: svn-buildpackage Version: 0.6.15 Severity: minor Tags: patch I notced a couple of errors/typos and a few bits of english that could be improved/clarified. Here is a patch.
-- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-1-k7 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages svn-buildpackage depends on: ii devscripts 2.9.26 Scripts to make the life of a Debi ii libsvn-perl 1.4.2dfsg1-2 Perl bindings for Subversion ii perl 5.8.8-6.1 Larry Wall's Practical Extraction ii subversion 1.4.2dfsg1-2 Advanced version control system ii subversion-tools 1.4.2dfsg1-2 Assorted tools related to Subversi svn-buildpackage recommends no packages. -- no debconf information
--- svn-buildpackage.orig 2006-12-14 12:27:48.963213009 +0000 +++ svn-buildpackage.1 2006-12-14 12:35:24.285476360 +0000 @@ -18,7 +18,7 @@ set the svn property mergeWithUpstream on the Debian directory ("svn propset mergeWithUpstream 1 debian"). .PP -The default behaviour is following: +The default behaviour is as follows: .P Check the working directory, complain on uncommited files (also see \-\-svn\-ignore\-new) .P @@ -127,11 +127,11 @@ svn\-buildpackage's behaviour can be modified using the file \fB~/.svn\-buildpackage.conf\fR. Additional parts can be added in each package working directory using the file \fB~/.svn/svn\-buildpackage.conf\fR. -It is basicaly a list of the long command line options (without leading -minus signs), one argument per line (but without quotes embrassing +It is essentially a list of the long command line options (without leading +minus signs), one argument per line (without quotes surrounding multi-word arguments). The variables are expanded with the system shell if -potential shell variables were found there. Avoid ~ sign because of unreliable -expansion, better use $HOME instead. +shell variables are found there. Avoid ~ sign because of unreliable +expansion: it is better to use $HOME instead. Example: .RS .PD 0 @@ -191,7 +191,7 @@ Export upstream source from the repository even if mergeWithUpstream property is set .SH RECOMMENDATIONS -First thing, using shell aliases makes sense. Example for the Bash: +First thing, using shell aliases makes sense. Here are some examples for Bash: .RS .PD 0 alias svn-b="svn-buildpackage -us -uc -rfakeroot --svn-ignore" @@ -199,11 +199,11 @@ alias svn-bt="svn-buildpackage --svn-tag -rfakeroot" .PD .RE -That simply has the meaning: "just build no matter what", the same without -re-exporting on repeated builds and "build for upload and tag". +Those commands have respective meanings: "just build no matter what", +"as above without re-exporting on repeated builds", and "build for upload and tag". .P To access remote repositories, the shell access (via ssh) is the easiest way to -create the link. However, it requires to enter the password and this happens +create the link. However, it requires entering the password and this happens more often with svn\-buildpackage. There are workarounds: use ssh key without passphrase (insecure and still slow connection) or use the fsh tool which keeps a persistent connection in background and behaves like a rsh/ssh