Open krocard opened 8 years ago
This bug is very inconvenient for Yocto integration as reported by @mgaio (who find the bug). Yocto build system expects release tarball hash to be immutable.
Proposals
$Format: %N$
in the .version
file. This implies a manual release step but has the advantage that, if we forget to do it, there is no problem doing it afterward.:+1: for the git note
solution.
I want to work on this bug. Is anyone already working on it???
Hi, @shivank01. We are not currently working on it and you are welcome to!
I am a noobie in open source contribution and i am working on this bug but unable to install asio in ubuntu. Can you please tell me how to install it on ubuntu.
Hi, deb package is libasio-dev
TLDR
Release tarball/zip content (thus hash) may change over time !
Context
All (sufficiently recent) release tarballs contain a
.version
file that is expected to contain the tag of the release. The tag name is added in the.version
file duringgit export
. The source controled.version
contains the%D
placeholder that is replaced with the commit ref names (not only tag, see git helpgitattributes
).Problem:
.version
contains the expected tag ANDmaster
.version
contains only the expected tagThus release tarballs are not immutable with current release process.