Thread: [Mesa3d-dev] Mesa 7.7.1 and Mesa 7.8 released!

Brought to you by: alanh, brianp, chadversary, keithw

mesa3d-dev

[Mesa3d-dev] Mesa 7.7.1 and Mesa 7.8 released!

From: Ian R. <id...@fr...> - 2010-03-28 23:55:59

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Final versions of both Mesa 7.8 and 7.7.1 have been released.  Links on
the Mesa website will still need to be updated, but I think Brian has to
do that.

The tag in the GIT repository for Mesa 7.8 is 'mesa-7.8'.  I had
originally intended to just use 7.8, but having a tag and a branch with
the same name makes GIT angry (i.e., you get "warning: refname '7.8' is
ambiguous.").

I also noticed that the Mesa-7.7.1 release candidates should have been
in /pub/mesa/7.7.1/RC instead of /pub/mesa/7.7/RC.  I have now linked
the 7.7.1 release candidates in both locations.

Mesa-7.7.1 available at ftp://freedesktop.org/pub/mesa/7.7.1/

md5sums:

3ab0638cfa7ce8157337a229cf0db2c4  MesaLib-7.7.1.tar.gz
46664d99e03f1e3ac078a7fea02af115  MesaLib-7.7.1.tar.bz2
4e73ba8abb59aff79485eb95d7cefff7  MesaLib-7.7.1.zip
bf1b108983995f7a712cf3343df1c918  MesaDemos-7.7.1.tar.gz
aeb39645d80d656e0adebaa09e5bcd03  MesaDemos-7.7.1.tar.bz2
01c49b7454fd292244eaf8bdc6ed8cf0  MesaDemos-7.7.1.zip
37ec6386693dcb6dc770d1efd63a7a93  MesaGLUT-7.7.1.tar.gz
1e16c85282f843791a21f7bc7b6a1ca8  MesaGLUT-7.7.1.tar.bz2
d352c9e36a8e4d1059f4abc017b131e0  MesaGLUT-7.7.1.zip

Mesa 7.8 available at ftp://freedesktop.org/pub/mesa/7.8/

md5sums:

5fcfde5383eccb3e9fd665f08a0ea59b  MesaLib-7.8.tar.gz
85cb891eecb89aae4fdd3499cccd934b  MesaLib-7.8.tar.bz2
754f39593006effc1c8ec3c27c2f1296  MesaLib-7.8.zip
c3869c29fa6c3dbdd763f7428d271e12  MesaDemos-7.8.tar.gz
9fe8ec184c7f78691e43c4c0a7f97d56  MesaDemos-7.8.tar.bz2
063a96947f7b83d4ad789c6cf291b184  MesaDemos-7.8.zip
5f4246756b7daaddb4fb3f970cad1e28  MesaGLUT-7.8.tar.gz
ca7048a4aa7a437dcc84cc2c7d731336  MesaGLUT-7.8.tar.bz2
b54581aeb79b585b158d6a32f94feff2  MesaGLUT-7.8.zip
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkuv7DAACgkQX1gOwKyEAw90OwCfTSKh/iZB1+7Rxi93qJvnVb/y
EgkAnjDU46hOCVSd4vsbArUNgKVa6Gxz
=MRYj
-----END PGP SIGNATURE-----

Re: [Mesa3d-dev] [Mesa3d-announce] Mesa 7.7.1 and Mesa 7.8 released!

From: Brian P. <br...@vm...> - 2010-03-29 17:02:16

Ian Romanick wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Final versions of both Mesa 7.8 and 7.7.1 have been released.  Links on
> the Mesa website will still need to be updated, but I think Brian has to
> do that.

I'll do that soon.

> The tag in the GIT repository for Mesa 7.8 is 'mesa-7.8'.  I had
> originally intended to just use 7.8, but having a tag and a branch with
> the same name makes GIT angry (i.e., you get "warning: refname '7.8' is
> ambiguous.").

Yeah, that's what I'm getting now - and I can't seem to update my 7.8 
branch to the latest commit:

$ git rebase origin/7.8
warning: refname '7.8' is ambiguous.
Current branch 7.8 is up to date.

I'm stuck at commit 59258498dc6fa51573b176d071644bd3e750b5ac now.  Help?

-Brian

Re: [Mesa3d-dev] [Mesa3d-announce] Mesa 7.7.1 and Mesa 7.8 released!

From: Ian R. <id...@fr...> - 2010-03-29 17:41:39

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Brian Paul wrote:
> Ian Romanick wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Final versions of both Mesa 7.8 and 7.7.1 have been released.  Links on
>> the Mesa website will still need to be updated, but I think Brian has to
>> do that.
> 
> I'll do that soon.
> 
> 
>> The tag in the GIT repository for Mesa 7.8 is 'mesa-7.8'.  I had
>> originally intended to just use 7.8, but having a tag and a branch with
>> the same name makes GIT angry (i.e., you get "warning: refname '7.8' is
>> ambiguous.").
> 
> Yeah, that's what I'm getting now - and I can't seem to update my 7.8
> branch to the latest commit:
> 
> $ git rebase origin/7.8
> warning: refname '7.8' is ambiguous.
> Current branch 7.8 is up to date.
> 
> I'm stuck at commit 59258498dc6fa51573b176d071644bd3e750b5ac now.  Help?

Hmm... I did 'git tag -d 7.8' and that fixed the problem locally.  I
thought pushing tags afterwards would delete the remote tag, but
apparently not.  I'll try to solve that today.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkuw5fcACgkQX1gOwKyEAw//tQCfZozsn1QERLAymiBIEqIjVyJh
+74AniUhr37oBq8Gx/aSmsxfA1XwYVup
=5WMT
-----END PGP SIGNATURE-----

Re: [Mesa3d-dev] [Mesa3d-announce] Mesa 7.7.1 and Mesa 7.8 released!

From: Brian P. <br...@vm...> - 2010-03-29 18:03:34

Brian Paul wrote:
> Ian Romanick wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Brian Paul wrote:
>>> Ian Romanick wrote:
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA1
>>>>
>>>> Final versions of both Mesa 7.8 and 7.7.1 have been released.  Links on
>>>> the Mesa website will still need to be updated, but I think Brian has to
>>>> do that.
>>> I'll do that soon.
>>>
>>>
>>>> The tag in the GIT repository for Mesa 7.8 is 'mesa-7.8'.  I had
>>>> originally intended to just use 7.8, but having a tag and a branch with
>>>> the same name makes GIT angry (i.e., you get "warning: refname '7.8' is
>>>> ambiguous.").
>>> Yeah, that's what I'm getting now - and I can't seem to update my 7.8
>>> branch to the latest commit:
>>>
>>> $ git rebase origin/7.8
>>> warning: refname '7.8' is ambiguous.
>>> Current branch 7.8 is up to date.
>>>
>>> I'm stuck at commit 59258498dc6fa51573b176d071644bd3e750b5ac now.  Help?
>> Hmm... I did 'git tag -d 7.8' and that fixed the problem locally.  I
>> thought pushing tags afterwards would delete the remote tag, but
>> apparently not.  I'll try to solve that today.
> 
> OK, "git tag -d 7.8" fixed the problem here.

Grrr, the 7.8 tag comes back after a git-fetch though.

-Brian

Re: [Mesa3d-dev] [Mesa3d-announce] Mesa 7.7.1 and Mesa 7.8 released!

From: Brian P. <br...@vm...> - 2010-03-29 17:51:16

Ian Romanick wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Brian Paul wrote:
>> Ian Romanick wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> Final versions of both Mesa 7.8 and 7.7.1 have been released.  Links on
>>> the Mesa website will still need to be updated, but I think Brian has to
>>> do that.
>> I'll do that soon.
>>
>>
>>> The tag in the GIT repository for Mesa 7.8 is 'mesa-7.8'.  I had
>>> originally intended to just use 7.8, but having a tag and a branch with
>>> the same name makes GIT angry (i.e., you get "warning: refname '7.8' is
>>> ambiguous.").
>> Yeah, that's what I'm getting now - and I can't seem to update my 7.8
>> branch to the latest commit:
>>
>> $ git rebase origin/7.8
>> warning: refname '7.8' is ambiguous.
>> Current branch 7.8 is up to date.
>>
>> I'm stuck at commit 59258498dc6fa51573b176d071644bd3e750b5ac now.  Help?
> 
> Hmm... I did 'git tag -d 7.8' and that fixed the problem locally.  I
> thought pushing tags afterwards would delete the remote tag, but
> apparently not.  I'll try to solve that today.

OK, "git tag -d 7.8" fixed the problem here.

-Brian

Re: [Mesa3d-dev] [Mesa3d-announce] Mesa 7.7.1 and Mesa 7.8 released!

From: Dan N. <dbn...@gm...> - 2010-03-29 21:50:34

On Mon, Mar 29, 2010 at 11:03 AM, Brian Paul <br...@vm...> wrote:
> Brian Paul wrote:
>> Ian Romanick wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> Brian Paul wrote:
>>>> Ian Romanick wrote:
>>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>>> Hash: SHA1
>>>>>
>>>>> Final versions of both Mesa 7.8 and 7.7.1 have been released.  Links on
>>>>> the Mesa website will still need to be updated, but I think Brian has to
>>>>> do that.
>>>> I'll do that soon.
>>>>
>>>>
>>>>> The tag in the GIT repository for Mesa 7.8 is 'mesa-7.8'.  I had
>>>>> originally intended to just use 7.8, but having a tag and a branch with
>>>>> the same name makes GIT angry (i.e., you get "warning: refname '7.8' is
>>>>> ambiguous.").
>>>> Yeah, that's what I'm getting now - and I can't seem to update my 7.8
>>>> branch to the latest commit:
>>>>
>>>> $ git rebase origin/7.8
>>>> warning: refname '7.8' is ambiguous.
>>>> Current branch 7.8 is up to date.
>>>>
>>>> I'm stuck at commit 59258498dc6fa51573b176d071644bd3e750b5ac now.  Help?
>>> Hmm... I did 'git tag -d 7.8' and that fixed the problem locally.  I
>>> thought pushing tags afterwards would delete the remote tag, but
>>> apparently not.  I'll try to solve that today.
>>
>> OK, "git tag -d 7.8" fixed the problem here.
>
> Grrr, the 7.8 tag comes back after a git-fetch though.

You might just have to go on annarchy and do "git --git-dir=$the_repo
tag -d 7.8". You might also be able to push an empty source to the
remote with "git push origin :refs/tags/7.8".

--
Dan

Re: [Mesa3d-dev] [Mesa3d-announce] Mesa 7.7.1 and Mesa 7.8 released!

From: Ian R. <id...@fr...> - 2010-03-30 00:47:31

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dan Nicholson wrote:
> On Mon, Mar 29, 2010 at 11:03 AM, Brian Paul <br...@vm...> wrote:
>> Brian Paul wrote:
>>> Ian Romanick wrote:
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA1
>>>>
>>>> Brian Paul wrote:
>>>>> Ian Romanick wrote:
>>>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>>>> Hash: SHA1
>>>>>>
>>>>>> Final versions of both Mesa 7.8 and 7.7.1 have been released.  Links on
>>>>>> the Mesa website will still need to be updated, but I think Brian has to
>>>>>> do that.
>>>>> I'll do that soon.
>>>>>
>>>>>
>>>>>> The tag in the GIT repository for Mesa 7.8 is 'mesa-7.8'.  I had
>>>>>> originally intended to just use 7.8, but having a tag and a branch with
>>>>>> the same name makes GIT angry (i.e., you get "warning: refname '7.8' is
>>>>>> ambiguous.").
>>>>> Yeah, that's what I'm getting now - and I can't seem to update my 7.8
>>>>> branch to the latest commit:
>>>>>
>>>>> $ git rebase origin/7.8
>>>>> warning: refname '7.8' is ambiguous.
>>>>> Current branch 7.8 is up to date.
>>>>>
>>>>> I'm stuck at commit 59258498dc6fa51573b176d071644bd3e750b5ac now.  Help?
>>>> Hmm... I did 'git tag -d 7.8' and that fixed the problem locally.  I
>>>> thought pushing tags afterwards would delete the remote tag, but
>>>> apparently not.  I'll try to solve that today.
>>> OK, "git tag -d 7.8" fixed the problem here.
>> Grrr, the 7.8 tag comes back after a git-fetch though.
> 
> You might just have to go on annarchy and do "git --git-dir=$the_repo
> tag -d 7.8". You might also be able to push an empty source to the
> remote with "git push origin :refs/tags/7.8".

It looks like airlied fixed this for us.  Thanks Dave!

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkuxScIACgkQX1gOwKyEAw/+nwCZARUvIojvbGeao5EGTXOhmH+v
b/AAn0ck1D2wnvlTLlDEEoHMOy8XcEJI
=zg1N
-----END PGP SIGNATURE-----