From: "Adrian Bunk" <bunk@stusta.de>
To: akuster808 <akuster808@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] [dunfell 1/2] Revert "jsoncpp: upgrade 1.9.2 -> 1.9.3"
Date: Sat, 18 Jul 2020 09:15:22 +0300 [thread overview]
Message-ID: <20200718061522.GH1229@localhost> (raw)
In-Reply-To: <ca9b789c-1aed-fb2e-207e-3312ff3d293f@gmail.com>
On Fri, Jul 17, 2020 at 01:57:24PM -0700, akuster808 wrote:
>
>
> On 7/17/20 12:53 PM, Adrian Bunk wrote:
> > On Fri, Jul 17, 2020 at 12:16:10PM -0700, akuster808 wrote:
> >>
> >> On 7/17/20 10:24 AM, Adrian Bunk wrote:
> >>> On Fri, Jul 17, 2020 at 08:20:54AM -0700, akuster wrote:
> >>>> ...
> >>>> --- a/meta-oe/recipes-devtools/jsoncpp/jsoncpp_1.9.3.bb
> >>>> +++ b/meta-oe/recipes-devtools/jsoncpp/jsoncpp_1.9.2.bb
> >>>> ...
> >>> This would make the version going backwards, please add
> >>> PV = "1.9.3+really1.9.2"
> >> right. Wouldn't EP = "1" do the same?
> > PE (not EP) would also solve this.
> right.
> >
> > The problem with an epoch is that it is permanent while
> > a +really version will go away with 1.9.4.
> I don't expect to every update to 1.9.4 as .3 may have introduced ABI
> changes otherwise I would not have reverted this to begin with.
Not in dunfell.
PE would have to stay forever in master.
cu
Adrian
next prev parent reply other threads:[~2020-07-18 6:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 15:20 [dunfell 0/2] dunfell patch review akuster
2020-07-17 15:20 ` [dunfell 1/2] Revert "jsoncpp: upgrade 1.9.2 -> 1.9.3" akuster
2020-07-17 17:24 ` [oe] " Adrian Bunk
2020-07-17 19:16 ` akuster
2020-07-17 19:53 ` Adrian Bunk
2020-07-17 20:57 ` akuster
2020-07-18 6:15 ` Adrian Bunk [this message]
2020-07-18 14:28 ` akuster
2020-07-20 7:33 ` Mikko Rapeli
2020-07-17 15:20 ` [dunfell 2/2] nss: Fix CVE-2020-12399 akuster
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=20200718061522.GH1229@localhost \
--to=bunk@stusta.de \
--cc=akuster808@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox