In glue.conf, there is a stanza:

        # Product name definition. There are 2 options:
        #
        # - type is 'manual'. Each bug id supplied during commit
        #   messages must be filed against the product name
        #   specified in value.
        #
        # - type is 'auto'. The product name will be
        #   autodetected. Value must be a comma(,)-separated list of
        #   regular expressions. Each regular expression must set the
        #   unnamed variable $1 to the product name.
        #
        # This policy is ALWAYS enabled
        product_name_definition => {
            type => 'manual',
            value => 'Bugzilla-CVS-Wiki integration'
            },

I've clearly got this wrong. I've tried checking out and editing this to

        product_name_definition => {
            type => 'auto',
            value => '/var/lib/cvs/([a-zA-Z0-9_-]*)/.*'
            },

but when I commit that I get 

** Scmbug error 39: Policy product_name_definition does not support the 'auto' 
configuration for CVS.

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.

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.

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:

(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.
(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.

Andrew's project did not get tagged 'eWTS_RELEASE_2-18-7' - 
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.

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'.

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.



Simon Brooke, Software Specialist
Cygnet Solutions Ltd
Registered office: Swan House, Darvel, Ayrshire, Scotland, KA17 0LP
Registered in Scotland No. SC158059
mail: [EMAIL PROTECTED]
www: http://www.cygnets.co.uk
tel: +44(0)1560 323444
fax: +44(0)1560 323432

_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users

Reply via email to