From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: overseers@sourceware.org, Carlos O'Donell <carlos@redhat.com>
Subject: Re: python3 mod_wsgi and patchwork
Date: Sun, 01 Dec 2019 17:21:00 -0000 [thread overview]
Message-ID: <0b0b814b-e466-0c2d-7efa-7e497a44cc2e@gotplt.org> (raw)
In-Reply-To: <20191201165931.GD2801580@elastic.org>
On 01/12/19 10:29 pm, Frank Ch. Eigler wrote:
> Hi -
>
>> [...] Can we upgrade these packages to enable the upgrade? It would
>> be ideal if we do a full OS upgrade to a newer version because I
>> suspect I'll run into more package version issues as I upgrade to
>> newer versions of patchwork; I'm updating a year at a time (i.e. now
>> I'm trying the 2015 version) and I've got a few years worth of
>> patchwork updates to go through :)
>
> The current sourceware server runs up-to-date RHEL 6, and is limited
> to packages distributed for that OS by RH or via Fedora EPEL.
> Updating the complete OS in situ is not practical, but the new
> sourceware server is under construction that will use CentOS 8 - so
> python3 will come with it.
That sounds great, do you know when the new sourceware server will be
deployed?
> EPEL does include a build of python 3.4, so we might try it, but if it
> interferes with the system, we can't hold onto it. Are you sure that
> e.g. mod_wsgi is necessary here, as opposed to reverse-proxying or
> calling out to the patchwork code via normal cgi?
>
AFAICT, python3 is already installed, just that the installed mod_wsgi
cannot use it since it does not support python3. I didn't give cgi a
thought for the deployment; let me try that with python3 and get back to
you.
Siddhesh
next prev parent reply other threads:[~2019-12-01 17:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-01 16:24 Siddhesh Poyarekar
2019-12-01 16:59 ` Frank Ch. Eigler
2019-12-01 17:21 ` Siddhesh Poyarekar [this message]
2019-12-01 17:25 ` Frank Ch. Eigler
2019-12-05 7:22 ` Siddhesh Poyarekar
2019-12-06 21:49 ` Frank Ch. Eigler
2019-12-08 11:58 ` Siddhesh Poyarekar
[not found] ` <20191209222559.GA9370@elastic.org>
2019-12-10 8:33 ` Siddhesh Poyarekar
2019-12-01 19:09 ` Yaakov Selkowitz
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=0b0b814b-e466-0c2d-7efa-7e497a44cc2e@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=carlos@redhat.com \
--cc=fche@elastic.org \
--cc=overseers@sourceware.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).