Trejkaz, thanks for the bug-report: http://bugzilla.mkgnu.net/show_bug.cgi?id=1255
- Can you also report which version of Scmbug with which version of Subversion demonstrate this ? - Where the commits both made on the same file ? - Is the wrong revision number also reported in the issue-tracker ? > This really should say 5614; it's almost as if scmbug is re-executing > svn to ask it what the latest revision is, when it should be using the > version passed in from the commit hook. There is no version number passed in from the commit hook. There is a transaction number passed in, and Scmbug uses that number with 'svnlook youngest' during the pre-commit script for verification. This logic is used again during the post-commit, though, even if the transaction number is explicitly specified. Hmmm.... this sounds like a bug. > Maybe it's just a cosmetic issue and we don't need to worry; in this > case the file was not modified in revision 5615 anyway so no > inconsistency could result from this instance. No, this is serious.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
