I believe my problem yesterday was related to the repository residing on a network file share and the drive letter not resolving correctly to the UNC path. I copied the repository to my C drive and I've gotten a little further.
I now get an error related to the regular expressions. When I try to commit a simple update, I get this error. Bugzilla-ID is the label I'm using in Subversion to identify my bugs. I *do* have a Bugzilla issue #1 open against my Test product. When it says no list of bug ids was found, where exactly is it looking? As you can see from the error, the log message does indeed contain a bug id that looks to me like it should match the regular expression. Thanks! - Paul Commit failed (details follow): Commit blocked by pre-commit hook (exit code 1) with output: Scmbug notice: --------------------------------------------------------- Scmbug notice: Preparing for VERIFICATION Scmbug ERROR> SCM.pm:509:Scmbug::Glue::SCM::prepare_final_log_message - ******************************************* ** ** ** Scmbug error 3: No list of bug ids was found that matches the log_bugid_regex '^\s*Bugzilla-ID\s*([\d|\s|,|#]*?):' and log_bugid_split_regex ',\s?#|\s?#|,|\s+' in the log message 'scmbug test Bugzilla-ID 1 '. ** ** ******************************************* >-----Original Message----- >From: Gillis, Paul >Sent: Tuesday, February 10, 2009 2:44 PM >To: 'Tsahi Asher'; Kristis Makris >Cc: [email protected] >Subject: RE: [scmbug-users] scmbug 0.26.13, Bugzilla 3.2.0, SVN1.5.5->pre- >commit.bat fails > >I just double checked and yes I've got all of those packages installed. > >What is it exactly that the pre-commit Perl scripts are trying to verify >anyways? I'm trying to figure out what Glue.pm is looking for when it >reads in Glue.conf. But between the regular expressions and handing off to >other modules, I'm at a loss to follow it! > >Thanks! > >>-----Original Message----- >>From: Tsahi Asher [mailto:[email protected]] >>Sent: Tuesday, February 10, 2009 2:23 PM >>To: Gillis, Paul; Kristis Makris >>Cc: [email protected] >>Subject: Re: [scmbug-users] scmbug 0.26.13, Bugzilla 3.2.0, SVN1.5.5->pre- >>commit.bat fails >> >> >>the required perl modules are listed on section 8.2, Installation. they >>are: >>Log::Log4perl >>XML::Simple >>Mail::Sendmail (if you want scmbug to send mail on commits) >>DBI (also required by bugzilla) >> >>usually you will replace the "::" with a minus sign (-) when searching for >>modules in your package manager. >> >>tsahi >> >> -- >>The day Micro$oft sells something that doesn't SUCK >>is the day they start selling vacuum cleaners. >>http://www.geocities.com/tsahi_75 >> >> >> >>----- Original Message ---- >>> From: "Gillis, Paul" <[email protected]> >>> To: Kristis Makris <[email protected]> >>> Cc: [email protected] >>> Sent: Tuesday, February 10, 2009 9:09:59 PM >>> Subject: Re: [scmbug-users] scmbug 0.26.13, Bugzilla 3.2.0, SVN1.5.5- >>>pre-commit.bat fails >>> >>> >>> >-----Original Message----- >>> >From: Kristis Makris [mailto:[email protected]] >>> >Sent: Tuesday, February 10, 2009 1:58 PM >>> >To: Gillis, Paul >>> >Cc: [email protected] >>> >Subject: RE: [scmbug-users] scmbug 0.26.13, Bugzilla 3.2.0, >>> SVN1.5.5->pre- >>> >commit.bat fails >>> > >>> >> environment must be set up. I find it hard to believe I'd be the >>> first >>> >> person to encounter this if that is indeed the problem. >>> > >>> >True. This is the first time we've had a report like this. Something >>> >else must be going on. >>> > >>> >Are you sure you have all the Perl modules needed ? >>> >>> I'm not sure because I don't know what they all are! The documentation >>> made a statement along the lines that you'd get errors and/or warnings >>> during the install if any were missing, but it does not tell you what >>> they are. There were a couple I had to install. When I got to the DBI >>> problem, I followed somebody's suggestion about commenting out the >>> section that checks for minimum revision because what I have installed >>> is a higher rev than what it said I was missing. >>> >>> > >>> >> I commented out that line in the glue.conf file that's in my >>> repository >>> >> hooks directory. I re-ran my commit and it failed, but it did not >>> >> create a C:\Temp\scmbug_glue.log file! Is there anything else I >>> must >>> >> do? >>> > >>> >I'm not sure what the problem is. You would probably have to start >>> >debugging this thing... By adding debugging statements in Perl that >>> emit >>> >stuff out to a file. >>> >>> I was hoping to avoid that because my Perl is pretty rusty. But I'll >>> keep at it until my frustration gets the best of me. I'm supposed to be >>> demo'ing this tomorrow to the rest of engineering. >>> >>> Thanks! >>> >>> >>> This e-mail message and all attachments thereto may contain technical >>data that >>> is subject to export control regulations, or confidential material, and >>is for >>> the sole use of the intended recipients. Review, dissemination, or other >>use by >>> anyone else is prohibited. If you are not an intended recipient, please >>contact >>> the sender and delete all copies. >>> _______________________________________________ >>> scmbug-users mailing list >>> [email protected] >>> http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users >> >> >> >> This e-mail message and all attachments thereto may contain technical data that is subject to export control regulations, or confidential material, and is for the sole use of the intended recipients. Review, dissemination, or other use by anyone else is prohibited. If you are not an intended recipient, please contact the sender and delete all copies.
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
