All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Steve Sakoman" <steve@sakoman.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Tim Orling <ticotimo@gmail.com>,
	 Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	 Tony Tascioglu <tony.tascioglu@windriver.com>,
	 Richard Purdie <richard.purdie@linuxfoundation.org>,
	 Tim Orling <timothy.t.orling@intel.com>
Subject: Re: [OE-core] [dunfell][PATCH 0/1] libxml2: Update to 2.9.12
Date: Mon, 19 Jul 2021 06:37:32 -1000	[thread overview]
Message-ID: <CAOSpxdaDjkNHS+MV_QzWHXT+QWMHZciXL6jYVq_7JihyELramQ@mail.gmail.com> (raw)
In-Reply-To: <CA+chaQcn3SPu=vf+iXCAbAOS=Azyukgit9HCNKUO5L_A6dqOOQ@mail.gmail.com>

On Sun, Jul 18, 2021 at 9:34 PM Martin Jansa <martin.jansa@gmail.com> wrote:
> Does it have compatible ABI with 2.9.10 currently in dunfell? Unfortunately
> https://abi-laboratory.pro/index.php?view=timeline&l=libxml2
> ends with 2.9.10 version, but previous patchfix releases were also often incompatible, so if 2.9.12 changes are even bigger, it might cause issues for people with prebuilt binaries on dunfell.

I downloaded the toolset used to generate the ABI compatibility
reports and ran the test for libxml2.

Sadly 2.9.11 is not 100% compatible with 2.9.10 (though 2.9.12 *is*
100% compatible with 2.9.11)

2.9.11 is given a 96.9% compatibility score against 2.9.10, with one
added symbol (xmlPopOutputCallbacks ( )), 2 medium severity data type
issues, 3 low severity data type issues, and 1 low severity symbol
issue. If anyone is interested I can send you the report.

So it seems that this version upgrade isn't a good candidate for dunfell.

Steve

      reply	other threads:[~2021-07-19 16:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19  0:14 [dunfell][PATCH 0/1] libxml2: Update to 2.9.12 Tim Orling
2021-07-19  0:15 ` [dunfell][PATCH 1/1] " Tim Orling
2021-07-19  7:34 ` [OE-core] [dunfell][PATCH 0/1] " Martin Jansa
2021-07-19 16:37   ` Steve Sakoman [this message]

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=CAOSpxdaDjkNHS+MV_QzWHXT+QWMHZciXL6jYVq_7JihyELramQ@mail.gmail.com \
    --to=steve@sakoman.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=ticotimo@gmail.com \
    --cc=timothy.t.orling@intel.com \
    --cc=tony.tascioglu@windriver.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.