www-infrastructure-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Geoffrey Corey <cor...@apache.org>
Subject Re: apache brooklyn projects -- set default github branch "master" on "brooklyn" and "brooklyn-docs" ?
Date Mon, 01 Feb 2016 18:16:25 GMT
I have fixed the above github mirrors to have master as the default branch.

On Mon, Feb 1, 2016 at 10:11 AM, Alex Heneveld <
alex.heneveld@cloudsoftcorp.com> wrote:

>
> Geoff/All-
>
> Two of our github mirrors have "0.4.0" as the default branch.  Can these
> be repointed to "master" branch?
>
> The two repos are:
>
> * https://github.com/apache/brooklyn
> * https://github.com/apache/brooklyn-docs
>
>
> Probably this is because I pushed in alpha order and the synch process
> kicked in before master got uploaded.  The others seem to have picked up
> "master".  (Still waiting on "brooklyn-ui" and "brooklyn-client" to synch
> but all branches are pushed to apache's git server.)
>
> Thanks again for the help.
>
> Best
> Alex
>
>
> On 01/02/2016 16:44, Geoffrey Corey wrote:
>
> Alex: You are in the brookly PMC ldap group, but not in the brooklyn ldap
> group.
>
> Please see http://www.apache.org/dev/pmc.html#karma for how to get
> yourself in the brooklyn ldap group. Note: this must be run from
> people.apache.org
>
> On Mon, Feb 1, 2016 at 8:31 AM, Alex Heneveld <
> alex.heneveld@cloudsoftcorp.com> wrote:
>
>>
>> heneveld
>>
>> Thanks
>> --A
>>
>>
>> On 01/02/2016 16:00, Geoffrey Corey wrote:
>>
>> Alex,
>>
>> What is your asf username? The above error is indicating that you might
>> not be in the Brooklyn ldap group (and yes, if you are in the Brooklyn PMC
>> ldap group, you must be in the Brooklyn ldap group as well for commits to
>> work).
>>
>>
>>
>> On Sun, Jan 31, 2016 at 9:02 AM, Hadrian Zbarcea < <hzbarcea@gmail.com>
>> hzbarcea@gmail.com> wrote:
>>
>>> Hi Alex,
>>>
>>> Repositories are created via automated scrips and access is controlled
>>> via groups, afaik. This should have nothing to do with the incubator repo
>>> (and I hope I am not wrong). We'll get this sorted out asap, no worries.
>>>
>>> Hadrian
>>>
>>>
>>> On 01/31/2016 07:33 AM, Alex Heneveld wrote:
>>>
>>>>
>>>> *Infra-*  We are ready to close the old incubating-brooklyn repository
>>>> and get write permission to the new one.
>>>>
>>>> *All-*  I don't seem to have permissions to write to the new repos
>>>> (brooklyn*.git, 6 in total).  Maybe this is awaiting incubator-brooklyn
>>>> being closed?
>>>>
>>>> I have the split-projects ready to go, with history and branches. You
>>>> can see examples in   ahgittin/brooklyn* .
>>>>
>>>> The error I get is:
>>>>
>>>> % git remote add apache-git
>>>> https://git-wip-us.apache.org/repos/asf/brooklyn.git
>>>> % get fetch apache-git
>>>> % git push apache-git master:master
>>>> ...
>>>> *remote: You are not authorized to edit this repository.*
>>>> remote:
>>>> To https://git-wip-us.apache.org/repos/asf/brooklyn.git
>>>>   ! [remote rejected] 0.4.0 -> 0.4.0 (pre-receive hook declined)
>>>> error: failed to push some refs to
>>>> 'https://git-wip-us.apache.org/repos/asf/brooklyn.git'
>>>>
>>>> Thanks
>>>> Alex
>>>>
>>>>
>>
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message