On Oct 28, 2011, at 19:37, Bruce Vining wrote:
> I have been using Subversion flawlessly (and happily) now for the past 6 months but performed the latest update via the Web Interface (Collabnet Subversion Edge) and now I have hell to pay.
> For the past 6 months I have been successfully using the post-commit bash script in the /hooks subfolder located under my SVN repositories to call a perl script commit-email.pl. I am not sure if you are familiar with this specific perl script, but it will email source changes to designated users upon change commit events in SVN. Post-update, I immediately began getting errors on the parameter list submitted to the svnlook command in said perl script and discovered that with the new update “rev” has been replaced with “–r” as a valid parameter identifier for this command. I had replaced all occurrences and this action corrected respective problem being reported.
> Now, to the next issue, when using the following command:
> ./svnlook info ats-mysqlbu -r 4
> I am getting an error as follows:
> svnlook: E000002: Can't open file 'ats-mysqlbu/format': No such file or directory
> Where ats-mysqlbu is a repository that I created a few months back. In fact I am seeing an error which shows the “/format” string being appended to my repository name in every case where I use the svnlook command. As I said before this command has worked flawlessly up to today, when I performed the update.
All I can say is...
* Yes, you use "-r X" to look at revision X. I don't know where "rev" came from but it must be a very old syntax that predates my involvement with the project (which began in 2004).
* Yes, svnlook looks for a format file inside your repository. My repository directories all contain that file. Don't yours?
* The commit-email.pl script was deprecated years ago; the replacement is mailer.py:
Received on 2011-10-29 07:24:48 CEST