All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Wang <liwang@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/1] travis: Add libefivar support
Date: Wed, 11 Nov 2020 17:22:09 +0800	[thread overview]
Message-ID: <CAEemH2cP8Tub5UjBcRoo2Nkwtku7KjtUYP9U9v75GHEywe=aXw@mail.gmail.com> (raw)
In-Reply-To: <20201110134625.GA6482@pevik>

On Tue, Nov 10, 2020 at 9:46 PM Petr Vorel <pvorel@suse.cz> wrote:

> Hi,
>
> > Travis CI:
> > https://travis-ci.org/github/pevik/ltp/builds/742684375
>
> Looks like Debian does not ship libefivar-dev for ppc64el
> https://travis-ci.org/github/pevik/ltp/jobs/742684377


From Travis CI, the CentOS8 reports miss efivar-devel package too.

Maybe fix it by the following?

--- a/travis/fedora.sh
+++ b/travis/fedora.sh
@@ -9,11 +9,11 @@ yum -y install \
        clang \
        gcc \
        findutils \
-       efivar-devel \
        libtirpc \
        libtirpc-devel \
        pkg-config \
        redhat-lsb-core

-# CentOS 8 doesn't have libmnl-devel
+# CentOS 8 doesn't have libmnl-devel and efivar-devel
 yum -y install libmnl-devel || yum -y install libmnl
+yum -y --skip-broken install efivar-devel

-- 
Regards,
Li Wang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20201111/0d77aaab/attachment-0001.htm>

  reply	other threads:[~2020-11-11  9:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10 12:00 [LTP] [PATCH 1/1] travis: Add libefivar support Petr Vorel
2020-11-10 13:46 ` Petr Vorel
2020-11-11  9:22   ` Li Wang [this message]
2020-11-11  9:31     ` Petr Vorel
2021-02-06 19:54     ` 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='CAEemH2cP8Tub5UjBcRoo2Nkwtku7KjtUYP9U9v75GHEywe=aXw@mail.gmail.com' \
    --to=liwang@redhat.com \
    --cc=ltp@lists.linux.it \
    /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.