From: Douglas Royds <douglas.royds@tait.co.nz>
To: openembedded-devel@lists.openembedded.org
Subject: Re: fatal: Not a git repository
Date: Tue, 03 Mar 2009 18:54:23 +1300 [thread overview]
Message-ID: <49ACC60F.9050808@tait.co.nz> (raw)
In-Reply-To: <20090303021719.GK26343@smtp.west.cox.net>
Tom Rini wrote:
> On Tue, Mar 03, 2009 at 12:12:38AM +0000, Vitus Jensen wrote:
>
>> Am Mon, 02 Mar 2009 16:55:54 +1300 schrieb Douglas Royds:
>>
>>> Anyone else getting this?
>>>
>>> NOTE: Handling BitBake files: / (6587/6587) [100 %] NOTE: Parsing
>>> finished. 6302 cached, 0 parsed, 285 skipped, 0 masked. NOTE: Cache
>>> is clean, not saving.
>>> NOTE: build 200903021645: started
>>> fatal: Not a git repository <----------------------
>>>
>>> OE Build Configuration:
>>> BB_VERSION = "1.8.12"
>>> ...
>>>
>> Yes, it happens on every build. I guess bitbake is testing the current
>> directory via git and would include the current head in the build number.
>>
>>
>>> The same complaint seems to crop up at various points during a build, as
>>> well.
>>>
>>> Suggestions?
>>>
>> Just ignore. Besides called "fatal" it isn't fatal at all.
>>
>
> Well, to git it's fatal :) Someone should dig to where the call is and
> redirect stderr somewhere, I suspect..
>
This silences it, though I'm not sure that it's the right solution:
diff --git a/classes/base.bbclass b/classes/base.bbclass
index 18afc1a..21b08a5 100644
--- a/classes/base.bbclass
+++ b/classes/base.bbclass
@@ -807,7 +807,7 @@ def base_get_metadata_svn_revision(d):
def base_get_metadata_git_branch(d):
import os
- branch = os.popen('cd %s; git branch | grep "^* " | tr -d "* "'
% base_get_scmbasepath(d)).read()
+ branch = os.popen('cd %s; git branch 2>&1 | grep "^* " | tr -d
"* "' % base_get_scmbasepath(d)).read()
if len(branch) != 0:
return branch
=======================================================================
This email, including any attachments, is only for the intended
addressee. It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
altered or corrupted during transmission.
=======================================================================
next prev parent reply other threads:[~2009-03-03 5:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 3:55 fatal: Not a git repository Douglas Royds
2009-03-03 0:12 ` Vitus Jensen
2009-03-03 2:17 ` Tom Rini
2009-03-03 5:54 ` Douglas Royds [this message]
2009-03-03 8:14 ` pHilipp Zabel
2009-03-03 1:28 ` Mike (mwester)
2009-03-03 8:45 ` Yuri Bushmelev
-- strict thread matches above, loose matches on Subject: below --
2011-10-14 1:57 T
2011-10-14 2:14 ` BlackSwan
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=49ACC60F.9050808@tait.co.nz \
--to=douglas.royds@tait.co.nz \
--cc=openembedded-devel@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.