All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Vincent Prince <vincent.prince.fr@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH 2/3] cppzmq: bump version 4.2.3 => 4.3.1
Date: Wed, 3 Apr 2019 14:15:14 +0300	[thread overview]
Message-ID: <20190403111514.GA20836@localhost> (raw)
In-Reply-To: <CAB2nKc9hnDrOTtKjNfk1cupK0yv8xXksEuvURJtS6ve_baOpJQ@mail.gmail.com>

On Wed, Apr 03, 2019 at 12:42:13PM +0200, Vincent Prince wrote:
> Then, it would need to rename cppzmq_git.bb into cppzmq_4.3.1.git or can we
> just remove +git${SRCPV} part of PV?
> 
> In following threads it seems first option should be chosen?
> https://www.mail-archive.com/openembedded-core@lists.openembedded.org/msg120575.html
>...

That is about putting PV in the recipe filename instead of "git",
in this case the discussion would be cppzmq_git.bb versus cppzmq_4.3.1.bb

I am not aware of anyone arguing against PV having a proper
version (without +git) for a release.

> Le mer. 3 avr. 2019 à 10:56, Adrian Bunk <bunk@stusta.de> a écrit :
> > On Wed, Apr 03, 2019 at 10:28:42AM +0200, Vincent Prince wrote:
>...
> > > diff --git a/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
> > b/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
> > > index 9aff59c..2f99417 100644
> > > --- a/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
> > > +++ b/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
> > > @@ -4,8 +4,8 @@ LICENSE = "MIT"
> > >  LIC_FILES_CHKSUM = "file://LICENSE;md5=db174eaf7b55a34a7c89551197f66e94"
> > >  DEPENDS = "zeromq"
> > >
> > > -SRCREV = "6aa3ab686e916cb0e62df7fa7d12e0b13ae9fae6"
> > > -PV = "4.2.3+git${SRCPV}"
> > > +SRCREV = "213da0b04ae3b4d846c9abc46bab87f86bfb9cf4"
> > > +PV = "4.3.1+git${SRCPV}"
> > >...
> >
> > These are the actual releases, PV should not say +git${SRCPV}
> > for them.
> >
> > Not a bug you introduced, but can be fixed now.
> >
> > cu
> > Adrian

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed



  parent reply	other threads:[~2019-04-03 11:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-03  8:28 [meta-oe][PATCH 1/3] zeromq: bump version 4.2.5 => 4.3.1 Vincent Prince
2019-04-03  8:28 ` [meta-oe][PATCH 2/3] cppzmq: bump version 4.2.3 " Vincent Prince
2019-04-03  8:56   ` Adrian Bunk
2019-04-03 10:42     ` Vincent Prince
2019-04-03 10:43       ` Vincent Prince
2019-04-03 11:15       ` Adrian Bunk [this message]
2019-04-03 11:36         ` Vincent Prince
2019-04-03 12:03           ` Martin Jansa
2019-04-03 12:31             ` Vincent Prince
2019-04-03 12:50               ` Martin Jansa
2019-04-03 16:52   ` Khem Raj
2019-04-03 19:33     ` Vincent Prince
2019-04-04  9:12       ` Vincent Prince
2019-04-04 16:34         ` Khem Raj
2019-04-03  8:28 ` [meta-oe][PATCH 3/3] czmq: bump version 4.1.1 => 4.2.0 Vincent Prince
2019-04-03  8:34   ` Vincent Prince

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190403111514.GA20836@localhost \
    --to=bunk@stusta.de \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=vincent.prince.fr@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.