qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Wainer dos Santos Moschetta <wainersm@redhat.com>
To: qemu-devel@nongnu.org
Cc: fam@euphon.net, philmd@redhat.com, alex.bennee@linaro.org
Subject: [RFC PATCH 2/6] travis.yml: Fix 'GCC9 with sanitizers' job on Ubuntu Bionic
Date: Mon, 17 Feb 2020 15:16:05 -0500	[thread overview]
Message-ID: <20200217201609.788825-3-wainersm@redhat.com> (raw)
In-Reply-To: <20200217201609.788825-1-wainersm@redhat.com>

This changes the 'GCC9 with sanitizers' job to run correctly
on Ubuntu Bionic. It was needed to solved the problems:

1) The new environment changed how APT sources are handled,
resulting on the error:

```
Disallowing sources: ubuntu-toolchain-r-test

To add unlisted APT sources, follow instructions in https://docs.travis-ci.com/user/installing-dependencies#Installing-Packages-with-the-APT-Addon
```

Thus, the reference to 'ubuntu-toolchain-r-test' is passed via
'sourceline' now.

2) Adjusted the name of some packages

3) Libssh-dev is not installed due known issue on Bionic

Signed-off-by: Wainer dos Santos Moschetta <wainersm@redhat.com>
---
 .travis.yml | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/.travis.yml b/.travis.yml
index e46c44bbee..232f84d196 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -336,7 +336,7 @@ matrix:
           update: true
           sources:
             # PPAs for newer toolchains
-            - ubuntu-toolchain-r-test
+            - sourceline: 'ppa:ubuntu-toolchain-r/test'
           packages:
             # Extra toolchains
             - gcc-9
@@ -346,7 +346,7 @@ matrix:
             - libattr1-dev
             - libbrlapi-dev
             - libcap-ng-dev
-            - libgnutls-dev
+            - libgnutls28-dev
             - libgtk-3-dev
             - libiscsi-dev
             - liblttng-ust-dev
@@ -354,14 +354,15 @@ matrix:
             - libncurses5-dev
             - libnss3-dev
             - libpixman-1-dev
-            - libpng12-dev
+            - libpng-dev
             - librados-dev
             - libsdl2-dev
             - libsdl2-image-dev
             - libseccomp-dev
             - libspice-protocol-dev
             - libspice-server-dev
-            - libssh-dev
+# https://bugs.launchpad.net/qemu/+bug/1838763
+#            - libssh-dev
             - liburcu-dev
             - libusb-1.0-0-dev
             - libvte-2.91-dev
-- 
2.24.1



  parent reply	other threads:[~2020-02-17 20:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-17 20:16 [RFC PATCH 0/6] Travis: Change default environment to Ubuntu Bionic Wainer dos Santos Moschetta
2020-02-17 20:16 ` [RFC PATCH 1/6] travis.yml: Bump " Wainer dos Santos Moschetta
2020-02-17 20:16 ` Wainer dos Santos Moschetta [this message]
2020-02-17 20:16 ` [RFC PATCH 3/6] travis.yml: Fix 'GCC check-acceptance' job on " Wainer dos Santos Moschetta
2020-02-17 20:16 ` [RFC PATCH 4/6] travis.yml: Fix 'Clang (main-softmmu)' " Wainer dos Santos Moschetta
2020-02-17 20:16 ` [RFC PATCH 5/6] travis.yml: Run '[ppc64] GCC check-tcg' " Wainer dos Santos Moschetta
2020-02-17 20:16 ` [RFC PATCH 6/6] travis.yml: Run '[aarch64] " Wainer dos Santos Moschetta

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=20200217201609.788825-3-wainersm@redhat.com \
    --to=wainersm@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=fam@euphon.net \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).