From: Petr Vorel <pvorel@suse.cz>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: Vitaly Chikunov <vt@altlinux.org>,
linux-integrity@vger.kernel.org,
Bruno Meneguele <bmeneg@redhat.com>
Subject: Re: [ima-evm-utils: PATCH 5/5] ima-evm-utils: travis: openssl gost engine
Date: Mon, 3 Aug 2020 15:07:55 +0200 [thread overview]
Message-ID: <20200803130755.GA30440@dell5510> (raw)
In-Reply-To: <1157c464d49cb6297fc2f20771d73a4cf7ce6599.camel@linux.ibm.com>
Hi all,
> On Fri, 2020-07-31 at 18:32 -0400, Mimi Zohar wrote:
> > > - Or even better, Bionic (which is supported by Travis) should have
> > > gost-engine already in the libengine-gost-openssl1.1 package.
> > > In that case `.travis.yml` should have `dist: bionic`.
> > > https://docs.travis-ci.com/user/reference/bionic/
> > Yes, for the internal git repo I made this change. The internal
> > travis support for bionic is different than the external
> > travis. I'll post what I have as an RFC.
> The internal travis support on ppc defaults to using Bionic, but the
> way of specifying it is different.
> +os: linux-ppc64le
> language: C
> addons:
> apt:
@Mimi: As I wrote, I'd suggest moving to docker based travis. I can do it once
other issues are addressed, if this setup work for your internal travis support
as well. See examples .travis.yml [1] [2], builds: [3] [4].
Advantages are more realistic builds for distro maintainers (different libc and
libraries versions, you can test old and new distro releases, etc), but maybe
that's not what you want/need.
Disadvantage is that sometimes docker releases have temporary packaging related
issues (first build in [3]; failure in first build [4] is a bug in LTP, corner
case, which would be otherwise undiscovered a long time).
Kind regards,
Petr
[1] https://github.com/linux-test-project/ltp/blob/master/.travis.yml
[2] https://github.com/iputils/iputils/blob/master/.travis.yml
[3] https://travis-ci.org/github/iputils/iputils/builds/714445071
[4] https://travis-ci.org/github/linux-test-project/ltp/builds/714400199
next prev parent reply other threads:[~2020-08-03 13:07 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 18:24 [ima-evm-utils: PATCH 0/5] initial travis support Mimi Zohar
2020-07-31 18:24 ` [ima-evm-utils: PATCH 1/5] ima-evm-utils: travis: define travis.yml Mimi Zohar
2020-07-31 18:24 ` [ima-evm-utils: PATCH 2/5] ima-evm-utils: travis: download, compile, and install a swTPM Mimi Zohar
2020-07-31 18:24 ` [ima-evm-utils: PATCH 3/5] ima-evm-utils: travis: dependency on TSS for initializing software TPM Mimi Zohar
2020-07-31 18:24 ` [ima-evm-utils: PATCH 4/5] ima-evm-utils: travis: support tpm2-tss Mimi Zohar
2020-07-31 18:24 ` [ima-evm-utils: PATCH 5/5] ima-evm-utils: travis: openssl gost engine Mimi Zohar
2020-07-31 18:56 ` Vitaly Chikunov
2020-07-31 20:18 ` Petr Vorel
2020-07-31 20:26 ` Vitaly Chikunov
2020-07-31 20:40 ` Petr Vorel
2020-07-31 21:06 ` Vitaly Chikunov
2020-07-31 22:32 ` Mimi Zohar
2020-08-03 3:09 ` Mimi Zohar
2020-08-03 13:07 ` Petr Vorel [this message]
2020-08-03 14:29 ` Mimi Zohar
2020-08-03 16:46 ` Petr Vorel
2020-08-03 17:16 ` Mimi Zohar
2020-08-04 7:22 ` Petr Vorel
2020-08-04 7:54 ` Petr Vorel
2020-08-04 13:23 ` Mimi Zohar
2020-08-05 9:42 ` Petr Vorel
2020-08-05 13:31 ` Mimi Zohar
2020-08-05 16:23 ` Vitaly Chikunov
2020-08-05 16:18 ` Vitaly Chikunov
2020-08-11 17:33 ` Petr Vorel
2020-08-11 22:04 ` Mimi Zohar
2020-08-12 13:05 ` Petr Vorel
2020-08-13 18:15 ` Mimi Zohar
2020-08-13 18:28 ` Petr Vorel
2020-08-13 20:11 ` Mimi Zohar
2020-08-03 16:32 ` Vitaly Chikunov
2020-08-03 16:36 ` Petr Vorel
2020-08-03 17:26 ` Mimi Zohar
2020-08-03 18:42 ` Vitaly Chikunov
2020-08-03 2:53 ` Mimi Zohar
2020-08-03 13:11 ` Petr Vorel
2020-08-03 14:33 ` Mimi Zohar
2020-08-04 12:05 ` [ima-evm-utils: PATCH v1 " Mimi Zohar
2020-08-04 14:45 ` Vitaly Chikunov
2020-08-04 18:11 ` Mimi Zohar
2020-07-31 20:19 ` [ima-evm-utils: PATCH 0/5] initial travis support Petr Vorel
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=20200803130755.GA30440@dell5510 \
--to=pvorel@suse.cz \
--cc=bmeneg@redhat.com \
--cc=linux-integrity@vger.kernel.org \
--cc=vt@altlinux.org \
--cc=zohar@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.