Re: Current dev lfs - setuptools - SOLVED
| Newsgroups | gmane.linux.lfs.support |
|---|---|
| Message-ID | <[email protected]> |
Am 11.12.24 um 04:49 schrieb Xi Ruoyao ([email protected] via lfs-support Mailing List): > On Tue, 2024-12-10 at 19:09 +0100, Frans de Boer wrote: >> Hi Bruce, >> >> The $PWD is translated into /sources-base/setuptools-75.6.0. Shown >> below is the exact result during execution. >> Also, I use the pip3 version (24.2) previously compiled by Phyton >> 3.13. >> >> i also downloaded the archive again, which solved the problem. There >> was a problem with the first archive, so it seems. > > You should check the md5sum before building LFS, as the book has > indicated. > > I can reproduce the issue with > https://github.com/pypa/setuptools/archive/v75.6.0/setuptools-75.6.0.tar.gz, > but we are using > https://pypi.org/packages/source/s/setuptools/setuptools-75.6.0.tar.gz > and we are explicitly saying: > > For some packages, the release tarball and the (Git or SVN) > repository snapshot tarball for that release may be published with > similar file names. A release tarball contains generated files (for Suggestion: [...] identical file names. But a release tarball may contain generated files (for example, [...] Rainer > example, a configure script generated by autoconf), in addition to > the contents of the corresponding repository snapshot. The book uses > release tarballs whenever possible. Using a repository snapshot > instead of a release tarball specified by the book will cause > problems. > > And do not top post. > > > -- http://lists.linuxfromscratch.org/sympa/info/lfs-support Unsubscribe: See the above information page