Hi Andrew, all,

Regarding the use of -m, if you use bash, I would think that you could use e.g.:

svn commit some_file -m "Some message
Bug: 1234"

This won't work in tcsh, which will complain about the missing closing quote, 
but bash will let you continue the line and insert a literal newline in that 
position, e.g.:

# echo "foo
> bar"
foo
bar

I haven't actually tested this with Subversion and scmbug but can't see why it 
wouldn't work, apologies if it has already been suggested.

Regards,
David


----------------------------------------------
David O'Shea
Engineer
DSpace Pty Ltd

[EMAIL PROTECTED]
www.dspace.com.au
T: +61 8 8260 8118


> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Andrew Sykes
> Sent: Tuesday, 2 October 2007 07:35
> To: [email protected]
> Subject: [scmbug-users] status command problems
> 
> 
> Kristis,
> 
> Sorry I managed to email you directly again - will make sure I post  
> to the list in future!
> 
> Ok, so just to reword for others, since I misunderstood your  
> explanation the first time.
> 
> It is not possible to issue a status command using the -m 
> option, you  
> MUST use an editor and add the status command on a new line.
> 
> I'm afraid, however I still don't quite have it working, I now get  
> the following error...
> 
> Scmbug error 7: Resolving bug '166' from state 'assigned' to state  
> 'resolved' would violate the workflow of the bug-tracker. Instead,  
> the resolution state could be changed to 'feedback' or 'resolved' or  
> 'closed' states.
> 
> I'm sure you remember by now, but for others reading the post, I'm  
> using Mantis BT.
> 
> This message is a bit bizarre, it seems to be saying 'resolved'  
> violates the workflow, use 'resolved' !?!
> 
> I'm sure there's a really simple explanation (as there was to 
> my last  
> prob), but I'm not seeing it, can you explain please?
> 
> Thanks
> - Andrew
> 
> 
> On 1 Oct 2007, at 18:37, Kristis Makris wrote:
> 
> > Hi Andrew,
> >
> > Please send all communication to the mailing list.
> >
> > On Mon, 2007-10-01 at 16:28 +0100, Andrew Sykes wrote:
> >> Kristis,
> >>
> >> Thanks for the quick reply, unfortunately I'm still having 
> problems -
> >> even after copying your example verbatim.
> >
> > That might be a problem. You shouldn't copy it verbatim. You should:
> >
> > $ svn commit some_file
> >
> > BUT NOT
> >
> > $ svn commit -m "some message" some_file
> >
> >> I don't know if "\n" is really a newline in the subversion message,
> >>> but
> >>> the point is that you do need to add a log message for "bug 166:  
> >>> some
> >>> comment here".
> >>>
> >
> > Because as I said, the '\n' character may not be interpreted in the
> > message. You should instead wait for a text editor to come up and  
> > enter
> > a message like:
> >
> > bug 166: my log message goes here and is over 50 characters long.
> > status 166: fixed.
> >
> >
> >> I have NOT modified any of the regexs.
> >
> > That's good. You shouldn't need to.
> >
> >> The error is...
> >> Scmbug error 3: No list of bug ids was found that matches the
> >> log_bugid_regex 'bug\s*([\d|\s|,|#]*?):' and 
> log_bugid_split_regex ',
> >> \s?#|\s?#|,|\s+' in the log message ''.
> >>
> >> It's interesting that the log message in the error comes 
> out as '' -
> >> could the default regex be too greedy?
> >
> > I doubt it.
> >
> > My best guess is that we are hitting a bug exactly 
> because... we have
> > not actually TESTED whether bug resolution works. We only 
> tested if  
> > the
> > resolution information is reported. I'll need to further test this  
> > here
> > in the lab.
> >
> >> For context, I'm using Mac OSX (locally)...
> >>
> >> Could there be some strange character set mismatch going on?
> >>
> >> andrew$ svn --version
> >> svn, version 1.4.4 (r25188)
> >>     compiled Jun 14 2007, 14:23:02
> >>
> >> Copyright (C) 2000-2006 CollabNet.
> >> Subversion is open source software, see 
> http://subversion.tigris.org/
> >> This product includes software developed by CollabNet (http://
> >> www.Collab.Net/).
> >>
> >> The following repository access (RA) modules are available:
> >>
> >> * ra_dav : Module for accessing a repository via WebDAV (DeltaV)
> >> protocol.
> >>    - handles 'http' scheme
> >>    - handles 'https' scheme
> >> * ra_svn : Module for accessing a repository using the svn network
> >> protocol.
> >>    - handles 'svn' scheme
> >> * ra_local : Module for accessing a repository on local disk.
> >>    - handles 'file' scheme
> >
> > I doubt it.
> >
> >
> 
> _______________________________________________
> scmbug-users mailing list
> [email protected]
> http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
> 
_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users

Reply via email to