From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users@googlegroups.com
Subject: Re: [PATCH] scripts/ci_build.sh: Don't fail on bullseye build errors
Date: Tue, 11 Aug 2020 09:01:32 +0200 [thread overview]
Message-ID: <aef28aaf-386e-2cd8-597b-68d73c5910dd@siemens.com> (raw)
In-Reply-To: <20200730160908.GC16281@yssyq.m.ilbers.de>
On 30.07.20 18:09, Baurzhan Ismagulov wrote:
> Hello Jan,
>
> On Mon, Jun 22, 2020 at 09:39:04AM +0200, Jan Kiszka wrote:
>> I'm carrying a disabling patch for bullseye in my queue as well.
>>
>> There are two issues, in fact. The bigger one is the above. The smaller
>> one is that cowsay needs a refreshment to build again, but only for
>> bullseye.
>
> Could you please share the cowsay one, too?
We need to bump the cowsay git uri to bullseye compatible revision while
keeping it at the current one for buster and before.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2020-08-11 7:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 20:08 Baurzhan Ismagulov
2020-06-22 7:39 ` Jan Kiszka
2020-07-30 16:09 ` Baurzhan Ismagulov
2020-08-11 7:01 ` Jan Kiszka [this message]
2020-06-22 10:42 ` Henning Schild
2020-07-30 16:08 ` Baurzhan Ismagulov
2020-08-18 11:23 ` Henning Schild
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=aef28aaf-386e-2cd8-597b-68d73c5910dd@siemens.com \
--to=jan.kiszka@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