From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH v2 1/2] bitbake: Update to the release 1.40.0
Date: Mon, 19 Nov 2018 08:46:56 +0100 [thread overview]
Message-ID: <5f875ef3-0fc5-21b6-9232-c1f91dbfe99d@siemens.com> (raw)
In-Reply-To: <20181109085903.8299-2-mosipov@ilbers.de>
On 09.11.18 09:59, Maxim Yu. Osipov wrote:
> Origin: https://github.com/openembedded/bitbake.git
> Commit: 2820e7aab2203fc6cf7127e433a80b7d13ba75e0
> Author: Richard Purdie <richard.purdie@linuxfoundation.org>
> Date: Sat Oct 20 14:26:41 2018 +0100
>
> bitbake: Bump version to 1.40.0
We may have a problem with this release, see
http://lists.openembedded.org/pipermail/bitbake-devel/2018-November/019558.html
Currently, I can't update jailhouse-images because of that. But before
suggesting to role back to 1.38.0, let's give upstream a chance to comment on this.
Jan
PS: This is not pristine 2820e7aa, bb_multiconfig_files.png differs. Please
perform a clean checkout next time.
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2018-11-19 7:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 8:59 [PATCH v2 0/2] Update to the latest bitbake release Maxim Yu. Osipov
2018-11-09 8:59 ` [PATCH v2 1/2] bitbake: Update to the release 1.40.0 Maxim Yu. Osipov
2018-11-19 7:46 ` Jan Kiszka [this message]
2018-11-21 8:30 ` Jan Kiszka
2018-11-09 8:59 ` [PATCH v2 2/2] meta: Set LAYERSERIES_* variables Maxim Yu. Osipov
2018-11-12 9:20 ` Henning Schild
2018-11-14 7:20 ` Henning Schild
2018-11-14 10:15 ` Jan Kiszka
2018-11-14 10:39 ` Maxim Yu. Osipov
2018-11-12 9:28 ` [PATCH v2 0/2] Update to the latest bitbake release Maxim Yu. Osipov
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=5f875ef3-0fc5-21b6-9232-c1f91dbfe99d@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=mosipov@ilbers.de \
/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