Wrong git tag in 3.6.3 release tarball

It seems that 3.6.3 release tarball has been prepared from git tag
3.6.4git :\

On Tue, Jan 22, 2013 at 2:05 AM, Barry J. [email protected]
wrote:

It seems that 3.6.3 release tarball has been prepared from git tag
3.6.4git :\

Indeed it has, thanks for catching this.

Fortunately, there is no difference in functionality, other than the
change
in the version string.

I’ll re-issue the tarball file on gnuradio.org.

Thanks again,

Johnathan

On Tue, Jan 22, 2013 at 9:48 AM, Richard F. [email protected]
wrote:

It should be noted, that it is generally bad to make a new tarball with
exactly the same name as it confuses people. I added gnuradio 3.6.3 in
gentoo and all of the users downloaded the package from your site and
the gentoo mirrors picked up the package. Now if the user gets it from
the mirrors or your website it would be different.

It would be best to avoid two different tarballs with different
checksums and the same name. Can we maybe call this 3.6.3.1?

Ok, fair enough. We’ve had a few minor bug fixes along the maint branch
since the release, and we do have a provision to make releases with that
fourth digit from this branch, so I think the most straightforward thing
to
do would be to tag and release a 3.6.3.1. I’ve got a couple more bug
fix
branches to merge in first.

Johnathan

On 01/22/2013 12:38 PM, Johnathan C. wrote:

in the version string.

I’ll re-issue the tarball file on gnuradio.org.

It should be noted, that it is generally bad to make a new tarball with
exactly the same name as it confuses people. I added gnuradio 3.6.3 in
gentoo and all of the users downloaded the package from your site and
the gentoo mirrors picked up the package. Now if the user gets it from
the mirrors or your website it would be different.

It would be best to avoid two different tarballs with different
checksums and the same name. Can we maybe call this 3.6.3.1?

Thanks,
Zero

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs