Martin Wille <[EMAIL PROTECTED]> writes: > David Abrahams wrote: >> It appears that the tagging step for Version_1_30_1 got messed up >> somehow. >> Please have a look at RC_1_30_2, which is our release candidate for >> Version 1_30_2, and let me know if there are any problems. > > I'm not able to run the Linux regression tests on that branch. > process_jam_log fails due to an out_of_range being thrown from > basic_string::substr. Probably, some files are still missing for > the tests to work properly.
It's hard to see how that's possible, but it is. Maybe someone with more CVS experience than I have can explain this. The following shows that only two files were removed between Version_1_30_0 and the end of the RC_1_30_0 branch. $ cvs diff -N -rVersion_1_30_0 -rRC_1_30_0 2>/dev/null | grep -B4 "[+][+][+] /dev/null" =================================================================== RCS file: libs/spirit/example/application/cpp_lexer/makefile diff -N libs/spirit/example/application/cpp_lexer/makefile --- libs/spirit/example/application/cpp_lexer/makefile 9 Feb 2003 02:49:59 -0000 1.3 +++ /dev/null 1 Jan 1970 00:00:00 -0000 -- =================================================================== RCS file: libs/spirit/test/runtests.sh diff -N libs/spirit/test/runtests.sh --- libs/spirit/test/runtests.sh 31 Jan 2003 11:33:47 -0000 1.1 +++ /dev/null 1 Jan 1970 00:00:00 -0000 Looks reasonable. I created RC_1_30_2 with: cvs tag -rRC_1_30_0 RC_1_30_2 . Ugh! The problem was that I hadn't checked out RC_1_30_0. I needed to use the "rtag" command if I wanted to tag a module without regard to the files in my working copy. cvs rtag -aRF -rRC_1_30_0 RC_1_30_2 boost Fixed the problem. That was also the cause of the problem with RC_1_30_1. Please try again, everybody. -- Dave Abrahams Boost Consulting www.boost-consulting.com _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
