Re: errors pushing tags to git

2015-10-14 Thread Sandro Tosi 
> Yep.  Again, I've seen this, but don't know the cause and don't think it
> actually has any negative effect.

it is because a new tag is being pushed, so the post-receive hook is
trying to get a diff of it, but it fails as.. there is no "previous"
state for that. it is harmless, but annoying to see the error, could
be fixed changing the hook to verify if the prevrev is all 0 and act
accordingly

-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

Re: errors pushing tags to git

2015-10-12 Thread Barry Warsaw 
On Oct 12, 2015, at 05:22 AM, Brian May wrote:

>git push --tags
>Total 0 (delta 0), reused 0 (delta 0)
>remote: Sending notification emails to:
>python-modules-comm...@lists.alioth.debian.org,
>python-django_...@packages.qa.debian.org
>remote: Sending notification emails to:
>python-modules-comm...@lists.alioth.debian.org,
>python-django_...@packages.qa.debian.org
>remote: Sending notification emails to:
>python-modules-comm...@lists.alioth.debian.org,
>python-django_...@packages.qa.debian.org
>remote: fatal: Invalid revision range
>..e2234da325c5962b54559e6c3d75dc4c116853f5
>remote: fatal: Invalid revision range
>..cdf0cc9f72f1847763290c018038990b3bcec4c1
>remote: fatal: Invalid revision range
>..e2f348a8f03d3f935e0233d7a747be5fd99c796f
>To git+ssh://git.debian.org/git/python-modules/packages/python-django.git
> * [new tag] debian/1.7.10-1 -> debian/1.7.10-1
> * [new tag] patched/1.7.10-1 -> patched/1.7.10-1
> * [new tag] upstream/1.7.10 -> upstream/1.7.10
>
>I think it worked...

Yep.  Again, I've seen this, but don't know the cause and don't think it
actually has any negative effect.

Cheers,
-Barry