[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Previous transaction name in pre-commit script?

From: Sas Janusz <j.sas_at_teta.com.pl>
Date: 2007-11-20 11:54:52 CET

Hi, I have such a problem
 
Client: Windows XP SP2
Server: Windows XP SP2
Subversion: Client & Server version 1.4.4.25188
 
Client action:
E:\T2K_WF\GL\serwer\Funkcje>svn add new_file.txt
A new_file.txt
 
E:\T2K_WF\GL\serwer\Funkcje>svn commit -m "adding new file"
Dodawanie Funkcje\new_file.txt
Przesyłanie treści pliku.
Zatwierdzona wersja 85.
 
E:\T2K_WF\GL\serwer\Funkcje>svn add new_file2.txt
A new_file2.txt
 
E:\T2K_WF\GL\serwer\Funkcje>svn commit -m "adding new file 2"
Dodawanie Funkcje\new_file2.txt
Przesyłanie treści pliku.
Zatwierdzona wersja 86.
 
Pre-commit.bat on the server side:
SET REPOS=%1
SET TXN=%2
FOR /F "tokens=1,2 delims= " %%i IN ('svnlook changed %REPOS%') DO (
    ECHO %%j %TXN%> E:\check-file.txt
)
EXIT 0
 
Content of E:\check-file.txt after the above 2 commits:
serwer/Funkcje/new_file.txt 85-1
 
This test has proved, that the second parameter of the pre-commit hook script equals to previous transaction name (85-1) instead of
current transaction name (should be "86-1", I guess). Every documentation, I have read, tells otherwise. I can't really believe, that it is a "general bug". I have tried to find in the web any descriptions of similar problems - with no results. Release notes of 1.4.5 version doesn't indicate any changes in this matter.
I would appreciate any suggestions. Thanks in advance.
 
Janusz

TETA S.A.
Al. Wiśniowa 1, 53-137 Wrocław
http://www.teta.com.pl
tel. +48.71.323.40.00, fax: +48.71.323.40.01
NIP: 897-000-94-77

Sąd Rejonowy dla Wrocławia-Fabrycznej we Wrocławiu,
VI Wydział Gospodarczy, KRS nr 0000111682
Kapitał akcyjny i wpłacony: 9 000 000 zł

BPH PBK S.A. Wrocław
Nr rachunku: 62 1060 0076 0000 3210 0004 8734
Received on Wed Nov 21 03:06:51 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.