From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: Claudius Heine <claudius.heine.ext@siemens.com>,
isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: Re: [PATCH 0/6] Fixing base-apt and ci
Date: Thu, 23 May 2019 14:26:46 +0200 [thread overview]
Message-ID: <56dee74e-58a2-f4be-4e77-2e8c02638896@ilbers.de> (raw)
In-Reply-To: <58fdefa2-f662-1484-8e15-a84fbca30ff9@siemens.com>
On 5/23/19 2:21 PM, Claudius Heine wrote:
> Hi Maxim,
>
> On 23/05/2019 13.59, Maxim Yu. Osipov wrote:
>> Hi Claudius,
>>
>> It seems that you need to rebase first against the current 'next'.
>> Definitely, this relates to ci_build.
>
> Ok, if I understand your changes to ci_build, then those two patches
> might no longer be needed, since the they should have resolved those
> issues.
shebang fix is OK.
Thanks,
Maxim.
> But I will do a CI run to be sure.
>
> thx,
> Claudius
>
>>
>> Regards,
>> Maxim.
>>
>> On 5/23/19 1:39 PM, claudius.heine.ext@siemens.com wrote:
>>> From: Claudius Heine <ch@denx.de>
>>>
>>> Hi,
>>>
>>> this patchset depends on the "pre-processing pipeline and transient
>>> package
>>> replacement" patchset and fixes some issues related to the base-apt
>>> implementation and CI test.
>>>
>>> CI test:
>>> http://isar-build.org:8080/job/isar_claudius_ilbers_fast_ci/33/console
>>> (This run was probably triggered with 'ci_build.sh -f -r')
>>>
>>> regards,
>>> Claudius
>>>
>>> Claudius Heine (6):
>>> sdkchroot: remove 'copy-package-cache' from ROOTFS_FEATURES
>>> bitbake: added DISTRO to REPO_BASE_{DB_}DIR
>>> isar-bootstrap: fix DISTRO_APT_PREMIRRORS regex in case of cached
>>> build
>>> base-apt: fix issues with creating and using the base-apt repository
>>> ci_build.sh: Remove rpi-stretch if CROSS_BUILD and REPRO_BUILD
>>> ci_build.sh/repro: disable build of non-cached targets
>>>
>>> meta/classes/image-cache-extension.bbclass | 10 ++++++++++
>>> meta/conf/bitbake.conf | 4 ++--
>>> meta/recipes-core/isar-bootstrap/isar-bootstrap.inc | 3 ++-
>>> meta/recipes-devtools/sdkchroot/sdkchroot.bb | 2 +-
>>> scripts/ci_build.sh | 13 +++++++++++--
>>> 5 files changed, 26 insertions(+), 6 deletions(-)
>>>
>>
>>
>
--
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
prev parent reply other threads:[~2019-05-23 12:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 11:39 claudius.heine.ext
2019-05-23 11:39 ` [PATCH 1/6] sdkchroot: remove 'copy-package-cache' from ROOTFS_FEATURES claudius.heine.ext
2019-05-23 11:39 ` [PATCH 2/6] bitbake: added DISTRO to REPO_BASE_{DB_}DIR claudius.heine.ext
2019-05-23 11:39 ` [PATCH 3/6] isar-bootstrap: fix DISTRO_APT_PREMIRRORS regex in case of cached build claudius.heine.ext
2019-05-23 11:39 ` [PATCH 4/6] base-apt: fix issues with creating and using the base-apt repository claudius.heine.ext
2019-05-23 11:39 ` [PATCH 5/6] ci_build.sh: Remove rpi-stretch if CROSS_BUILD and REPRO_BUILD claudius.heine.ext
2019-05-23 11:39 ` [PATCH 6/6] ci_build.sh/repro: disable build of non-cached targets claudius.heine.ext
2019-05-23 11:59 ` [PATCH 0/6] Fixing base-apt and ci Maxim Yu. Osipov
2019-05-23 12:21 ` Claudius Heine
2019-05-23 12:26 ` Maxim Yu. Osipov [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=56dee74e-58a2-f4be-4e77-2e8c02638896@ilbers.de \
--to=mosipov@ilbers.de \
--cc=ch@denx.de \
--cc=claudius.heine.ext@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