public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Andreas Reichel <andreas.reichel.ext@siemens.com>,
	"Maxim Yu. Osipov" <mosipov@ilbers.de>,
	Claudius Heine <ch@denx.de>,
	Henning Schild <henning.schild@siemens.com>
Cc: claudius.heine.ext@siemens.com, isar-users@googlegroups.com
Subject: Re: [PATCH v4 1/9] isar-bootstrap-host: disable DISTRO_APT_KEYS usage
Date: Tue, 30 Apr 2019 17:30:42 +0200	[thread overview]
Message-ID: <d19ca607-1e6f-e1a2-9e1c-12f94ccf8013@siemens.com> (raw)
In-Reply-To: <20190430152246.GA13521@iiotirae>

On 30.04.19 17:22, Andreas Reichel wrote:
> On Tue, Apr 30, 2019 at 04:30:46PM +0300, Maxim Yu. Osipov wrote:
>> On 4/30/19 12:34 PM, Andreas Reichel wrote:
>>> On Fri, Apr 26, 2019 at 11:41:16AM +0300, Maxim Yu. Osipov wrote:
>>>> Hi Claudius, Andreas,
>>>>
>>>> @Andreas
>>>> Your input is very welcome at this topic as you were busy with all this APT
>>>> keys stuff.
>>>>
>>>
>>> Thank you. Well in my eyes, Claudius delivers important changes to Isar
>>> which improve code quality and the build steps as a whole. Also as I
>>> know him, he is never ever interested in any personal "affairs" whatsoever,
>>> which I also learnt from his reviews on my code. He has a sharp mind and
>>> always tries to get out the best of the code up to his knowledge and
>>> techniques. Furthermore, if he may sometimes sound direct or even
>>> annoying to some - this is merely a personal question of how one focuses
>>> on mails. I also did not understand everything he criticized on my code
>>> in the beginning - but after I understood him, it was always great
>>> improvement. So, Maxim, I beg that you do not take anything personal on
>>> any mail, regarding any words or writing style but just focus on the
>>> code as I always try - which always helps to go on further with the
>>> project and to improve it. That's my input.
>>>
>>> Andreas
>>
>> I would prefer to focus on technical aspects of the modification under
>> review. Are you OK with this modification?
>>
> I am OK with these.
> 
> However I want MY patch series (version 9) merged before this one,
> because it is now very well reviewed and weeks old.
> And please don't argue with failed CI now. Investigating, understanding
> and fixing CI is a different topic and out of my scope.

So, to state this differently: You observation is that current next or master 
does not reliably build in Isar upstream CI, right? Then this issue would be of 
topmost priority to understand and resolve.

Andreas, Henning, Claudius, do we have current references to upstream CI build 
with that behaviour, even if that was sporadic?

Jan

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

  reply	other threads:[~2019-04-30 15:30 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-25 13:44 [PATCH v4 0/9] Cleanup rootfs creation claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 1/9] isar-bootstrap-host: disable DISTRO_APT_KEYS usage claudius.heine.ext
2019-04-25 18:20   ` Maxim Yu. Osipov
2019-04-26  7:36     ` Claudius Heine
2019-04-26  8:41       ` Maxim Yu. Osipov
2019-04-26 10:39         ` Claudius Heine
2019-04-26 10:45           ` Claudius Heine
2019-04-26 11:22             ` Maxim Yu. Osipov
2019-04-26 11:47               ` Jan Kiszka
2019-04-30  9:34         ` Andreas Reichel
2019-04-30 13:30           ` Maxim Yu. Osipov
2019-04-30 15:22             ` Andreas Reichel
2019-04-30 15:30               ` Jan Kiszka [this message]
2019-04-30 15:46               ` Maxim Yu. Osipov
2019-05-02 12:14                 ` Andreas Reichel
2019-04-26 11:31       ` Jan Kiszka
2019-04-26 11:50         ` Jan Kiszka
2019-05-14  9:22           ` Fwd: " Maxim Yu. Osipov
2019-05-14 11:32           ` Claudius Heine
2019-05-14 11:35             ` Claudius Heine
2019-04-25 13:44 ` [PATCH v4 2/9] isar-bootstrap-helper: move 'HOST_ARCH' and 'HOST_DISTRO' to base.bbclass claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 3/9] move 'HOST_DISTRO_APT_SOURCES' from bootstrap-helper to isar-bootstrap claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 4/9] buildchroot.bbclass: only cross build if HOST_ARCH != DISTRO_ARCH claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 5/9] isar-bootstrap/buildchroot/sdkchroot: refactor PF and WORKDIR claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 6/9] bitbake.conf: remove unneeded and differently used variables claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 7/9] image.bbclass: make IMAGE_ROOTFS overwritable claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 8/9] bitbake.conf: set default QEMU_ARCH variables claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 9/9] buildchroot/configscript: make creation of builder uid/gid idempotent claudius.heine.ext

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=d19ca607-1e6f-e1a2-9e1c-12f94ccf8013@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=andreas.reichel.ext@siemens.com \
    --cc=ch@denx.de \
    --cc=claudius.heine.ext@siemens.com \
    --cc=henning.schild@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