public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH 1/3] bitbake: Update to fixed master revision
Date: Thu, 22 Nov 2018 15:28:06 +0100	[thread overview]
Message-ID: <3222ef02-53d9-30b0-4121-f20888a69e75@siemens.com> (raw)
In-Reply-To: <20181122145809.7181d469@md1za8fc.ad001.siemens.net>

On 22.11.18 14:58, Henning Schild wrote:
> Am Thu, 22 Nov 2018 14:25:25 +0100
> schrieb Jan Kiszka <jan.kiszka@siemens.com>:
> 
>> On 22.11.18 14:18, Henning Schild wrote:
>>> Am Thu, 22 Nov 2018 14:14:11 +0100
>>> schrieb Jan Kiszka <jan.kiszka@siemens.com>:
>>>    
>>>> On 22.11.18 14:12, Henning Schild wrote:
>>>>> I got a report that bitbake 1.40 and this one are affected by a
>>>>> "gitsm://" bug. Still waiting for details but this will only fix
>>>>> one new bitbake bug.
>>>>> Was there a reason to bump, except wanting to stay up to date?
>>>>
>>>> Broken multiconfig in current next. So far a downstream issue
>>>> (jailhouse-images, possibly other multiconfig-using layers), with
>>>> patch 3 then also an upstream topic. But patch 3 is needed for
>>>> other reasons (see log).
>>>
>>> Is that the answer to 1.37->1.40 or just 1.40 -> this ?
>>>    
>>
>> The step 1.37->1.40 caused the multiconfig problem
>> (http://lists.openembedded.org/pipermail/bitbake-devel/2018-November/019558.html)
>> that is now fixed with this update again.
> 
> I got that, i was already thinking about going back to 1.37 ... maybe.

Well, if we cannot sort out the gitsm issue AND it is blocking for you, I would 
consider that.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2018-11-22 14:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-22 12:58 [PATCH 0/3] Bitbake fix, kernel-specific package naming Jan Kiszka
2018-11-22 12:58 ` [PATCH 1/3] bitbake: Update to fixed master revision Jan Kiszka
2018-11-22 13:12   ` Henning Schild
2018-11-22 13:14     ` Jan Kiszka
2018-11-22 13:18       ` Henning Schild
2018-11-22 13:25         ` Jan Kiszka
2018-11-22 13:58           ` Henning Schild
2018-11-22 14:28             ` Jan Kiszka [this message]
2018-11-22 15:36               ` Henning Schild
2018-11-22 15:42                 ` Jan Kiszka
2018-11-22 13:19       ` Jan Kiszka
2018-11-23 11:27   ` Maxim Yu. Osipov
2018-11-22 12:58 ` [PATCH 2/3] RECIPE-API-CHANGELOG: Reorder and capitalize sentences Jan Kiszka
2018-11-22 13:10   ` [PATCH v2 " Jan Kiszka
2018-11-23 11:28     ` Maxim Yu. Osipov
2018-11-22 12:58 ` [PATCH 3/3] Append KERNEL_NAME to dependent custom modules and u-boot-script Jan Kiszka
2018-11-23 11:28   ` Maxim Yu. Osipov
2018-11-23 11:34     ` Jan Kiszka
2018-11-23 11:38       ` [PATCH v2 " Jan Kiszka
2018-11-23 12:35         ` 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=3222ef02-53d9-30b0-4121-f20888a69e75@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.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