required host packages on Travis CI
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?
# I'm planning to update the list for UEFI secure boot test.
-Takahiro Akashi
Quoted 11 lines · AKASHI Takahiro
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
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!
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: <http://lists.denx.de/pipermail/u-boot/attachments/20191030/4bdd72d8/attachment.sig>
Tom,
Quoted 10 lines · Tom Rini
Quoted 8 lines · AKASHI Takahiro
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).
Quoted 6 lines
Quoted 3 lines
* 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.
Quoted 3 lines
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?
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?
3) (Not specific to secure boot test)
Does "su" or "sudo" command work on Travis CI server?
Thanks,
-Takahiro Akashi
Quoted 2 lines
Signature · 1 line
Tom
Quoted 26 lines · AKASHI Takahiro
Tom,
Quoted 10 lines · Tom Rini
Quoted 8 lines · AKASHI Takahiro
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).Quoted 6 lines
Quoted 3 lines
* 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=138421Oooops, I haven't noticed it.
Quoted 3 lines
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!
Quoted 5 lines
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.
Quoted 7 lines
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? If not, can we grab only the tool .deb and install that by hand? We have to do that for libmpfr4 for example today. 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).
Quoted 2 lines
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.
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: <http://lists.denx.de/pipermail/u-boot/attachments/20191101/bafc6afd/attachment.sig>
Tom,
Quoted 27 lines · Tom Rini
Quoted 26 lines · AKASHI Takahiro
Tom,
Quoted 10 lines · Tom Rini
Quoted 8 lines · AKASHI Takahiro
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).Quoted 6 lines
Quoted 3 lines
* 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=138421Oooops, I haven't noticed it.
Quoted 3 lines
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!
Quoted 8 lines
Quoted 5 lines
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.
Quoted 10 lines
Quoted 7 lines
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.
Quoted 3 lines
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.
Quoted 4 lines
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).
Quoted 5 lines
Quoted 3 lines
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
Quoted 2 lines
Signature · 1 line
Tom
Quoted 55 lines · AKASHI Takahiro
Tom,
Quoted 27 lines · Tom Rini
Quoted 26 lines · AKASHI Takahiro
Tom,
Quoted 10 lines · Tom Rini
Quoted 8 lines · AKASHI Takahiro
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).Quoted 6 lines
Quoted 3 lines
* 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=138421Oooops, I haven't noticed it.
Quoted 3 lines
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!
Quoted 8 lines
Quoted 5 lines
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.
Quoted 10 lines
Quoted 7 lines
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.
Quoted 7 lines
Quoted 3 lines
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.
We wget it from 16.04 and install it manually, as it's otherwise stand-alone. You would need to explore doing that for this tool, but grabbing from cosmic.
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: <http://lists.denx.de/pipermail/u-boot/attachments/20191106/784fd2a5/attachment.sig>