From: Mattijs Korpershoek <mkorpershoek@kernel.org>
To: Mattijs Korpershoek <mkorpershoek@kernel.org>,
Tom Rini <trini@konsulko.com>,
Mattijs Korpershoek <mkorpershoek@kernel.org>
Cc: Simon Glass <sjg@chromium.org>, u-boot@lists.denx.de
Subject: Re: [PATCH] tools/make_pip: Use virtualenv when invoking pip
Date: Wed, 16 Apr 2025 14:38:00 +0200 [thread overview]
Message-ID: <87fri846zb.fsf@kernel.org> (raw)
In-Reply-To: <87ikn44io3.fsf@kernel.org>
On mer., avril 16, 2025 at 10:25, Mattijs Korpershoek <mkorpershoek@kernel.org> wrote:
> Hi Tom,
>
> On mar., avril 15, 2025 at 11:59, Tom Rini <trini@konsulko.com> wrote:
>
>> On Wed, Apr 09, 2025 at 09:46:34AM +0200, Mattijs Korpershoek wrote:
>>
>>> Recent Ubuntu versions (24.04+) disallow pip by default when
>>> installing packages. The recommended approach is to use a virtualenv
>>> instead.
>>> Because of this, "make pip" is failing on such versions.
>>>
>>> To prepare CI container migration to Ubuntu 24.04, use a virtualenv
>>> in the make_pip script.
>>>
>>> Note: This has been reported on [1]
>>>
>>> [1] https://source.denx.de/u-boot/custodians/u-boot-dm/-/issues/37
>>>
>>> Signed-off-by: Mattijs Korpershoek <mkorpershoek@kernel.org>
>>> Reviewed-by: Tom Rini <trini@konsulko.com>
>>> ---
>>> This has been tested in docker on ubuntu:24.04 after running:
>>> $ apt install python3 python3-virtualenv
>>>
>>> with:
>>> $ ./scripts/make_pip.sh u_boot_pylib "-n"
>>>
>>> And shows:
>>> Successfully built u_boot_pylib-0.0.6.tar.gz and u_boot_pylib-0.0.6-py3-none-any.whl
>>>
>>> Also tested with "$ make pip".
>>> ---
>>> scripts/make_pip.sh | 6 ++++++
>>> 1 file changed, 6 insertions(+)
>>
>> So, this ends up failing with Ubuntu 22.04 thusly:
>> https://source.denx.de/u-boot/u-boot/-/jobs/1103567
>
> Argh, sorry I did not test that.
>
>>
>> And in short, I think your original plan to use venv not virtualenv is
>> correct, sorry for the noise. I'll post something to install
>> python3-venv to our container shortly and switch to venv not virtualenv
>> as that seems to be the long term best answer.
>
> Ok, will send a v2 to use venv instead.
Posted here:
https://lore.kernel.org/all/87ikn44io3.fsf@kernel.org/
As mentioned in the cover letter, this requires python3-venv to be added
in the container and I've assumed you will be doing that, Tom.
Thanks!
>
>>
>> --
>> Tom
next prev parent reply other threads:[~2025-04-16 12:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 7:46 [PATCH] tools/make_pip: Use virtualenv when invoking pip Mattijs Korpershoek
2025-04-11 19:06 ` Tom Rini
2025-04-15 17:59 ` Tom Rini
2025-04-16 8:25 ` Mattijs Korpershoek
2025-04-16 12:38 ` Mattijs Korpershoek [this message]
2025-04-16 13:58 ` Tom Rini
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=87fri846zb.fsf@kernel.org \
--to=mkorpershoek@kernel.org \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.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