# Changing release tarballs without bumping the version number is bad for packagers

**URL:** <https://forum.ansible.com/t/changing-release-tarballs-without-bumping-the-version-number-is-bad-for-packagers/14781>\
**Category:** Ansible Project\
**Created:** [March 15, 2014, 4:40pm UTC](https://forum.ansible.com/t/changing-release-tarballs-without-bumping-the-version-number-is-bad-for-packagers/14781 "2014-03-15T16:40:18Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Robert\_Peichaer](https://avatars.discourse-cdn.com/v4/letter/r/7c8e57/32.png) [@Robert\_Peichaer](https://forum.ansible.com/u/Robert_Peichaer)\
**Post date:** [March 15, 2014, 4:40pm UTC](https://forum.ansible.com/t/changing-release-tarballs-without-bumping-the-version-number-is-bad-for-packagers/14781/1 "2014-03-15T16:40:18Z")

</div>

Hello Michael

The Ansible Project changed the 1.5.3 release tarball to include [https://github.com/ansible/ansible/pull/6491](https://github.com/ansible/ansible/pull/6491) without changing the release version number.  
That’s bad for packagers because it breaks most of the packaging systems out there, due to the changed checksum of the tarball.  
And it causes all sorts of unnecessary bug reports from users that fail to install ansible using packages.  
It’s much saner to bump the version number a 4th time in a short time than to do that.

Cheers  
Robert