From: Stefano Brivio <sbrivio@redhat.com>
To: passt-dev@passt.top, passt-user@passt.top
Cc: Paul Holzinger <pholzing@redhat.com>
Subject: Re: new version 2022_10_26.f212044 available
Date: Thu, 27 Oct 2022 12:56:33 +0200 [thread overview]
Message-ID: <20221027125633.279ef28e@elisabeth> (raw)
In-Reply-To: <20221027111255.4a12293a@elisabeth>
On Thu, 27 Oct 2022 11:12:55 +0200
Stefano Brivio <sbrivio@redhat.com> wrote:
> Actually, it's:
>
> On Thu, 27 Oct 2022 09:00:26 +0200
> Stefano Brivio <sbrivio@redhat.com> wrote:
>
> > - Copr (CentOS Stream, EPEL, Fedora, Mageia, openSUSE):
> > https://copr.fedorainfracloud.org/coprs/sbrivio/passt/build/4991606/
> > permanent mirror: https://passt.top/builds/copr/0^20221026.ge4df8b0/
>
> https://copr.fedorainfracloud.org/coprs/sbrivio/passt/build/4992985/
>
> ...and the mirror hasn't picked it up yet, because the index at:
> https://download.copr.fedorainfracloud.org/results/sbrivio/passt/srpm-builds/
>
> is stale. I filed https://pagure.io/fedora-infrastructure/issue/10960
> for this. Meanwhile, if you're looking for Copr builds, use direct
> links from https://copr.fedorainfracloud.org/coprs/sbrivio/passt/.
Solved. I wasn't aware of caching and existence of non-cached URLs:
https://docs.pagure.org/copr.copr/user_documentation.html#build-succeeded-but-i-don-t-see-the-built-results
I switched mirror and scripting to take versions from there now.
--
Stefano
prev parent reply other threads:[~2022-10-27 10:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 7:00 new version 2022_10_26.f212044 available Stefano Brivio
2022-10-27 9:12 ` Stefano Brivio
2022-10-27 10:56 ` Stefano Brivio [this message]
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=20221027125633.279ef28e@elisabeth \
--to=sbrivio@redhat.com \
--cc=passt-dev@passt.top \
--cc=passt-user@passt.top \
--cc=pholzing@redhat.com \
/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 IMAP folder(s).