public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Roos, Thomas" <throos@amazon.de>
To: Vyacheslav Yurkov <uvv.mail@gmail.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: AW: [OE-core] kirkstone boost upgrade?
Date: Fri, 21 Jul 2023 08:25:46 +0000	[thread overview]
Message-ID: <11b360cb14ab463b88b5cec298e0b2c6@amazon.de> (raw)
In-Reply-To: <f8527dac-70d8-488f-dbcb-78d29acd8e01@gmail.com>

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

Hi Vyacheslav,
I think it's this error: boost beast "Fixed WebSocket handshake response on failure."
Fixed in 1.79.
My question was what is the policy of upgrading boost in an LTS branch? I guess there is no change?
I totally agree that there are breaking changes - I had experienced a lot in the past...
Cheers, Thomas

________________________________
Von: Vyacheslav Yurkov <uvv.mail@gmail.com>
Gesendet: Freitag, 21. Juli 2023 08:07:32
An: Roos, Thomas; openembedded-core@lists.openembedded.org
Betreff: RE: [EXTERNAL][OE-core] kirkstone boost upgrade?


CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.


I would be cautious with boost upgrade in stable branch.

Boost is known for having breaking changes almost each new version. I only had a glance at 1.79-1.81 https://www.boost.org/users/history/ and there are a couple of them.

Are you affected by some particular bug or vulnerability in 1.78?

Vyacheslav

On 21.07.2023 06:49, Thomas Roos via lists.openembedded.org wrote:

Hi,
we are hitting an issue with boost version 1.78 and like to ask if and how there is a boost upgrade on kirkstone branch?
Cheers, Thomas



Amazon Web Services EMEA SARL
38 avenue John F. Kennedy, L-1855 Luxembourg
Sitz der Gesellschaft: L-1855 Luxemburg
eingetragen im Luxemburgischen Handelsregister unter R.C.S. B186284

Amazon Web Services EMEA SARL, Niederlassung Deutschland
Marcel-Breuer-Str. 12, D-80807 Muenchen
Sitz der Zweigniederlassung: Muenchen
eingetragen im Handelsregister des Amtsgerichts Muenchen unter HRB 242240, USt-ID DE317013094





Amazon Web Services EMEA SARL
38 avenue John F. Kennedy, L-1855 Luxembourg
Sitz der Gesellschaft: L-1855 Luxemburg
eingetragen im Luxemburgischen Handelsregister unter R.C.S. B186284

Amazon Web Services EMEA SARL, Niederlassung Deutschland
Marcel-Breuer-Str. 12, D-80807 Muenchen
Sitz der Zweigniederlassung: Muenchen
eingetragen im Handelsregister des Amtsgerichts Muenchen unter HRB 242240, USt-ID DE317013094




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

  reply	other threads:[~2023-07-21  8:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-21  4:49 kirkstone boost upgrade? Roos, Thomas
2023-07-21  6:07 ` [OE-core] " Vyacheslav Yurkov
2023-07-21  8:25   ` Roos, Thomas [this message]
2023-07-21 11:42     ` Ross Burton
2023-07-21 14:21       ` AW: " Roos, Thomas
2023-07-21  6:09 ` Christian Eggers
2023-07-21  6:29 ` Christian Eggers
2023-07-21  8:21   ` Martin Jansa

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=11b360cb14ab463b88b5cec298e0b2c6@amazon.de \
    --to=throos@amazon.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=uvv.mail@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox