From: Sumit Garg <sumit.garg@linaro.org>
To: Paul Barker <paul.barker.ct@bp.renesas.com>, robh+dt@kernel.org
Cc: u-boot@lists.denx.de, u-boot-amlogic@groups.io,
u-boot-custodians@lists.denx.de, trini@konsulko.com,
sjg@chromium.org, krzysztof.kozlowski+dt@linaro.org,
conor@kernel.org, neil.armstrong@linaro.org,
caleb.connolly@linaro.org, ff@shokubai.tech,
daniel.thompson@linaro.org, dgilmore@fedoraproject.org,
pbrobinson@gmail.com, ilias.apalodimas@linaro.org,
b.galvani@gmail.com, xypron.glpk@gmx.de, michal.simek@amd.com,
seanga2@gmail.com, rasmus.villemoes@prevas.dk, peng.fan@nxp.com,
jh80.chung@samsung.com, rfried.dev@gmail.com, marex@denx.de,
mibodhi@gmail.com, bb@ti.com, mark.kettenis@xs4all.nl,
festevam@gmail.com, nm@ti.com, andre.przywara@arm.com,
ijc@hellion.org.uk
Subject: Re: [PATCH v5 08/11] doc: devicetree: Updates for devicetree-rebasing subtree
Date: Mon, 19 Feb 2024 12:10:27 +0530 [thread overview]
Message-ID: <CAFA6WYPYSj4Am1jZMyAM-4VpxoqMbBiSOTSVMsjF2MabA-UeXQ@mail.gmail.com> (raw)
In-Reply-To: <e5eec82e-359d-45ad-a01d-6d852fe78d99@bp.renesas.com>
On Fri, 16 Feb 2024 at 16:17, Paul Barker <paul.barker.ct@bp.renesas.com> wrote:
>
> On 14/02/2024 13:32, Sumit Garg wrote:
> > On Wed, 14 Feb 2024 at 03:01, Paul Barker <paul.barker.ct@bp.renesas.com> wrote:
> >> On 02/02/2024 13:05, Sumit Garg wrote:
> >>> +Dependencies
> >>> +~~~~~~~~~~~~
> >>> +
> >>> +The DT schema project must be installed in order to validate the DT schema
> >>> +binding documents and validate DTS files using the DT schema. The DT schema
> >>> +project can be installed with pip::
> >>> +
> >>> + pip3 install dtschema
> >>
> >> Unfortunately this won't work on recent distro versions, e.g. on Debian
> >> 12 I get:
> >>
> >> error: externally-managed-environment
> >>
> >> × This environment is externally managed
> >> ╰─> To install Python packages system-wide, try apt install
> >> python3-xyz, where xyz is the package you are trying to
> >> install.
> >>
> >> If you wish to install a non-Debian-packaged Python package,
> >> create a virtual environment using python3 -m venv path/to/venv.
> >> Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
> >> sure you have python3-full installed.
> >>
> >> If you wish to install a non-Debian packaged Python application,
> >> it may be easiest to use pipx install xyz, which will manage a
> >> virtual environment for you. Make sure you have pipx installed.
> >>
> >> See /usr/share/doc/python3.11/README.venv for more information.
> >>
> >> note: If you believe this is a mistake, please contact your Python
> >> installation or OS distribution provider. You can override this, at the
> >> risk of breaking your Python installation or OS, by passing
> >> --break-system-packages.
> >> hint: See PEP 668 for the detailed specification.
> >>
> >> I don't have a good solution to recommend here - there's no consensus on
> >> how to install Python tools for use in development. You could use
> >> `pipx`, you could create a virtualenv, and I'm sure there are other
> >> options as well. Perhaps we just need to leave it up to the reader to
> >> find out how to install dtschema on their system.
> >
> > I suppose you haven't installed python3-pip package [1] on your Debian
> > 12. BTW, `pip3` is being used as the common way to install dtschema
> > [2]. Also, every user may not be aware about python virtual
> > environments. So it's better to provide the commonly used pip3 option
> > for installation.
>
> The python3-pip package is installed, it's the pip3 program that is
> printing the error message I saw. This is the new behaviour in Debian
> 12, also seen in rolling distributions like Arch Linux and OpenSuSE
> Tumbleweed since the middle of last year. There is a good guide to this
> from Python=>Speed [1] and more detail in the Python packaging spec [2].
> Sadly it's something we now have to live with in recent Linux distro
> releases, and I expect all distros will enable this in upcoming
> releases.
Okay I see, thanks for bringing it up. I hope Rob will take note of
this and update dtschema installation instructions [1] accordingly.
As part of v6, I will rather guide users towards the dtschema github
page in order to get installation instructions.
[1] https://github.com/devicetree-org/dt-schema/tree/main?tab=readme-ov-file#installing
-Sumit
>
> [1]: https://pythonspeed.com/articles/externally-managed-environment-pep-668/
> [2]: https://packaging.python.org/en/latest/specifications/externally-managed-environments/#externally-managed-environments
>
> Thanks,
>
> --
> Paul Barker
next prev parent reply other threads:[~2024-02-19 11:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 13:05 [PATCH v5 00/11] An effort to bring DT bindings compliance within U-Boot Sumit Garg
2024-02-02 13:05 ` [PATCH v5 01/11] CI: Exclude devicetree-rebasing subtree for CONFIG checks Sumit Garg
2024-02-02 13:05 ` [PATCH v5 02/11] Makefile: Add support for DT bindings schema checks Sumit Garg
2024-02-02 13:05 ` [PATCH v5 03/11] scripts/Makefile.lib: Statically define *-u-boot.dtsi files location Sumit Garg
2024-02-02 13:05 ` [PATCH v5 04/11] Makefile: Allow upstream DT subtree to provide DT includes Sumit Garg
2024-02-02 13:05 ` [PATCH v5 05/11] dts: Add alternative location for upstream DTB builds Sumit Garg
2024-02-02 13:05 ` [PATCH v5 06/11] dts: Add script to uprev dts/upstream subtree Sumit Garg
2024-02-06 0:21 ` Marek Vasut
2024-02-06 6:20 ` Sumit Garg
2024-02-14 12:26 ` Sumit Garg
2024-02-02 13:05 ` [PATCH v5 07/11] doc: devicetree: Align documentation to use Kconfig options Sumit Garg
2024-02-02 13:05 ` [PATCH v5 08/11] doc: devicetree: Updates for devicetree-rebasing subtree Sumit Garg
[not found] ` <518d87fc-457e-4d77-ba66-9e3a5aa15279@bp.renesas.com>
2024-02-14 13:32 ` Sumit Garg
[not found] ` <e5eec82e-359d-45ad-a01d-6d852fe78d99@bp.renesas.com>
2024-02-19 6:40 ` Sumit Garg [this message]
2024-02-02 13:05 ` [PATCH v5 09/11] MAINTAINERS: Add myself as devicetree-rebasing maintainer Sumit Garg
2024-02-02 13:05 ` [PATCH v5 10/11] dts: meson-gxbb: Switch to using upstream DT Sumit Garg
2024-02-02 13:05 ` [PATCH v5 11/11] dts: meson-gxbb: Drop redundant devicetree files Sumit Garg
2024-02-02 18:02 ` [PATCH v5 00/11] An effort to bring DT bindings compliance within U-Boot Tom Rini
2024-02-06 5:27 ` Sumit Garg
2024-02-06 13:00 ` Tom Rini
2024-02-13 12:55 ` Sumit Garg
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=CAFA6WYPYSj4Am1jZMyAM-4VpxoqMbBiSOTSVMsjF2MabA-UeXQ@mail.gmail.com \
--to=sumit.garg@linaro.org \
--cc=andre.przywara@arm.com \
--cc=b.galvani@gmail.com \
--cc=bb@ti.com \
--cc=caleb.connolly@linaro.org \
--cc=conor@kernel.org \
--cc=daniel.thompson@linaro.org \
--cc=dgilmore@fedoraproject.org \
--cc=festevam@gmail.com \
--cc=ff@shokubai.tech \
--cc=ijc@hellion.org.uk \
--cc=ilias.apalodimas@linaro.org \
--cc=jh80.chung@samsung.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=marex@denx.de \
--cc=mark.kettenis@xs4all.nl \
--cc=mibodhi@gmail.com \
--cc=michal.simek@amd.com \
--cc=neil.armstrong@linaro.org \
--cc=nm@ti.com \
--cc=paul.barker.ct@bp.renesas.com \
--cc=pbrobinson@gmail.com \
--cc=peng.fan@nxp.com \
--cc=rasmus.villemoes@prevas.dk \
--cc=rfried.dev@gmail.com \
--cc=robh+dt@kernel.org \
--cc=seanga2@gmail.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot-amlogic@groups.io \
--cc=u-boot-custodians@lists.denx.de \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
/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).