code-google-com / editra-plugins

Automatically exported from code.google.com/p/editra-plugins
0 stars 0 forks source link

Project Plugin / hg repo issue #108

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Project Plugin has problems with hg 1.1.1 Repos since there is a
backward-incompatible change, 
this issue renderes the source control(hg) of Editra unusable (no crash though)

Editra log msg: "abort: requirement 'fncache' not supported!"
also see: http://www.selenic.com/mercurial/wiki/fncacheRepoFormat

Reproduce:
download newest HG, create repo, add some files, try to import in Editra
Project Plugin

Patrik

Original issue reported on code.google.com by patrik.p...@gmail.com on 22 May 2009 at 8:38

GoogleCodeExporter commented 9 years ago
Hello,

From the error message that you are showning and its description in the 
document you
linked to it would seem that there is another pre 1.1 version of Mercurial on 
your
path that is getting called instead of the new one you installed. By default the
Projects plugin just calls 'hg' so whatever one is first your path is what will 
be
executed.

You should set the hg path in the Projects configuration to explicitly point to 
the
new one if it is not the default one on your path.

Let me know if this is the case so I can close this as invalid.

NOTE: in the latest version of the projects plugin there is a bug in preferences
saving, that may prevent you from saving your settings after closing Editra. I 
will
be putting out a new version this weekend to correct this issue.

Original comment by CodyPrec...@gmail.com on 22 May 2009 at 9:26

GoogleCodeExporter commented 9 years ago
Assuming that my assumption is correct for now and that this is invalid.

If you have further issues don't hesitate to ask or reopen this issue.

Cody

Original comment by CodyPrec...@gmail.com on 26 May 2009 at 8:44

GoogleCodeExporter commented 9 years ago
Sry, I have this bug only in windows@work so I couldn't check lately. 

You are correct, this bug was directly related to Mercurial though I didn't 
have 2
versions installed. Recreating/initing the repo solved the issue.

Thanks

Original comment by patrik.p...@gmail.com on 27 May 2009 at 10:18