Openembedded Core Discussions
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [thud][PATCH] Revert "boost: update to 1.69.0"
Date: Tue, 2 Apr 2019 10:51:22 -0700	[thread overview]
Message-ID: <17cbc6a5-4ef8-b618-91fc-6b4b16862213@gmail.com> (raw)
In-Reply-To: <CA+chaQfznYy8kNoRYynaZQuc1wA7VOxroxcgcPqp8dJcUB3V9A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2325 bytes --]



On 4/2/19 12:18 AM, Martin Jansa wrote:
> Any update on this one? Or should we downgrade it on our side when
> bumping oe-core/thud revision?
I have this stagged but it missed the QA cutoff. 

- armin
>
> On Sun, Mar 24, 2019 at 7:48 PM Martin Jansa <martin.jansa@gmail.com
> <mailto:martin.jansa@gmail.com>> wrote:
>
>     On Sun, Mar 24, 2019 at 11:45:08AM -0700, akuster808 wrote:
>     >
>     >
>     > On 3/24/19 11:01 AM, Martin Jansa wrote:
>     > > On Tue, Mar 19, 2019 at 07:52:06AM +0000, Mikko.Rapeli@bmw.de
>     <mailto:Mikko.Rapeli@bmw.de> wrote:
>     > >> On Mon, Mar 18, 2019 at 06:03:05PM +0100, Andreas Müller wrote:
>     > >>> On Mon, Mar 18, 2019 at 5:45 PM Armin Kuster
>     <akuster808@gmail.com <mailto:akuster808@gmail.com>> wrote:
>     > >>>> This reverts commit a384248938ea9db096866bf4ec8678d35ca62a12.
>     > >>>>
>     > >>>> This package update slipped in doing the maint process.
>     Removing it.
>     > >> <snip>
>     > >>> Just my opinion - don't consider this as NAK.
>     > >>>
>     > >>> * I already fixed the recipes that failed for me. For at
>     least one the
>     > >>> change is no more compatible to 1.68.0.
>     > >>> * This makes PV going backwards
>     > >>>
>     > >>> Thanks for addressing - what do others think?
>     > >> I'm not using thud yet, but updating boost in stable branch
>     would break
>     > >> too many things and I would have to revert that change in our
>     trees. Some boost
>     > >> updates are in the end quite trivial and just require recompiling
>     > >> everything but still, I would prefer that boost is not
>     updated in stable
>     > >> branches unless there is a huge security/stability issue with
>     the old version.
>     > > Agreed.
>     > >
>     > > I care less for PV going backwards nowadays, it's probably
>     less annoying than
>     > > bumping PE first in master and then backporting PE bump to thud.
>     > >
>     > > People with build issues related to boost upgrade probably never
>     > > built whole image to push it as an upgrade to end devices.
>     >
>     > So do you agree with the revert?
>
>     I do.
>
>     -- 
>     Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com
>     <mailto:Martin.Jansa@gmail.com>
>


[-- Attachment #2: Type: text/html, Size: 4190 bytes --]

      reply	other threads:[~2019-04-02 17:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-18 16:45 [thud][PATCH] Revert "boost: update to 1.69.0" Armin Kuster
2019-03-18 17:03 ` Andreas Müller
2019-03-19  7:52   ` Mikko.Rapeli
2019-03-24 18:01     ` Martin Jansa
2019-03-24 18:45       ` akuster808
2019-03-24 18:48         ` Martin Jansa
2019-04-02  7:18           ` Martin Jansa
2019-04-02 17:51             ` akuster808 [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=17cbc6a5-4ef8-b618-91fc-6b4b16862213@gmail.com \
    --to=akuster808@gmail.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@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