qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: luoyonggang@gmail.com
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	qemu-level <qemu-devel@nongnu.org>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [PATCH] cirrus.yml: Replace the hard-coded python-sphinx version with the generic one
Date: Tue, 12 Jan 2021 10:12:48 +0100	[thread overview]
Message-ID: <d7e3d0cf-f8d3-0772-1098-f98af7d27e94@redhat.com> (raw)
In-Reply-To: <CAE2XoE_pKkoW9=CojK1TumH10uf_rCDSKNLS-AAPH51QXP2DzA@mail.gmail.com>

On 11/01/2021 21.16, 罗勇刚(Yonggang Luo) wrote:
> 
> 
> On Mon, Jan 11, 2021 at 6:34 PM Thomas Huth <thuth@redhat.com 
> <mailto:thuth@redhat.com>> wrote:
>  >
>  > The mingw-w64-x86_64-python-sphinx-2.3.1 package has been removed from
>  > the server, so the windows_msys2_task is currently failing. Replace the
>  > old version with the current generic one to fix the issue (the current
>  > version seems to work fine now, too).
>  >
>  > Signed-off-by: Thomas Huth <thuth@redhat.com <mailto:thuth@redhat.com>>
>  > ---
>  >  Successful run (with sphinx building the docs) can be seen here:
>  > https://cirrus-ci.com/task/6568987054047232 
> <https://cirrus-ci.com/task/6568987054047232>
>  >
>  >  .cirrus.yml | 6 +-----
>  >  1 file changed, 1 insertion(+), 5 deletions(-)
>  >
>  > diff --git a/.cirrus.yml b/.cirrus.yml
>  > index 3907e036da..886addedd3 100644
>  > --- a/.cirrus.yml
>  > +++ b/.cirrus.yml
>  > @@ -117,12 +117,8 @@ windows_msys2_task:
>  >            mingw-w64-x86_64-curl \
>  >            mingw-w64-x86_64-gnutls \
>  >            mingw-w64-x86_64-libnfs \
>  > +          mingw-w64-x86_64-python-sphinx
>  >            "
>  > -        bitsadmin /transfer msys_download /dynamic /download /priority 
> FOREGROUND `
>  > - 
> https://repo.msys2.org/mingw/x86_64/mingw-w64-x86_64-python-sphinx-2.3.1-1-any.pkg.tar.xz 
> <https://repo.msys2.org/mingw/x86_64/mingw-w64-x86_64-python-sphinx-2.3.1-1-any.pkg.tar.xz> 
> `
>  > -          C:\tools\mingw-w64-x86_64-python-sphinx-2.3.1-1-any.pkg.tar.xz
>  > -        C:\tools\msys64\usr\bin\bash.exe -lc "pacman --noconfirm -U 
> /c/tools/mingw-w64-x86_64-python-sphinx-2.3.1-1-any.pkg.tar.xz"
>  > -        del C:\tools\mingw-w64-x86_64-python-sphinx-2.3.1-1-any.pkg.tar.xz
>  >          C:\tools\msys64\usr\bin\bash.exe -lc "rm -rf 
> /var/cache/pacman/pkg/*"
>  >          cd C:\tools\msys64
>  >          echo "Start archive"
>  > --
>  > 2.27.0
>  >
> Hi, I've done that in my previous patch and queued by Paolo Bonzini 4 days, 
> 8 hours ago
> 
> https://patchew.org/QEMU/20210107101919.80-1-luoyonggang@gmail.com/ 

Ah, alright, then please ignore my patch here!

  Thanks,
   Thomas



      reply	other threads:[~2021-01-12  9:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-11 10:34 [PATCH] cirrus.yml: Replace the hard-coded python-sphinx version with the generic one Thomas Huth
2021-01-11 15:53 ` Philippe Mathieu-Daudé
2021-01-11 20:16 ` 罗勇刚(Yonggang Luo)
2021-01-12  9:12   ` Thomas Huth [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=d7e3d0cf-f8d3-0772-1098-f98af7d27e94@redhat.com \
    --to=thuth@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=f4bug@amsat.org \
    --cc=luoyonggang@gmail.com \
    --cc=qemu-devel@nongnu.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 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 NNTP newsgroup(s).