From: "Roos, Thomas" <throos@amazon.de>
To: Ross Burton <Ross.Burton@arm.com>
Cc: 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 14:21:55 +0000 [thread overview]
Message-ID: <aec5abd544f84568b61ccd9ed7415bcb@amazon.de> (raw)
In-Reply-To: <76EB3148-B3B7-4D74-8F4B-5343A63C71F1@arm.com>
[-- Attachment #1: Type: text/plain, Size: 1551 bytes --]
thank you, Ross - will try.
Cheers, Thomas
________________________________
Von: Ross Burton <Ross.Burton@arm.com>
Gesendet: Freitag, 21. Juli 2023 13:42:02
An: Roos, Thomas
Cc: Vyacheslav Yurkov; 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.
On 21 Jul 2023, at 09:25, Thomas Roos via lists.openembedded.org <throos=amazon.de@lists.openembedded.org> wrote:
>
> 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...
If you can isolate the fix to a small patch that doesn’t break anything else, then you can submit that as a patch. If it needs to be an invasive upgrade, that’s less likely to happen.
Ross
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: 2649 bytes --]
next prev parent reply other threads:[~2023-07-21 14:22 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 ` AW: " Roos, Thomas
2023-07-21 11:42 ` Ross Burton
2023-07-21 14:21 ` Roos, Thomas [this message]
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=aec5abd544f84568b61ccd9ed7415bcb@amazon.de \
--to=throos@amazon.de \
--cc=Ross.Burton@arm.com \
--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