Thanks for the hint - that may be due to the fact that mercurial as
package only comes via a repository dating back to SLES 11 SP1 - there
seems to be no newer one. I just looked up the version: instead of
current v2.6.2 it's v1.0.2 (!)
On the other hand I'm glad that this reads like it does not
On Tue, Jun 18, 2013 at 10:54 AM, Sebastian Schaaf <
sch...@ibe.med.uni-muenchen.de> wrote:
> Thus, the cloning process as the LDAP user (did not want to store the
> foreign username/password explicitly in the galaxy user files) worked,
> although I get this message:
> "*** failed to import extens
Hi Saket,
First of all thanks a lot for your really quick reply. To sum it up: you
were right.
After ensuring the SSH out (works) your comments led me to the idea to
test the 'hg clone' command with a user account, which is neither root
nor galaxy. These two are local users, while my persona
You might want to ssh out and check if that is allowed. If you can ssh out,
you should be able to clone from bitbucket ssh too [ Though you might not
be able to push, depending on whether or not you own the repository]
On 18 June 2013 19:59, Saket Choudhary wrote:
> Hi Sebastian,
>
>
> I work b
Hi Sebastian,
I work behind a proxy too(In my case I have to supply a username and
password too )
I have the following thins setup in my ~/.bashrc:
export http_proxy= http://username:password@proxy-url:proxy-port/
then source it:
$ source ~/.bashrc
or maybe relogin .
and the .hgrc settings t
