From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
Anthony PERARD <anthony.perard@vates.tech>,
Stefano Stabellini <sstabellini@kernel.org>,
Michal Orzel <michal.orzel@amd.com>,
Doug Goldstein <cardoe@cardoe.com>
Subject: Re: [PATCH] CI: Fix package installation for Coverity run
Date: Wed, 6 Nov 2024 13:11:42 +0000 [thread overview]
Message-ID: <7ab2705e-02ba-4e5f-8dd9-ac00a93ba39a@citrix.com> (raw)
In-Reply-To: <ZytVxKOtQfR7DWeX@macbook>
On 06/11/2024 11:40 am, Roger Pau Monné wrote:
> On Tue, Nov 05, 2024 at 08:46:03PM +0000, Andrew Cooper wrote:
>> Something has changed recently in the Github Actions environment and the
>> golang metapacakge resolves to something that no longer exists:
>>
>> https://github.com/xen-project/xen/actions/runs/11539340171/job/32120834909
>>
>> Update metadata before installing, which fixes things.
>>
>> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> Acked-by: Roger Pau Monné <roger.pau@citrix.com>
>
> Seems like the current Ubuntu image has a stale apt cache? It's good
> practice to update before we install anyway.
Thanks, and yeah. As chance would have it, the problem resolved itself
in this mornings run, but we should take the patch anyway.
A couple of weeks ago, they did strip out one of the versions of Go, but
it wasn't the version of Go we were trying to use. But in hindsight,
that doesn't mean that the metadata was kept properly up to date.
~Andrew
next prev parent reply other threads:[~2024-11-06 13:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 20:46 [PATCH] CI: Fix package installation for Coverity run Andrew Cooper
2024-11-06 11:40 ` Roger Pau Monné
2024-11-06 13:11 ` Andrew Cooper [this message]
2024-11-06 13:01 ` Stefano Stabellini
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=7ab2705e-02ba-4e5f-8dd9-ac00a93ba39a@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=cardoe@cardoe.com \
--cc=michal.orzel@amd.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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 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.