On Tue, Jul 11, 2023 at 6:11 PM Marek Vasut <ma...@denx.de> wrote: > > The version 0.25 has been released, it has not been tagged however. > Update the this version anyway.
hmm how do we know where to peg SRCREV ? I wonder if we should wait for tag to appear. I agree in waiting for tag to be published. Also, would it make sense to rename the recipe file according to the actual version rather than 'git'? In the past I think the recipe referred arbitrary git commits, however we have moved to referring actual release commits now. > > Signed-off-by: Marek Vasut <ma...@denx.de> > --- > Cc: Christian Eggers <cegg...@arri.de> > Cc: Khem Raj <raj.k...@gmail.com> > Cc: Martin Siegumfeldt <m...@gomspace.com> > --- > meta-oe/recipes-support/libiio/libiio_git.bb | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/meta-oe/recipes-support/libiio/libiio_git.bb > b/meta-oe/recipes-support/libiio/libiio_git.bb > index ea51c19f4..b89ae29ea 100644 > --- a/meta-oe/recipes-support/libiio/libiio_git.bb > +++ b/meta-oe/recipes-support/libiio/libiio_git.bb > @@ -4,8 +4,8 @@ SECTION = "libs" > LICENSE = "LGPL-2.1-or-later" > LIC_FILES_CHKSUM = "file://COPYING.txt;md5=7c13b3376cea0ce68d2d2da0a1b3a72c" > > -SRCREV = "c4498c27761d04d4ac631ec59c1613bfed079da5" > -PV = "0.24" > +SRCREV = "eee8cba6f42177a094ebe16759606a719676fda7" > +PV = "0.25" > > SRC_URI = > "git://github.com/analogdevicesinc/libiio.git;protocol=https;branch=master" > UPSTREAM_CHECK_GITTAGREGEX = "v(?P<pver>\d+(\.\d+)+)" > -- > 2.40.1 > ________________________ This email was scanned by Bitdefender
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#103827): https://lists.openembedded.org/g/openembedded-devel/message/103827 Mute This Topic: https://lists.openembedded.org/mt/100091776/21656 Group Owner: openembedded-devel+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
