Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: Tom King <ka6sox@gmail.com>,
	openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: OE-Core repo broken again
Date: Tue, 17 May 2011 18:22:45 +0100	[thread overview]
Message-ID: <1305652965.3424.268.camel@rex> (raw)
In-Reply-To: <BANLkTikgu6bKT603XFgpvK2b0ikroOTZhQ@mail.gmail.com>

On Tue, 2011-05-17 at 09:56 -0700, Khem Raj wrote:
> On Tue, May 17, 2011 at 4:11 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > Hi Guys,
> >
> > Something is broken with the oe-core repository as I can't push to it:
> >
> > $ 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), 628 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'
> >
> >
> 
> its the same error I fixed last time. Somehow the description files in
> repo got lost after melo rebooted. I have put them back
> can you try and confirm if it works now ?

I've confirmed its working again, thanks. I'm hoping this doesn't happen
again...

Richard




      reply	other threads:[~2011-05-17 17:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-17 11:11 OE-Core repo broken again Richard Purdie
2011-05-17 16:56 ` Khem Raj
2011-05-17 17:22   ` Richard Purdie [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1305652965.3424.268.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=ka6sox@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox