On 06/16/2017 06:21 AM, Burton, Ross wrote: > > On 16 June 2017 at 00:17, Alejandro del Castillo > <alejandro.delcasti...@ni.com <mailto:alejandro.delcasti...@ni.com>> wrote: > > SRCREV = "1a708fd73d10c2b7677dd4cc4e017746ebbb9166" > -PV = "0.3.4+git${SRCPV}" > +PV = "0.3.5+git${SRCPV}" > > > As Martin said you're missing a srcrev bump. > > 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.
On commit d6b04e12127dd65b96ac7f4509b829510ef21071 the SRCREV was moved to the rev that eventually became 0.3.5. In this change I am making the PV match that, since I just tagged the 0.3.5 opkg-utils release. But you are right...now that I am tagging releases I should probably rename the recipe. I'll send a V2 with the rename. -- Cheers, Alejandro -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core