fatal: Not a git repository

fatal: Not a git repository

[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"
    ...

The same complaint seems to crop up at various points during a build, as 
well.

Suggestions?
Douglas.






=======================================================================
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.
=======================================================================

Re: fatal: Not a git repository

[Vitus Jensen]

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.

Bye,
 Vitus

Re: fatal: Not a git repository

[Mike (mwester)]

Douglas Royds wrote:
> 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"
>    ...
> 
> The same complaint seems to crop up at various points during a build, as
> well.

Yes, I see that as well.  Of course, since I -- at the time -- was
building from a snapshot and not the original git repo, and the build
results seemed quite normal, I gave it no further thought.


> =======================================================================
> 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.
> =======================================================================

I guess I'm not sure that I am the intended addressee.  Can you tell me
if you did, in fact, intend to send the original email to me, in the
legal sense of the definition of "intended addressee"?

In any case, please inform your legal department that I do not accept
apologies from lawyers, and that this email constitutes my notification
of that to your lawyers, that I have deleted all copies -- at least
those copies that _I_ possess; the email notice is rather vague as to
whether I am required to track down all copies that might exist in the
world today -- and I also shall perform no other act on the email.

- Mike (mwester)

P.S.  Neither can I warrant that my response to this email has not been
altered or corrupted during transmission.  And I'll go one better than
your lawyers, and note that you'll never know if my original email was
full of typos -- and that it was actually *corrected* during
transmission.  Poor lawyers...  that sort of disclaimer rather makes the
entire footnote they added there completely ridiculous and pointless,
doesn't it??!

Re: fatal: Not a git repository

[Tom Rini]

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..

-- 
Tom Rini

Re: fatal: Not a git repository

[Douglas Royds]

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.
=======================================================================

Re: fatal: Not a git repository

[pHilipp Zabel]

On Tue, Mar 3, 2009 at 6:54 AM, Douglas Royds <douglas.royds@tait.co.nz> wrote:
> 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

Maybe it should test whether
os.path.join(base_get_scmbasepath(d),'.git') exists before calling out
to git?

regards
Philipp

Re: fatal: Not a git repository

[Yuri Bushmelev]

Hello!

> Douglas Royds wrote:
> > 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"
> >    ...
> >
> > The same complaint seems to crop up at various points during a build,
> > as well.
>
> Yes, I see that as well.  Of course, since I -- at the time -- was
> building from a snapshot and not the original git repo, and the build
> results seemed quite normal, I gave it no further thought.

I have this too.

I think we should add some parameter to conf-files which allows to point 
where is git repository located.

This is useful when publishing build stats to tinderbox.

-- 
Yuri Bushmelev

fatal: Not a git repository

[T]

I am on RedHat Linux Server 5.7, installed git and all worked great.

Performed a "git add ." and sat back and watched it chew up GB fo data and create the .git repository, which I was going to study.  But then I decided to delete the .git repository before the commit, and redo the work after I added additional files to the filesystem.

The git application no longer works.  I have done a complete deletion of all files that I know of and a complete reinstallation and yet every time that I attempt to get git to reread the directory and recreate the repository or ANY repository on the system even while root the error message is:



[root@localhost wizdom]# git add .
fatal: Not a git repository (or any of the parent directories): .git




Any idea on how to fix this problem so that I can get on with using git?

Wizdom is a dir of management information systems related files, 29.4GB in size, containing 264380 files, for systems administration and when git had complete the add command it had create a dir /home/Object/wizdon/.git that was 26.1GB in size and with 212774 files in 256 sub-folders.


============================================
[root@localhost ~]# mkdir /tmp/git_source
[root@localhost ~]# cp /home/Object/Desktop/100511/git/git-1.7.7.tar.gz /tmp/git_source/.
[root@localhost ~]# openssl dgst -sha1 /tmp/git_source/git-1.7.7.tar.gz
SHA1(/tmp/git_source/git-1.7.7.tar.gz)= bbf85bd767ca6b7e9caa1489bb4ba7ec64e0ab35
[root@localhost ~]# cd /tmp/git_source/
[root@localhost git_source]# tar -xzf git-1.7.7.tar.gz
[root@localhost git_source]# ls
git-1.7.7  git-1.7.7.tar.gz
[root@localhost git_source]# ./configure
[root@localhost git-1.7.7]# make
[root@localhost git-1.7.7]# make install
[root@localhost git-1.7.7]# updatedb
[root@localhost git-1.7.7]# which git
/usr/local/bin/git
[root@localhost ~]# ls -al /usr/local/bin/gi*
-rwxr-xr-x 109 root root 5113079 Oct 13 13:14 /usr/local/bin/git
-rwxr-xr-x   2 root root  120939 Oct 13 13:14 /usr/local/bin/git-cvsserver
-rwxr-xr-x   1 root root  324172 Oct 13 13:14 /usr/local/bin/gitk
-rwxr-xr-x 109 root root 5113079 Oct 13 13:14 /usr/local/bin/git-receive-pack
-rwxr-xr-x   2 root root 2144914 Oct 13 13:14 /usr/local/bin/git-shell
-rwxr-xr-x 109 root root 5113079 Oct 13 13:14 /usr/local/bin/git-upload-archive
-rwxr-xr-x   2 root root 2195752 Oct 13 13:14 /usr/local/bin/git-upload-pack



Just to see what it would do, or what it does, I ran git against my systems administration collection called wizdom on a Dell T-410 with one socket in use.


[root@localhost git-1.7.7]# git --version
git version 1.7.7
[root@localhost wizdom]# git init
Initialized empty Git repository in /home/Object/Desktop/wizdom/.git/
[root@localhost wizdom]# git add .
[root@localhost wizdom]#



And in another window while "git add ." ran, I execute the top command to see what the processor had to say:

[root@localhost ~]# top
top - 16:12:43 up 1 day, 21:19,  4 users,  load average: 1.35, 0.73, 0.32
Tasks: 232 total,   2 running, 230 sleeping,   0 stopped,   0 zombie
Cpu0  :  0.0%us,  0.0%sy,  0.0%ni,100.0%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Cpu1  :  0.0%us,  0.0%sy,  0.0%ni,100.0%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Cpu2  :  0.7%us,  0.0%sy,  0.0%ni, 99.3%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Cpu3  :  0.0%us,  2.0%sy,  0.0%ni, 46.7%id, 50.7%wa,  0.3%hi,  0.3%si,  0.0%st
Cpu4  :  0.0%us,  1.0%sy,  0.0%ni, 99.0%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Cpu5  :  0.0%us,  0.0%sy,  0.0%ni,100.0%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Cpu6  :  0.0%us,  0.0%sy,  0.0%ni,100.0%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Cpu7  : 93.7%us,  2.7%sy,  0.0%ni,  3.3%id,  0.3%wa,  0.0%hi,  0.0%si,  0.0%st
Mem:   5968036k total,  5932372k used,    35664k free,   191688k buffers
Swap:  8159224k total,        0k used,  8159224k free,  4938104k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
16250 root      25   0 17344 1428  792 D 96.2  0.0   1:09.41 git-fast-import
16233 root      18   0 44348  29m 1036 S  1.3  0.5   0:53.89 git
...



Thanks!

Re: fatal: Not a git repository

[BlackSwan]

Sorry.... I figured it out, and it was right in front of me.

[root@localhost wizdom]# git init


Thanks all!

--
View this message in context: http://git.661346.n2.nabble.com/fatal-Not-a-git-repository-tp6891065p6891093.html
Sent from the git mailing list archive at Nabble.com.