oh, I didnt know that, sorry!!!. So I need to name the tag 2.2.1 to be 2.2.2
and recover the hash from 2.2.1 and tag it again, is that correct?
Vicky
On Tue, Apr 19, 2016 at 3:13 PM, Sebastiaan Couwenberg <sebastic@xs4all.nl> wrote:
On 04/19/2016 10:07 PM, Vicky Vergara wrote: > Hello Sebastian, Christoph: > I will contact the people of the debian link, > it so happens, that yesterday I made the tag, but this morning I > realized that I didn't update news and change log so I deleted > the tag, and made a new one. and to this last one I made the release. > And in the link you are giving me, it looks like it took yesterday's tag.
Please don't do that.
Once a release is published, you cannot take it back.
Now there are two different 2.2.1 releases which differ in content, but not version number.
The fixes you made, make it appropriate to bump the version to 2.2.2. > I don't know how much affects this in what you are doing > to make the release.
I need to create a tarball which includes a Debian specific version suffix to differentiate it from the 2.2.1 I packaged earlier.
I'd rather not do that, and package 2.2.2 instead after you've fixed the tags in the git repository. > Thanks for your help and patience. I want to make things correctly and > I really appreciate your help.
