Re: How to insure SRCREV is consistent with PV

Martin Jansa

In webOS we use do_unpack postinst which checks that the SRCREV matches with the expected tag name and that the tag is annotated, see

Then for our own components (mostly using CMake) we also pass the version from the recipe into CMake:
which is then compared with the version inside the component source during the build:
so you cannot claim different version even if you tag matches it.

It's a bit more complicated, because we use WEBOS_VERSION variable which is then split into PV (VERSION + SUBMISSION) and SRCREV,
but with enforced consistency across all our components this worked quite well.


On Tue, Aug 9, 2022 at 11:00 AM Philippe Midol-Monnet <philippe.midol-monnet@...> wrote:

Since the last version of bibake it looks like SRCREV must be set with a SHA1 in order to fetch source from a git repository. We previously set it with a tag corresponding to PV.
Manually retrieving the sha1 of the commit of a tag can easily lead to mistakes.

Is there a way to ensure that the SRCREV is consistent with  PV?



Join to automatically receive all group messages.