I think I am tired or something, `make stagedevrel` produces an error:

$ make stagedevrel
mkdir -p dev
(cd rel && ../rebar generate target_dir=../dev/dev1
overlay_vars=vars/dev1_vars.config)
==> rel (generate)
ERROR: Release target directory
"/Users/jeremiah/Projects/riak/rel/../dev/dev1" already exists!
make: *** [dev1] Error 1

---
Jeremiah Peschka
Managing Director, Brent Ozar PLF, LLC


On Wed, Feb 15, 2012 at 10:42 PM, Jeremiah Peschka <
jeremiah.pesc...@gmail.com> wrote:

> Thanks!
>
> I assume, too, that since riak control is now a requirement I should do
> `make deps`, `make all`, `make stagedevrel` ?
>
> ---
> Jeremiah Peschka
> Managing Director, Brent Ozar PLF, LLC
>
>
> On Wed, Feb 15, 2012 at 10:31 PM, Sean Cribbs <s...@basho.com> wrote:
>
>> Jeremiah,
>>
>> `make stagedevrel` is what you want.
>>
>> On Thu, Feb 16, 2012 at 1:23 AM, Jeremiah Peschka <
>> jeremiah.pesc...@gmail.com> wrote:
>>
>>> Let's say that I have a copy of the riak 1.0.0 source in
>>> ~/src/basho/riak and that I've built a local 4 node clustering using `make
>>> devrel`. I've gone through and made some configuration changes for working
>>> on the .NET client. Now that 1.1 is out, I'd like to test the 1.1 branch
>>> against my current client code.
>>>
>>> Is there a way to rebuild my 4 node cluster without wiping out my
>>> configuration?
>>>
>>> I spoke with Ryan about this at Surge and he showed me a trick, but I
>>> can't recall how to get this working. Any help would be appreciated.
>>> ---
>>> Jeremiah Peschka
>>> Managing Director, Brent Ozar PLF, LLC
>>>
>>> _______________________________________________
>>> riak-users mailing list
>>> riak-users@lists.basho.com
>>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>>>
>>>
>>
>>
>> --
>> Sean Cribbs <s...@basho.com>
>> Software Engineer
>> Basho Technologies, Inc.
>> http://basho.com/
>>
>>
>
_______________________________________________
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Reply via email to