All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Boyer <aboyer@pensando.io>
To: David Marchand <david.marchand@redhat.com>
Cc: dev <dev@dpdk.org>, Aaron Conole <aconole@redhat.com>,
	Michael Santana <maicolgabriel@hotmail.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH] ci: fix package installation in GitHub Actions
Date: Wed, 30 Dec 2020 13:00:03 -0500	[thread overview]
Message-ID: <1430424D-F3A9-4AB8-93F7-F1A38A7C33E6@pensando.io> (raw)
In-Reply-To: <CAJFAV8wskdjeqUFymq_Q-HHZ4M7b5ccth8LXueet7-QdFPWCXQ@mail.gmail.com>

Hello David,
I’m hitting this issue on the next/dpdk-next-net branch. Is there a way to pull the patch into all of the next-* branches so that others don’t hit it too?

For now I've pulled it into my own branch.

This Actions thing is cool. It’s a huge timesaver.

Thank you,
Andrew

> On Dec 21, 2020, at 12:27 PM, David Marchand <david.marchand@redhat.com> wrote:
> 
> On Sat, Dec 19, 2020 at 9:26 AM David Marchand
> <david.marchand@redhat.com> wrote:
>> 
>> APT cache must be updated to avoid trying to install an unavailable
>> version of a package.
>> 
>> Fixes: 87009585e293 ("ci: hook to GitHub Actions")
>> 
>> Signed-off-by: David Marchand <david.marchand@redhat.com>
> 
> Applied.
> 
> 
> -- 
> David Marchand
> 


  reply	other threads:[~2020-12-30 19:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-19  8:26 [dpdk-dev] [PATCH] ci: fix package installation in GitHub Actions David Marchand
2020-12-21 17:27 ` David Marchand
2020-12-30 18:00   ` Andrew Boyer [this message]
2021-01-04 12:26     ` Ferruh Yigit
2021-01-05  8:49     ` David Marchand

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=1430424D-F3A9-4AB8-93F7-F1A38A7C33E6@pensando.io \
    --to=aboyer@pensando.io \
    --cc=aconole@redhat.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=maicolgabriel@hotmail.com \
    --cc=thomas@monjalon.net \
    /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.