Package: svn-buildpackage
Version: 0.6.25
Severity: important
Hello,
While doing svn update in the trunk/ directory of the pkg-java
repository - svn+ssh://svn.debian.org/svn/pkg-java/trunk I've noticed
a new tags/ directory where recent svn-buildpackage --svn-tag* did
stored its tags. It's quite bad, as it will make the /trunk directory
very quickly unusable - whereas it is the whole point of having the
trunk/package tags/package layout.
My guess is that the fault lies with svn-buildpackage, in the
heuristics used for detecting the location of the tags directory. It
would be very easy to look for a ../tags directory only if the current
path matches /trunk\/?$/ -- else, if a tags/ directory accidentally
gets created in the trunk/ directory (and why not a package named tags
?), svn-bp is picking up the wrong location. Or try that one last ?
In any case, it is very painful for now. I hope I've provided you
with enough information to track down the problem.
Cheers,
Vincent
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.29-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Versions of packages svn-buildpackage depends on:
ii devscripts 2.10.51 scripts to make the life of a Debi
ii file 5.03-1 Determines file type using "magic"
ii libcapture-tiny-perl 0.06-1 Perl module to capture STDOUT and
ii libfile-libmagic-perl 0.91-2 Perl interface to libmagic for det
ii libsvn-perl 1.5.6dfsg-1 Perl bindings for Subversion
ii liburi-perl 1.37+dfsg-1 Manipulates and accesses URI strin
ii perl 5.10.0-23 Larry Wall's Practical Extraction
ii subversion 1.5.6dfsg-1 Advanced version control system
ii unp 1.0.15 unpack (almost) everything with on
ii wget 1.11.4-2 retrieves files from the web
svn-buildpackage recommends no packages.
svn-buildpackage suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]