This repository was archived by the owner on Aug 5, 2022. It is now read-only.
Repository navigation
This repository was archived by the owner on Aug 5, 2022. It is now read-only.
Release tarball changes after realease #372
Description
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 during git export. The source controled .version contains the %D placeholder that is replaced with the commit ref names (not only tag, see git help gitattributes).
Problem:
- If no patch as been merged after a release is taged, the
.versioncontains the expected tag ANDmaster - After at least one patch is merged, the
.versioncontains only the expected tag
Thus release tarballs are not immutable with current release process.
Activity
krocard commentedon Jul 27, 2016
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.
dawagner commentedon Jul 28, 2016
Proposals
$Format: %N$in the.versionfile. This implies a manual release step but has the advantage that, if we forget to do it, there is no problem doing it afterward.krocard commentedon Jul 28, 2016
👍 for the
git notesolution.shivank01 commentedon Jan 10, 2017
I want to work on this bug. Is anyone already working on it???
dawagner commentedon Jan 10, 2017
Hi, @shivank01. We are not currently working on it and you are welcome to!
shivank01 commentedon Feb 5, 2017
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.
mgaio commentedon Feb 6, 2017
Hi, deb package is libasio-dev