From: Chuck Lever <chuck.lever@oracle.com>
To: Jeff Layton <jlayton@kernel.org>, kdevops@lists.linux.dev
Cc: Scott Mayhew <smayhew@redhat.com>,
Anna Schumaker <anna@kernel.org>,
Olga Kornievskaia <aglo@umich.edu>
Subject: Re: [PATCH kdevops v2] pynfs: install xdrlib3
Date: Tue, 11 Feb 2025 11:52:13 -0500 [thread overview]
Message-ID: <19a426e7-e13e-428b-b41b-9cd6bd500d7d@oracle.com> (raw)
In-Reply-To: <20250211-xdrlib-v2-1-95a39f4e8b02@kernel.org>
On 2/11/25 11:38 AM, Jeff Layton wrote:
> As of python 3.13, xdrlib is no longer included. Install xdrlib3, which
> is a fork of the original xdrlib module.
>
> Signed-off-by: Jeff Layton <jlayton@kernel.org>
> ---
> Changes in v2:
> - use ansible pip module instead of running shell command
> - Link to v1: https://lore.kernel.org/r/20250211-xdrlib-v1-1-71e9c96948a8@kernel.org
> ---
> playbooks/roles/pynfs/tasks/main.yml | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/playbooks/roles/pynfs/tasks/main.yml b/playbooks/roles/pynfs/tasks/main.yml
> index c6add8e47fec298e2c7351805a42307ee8398e3c..d3b8832409b17fbc03a2a3e625e0d319a45af919 100644
> --- a/playbooks/roles/pynfs/tasks/main.yml
> +++ b/playbooks/roles/pynfs/tasks/main.yml
> @@ -70,6 +70,11 @@
> when:
> - not kdevops_workflows_dedicated_workflow|bool
>
> +- name: Install xdrlib3
> + tags: [ 'pynfs' ]
> + ansible.builtin.pip:
> + name: xdrlib3
> +
> - name: Build pynfs
> tags: [ 'pynfs' ]
> command: ./setup.py build
>
> ---
> base-commit: 447b2ca0ac70d6538e62c05a3216434f12418470
> change-id: 20250211-xdrlib-bd75594d67dc
>
> Best regards,
Reviewed-by: Chuck Lever <chuck.lever@oracle.com>
--
Chuck Lever
next prev parent reply other threads:[~2025-02-11 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 16:38 [PATCH kdevops v2] pynfs: install xdrlib3 Jeff Layton
2025-02-11 16:52 ` Chuck Lever [this message]
2025-02-12 7:41 ` Daniel Gomez
2025-02-12 13:00 ` Chuck Lever
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=19a426e7-e13e-428b-b41b-9cd6bd500d7d@oracle.com \
--to=chuck.lever@oracle.com \
--cc=aglo@umich.edu \
--cc=anna@kernel.org \
--cc=jlayton@kernel.org \
--cc=kdevops@lists.linux.dev \
--cc=smayhew@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.