linux fatal: cannot describe <sha1>

linux fatal: cannot describe <sha1>

[Jan Engelhardt]

Hi,


Just a note that when you run git-describe, you should probably quiten it.

fatal: cannot describe 'bd7364a0fd5a4a2878fe4a224be1b142a4e6698e'

This happens when tags are not present, which can happen if Linus's tree 
is sent upwards again, IOW:

 machine1$  git-clone torvalds/linux-2.6.git
 machine1$  git push elsewhere master

 machine2$  git-clone elsewhere:/linux
 machine2$  git-describe HEAD
 fatal: cannot describe that

Re: linux fatal: cannot describe <sha1>

[Sam Ravnborg]

On Tue, Jul 01, 2008 at 06:20:17PM +0200, Jan Engelhardt wrote:
> Hi,
> 
> 
> Just a note that when you run git-describe, you should probably quiten it.
> 
> fatal: cannot describe 'bd7364a0fd5a4a2878fe4a224be1b142a4e6698e'
> 
> This happens when tags are not present, which can happen if Linus's tree 
> is sent upwards again, IOW:
> 
>  machine1$  git-clone torvalds/linux-2.6.git
>  machine1$  git push elsewhere master
> 
>  machine2$  git-clone elsewhere:/linux
>  machine2$  git-describe HEAD
>  fatal: cannot describe that

Hi Jan.

Any specific reason why you sent it to me?
Maybe because I do not use git describe at all?

	Sam

Re: linux fatal: cannot describe <sha1>

[Sebastian Siewior]

* Sam Ravnborg | 2008-07-01 22:09:51 [+0200]:

>> Just a note that when you run git-describe, you should probably quiten it.
>> 
>> fatal: cannot describe 'bd7364a0fd5a4a2878fe4a224be1b142a4e6698e'
>> 
>> This happens when tags are not present, which can happen if Linus's tree 
>> is sent upwards again, IOW:
>> 
>>  machine1$  git-clone torvalds/linux-2.6.git
>>  machine1$  git push elsewhere master
>> 
>>  machine2$  git-clone elsewhere:/linux
>>  machine2$  git-describe HEAD
>>  fatal: cannot describe that
>
>Hi Jan.
>
>Any specific reason why you sent it to me?
>Maybe because I do not use git describe at all?
Maybe he was thinking about this (and didn't know that you were moving):

---
scripts: don't desribe if there is nothing to describe

Signed-off-by: Sebastian Siewior <sebastian@breakpoint.cc>
---
 scripts/setlocalversion |    4 +++-
 1 files changed, 3 insertions(+), 1 deletions(-)

diff --git a/scripts/setlocalversion b/scripts/setlocalversion
index 1c1bdaf..83b7512 100755
--- a/scripts/setlocalversion
+++ b/scripts/setlocalversion
@@ -12,7 +12,9 @@ cd "${1:-.}" || usage
 if head=`git rev-parse --verify HEAD 2>/dev/null`; then
 	# Do we have an untagged version?
 	if git name-rev --tags HEAD | grep -E '^HEAD[[:space:]]+(.*~[0-9]*|undefined)$' > /dev/null; then
-	        git describe | awk -F- '{printf("-%05d-%s", $(NF-1),$(NF))}'
+		if tag=`git describe 2>/dev/null`; then
+			echo $tag | awk -F- '{printf("-%05d-%s", $(NF-1),$(NF))}'
+		fi
 	fi
 
 	# Are there uncommitted changes?
-- 
1.5.5.4

Re: linux fatal: cannot describe <sha1>

[Jan Engelhardt]

On Wednesday 2008-07-02 00:18, Sebastian Siewior wrote:
>* Sam Ravnborg | 2008-07-01 22:09:51 [+0200]:
>
>>> Just a note that when you run git-describe, you should probably quiten it.
>>> 
>>> fatal: cannot describe 'bd7364a0fd5a4a2878fe4a224be1b142a4e6698e'
>>> 
>>
>>Hi Jan.
>>
>>Any specific reason why you sent it to me?

You are the buildsystem maintainer :)

>Maybe he was thinking about this (and didn't know that you were moving):

I only took note of that briefly. Should there have been someone
else to send it to?

>---
>scripts: don't desribe if there is nothing to describe
>diff --git a/scripts/setlocalversion b/scripts/setlocalversion
>index 1c1bdaf..83b7512 100755
>--- a/scripts/setlocalversion
>+++ b/scripts/setlocalversion
>@@ -12,7 +12,9 @@ cd "${1:-.}" || usage
> if head=`git rev-parse --verify HEAD 2>/dev/null`; then
> 	# Do we have an untagged version?
> 	if git name-rev --tags HEAD | grep -E '^HEAD[[:space:]]+(.*~[0-9]*|undefined)$' > /dev/null; then
>-	        git describe | awk -F- '{printf("-%05d-%s", $(NF-1),$(NF))}'
>+		if tag=`git describe 2>/dev/null`; then
>+			echo $tag | awk -F- '{printf("-%05d-%s", $(NF-1),$(NF))}'
>+		fi
> 	fi
> 
> 	# Are there uncommitted changes?

looks ok i'd say.

Re: linux fatal: cannot describe <sha1>

[Sam Ravnborg]

On Sat, Jul 05, 2008 at 02:58:48PM +0200, Jan Engelhardt wrote:
> On Wednesday 2008-07-02 00:18, Sebastian Siewior wrote:
> >* Sam Ravnborg | 2008-07-01 22:09:51 [+0200]:
> >
> >>> Just a note that when you run git-describe, you should probably quiten it.
> >>> 
> >>> fatal: cannot describe 'bd7364a0fd5a4a2878fe4a224be1b142a4e6698e'
> >>> 
> >>
> >>Hi Jan.
> >>
> >>Any specific reason why you sent it to me?
> 
> You are the buildsystem maintainer :)
> 
> >Maybe he was thinking about this (and didn't know that you were moving):
> 
> I only took note of that briefly. Should there have been someone
> else to send it to?
I just failed to see the connection to kbuild - I had long
forgotten that we uses git describe in setlocalversion script.

	Sam

Re: linux fatal: cannot describe <sha1>

[Sam Ravnborg]

On Wed, Jul 02, 2008 at 12:18:08AM +0200, Sebastian Siewior wrote:
> * Sam Ravnborg | 2008-07-01 22:09:51 [+0200]:
> 
> >> Just a note that when you run git-describe, you should probably quiten it.
> >> 
> >> fatal: cannot describe 'bd7364a0fd5a4a2878fe4a224be1b142a4e6698e'
> >> 
> >> This happens when tags are not present, which can happen if Linus's tree 
> >> is sent upwards again, IOW:
> >> 
> >>  machine1$  git-clone torvalds/linux-2.6.git
> >>  machine1$  git push elsewhere master
> >> 
> >>  machine2$  git-clone elsewhere:/linux
> >>  machine2$  git-describe HEAD
> >>  fatal: cannot describe that
> >
> >Hi Jan.
> >
> >Any specific reason why you sent it to me?
> >Maybe because I do not use git describe at all?
> Maybe he was thinking about this (and didn't know that you were moving):
> 
> ---
> scripts: don't desribe if there is nothing to describe

Applied.

	Sam