From: Michael Roth <michael.roth@amd.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Thomas Huth <thuth@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
qemu-stable <qemu-stable@nongnu.org>
Subject: Re: QEMU stable 7.2.1
Date: Thu, 6 Apr 2023 10:01:26 -0500 [thread overview]
Message-ID: <20230406150126.tan4npfartb4oyhm@amd.com> (raw)
In-Reply-To: <199575b7-b4ce-b502-a1dd-d5f1174c0b87@msgid.tls.msk.ru>
On Thu, Apr 06, 2023 at 09:54:55AM +0300, Michael Tokarev wrote:
> 06.04.2023 09:48, Thomas Huth пишет:
> ..>> There's one minor caveat still, though: it is missing in the
> > > "Full list of releases" for whatever reason. Dunno how that
> > > happened, maybe that page hasn't been (re)generated yet.
> >
> > FWIW, I can see it on https://download.qemu.org/ now.
>
> I still can't, no matter how many times I hit browser "Reload"
> button, or try another browser or even another computer.
>
> It's available as a direct link but not in the listing page.
Yah... I'm noticing the same issue with 8.0.0-rc3 not showing up under
"Full list of releases" either. 8.0.0-rc2 shows up fine however, and I'm
not aware of any changes between -rc2 and -rc3 that would affect how
these pages are generated.
The associated gitlab build jobs for the latest qemu-web.git update look
okay to me too:
https://gitlab.com/qemu-project/qemu-web/-/pipelines/830133154/builds
I'm not even sure this page is actually generated by those jobs though,
it just seems like a direct link to whatever download.qemu.org statically
points to. So maybe there something else server-side that might be going
wrong?
I suppose it could just be some aggressive caching somewhere
server-side. I've never actually checked the "Full list of releases"
right after uploading, so it's possible it takes ~days to refresh and
we just happen to be noticing that now.
-Mike
>
> /mjt
>
next prev parent reply other threads:[~2023-04-06 15:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 11:54 QEMU stable 7.2.1 Michael Tokarev
2023-04-05 13:58 ` Michael Roth via
2023-04-05 14:16 ` Michael Tokarev
2023-04-05 18:57 ` Michael Roth
2023-04-05 19:25 ` Peter Maydell
2023-04-05 21:06 ` Michael Roth
2023-04-06 6:33 ` Michael Tokarev
2023-04-06 6:48 ` Thomas Huth
2023-04-06 6:54 ` Michael Tokarev
2023-04-06 15:01 ` Michael Roth [this message]
2023-04-06 14:32 ` Michael Roth
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=20230406150126.tan4npfartb4oyhm@amd.com \
--to=michael.roth@amd.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=thuth@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 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.