On Fri, 2007-01-12 at 17:58 +0800, Homer Simpson wrote:
> Thanks for the reply Kristis,
> 
> Some time tags or branches may not be made by the developer, instead
> the admin might do it. The website example assumes you are using a
> working copy to create a branch which means the user has to either
> switch their working copy to the correct path, copy and then commit. 

This has to be a bug then. I had the impression that Subversion would
still execute it's hooks when copying remotely. I'll try to test it too.

http://bugzilla.mkgnu.net/show_bug.cgi?id=919

Thanks!

> If the admin were to create the branch/tag, and he had remote access
> to the repository, he could create a branch like this:
> 
> "svn copy svn://remotehost/Product/trunk
> svn://remotehost/Product/branch/bug0-1-9 
> 
> with '^bug[0-9]-[0-9]-[0-9]$' as a rule. (also assume unauthorized
> users had write access).
> 
> I can't test this right now without first asking our product head but
> from what he told me, this bypasses scmbug's label check. 
> 
> Your two step method should work because I've tested it before. I
> won't get a chance to test the "direct" svn copy and whether the label
> checks are enforced until monday.
> 
> I'll get back to you with my findings. 
> 
> H.S
> 
> 
> On 1/12/07, Kristis Makris <[EMAIL PROTECTED]> wrote:
>         Hi Homer,
>         
>         On Fri, 2007-01-12 at 10:01 +0800, Homer Simpson wrote:
>         > Hello, I have a few questions about the labeling operations.
>         I tried
>         > to enforce rules for the tags and branch folders but it
>         didn't seem to 
>         > work.
>         
>         Has a more relaxed definition of the expressions worked ?
>         
>         > Here is what I have in my conf:
>         >
>         >         # Format of label names (tag or branch names)
>         defined as
>         >         # regular expressions. 
>         >         label_name => {
>         >             enabled => 1,
>         >             names => [
>         >                       # Convention for official releases.
>         >                       # For example:
>         >                       # SCMBUG_RELEASE_0-2-7
>         >                       #'^.+?_RELEASE_[0-9]+-[0-9]+-[0-9]+$',
>         >                       '^ACM[0-9]+$',
>         >
>         >                       # Convention for development builds. 
>         >                       # For example:
>         >                       #
>         SCMBUG_BUILD_28_added_a_policies_mechanism
>         >                       #'^.+?_BUILD_[0-9]+_.+$',
>         >                       '^D_ACM[0-9]+$', 
>         >
>         >                       # Convention for branches.
>         >                       # For example:
>         >                       #
>         b_experimenting_with_policies_on_glue_side
>         >                       #'^b_.+$', 
>         >                       '^B_ACM[0-9]+$',
>         >
>         >                       # Convention for private developer
>         tags. Uses
>         >                       # the developer's initials (either 2
>         or 3).
>         >                       # For example:
>         >                       #
>         p_kpm_prior_to_bug353_stabilization_fixes
>         >                       '^p_[a-zA-Z][a-zA-Z]?[a-zA-Z]_.+$'
>         >                       ]
>         >                   },
>         >
>         > I'm not too familiar with the coding used for the default
>         scmbug
>         > examples but if someone could help me out a bit with
>         expanations I
>         > would greatly appreciate it .e.g the +$ ^ etc... 
>         >
>         > This is what I want in my repository:
>         >   tags/CM0100101
>         >   branches/B_CM0100101 or D_CM01000101
>         >
>         > The only values that would change would be the last 3 which
>         means
>         > something like: B_CM0100[0-9][0-9][0-9] ? 
>         
>         This expression looks pretty good. It should be, more
>         precisely:
>         
>         ^B_CM0100[0-9][0-9][0-9]$
>         
>         So, modify glue.conf to:
>         
>         names => [
>                               '^ACM[0-9]+$',
>                               '^D_ACM[0-9]+$', 
>                               '^B_ACM[0-9]+$',
>                               '^B_CM0100[0-9][0-9][0-9]$',
>                               '^p_[a-zA-Z][a-zA-Z]?[a-zA-Z]_.+$'
>                              ]
>         
>         and see if the commit is accepted. 
>         
>         > Also from the example in the website:
>         >
>         
> http://files.mkgnu.net/files/scmbug/doc/latest_manual/html-multi/x210.html 
>         > it seems as though you are working from a working copy with
>         the commit
>         > statement, is the commit statement neccessary?
>         
>         Yes it is. Just issuing the 'svn copy' would flag the working
>         copy with 
>         a new directory to be added, but would not commit it yet.
>         
>         > I just want to be able to do something like this from my
>         client
>         > machine:
>         > svn copy svn://repos/PRODUCT/trunk
>         > svn://repos/PRODUCT/branches/B_CM0100402 
>         > which was not enforced with the conf from above.
>         
>         Did you mean that this copy was accepted ? It shouldn't have,
>         since you
>         were missing the regex above.
>         
>         I wonder if we have a bug here. E.g. if 'svn copy' on a
>         remote 
>         repository does not work. Have you also tried doing this in
>         two separate
>         steps as in the example in the website you posted above ? Can
>         you try it
>         and report back ?
>         
>         
>         
> 

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

Reply via email to