I'm on linux ubuntu 14.04 lts and I use Mercurial Distributed SCM (version 3.3.2). I try to unbundle a mercurial hg bundle made on Mac osx with command line:
hg unbundle XXX.hg
abort: XXX.hg: unknown bundle version 20
Does anyone have a clue what is going on? Google research has not been providing much informations about that.
I had to add type='bzip2-v1' to the bundle call
from mercurial.commands import bundle
bundle(ui, repo, tmpfile.name, dest=None, base=(parentc.rev(),), rev=(c.rev(),), type='bzip2-v1')
It looks like mercurial introduced a new version of their bundle module somewhere around 3.2, according to:
https://hglabhq.com/blog/2014/4/29/what-s-new-in-mercurial-3-0
Your version should have support for bundle2, but there may be some problems unbundling from newer versions of mercurial.
Related
I'm getting this error when i try to run apache:
./httpd: error while loading shared libraries: libpcre.so.0: cannot open shared object file: No such file or directory
when i do a search for the lib i receive this:
/usr/lib/libpcre.so.1
/usr/lib/libpcre.so.1.2.1
/usr/lib/libpcre16.so.0
/usr/lib/libpcre16.so.0.2.1
/usr/lib/libpcre32.so.0
/usr/lib/libpcre32.so.0.0.1
/usr/lib/libpcrecpp.so.0
/usr/lib/libpcrecpp.so.0.0.0
/usr/lib/libpcreposix.so.0
/usr/lib/libpcreposix.so.0.0.2
/usr/lib64/libpcre.so.1
/usr/lib64/libpcre.so.1.2.1
/usr/lib64/libpcre16.so.0
/usr/lib64/libpcre16.so.0.2.1
/usr/lib64/libpcre32.so.0
/usr/lib64/libpcre32.so.0.0.1
/usr/lib64/libpcrecpp.so.0
/usr/lib64/libpcrecpp.so.0.0.0
/usr/lib64/libpcreposix.so.0
/usr/lib64/libpcreposix.so.0.0.2
I tried to upgrade my pcre, to get the so.0 :
Package pcre-8.33-11.fc20.x86_64 already installed and latest version
Nothing to do
I'm out of ideas, hope someone can help.
This error is occurring because the version of Apache that is currently installed was built against an older version of pcre.
First upgrade Apache to the latest version in the Fedora repositories. The latest version should have been built against the newer pcre shared object.
If you can't, or won't upgrade Apache, you can downgrade the pcre package to the first version that contains libpcre.so.0, which is 7.8 I think.
If you need a quick fix and aren't using this web server for anything too serious you may be able to make it work by sym-linking libpcre.so.0 to libpcre.so.1.
lastly, you could rebuild Apache manually, which should use the pcre that is currently installed.
I want to add Doxygen plugin to QtCreator.
I am using QtCreator 2.5.2 in ubuntu 12.10 and the latest Doxygen version for QT is 2.4.0.
I've changed the doxygen.pluginspec file to get rid of version error.
But now I've got another error:
can not load library libdoxygen.so (libQtconcurrent.so can not open shared object file:No such file or directory)
Any suggestion would be appreciated.
I hope you are no longer stuck, but if not, I will still try to help.
Yes, the quick install binaries are available only for QtCreator 2.4, but the plugin stays easy to install without it : you have to download the sources and build them yourself, as written in the wiki.
Moreover, you have to build it with the same version of Qt4 as the one that was used for build your QtCreator (have a look here)
It became compatible with QtCreator 2.7 and Qt5 at the end of March, and I succeeded in installing in in QtCreator2.8-beta.
If you have any other question, I guess it would be better to ask them in the plugin forum where developpers always answer to people in need.
Hope this helps (you and other people in need).
You can install Doxywizard wich provides an user interface to use Doxygen.
I'm not shure I'm using fedora to install I used.
yum install doxygen-doxywizard.x86_64.
For Ubuntu it should be if the package name is the same.
apt-get install doxygen-doxywizard.x86_64
(as root)
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.
I have tried installing Groovy plugin via STS's dashboard install feature in both 2.7 (the version I downloaded initially which was the latest version at the time). My colleague recommended downloading 2.5.2, the version he is using, so I did; however the Groovy plugin installer still fails. It starts with:
Cannot complete the install because of a conflicting dependency.
Software being installed: Groovy-Eclipse Feature 2.5.2.xx-20110808-1400-e36 (org.codehaus.groovy.eclipse.feature.feature.group 2.5.2.xx-20110808-1400-e36)
Windows 7 64B
groovy v 1.8.2
grails v 1.3.7
jvm 1.6.0_26
Greatly appreciate any hints/recommendations/ideas. THANK YOU!
Make sure that your STS install is in a directory where the current user has write permissions. Also, there is a problem with installing into the Program Files directory (it is not really writable, even if you think it is).
The reason for this problem is the feature patch that comes with Groovy-Eclipse must be installed into the same directory as the rest of STS (an Eclipse limitation). This patch is the thing that patches the jdt compiler so that it can also compile groovy code.
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.