[OE-core] Unable to push to the repository?

Koen Kooi koen at dominion.thruhere.net
Mon May 23 15:02:08 UTC 2011


Op 23 mei 2011, om 17:01 heeft Cliff Brake het volgende geschreven:

> On Mon, May 23, 2011 at 10:43 AM, Richard Purdie
> <richard.purdie at linuxfoundation.org> wrote:
>> On Sat, 2011-05-07 at 09:51 +0100, Richard Purdie wrote:
>>> On Sat, 2011-05-07 at 01:37 -0700, Khem Raj wrote:
>>>> On Sat, May 7, 2011 at 1:24 AM, Richard Purdie
>>>> <richard.purdie at linuxfoundation.org> wrote:
>>>>> On Sat, 2011-05-07 at 01:21 -0700, Khem Raj wrote:
>>>>>> On Sat, May 7, 2011 at 1:13 AM, Khem Raj <raj.khem at gmail.com> wrote:
>>>>>>> On Sat, May 7, 2011 at 1:08 AM, Richard Purdie
>>>>>>> <richard.purdie at linuxfoundation.org> wrote:
>>>>>>>> Hi,
>>>>>>>> 
>>>>>>>> It seems something on the server was broken and I'm unable to push to the repository:
>>>>>>>> 
>>>>>>>> $ git push origin master:master
>>>>>>>> Counting objects: 9, done.
>>>>>>>> Delta compression using up to 2 threads.
>>>>>>>> Compressing objects: 100% (5/5), done.
>>>>>>>> Writing objects: 100% (5/5), 490 bytes, done.
>>>>>>>> Total 5 (delta 4), reused 0 (delta 0)
>>>>>>>> remote: sed: can't read ./description: No such file or directory
>>>>>>>> remote: *** Project description file hasn't been set
>>>>>>>> remote: error: hook declined to update refs/heads/master
>>>>>>>> To ssh://git@git.openembedded.org/openembedded-core
>>>>>>>>  ! [remote rejected] master -> master (hook declined)
>>>>>>>> error: failed to push some refs to 'ssh://git@git.openembedded.org/openembedded-core'
>>>>>>>> 
>>>>>>>> Any ideas what's wrong?
>>>>>>> 
>>>>>>> hmmm I added ml hooks but they are same as classic oe so it should
>>>>>>> have worked but let me see.
>>>>>> 
>>>>>> OK I think I used wrong repo name probably that was it. Please retry
>>>>>> and see if it works
>>>>> 
>>>>> No, still the same error :(
>>>> 
>>>> one more time. Now I have added description files.
>>> 
>>> It worked this time, thanks.
>> 
>> and its broken again once more :(
> 
> Its fixed now.  The root cause has also been fixed, so I don't expect
> this to be a problem in the future.

Out of curiosity, what was the root cause? 



More information about the Openembedded-core mailing list