<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 16 June 2017 at 00:17, Alejandro del Castillo <span dir="ltr"><<a href="mailto:alejandro.delcastillo@ni.com" target="_blank">alejandro.delcastillo@ni.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":2jz" class="a3s aXjCH m15cae5bbbb5a54ee"> SRCREV = "<wbr>1a708fd73d10c2b7677dd4cc4e0177<wbr>46ebbb9166"<br>
-PV = "0.3.4+git${SRCPV}"<br>
+PV = "0.3.5+git${SRCPV}"<br></div></blockquote></div><br>As Martin said you're missing a srcrev bump.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Also if you're just tracking the release SHA, then for simplicity you can rename the recipe to opkg-utils_0.3.5 and just have the SRCREV set. No need for a SHA in PV if it's the 0.3.5 tag.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>