Changeset 0b4c0a0


Ignore:
Timestamp:
08/26/2022 12:32:26 PM (3 months ago)
Author:
Xi Ruoyao <xry111@…>
Branches:
xry111/queue-11.3
Parents:
1da889e
git-author:
Xi Ruoyao <xry111@…> (08/26/2022 11:35:47 AM)
git-committer:
Xi Ruoyao <xry111@…> (08/26/2022 12:32:26 PM)
Message:

python: supress "failed to check new pip version" or "a new pip version is available" warnings

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter08/python.xml

    r1da889e r0b4c0a0  
    103103    of this recommendation is for avoiding a conflict with the system
    104104    package manager (<command>dpkg</command> for example), but LFS does not
    105     have a system-wide package manager so this is not a problem.  If desired,
    106     suppress this warning by running the following commands:</para>
     105    have a system-wide package manager so this is not a problem.  And,
     106    <command>pip3</command> will attempt to check for a new version of
     107    itself whenever it's run.  As domain name resolving is not configured
     108    yet in LFS chroot environment, it will fail to check for a new version
     109    and produce a warning.  Once we boot the LFS system and set up network
     110    connection, it will then produce a warning telling the user to update it
     111    from a pre-built wheel on PyPI if any new version is available.  But LFS
     112    consider <command>pip3</command> a part of Python 3 so it should not be
     113    updated separately, and an update from a pre-built wheel will deviate
     114    from our purpose to build a Linux system from source code.  So the
     115    warning for a new <command>pip3</command> version should be ignored as
     116    well. If desired, suppress these warnings by running the following
     117    commands:</para>
    107118
    108119 <screen><userinput remap="install">cat &gt; /etc/pip.conf &lt;&lt; EOF
    109120[global]
    110121root-user-action = ignore
     122disable-pip-version-check = true
    111123EOF
    112124</userinput></screen>
Note: See TracChangeset for help on using the changeset viewer.