Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "Khem Raj" <raj.khem@gmail.com>
To: akuster808 <akuster808@gmail.com>, Martin Jansa <Martin.Jansa@gmail.com>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] [dunfel 03/32] jsoncpp: upgrade 1.9.2 -> 1.9.3
Date: Fri, 10 Jul 2020 09:18:24 -0700	[thread overview]
Message-ID: <ab6083eb-e8b3-d427-ecd1-146cdd960f52@gmail.com> (raw)
In-Reply-To: <1110a82f-3ba0-66e7-ac39-276b7b5ee6d5@gmail.com>



On 7/10/20 8:55 AM, akuster808 wrote:
> 
> 
> On 7/9/20 6:08 PM, Khem Raj wrote:
>>
>> On 7/9/20 9:48 AM, Martin Jansa wrote:
>>> I don't have a strong opinion about this one.
>>>
>>> It's easy enough to undo by downstream layers if they care about ABI.
>>>
>>> At LGE we do have some prebuilt binaries which use jsoncpp, so we do
>>> care, but haven't updated to dunfell yet and when we do get those
>>> prebuilt binaries to be rebuilt, we might as well use newer jsoncpp (and
>>> in that case might backport this upgrade anyway even if it gets reverted
>>> in dunfell).
>>>
>>> Maybe someone else will share an opinion on this as well.
>> I checked https://github.com/open-source-parsers/jsoncpp/releases/tag/1.9.3
>>
>> and it does not mention ABI change there from 1.9.2 to 1.9.3
> that what lead me to believe it was worthy of backport.
>>
>> but then I see
>>
>> https://github.com/open-source-parsers/jsoncpp/commit/8b7ea09b8055df01866a5ce4142b12ed8f9f13eb
>>
>> I dont know if there are API changes which means it will need porting
>> effors for users or is it just a relinking that is needed.
> 
> Same conclusion I came to.  Still the question is open. Should this be
> reverted?

from my own usecase it does not matter since dunfell is still under 
porting effort and any version can be used, but others might have 
different view.

> 
> -armin
>>> On Thu, Jul 9, 2020 at 6:06 PM akuster808 <akuster808@gmail.com
>>> <mailto:akuster808@gmail.com>> wrote:
>>>
>>>
>>>
>>>      On 7/9/20 8:21 AM, Martin Jansa wrote:
>>>>      FYI this "small" upgrade changes ABI version from libjsoncpp22
>>>>      to libjsoncpp24 which might cause some issues to people who expect
>>>>      relatively stable ABIs in LTS dunfell.
>>>      Well that is not good. I did look at the details but apparently I
>>>      failed to catch the "soversion" change.
>>>
>>>      Would you recommend reverting this?
>>>
>>>      -armin
>>>>      On Wed, Jul 1, 2020 at 2:07 AM akuster <akuster808@gmail.com
>>>>      <mailto:akuster808@gmail.com>> wrote:
>>>>
>>>>          From: Pierre-Jean Texier <pjtexier@koncepto.io
>>>>          <mailto:pjtexier@koncepto.io>>
>>>>
>>>>          See full changelog
>>>>          https://github.com/open-source-parsers/jsoncpp/releases/tag/1.9.3
>>>>
>>>>          Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io
>>>>          <mailto:pjtexier@koncepto.io>>
>>>>          Signed-off-by: Khem Raj <raj.khem@gmail.com
>>>>          <mailto:raj.khem@gmail.com>>
>>>>          (cherry picked from commit
>>>>          65e124eef373680726ac045677cbec7d9080a289)
>>>>          Signed-off-by: Armin Kuster <akuster808@gmail.com
>>>>          <mailto:akuster808@gmail.com>>
>>>>          ---
>>>>           .../jsoncpp/{jsoncpp_1.9.2.bb <http://jsoncpp_1.9.2.bb> =>
>>>>          jsoncpp_1.9.3.bb <http://jsoncpp_1.9.3.bb>}              | 2 +-
>>>>           1 file changed, 1 insertion(+), 1 deletion(-)
>>>>           rename meta-oe/recipes-devtools/jsoncpp/{jsoncpp_1.9.2.bb
>>>>          <http://jsoncpp_1.9.2.bb> => jsoncpp_1.9.3.bb
>>>>          <http://jsoncpp_1.9.3.bb>} (93%)
>>>>
>>>>          diff --git a/meta-oe/recipes-devtools/jsoncpp/jsoncpp_1.9.2.bb
>>>>          <http://jsoncpp_1.9.2.bb>
>>>>          b/meta-oe/recipes-devtools/jsoncpp/jsoncpp_1.9.3.bb
>>>>          <http://jsoncpp_1.9.3.bb>
>>>>          similarity index 93%
>>>>          rename from meta-oe/recipes-devtools/jsoncpp/jsoncpp_1.9.2.bb
>>>>          <http://jsoncpp_1.9.2.bb>
>>>>          rename to meta-oe/recipes-devtools/jsoncpp/jsoncpp_1.9.3.bb
>>>>          <http://jsoncpp_1.9.3.bb>
>>>>          index a88410f2ff..97c6361ad8 100644
>>>>          --- a/meta-oe/recipes-devtools/jsoncpp/jsoncpp_1.9.2.bb
>>>>          <http://jsoncpp_1.9.2.bb>
>>>>          +++ b/meta-oe/recipes-devtools/jsoncpp/jsoncpp_1.9.3.bb
>>>>          <http://jsoncpp_1.9.3.bb>
>>>>          @@ -11,7 +11,7 @@ SECTION = "libs"
>>>>           LICENSE = "MIT"
>>>>           LIC_FILES_CHKSUM =
>>>>          "file://LICENSE;md5=fa2a23dd1dc6c139f35105379d76df2b"
>>>>
>>>>          -SRCREV = "d2e6a971f4544c55b8e3b25cf96db266971b778f"
>>>>          +SRCREV = "6aba23f4a8628d599a9ef7fa4811c4ff6e4070e2"
>>>>           SRC_URI = "git://github.com/open-source-parsers/jsoncpp
>>>>          <http://github.com/open-source-parsers/jsoncpp>"
>>>>
>>>>           S = "${WORKDIR}/git"
>>>>          --
>>>>          2.17.1
>>>>
>>>>
>>>
>>> 
>>>
> 

  reply	other threads:[~2020-07-10 16:18 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-01  0:06 [dunfel 00/32] Patch review akuster
2020-07-01  0:06 ` [dunfel 01/32] zchunk: upgrade 1.1.5 -> 1.1.6 akuster
2020-07-01  0:06 ` [dunfel 02/32] uriparser: upgrade 0.9.3 -> 0.9.4 akuster
2020-07-01  0:06 ` [dunfel 03/32] jsoncpp: upgrade 1.9.2 -> 1.9.3 akuster
2020-07-09 15:21   ` [oe] " Martin Jansa
2020-07-09 16:06     ` akuster
2020-07-09 16:48       ` Martin Jansa
2020-07-10  1:08         ` Khem Raj
2020-07-10  7:37           ` Mikko Rapeli
2020-07-12 18:41             ` akuster
2020-07-13  8:25               ` Mikko Rapeli
2020-07-13 15:46                 ` Khem Raj
2020-07-15  3:52                   ` akuster
2020-07-10 15:55           ` akuster
2020-07-10 16:18             ` Khem Raj [this message]
2020-07-01  0:06 ` [dunfel 04/32] proj: upgrade 7.0.0 -> 7.0.1 akuster
2020-07-01  0:06 ` [dunfel 05/32] netkit-rsh: properly append PACKAGECONFIG akuster
2020-07-01  0:06 ` [dunfel 06/32] zile: " akuster
2020-07-01  0:06 ` [dunfel 07/32] postgresql: 12.2 -> 12.3 akuster
2020-07-01  0:06 ` [dunfel 08/32] multipath-tools: Fix build with json-c 0.14 and newer akuster
2020-07-01  8:48   ` [oe] " Adrian Bunk
2020-07-01 16:56     ` akuster
2020-07-01  0:06 ` [dunfel 09/32] libblockdev: upgrade 2.23 -> 2.24 akuster
2020-07-01  0:06 ` [dunfel 10/32] libvpx: upgrade 1.8.1 -> 1.8.2 akuster
2020-07-01  0:06 ` [dunfel 11/32] vlc: Fix build with qt5 in PACKAGECONFIG and Qt >= 5.15 / renumber patches akuster
2020-07-01  0:28   ` [oe] " Martin Jansa
2020-07-01  2:07     ` akuster
2020-07-01  0:06 ` [dunfel 12/32] jpnevulator: upgrade 2.3.4 -> 2.3.5 akuster
2020-07-01  0:06 ` [dunfel 13/32] libnftnl: upgrade 1.1.6 -> 1.1.7 akuster
2020-07-01  0:06 ` [dunfel 14/32] nftables: upgrade 0.9.4 -> 0.9.5 akuster
2020-07-01  0:07 ` [dunfel 15/32] haveged: upgrade 1.9.8 -> 1.9.9 akuster
2020-07-01  0:07 ` [dunfel 16/32] mm-common: upgrade 1.0..0 -> 1.0.1 akuster
2020-07-01  0:07 ` [dunfel 17/32] python-django: add RDEPENDS akuster
2020-07-01  0:07 ` [dunfel 18/32] python-m2crypto: Add RDEPENDS akuster
2020-07-01  0:07 ` [dunfel 19/32] python-django: set CVE_PRODUCT to be django akuster
2020-07-01  0:07 ` [dunfel 20/32] python3-m2crypto: add the missing rdepends akuster
2020-07-01  0:07 ` [dunfel 21/32] zstd: Upgrade 1.4.4 -> 1.4.5 akuster
2020-07-01  0:07 ` [dunfel 22/32] rsnapshot: upgrade 1.4.2 -> 1.4.3 akuster
2020-07-01  0:07 ` [dunfel 23/32] fuse3: upgrade 3.9.1 -> 3.9.2 akuster
2020-07-01  0:07 ` [dunfel 24/32] protobuf-c: disable parallelism to avoid race condition akuster
2020-07-01  0:07 ` [dunfel 25/32] openipmi: upgrade 2.0.28 -> 2.0.29 akuster
2020-07-01  0:07 ` [dunfel 26/32] twm: upgrade 1.0.10 -> 1.0.11 akuster
2020-07-01  0:07 ` [dunfel 27/32] libtalloc: fix upstream url akuster
2020-07-01  0:07 ` [dunfel 28/32] linuxptp: Fix segmentation fault on 32 bit platforms with 64 bit time_t akuster
2020-07-01  0:07 ` [dunfel 29/32] openh264: upgrade 2.1.0 -> 2.1.1 akuster
2020-07-01  0:07 ` [dunfel 30/32] tcpreplay: upgrade 4.3.2 -> 4.3.3 akuster
2020-07-01  0:07 ` [dunfel 31/32] python3-sqlalchemy: Upgrade 1.3.12 -> 1.3.17 akuster
2020-07-01  0:07 ` [dunfel 32/32] ntp: update 4.2.8p15 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=ab6083eb-e8b3-d427-ecd1-146cdd960f52@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=Martin.Jansa@gmail.com \
    --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