#10081 closed defect (worksforme)
mercurial-plugin does no work with mercurial 1.8
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | plugin/mercurial | Version: | 0.12.2 |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
The Browse source
link does not appear in the main navigation if the mercurial 1.8 binary is used, and trac displays the following warning on every page:
Warning: Can't synchronize with repository "(default)" (Unsupported version control system "hg": Can't find an appropriate component, maybe the corresponding plugin was not enabled? ). Look in the Trac log for more information.
The log file doesn't say anything relevant as far as I can see.
Everything works fine if the mercurial 1.7.1 binary is used.
To replicate on Windows XP Pro SP3 32-bit:
- Install Python 2.6.6
- Install setuptools 0.6c11
- easy_install genshi (0.6)
- Install trac 0.12.2
- Install mercurial 1.8 Python 2.6.2 bindings (Python 2.6.6 bindings are not available)
- Edit trac.ini.
- Run tracd from the command line.
Attachments (0)
Change History (12)
comment:1 by , 14 years ago
Milestone: | → plugin - mercurial |
---|
follow-up: 3 comment:2 by , 14 years ago
I haven't got a C compiler and haven't tried installing as pure Python (yet).
After further testing, I found that mercurial 1.7.5 doesn't work either.
If you ask for any tests on this ticket, I'll do what I can.
comment:3 by , 14 years ago
Replying to blokeley@…:
After further testing, I found that mercurial 1.7.5 doesn't work either.
So this must be either a Windows-specific issue, or an issue with the Mercurial installer. It works for me with Mercurial 1.7.5 on Linux.
comment:4 by , 14 years ago
Works for me, Python 2.6.5 (x86) on Windows 7, using the Mercurial installer from the link provided above (mercurial-1.8.win32-py2.6.exe).
Please try to see what happens when you use the Mercurial API from the command line.
Besides, which version of the TracMercurial plugin are you using?
comment:5 by , 14 years ago
At least one other person has experienced the same problem. I'll try the API from the command line today.
comment:6 by , 14 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Chances are that you simply miss the msvc9 redist package.
In any case, this is an InstallationIssue.
comment:7 by , 14 years ago
Milestone: | plugin - mercurial |
---|
follow-up: 10 comment:8 by , 14 years ago
For the record:
- Problem also exists with mercurial 1.8.1.
- The msvc9 redist package was already installed. Re-installing has no effect.
- Accessing mercurial from the python command line works fine on all versions.
@cboos: which mercurial installer did you use in comment:4? All versions after 1.7.1 don't work for me and some other people.
This seems to be a genuine bug and I would help if pointed in the right direction.
comment:10 by , 14 years ago
Replying to blokeley@…:
For the record:
- Problem also exists with mercurial 1.8.1.
- The msvc9 redist package was already installed. Re-installing has no effect.
- Accessing mercurial from the python command line works fine on all versions.
@cboos: which mercurial installer did you use in comment:4? All versions after 1.7.1 don't work for me and some other people.
The 1.8 one you used in the first place (comment:4 updated). I just tried now with 1.7.1 then with 1.8.1, and they both work fine for me (and in each case I see the expected version of Mercurial in /about).
This seems to be a genuine bug and I would help if pointed in the right direction.
Try following the same advices I gave for Subversion troubleshooting on windows, in TracSubversion#checklist-windows, but for the server. The fact that it works on the command line but not for tracd.exe
is a bit puzzling, as I don't do anything fancy in the plugin. Possibly the Python interpreter involved in either situation is not the same.
follow-up: 12 comment:11 by , 14 years ago
I installed mercurial from source: 1.7.5 works, 1.8.4 fails. Same behaviour for tracmercurial 0.12.0.27
System Information
Trac 0.12.2 FullBlog 0.1.1 Genshi 0.6 Mercurial 1.7.5 mod_wsgi 3.3 (WSGIProcessGroup WSGIApplicationGroup %{GLOBAL}) psycopg2 2.4.1 Python 2.7.2 (default, Jun 12 2011, 15:08:59) [MSC v.1500 32 bit (Intel)] pytz 2011g setuptools 0.6c11 Subversion 1.6.15 (r1038135) jQuery: 1.4.2
Installed Plugins
tick N/A d:\home\web\trac\scm\plugins\tick.pyc tracaccountmanager 0.3dev-r10294 c:\apps\python27\lib\site-packages\tracaccountmanager-0.3dev_r10294-py2.7.egg tracdiscussion 0.8 c:\apps\python27\lib\site-packages\tracdiscussion-0.8-py2.7.egg tracdownloads 0.3 c:\apps\python27\lib\site-packages\tracdownloads-0.3-py2.7.egg tracfullblogplugin 0.1.1 c:\apps\python27\lib\site-packages\tracfullblogplugin-0.1.1-py2.7.egg trachttpauth 1.1 c:\apps\python27\lib\site-packages\trachttpauth-1.1-py2.7.egg tracloginrequiredplugin 0.1.0 c:\apps\python27\lib\site-packages\tracloginrequiredplugin-0.1.0-py2.7.egg tracmercurial 0.12.0.28dev-r10698 c:\apps\python27\lib\site-packages\tracmercurial-0.12.0.28dev_r10698-py2.7.egg tractags 0.6 c:\apps\python27\lib\site-packages\tractags-0.6-py2.7.egg tractocmacro 11.0.0.3 c:\apps\python27\lib\site-packages\tractocmacro-11.0.0.3-py2.7.egg
comment:12 by , 14 years ago
Replying to baloand@…:
I installed mercurial from source: 1.7.5 works, 1.8.4 fails.
Fails how? For which operation? What's in the Trac log?
I just tested Trac 0.12-stable with Mercurial 1.8.4 and TracMercurial 0.12.0.28dev-r10698 and couldn't trigger an error.
I haven't had a chance to test 1.8 yet. Thanks for the heads-up!
Do you happen to know if this is only an issue with the binary installer, or if it also happens when installing from source?