From: Charles Brown <cab_77573@yahoo.com>
To: IPFire Development <development@lists.ipfire.org>
Subject: Failed Build of 'next' x86_64 on GNU/Linux 13 (trixie)
Date: Sun, 7 Sep 2025 18:52:24 -0500 [thread overview]
Message-ID: <91d9cd50-25da-4eb2-8500-88978d759a7b@yahoo.com> (raw)
In-Reply-To: <91d9cd50-25da-4eb2-8500-88978d759a7b.ref@yahoo.com>
Similar to this ... " [FAILED] Nightly Build of next (0cbb983) for
riscv64 on riscv64-01.haj.ipfire.org"
Having same issue building 'next' x86_64 on GNU/Linux 13 (trixie)"
...
ERROR Missing dependencies:
setuptools>=77
make: *** [python3-pillow:77: /usr/src/log/pillow-11.3.0] Error 1
make: Leaving directory '/usr/src/lfs'
ERROR: Building python3-pillow [ FAIL ]
Check
/home/cbrown/myProject/ipfire-2.x/log_x86_64/_build.ipfire.log for
errors if applicable[ FAIL ]
and from my _build.ipfire.log ...
Sep 7 18:47:25: Building python3-pillow make: Entering directory
'/home/cbrown/myProject/ipfire-2.x/lfs'
-e Download: https://source.ipfire.org/source-2.x/pillow-11.3.0.tar.gz
2025-09-07 13:47:29
URL:https://source.ipfire.org/source-2.x/pillow-11.3.0.tar.gz
[47113069/47113069] -> "/tmp/pillow-11.3.0.tar.gz" [1]
make: Leaving directory '/home/cbrown/myProject/ipfire-2.x/lfs'
make: Entering directory '/usr/src/lfs'
pillow-11.3.0.tar.gz checksum OK
====================================== Installing pillow-11.3.0 ...
Install started; saving file list to /usr/src/lsalr ...
cd /usr/src/pillow-11.3.0 && patch -Np1 <
/usr/src/src/patches/python3-pillow-11.3.0-fix-license.patch
patching file pyproject.toml
cd /usr/src/pillow-11.3.0 && python3 -m build --wheel --no-isolation
* Getting dependencies for wheel...
/usr/lib/python3.10/site-packages/setuptools/config/pyprojecttoml.py:104:
_BetaConfiguration: Support for `[tool.setuptools]` in `pyproject.toml`
is still *beta*.
warnings.warn(msg, _BetaConfiguration)
running egg_info
writing src/pillow.egg-info/PKG-INFO
writing dependency_links to src/pillow.egg-info/dependency_links.txt
writing requirements to src/pillow.egg-info/requires.txt
writing top-level names to src/pillow.egg-info/top_level.txt
listing git files failed - pretending there aren't any
reading manifest file 'src/pillow.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no files found matching '*.c'
warning: no files found matching '*.h'
warning: no files found matching '*.sh'
warning: no files found matching '*.txt'
warning: no files found matching '.flake8'
warning: no previously-included files found matching '.clang-format'
warning: no previously-included files found matching '.coveragerc'
warning: no previously-included files found matching '.editorconfig'
warning: no previously-included files found matching '.readthedocs.yml'
warning: no previously-included files found matching 'codecov.yml'
warning: no previously-included files found matching 'renovate.json'
warning: no previously-included files matching '.git*' found anywhere in
distribution
warning: no previously-included files matching '*.so' found anywhere in
distribution
no previously-included directories found matching '.ci'
no previously-included directories found matching 'wheels'
adding license file 'LICENSE'
writing manifest file 'src/pillow.egg-info/SOURCES.txt'
ERROR Missing dependencies:
setuptools>=77
make: *** [python3-pillow:77: /usr/src/log/pillow-11.3.0] Error 1
make: Leaving directory '/usr/src/lfs'
parent reply other threads:[~2025-09-07 23:52 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <91d9cd50-25da-4eb2-8500-88978d759a7b.ref@yahoo.com>]
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=91d9cd50-25da-4eb2-8500-88978d759a7b@yahoo.com \
--to=cab_77573@yahoo.com \
--cc=development@lists.ipfire.org \
/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