I am running all on virtualbox on fedora 23.
Looks like one of the locator processes stuck.
I killed the process, than start it again and it worked – actually very simple.
But since I had an exception when I ran the locator above I didn’t thought that
although the exception the process remain s
On second thought, since we are close to a release and will be updating the
master soon after, I think it will be good to leave the default branch as
master. So that when somebody clones the repo they are on a stable released
code.
On Mon, Jan 25, 2016 at 10:51 AM, William Markito
wrote:
> If w
I think this has to be done by filing an INFRA ticket:
https://issues.apache.org/jira/browse/INFRA-9208
https://issues.apache.org/jira/browse/INFRA-7659
Anthony
> On Jan 25, 2016, at 10:41 AM, Swapnil Bawaskar wrote:
>
> Yes, the default branch can be changed by following instructions here:
If we want to change that someone needs to open a ticket with ASF infra.
Sent from my iPhone
> On Jan 25, 2016, at 10:41 AM, Swapnil Bawaskar wrote:
>
> Yes, the default branch can be changed by following instructions here:
> https://help.github.com/articles/setting-the-default-branch/
> I
Yes, the default branch can be changed by following instructions here:
https://help.github.com/articles/setting-the-default-branch/
I think it is enough to change this only on github, since we do not point
users to ASF.
I don't have permissions to change this, Anthony/Roman can either of you
pleas
Is it possible to set the default branch to develop? That will save a lot of
head-scratching, though once we have a regular release cadence going it won’t
be as much of an issue.
Anthony
> On Jan 25, 2016, at 8:38 AM, Joseph Winston
> wrote:
>
> Jinmei —
>
> It appears that the issue that
Jinmei —
It appears that the issue that I was running into is that I was on the branch
master and not develop.
Thanks
Hi, Joseph, please pull from the develop branch. The master branch is very
outdated. Thanks!
On Mon, Jan 25, 2016 at 7:22 AM, Joseph Winston
wrote:
> Jinmei —
>
> I’m using master with the last commit:
>
> == Most Recent Commit
> commit 6902465937cd9619cf71cc647bdbfe80f5ae71a4
> Author: Kirk Lun
Jinmei —
I’m using master with the last commit:
== Most Recent Commit
commit 6902465937cd9619cf71cc647bdbfe80f5ae71a4
Author: Kirk Lund mailto:kl...@pivotal.io>>
Date: Tue Jul 7 11:57:17 2015 -0700
Closes #3 *Already completed*
That's good news! What did you have to do to get it to work?
--Jens
On Mon, Jan 25, 2016 at 6:05 AM, Dor Ben Dov wrote:
> Yes ,
>
> I succeeded to run both locator service with the default parameters as
> well as the server.
>
>
>
> Dor
>
>
>
> *From:* Jens Deppe [mailto:jde...@pivotal.io]
> *S
Yes ,
I succeeded to run both locator service with the default parameters as well as
the server.
Dor
From: Jens Deppe [mailto:jde...@pivotal.io]
Sent: יום ב 25 ינואר 2016 15:56
To: user@geode.incubator.apache.org
Subject: Re: failed building the latest version downloaded from github
Hello Dor,
Hello Dor,
Were you able to get this working correctly? If not can you also send the
locator log which is created (even though the locator does not appear to
start correctly).
I was never able to reproduce this in the same way you had it failing. I
tried in both a Fedora 23 Docker container as we
12 matches
Mail list logo
