The mercurial clone wizard create hgrc entry:
default = https://nnguyen:****@hg.netbeans.org/main/
default = http://hg.netbeans.org/main/
default-push = https://nnguyen:****@hg.netbeans.org/main/
This put authentication information into _pull_ path, whereas it should only be in _push_ path, and probably cause push
abort: pretxnchangegroup.subject hook failed
Did you clone from http://hg.netbeans.org/main/?
My understanding is that is that it is mercurial itself, not the mercurial plugin which sets the hgrc entry.
I believe that the recommendation is that you clone from http://hg.netbeans.org/main/ and set default-push path manually
after the clone.
I thought that the error "abort: pretxnchangegroup.subject hook failed" is caused by not having username set to NetBeans
I specified repository URL: https://nnguyen:****@hg.netbeans.org/main/ on the first page of the wizard. So I get only
one paths entry 'default', no 'default-push'. This causing the error when I push. Correcting the entry by adding
'default-push' does not help because the repository is already populated with changesets with
https://nnguyen:****@hg.netbeans.org/main information. To avoid this confusing situation,
I guess we could improve the wizard by have separate fields for user, password and checkbox for whether to use them in
default path (default is false). The plugin could add default-push entry after the hg clone command complete.
Proposal to sort this out:
Add a new step, Mercurial Paths:
1. Mercurial Repository
2. Mercurial Paths
3. Destination Directory
This will have two text fields:
Initially they will be filled in with the url information entered in step 1. Mercurial Repository. If the user wishes to
modify them at this stage they can.
The paths will be stored in the <cloned project>/.hg/hgrc file and available from the Mercurial -> Properties menu for
this cloned project.
Agree. This give users more control, seems like a better design.
Created attachment 56613 [details]
Created attachment 56614 [details]
Created new Wizard step as described (see screenshot), Mercurial Paths, allows user to set default push and default pull
paths during Clone Other.
I am not validating the paths as its hard to tell what I should validate them against, they could be remote URI's, but
they could just as easily be local file paths to a local repo. If they mess up the paths subsequent actions on the repo
might fail, but the user will be told and they can always adjust the paths using the Mercurial->Properties dialog.
date: Wed Feb 13 15:23:29 2008 +0000
#126357: Clone Other - add support to specify the default push and pull paths as another Wizard step, defaults to