Hi Simon, Welcome to the integration problem...
On Fri, 2008-04-18 at 12:32 +0100, Simon Brooke wrote: > but when I commit that I get > > ** Scmbug error 39: Policy product_name_definition does not support the > 'auto' configuration for CVS. The reason is that CVS 1.11.x does not provide a mechanism for collecting the product name. CVS 1.12.x provides such a mechanism, but Scmbug has yet to implement support for it. http://bugzilla.mkgnu.net/show_bug.cgi?id=746#c1 > and, worse still, I then can't commit the corrected file back to CVS until I > have edited the existing one in place in > /var/lib/cvs/CVSROOT/etc/scmbug/glue.conf, because if I try I still get error > 39. That's a limitation of CVS. It was appropriate to edit glue.conf in place in the repository. A better approach would be to actually use RCS commands to do so: $ cd /var/lib/cvs/CVSROOT/etc/scmbug $ co -l glue.conf $ # edit as needed $ ci glue.conf $ co -u glue.conf > If I understand correctly this means that I can use scmbug to handle only one > of the thirty-three currently active of the one hundred and eight projects in > our CVS. That's not entirely true. If you are running CVS 1.12.x and bug 746 is implemented you could lift this limitation. Additionally, and perhaps arguably, you shouldn't be maintaining 188 projects in a single repository. You should be maintaining 188 repositories. Creating/managing these can be automated. How would you "relocate" one of those to a different machine, or organization, if you needed to ? > I've currently got valid_product_name disabled, and until this morning I > thought that was an acceptable workaround for the problem. However, this > morning a user reported to me as follows: It is. > (10:56:09 AM) Andrew: Simon, is there a problem with tagging on CVS at the > moment? > (10:56:48 AM) Simon: Shouldn't be. I really, really hope not. Are you using > the documented tag format? > (10:57:01 AM) Andrew: I got a "cvs [tag aborted]: correct the above errors > first!" though there weren't any other errors in the log. Is Andrew sure ? I have run into similar problems in the past, without valid_product_name being involved at all. e.g. I had files marked for additions that were not committed, and tried to tag. More precisely, I had the following happen to me: http://bugzilla.mkgnu.net/show_bug.cgi?id=708 > (10:57:27 AM) Andrew: Yes. Does the tag have to have a name which matches a > Bugzilla product name? > (10:57:56 AM) Simon: Uhhmm... documentation on the Wiki: > (10:59:03 AM) Simon: > http://wiki.cygnets.co.uk/index.php?title=CVS#Release.2C_Build_and_Branch_tagging > (10:59:12 AM) Simon: It succeeded but said it had failed? > (10:59:52 AM) Andrew: Oh, hold on. It said "tag aborted". I started one with > the wrong tag, and aborted it, then tried again with the correct tag. > (11:00:05 AM) Andrew: I wonder if it got confused and aborted the second one > too. > (11:01:23 AM) Andrew: Nah, got the same error again. > (11:01:57 AM) Andrew: Was using tag "eWTS_RELEASE_2-18-7" "eWTS" is a > valid Bugzilla product name. > > Checking the activity log shows 154 lines of the form: > Fri Apr 18 11:01:22 2008 127.0.0.1:34289 Processing an 'activity_tag' for > 'eWTS_RELEASE_2-18-7' from SCM user 'af' > (obviously the timestamp varies a little). There's nothing related in the > error log. Clearly, Scmbug accepted the tag operation. This is not a Scmbug error. CVS failed to apply the tag. > Andrew's project did not get tagged 'eWTS_RELEASE_2-18-7' - Because CVS failed to apply the tag. > grep -r 'eWTS_RELEASE_2-18-7' /var/lib/cvs/eWTS/ returns nothing. However, > 'eWTS_RELEASE_2-18-7' did get added as a version of the product > 'Bugzilla-CVS-Wiki integration' in Bugzilla. Because Scmbug did not fail to capture the tag operation and integrate it. > I ran, from the command line, > > [EMAIL PROTECTED]:~/CVSROOT/etc/scmbug$ cvs tag > p_sb_20080418_testing_tag_activity > Scmbug notice: --------------------------------------------------------- > Scmbug notice: Reading configuration > Scmbug notice: Checking configuration > Scmbug notice: Preparing for tagging > Scmbug notice: Processing activity > Scmbug notice: Submitting request > Scmbug notice: Request submission was accepted > cvs tag: Tagging . > T glue.conf > T log_template > > and this went through successfully, correctly tagging the version in CVS and > also creating a Bugzilla product version, but that was in the context of the > product 'Bugzilla-CVS-Wiki integration'. Clearly, Scmbug does not have problems applying the tags. I suspect a user error in Andrews case. > I need my users to be able to tag their versions of their products. I need > the tagging to work. I'm quite happy to enforce a standard tag format, but if > they use that format it's got to go through against their current project. > > What are my options? We have a medium term plan to switch from CVS to > Subversion, but currently we have 3.9 gigabytes of source (and junk, but > weeding would be a major pain) in our CVS, including code which is mission > critical or safety critical for around thirty customers, so it's not a switch > which I can perform overnight. I think Scmbug is working well for you. Just double-check things yourself when problems arise. We've seen a lot of issues with Scmbug and debugged a lot of them. I'd highly recommend you search through our Bugtracker at bugzilla.mkgnu.net when you run into trouble. As far as options go, you could implement 746 (and if you are running CVS 1.12.x) just to get Scmbug to integrate the tags in Bugzilla as versions. But you don't need it. I hope this helps. -Kristis
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
