I am trying to get Mercurial to be hosted via "hgweb.cgi" on IIS 7.5. I have everything configured according to http://www.jeremyskinner.co.uk/mercurial-on-iis7/ except for that I installed python 2.6 and Mercurial 1.7.3. When I try to go to the hgweb.cgi script, I get the following error:
"No module named osutil"
After a bit of searching, I've found that I need to install the python-dev packages, but that seems to only apply to unix. Is there anything else I need to get this working on windows?
Thanks.
Note that I tried the mercurial binaries/library.zip on both both HgTortoise and the Mercurial x86 installer available here:
https://www.mercurial-scm.org/downloads
(Mercurial 1.7.3 Inno Setup installer - x86 Windows - does not require admin rights)
I had the same issue trying to re-create an HgWeb server with Mercurial 2.1.1. I posted a question on the Mercurial mailing list.
Because HgWeb requires Python, you have to get Mercurial as a Python module. Fortunately, the Mercurial folks supply one; it's tagged py2.6 with the description
installs Mercurial source as Python modules and thus requires Python 2.6 installed. This is recommended for hgweb setups
Once I ran that installer, HgWeb started working.
Looking at the available downloads and the version specified in the question, it looks like you might have installed TortoiseHg 1.1.8 with Mercurial 1.7.3, which is probably missing some python packages.
I've been researching this problem myself (except I'm trying to run Mercurial via ISAPI), and it appears 1.7.1 is the last version that works with IIS due to dependency problems with msvcr90.dll in all later versions, including the newly released 1.8.2.
See this issue, which ultimately seems to be caused by this still open 1-year-old Python issue.
Judging by the conversation, a fix is not easy. I know of no workarounds, so I am forced to use 1.7.1 in the meantime.
Edit: CGI works with 1.8.2 though, so the above issue seems to only affect running Mercurial through ISAPI.
Related
I have a Linux Mint VM, where I installed formerly NetBeans 12.x (up to 12.6) and now I've updated it to 13.0, all with flatpak, and even starting from a clean setup.
With all those setups, NetBeans can't find Mercurial, even if I really have it in /usr/bin/hg available and working (when used from the shell).
From menu Team / Mercurial / Initialize repository... I get the error "Mercurial could not be found", asking to check PATH.
The strange behavior is that if I even browse for Options and Mercurial Executable Path to /usr/bin I can't see hg in there, while it is in the filesystem!
Is NB browsing somewhere else when I open /usr/bin?
Is it accessing some virtual environment? I'm confused
I have a partial solution: the flatpak package is indeed at fail, as for some reason it's not seeing my /usr/bin but a virtualized (?) directory, where many files are missing - notably hg and hg-ssh
So I removed the package suggested by the Linux Mint Software Manager and installed the package got from the Apache NetBeans site, similarly to what #flied-onion did.
What's still missing is that NetBeans relies on the hgk application as an hg GUI interface for some functions (see Team / View). This is unknown to me, and I don't find it in any (recent) Debian flavor.
I am trying to run a code which uses feeder (feedr on git repository) library. I am getting error while installing it. I have tried pip, cloning git, and previous versions but still getting same error on all PC. Please tell how to solve it or any alternative for feeder. Original code link is https://github.com/nashory/DeLF-pytorch/tree/master/notebook enter image description here
feedr uses infi.docopt_completion==0.2.1 which in turn uses distribute which is so old (last release in 2013) that it could hardly be installed in modern Python. I failed to install it in Python 2.7.
In short: the project feedr is old, outdated and abandoned. Forget about it. Or try to update in manually to use newer versions of dependencies. You can send pull request(s) to the author.
I have a RHEL system which by default was running Python2.7 and Python3.4
I needed Python3.6 for a project I wanted to work on and so I downloaded it and built it from source. I ran make and make install which hindsight may have been the wrong decision.
Now I do not seem to have any internet connectivity. Does anyone know what I may have over written to cause this or at least where specifically I can look to track this issue down?
Note: I can Putty into the Linux machine but it doesn't seem to have any other connectivity, specifically HTTPS
It's a bit weird that this would break network connectivity. One possible explanation is that the system has networking scripts or a network manager that relies on Python, and it got broken after make install replaced your default Python installation. It may be possible to fix this by reinstalling your RHEL Python packages (sorry, cannot offer more detailed help there, as I don't have access to a RHEL box).
I guess the lesson is "be careful about running make install as superuser". To easily install and manage different Python versions (separate from the system Python), the Anaconda Python distribution would be a good solution.
I suggest to undo that 3.6 installation and use the Software Collections version of python 3.6. See here for python 3.6 installation. Software Collections install "along side" the original versions so as to not affect the OS - and they are included in the subscription.
So after a lot of time slamming my head against the wall I got it worked out. My best guess is that the system (RHEL 7) relied on something from its default Python2.7 installation to handle SSL negotiations. Installing 3.6 alongside must have overwritten some pointer. Had I done this correctly, with altinstall all would have likely been fine.
The most frustrating part of this is that there were no error messages, connections just timed out.
To fix this, I had to uninstall all Python versions and then reinstalled Python2.7 - Once Python2 was back in the system it all seemed to work well.
I'm having a problem with Subclipse, when trying to do anything like committing, updating or viewing history the first time nothing happens, and the second time I try this error show up:
All this used to work just fine but suddenly it stopped working. All the required packages are installed:
The "SVN interface" option in the preferences is empty/greyed out:
I have another Eclipse installation (Java EE) which has the same packages installed and everything is still working fine there.
I've already tried reinstalling all the SVN packages but to no avail. I'm running Eclipse Kepler on Linux Mint 16 Petra, SVN is version 1.7.9.
Any help would be greatly appreciated.
EDIT: I figured out that the other Eclipse installation had different (older) versions of the plugins. After updating these, that installation also stopped working. I suspect that my SVN version (1.7.9) is too old. I see 1.8.x has already been released, how can I install that version in my Linux installation? Running apt-get update/upgrade doesn't do it. I've seen some people talking about running dist-upgrade but that has broken things in the past so I'm very reluctant to do so unless absolutely necessary.
EDIT: I managed to install subversion 1.8.10 using these steps, but to no avail.
I managed to solve the issue my removing SVNKit and installing the "Subversion JavaHL Native Library Adapter" instead. I tried that before but it did work after I had also updated subversion to 1.8.
This might be more of a CYGWIN question than a Nodejs but here goes.
I installed Cygwin yesterday and on the packages selection I just clicked next as it looked like most were pre-selected, and then today read this guide http://boxysystems.com/index.php/step-by-step-instructions-to-install-nodejs-on-windows/ on installing nodejs.
The ./configure had an error that it was unable to remap python lib-dynload/itertools.dll to same address as parent. As the process still completed I tried the make command, but it fails on the same error.
So, I opened cygwin setup.exe and this time I clicked the source checkbox for all the Python packages. But still get the same error. Should I now go to Cygwin and check all the source packages for the Make packages, delete it and reinstall from scratch using the above guide. Or something else?
Any help gratefull received/
Use the official 0.5.x windows build from http://nodejs.org/#download - you just have to download a .exe file and you can start it.
Versions 0.5.X have problems with Cygwin and because of developing clean Windows version Cygwin environment is now unsupported. Stable version 0.4.12 builds on Cygwin with no problems. If you want to use node.js unstable 0.5.X branch on Windows use windows build at official node.js site.
check this out:
https://github.com/joyent/node/wiki/Building-node.js-on-Cygwin-(Windows)
Update Sept 1, 2011 -- as of today, v0.5.5 does not build on Cygwin (errors on make). Use v.0.5.4 (ie. follow instructions below and use "git checkout v0.5.4".
https://github.com/joyent/node/wiki/API-changes-between-v0.4-and-v0.6
Cygwin build is no longer supported. Use native windows builds instead.