mirror of
https://git.linuxfromscratch.org/lfs.git
synced 2025-06-18 19:29:21 +01:00
python: supress "failed to check new pip version" or "a new pip version is available" warnings
The non-text change during freeze is approved by bdubbs.
This commit is contained in:
parent
5353a1948f
commit
bf6f9e75ee
@ -102,12 +102,24 @@
|
||||
<systemitem class='username'>root</systemitem> user. The main reason
|
||||
of this recommendation is for avoiding a conflict with the system
|
||||
package manager (<command>dpkg</command> for example), but LFS does not
|
||||
have a system-wide package manager so this is not a problem. If desired,
|
||||
suppress this warning by running the following commands:</para>
|
||||
have a system-wide package manager so this is not a problem. And,
|
||||
<command>pip3</command> will attempt to check for a new version of
|
||||
itself whenever it's run. As domain name resolving is not configured
|
||||
yet in LFS chroot environment, it will fail to check for a new version
|
||||
and produce a warning. Once we boot the LFS system and set up network
|
||||
connection, it will then produce a warning telling the user to update it
|
||||
from a pre-built wheel on PyPI if any new version is available. But LFS
|
||||
consider <command>pip3</command> a part of Python 3 so it should not be
|
||||
updated separately, and an update from a pre-built wheel will deviate
|
||||
from our purpose to build a Linux system from source code. So the
|
||||
warning for a new <command>pip3</command> version should be ignored as
|
||||
well. If desired, suppress these warnings by running the following
|
||||
commands:</para>
|
||||
|
||||
<screen><userinput remap="install">cat > /etc/pip.conf << EOF
|
||||
[global]
|
||||
root-user-action = ignore
|
||||
disable-pip-version-check = true
|
||||
EOF
|
||||
</userinput></screen>
|
||||
<!--
|
||||
|
Loading…
Reference in New Issue
Block a user