From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: libc-alpha@sourceware.org
Cc: DJ Delorie <dj@redhat.com>, Carlos O'Donell <carlos@redhat.com>,
Mark Wielaard <mjw@gnu.org>
Subject: Re: patchwork upgrade week
Date: Wed, 22 Jun 2022 12:23:56 +0530 [thread overview]
Message-ID: <c4030cfc-66d3-d99e-5a62-835a977a5b20@gotplt.org> (raw)
In-Reply-To: <ece4a51a-4e42-cbab-c66c-4bf5e68bff5f@gotplt.org>
On 20/06/2022 15:56, Siddhesh Poyarekar wrote:
> Hello,
>
> This week I'm going to attempt to do some updates to the patchwork
> infrastructure to get it up to the latest version. You'll likely see
> tiny downtimes or if I mess up, large periods of it :D A bulk of the
> manual patchwork usage happens on Mondays during the review call, so I'm
> going to start after the call.
>
> If you see patches that have gone missing off patchwork or are having
> any trouble with your account, please let me know.
This is now done. We're at patchwork 3.0.5, which is the latest
available. Our django installation is at 3.1.14 because 3.1 is the
latest patchwork officially claims to support at the moment.
I did a quick test with django 3.2.13 and the server did come up but
with some warnings. Hopefully once patchwork is updated to support this
and future updates will be easy enough.
I have changed things around a bit in the sourceware patchwork directory
and have documented steps for testing and deploying upgrades to
patchwork, django and anything else in a README file in the home directory.
Cheers,
Sid
next prev parent reply other threads:[~2022-06-22 6:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 10:26 Siddhesh Poyarekar
2022-06-22 6:53 ` Siddhesh Poyarekar [this message]
2022-06-22 21:27 ` Mark Wielaard
2022-06-23 2:16 ` Siddhesh Poyarekar
2022-06-23 7:55 ` Mark Wielaard
2022-06-23 8:39 ` Siddhesh Poyarekar
2022-06-27 17:23 ` DJ Delorie
2022-07-01 11:04 ` Mark Wielaard
2022-07-01 21:01 ` DJ Delorie
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=c4030cfc-66d3-d99e-5a62-835a977a5b20@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=carlos@redhat.com \
--cc=dj@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=mjw@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).