From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] required host packages on Travis CI
Date: Wed, 6 Nov 2019 16:12:40 +0900 [thread overview]
Message-ID: <20191106071238.GB22427@linaro.org> (raw)
In-Reply-To: <20191101130704.GP11173@bill-the-cat>
Tom,
On Fri, Nov 01, 2019 at 09:07:04AM -0400, Tom Rini wrote:
> On Fri, Nov 01, 2019 at 02:34:35PM +0900, AKASHI Takahiro wrote:
> > Tom,
> >
> > On Wed, Oct 30, 2019 at 07:17:29AM -0400, Tom Rini wrote:
> > > On Wed, Oct 30, 2019 at 03:30:58PM +0900, AKASHI Takahiro wrote:
> > >
> > > > Hi Tom,
> > > >
> > > > In test/py/README.md, all the required host packages and their
> > > > versions to be used on 14.04(Trusty) are listed. On the other hand,
> > > > ".travis.yml" names a similar but different list of packages.
> > > > The latter also specifies the distribution to be used, which is
> > > > xenial(16.04).
> > > >
> > > > * How would like to sync those two different lists?
> > > > * Do you still think it appropriate to mention the "tested versions"
> > > > in README.md at all?
> > >
> > > The README is woefully out of date and I addressed that as part of:
> > > http://patchwork.ozlabs.org/project/uboot/list/?series=138421
> >
> > Oooops, I haven't noticed it.
> >
> > > Please note that moving forward, the GitLab and Azure CI files need to
> > > be kept up to date as well, but with at least one of them being updated
> > > I can help with the other two. Thanks!
> >
> > Although I don't understand what you mean above very well,
> > some questions:
> > 1) Is it good enough just to put a package name in .travis.yml's addons
> > if all the required binaries (commands) are installed in standard
> > PATH?
>
> For Travis, the list of packages there is what we apt-get install, so
> yes, it's found in the normal PATH and we can add to that as needed.
Good.
> > 2) I need efitools package, but a version provided in xenial(16.04) is
> > quite old and some command has a fatal bug. So my current py test
> > will fail.
> > We need v1.5.2 or later of efitools, which is only available
> > in cosmic(18.10) and later.
> > How can we address this issue? Do we need some script to build efitools
> > on our own on GitLab/Travis server?
>
> Currently, Travis, GitLab and Azure all use Bionic. Is the version of
> the tool available there good enough?
Not really. The version in Bionic(18.04) is still v1.4.2.
Only Cosmic(18.10) and later support v1.8.1, which should work.
> If not, can we grab only the
> tool .deb and install that by hand? We have to do that for libmpfr4 for
> example today.
From where do you fetch a pre-built package of libmpfr4?
future release of ubuntu?
If so, we may want to try one from Cosmic or later.
> If we can't then yes, this is yet another thing that we
> need to figure out a better way of dealing with between Travis (where we
> build QEMU as needed) and GitLab/Azure (which uses a Docker container we
> manage, and so build QEMU once).
Or I don't think it difficult to build it on our own
as it depends only on libefi, sbsigntool and openssl (command).
>
> > 3) (Not specific to secure boot test)
> > Does "su" or "sudo" command work on Travis CI server?
>
> sudo is available and is working today in all 3 CI servers.
Good.
Thanks,
-Takahiro Akashi
> --
> Tom
next prev parent reply other threads:[~2019-11-06 7:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 6:30 [U-Boot] required host packages on Travis CI AKASHI Takahiro
2019-10-30 11:17 ` Tom Rini
2019-11-01 5:34 ` AKASHI Takahiro
2019-11-01 13:07 ` Tom Rini
2019-11-06 7:12 ` AKASHI Takahiro [this message]
2019-11-06 12:29 ` Tom Rini
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=20191106071238.GB22427@linaro.org \
--to=takahiro.akashi@linaro.org \
--cc=u-boot@lists.denx.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