public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: Michael Tremer <michael.tremer@ipfire.org>
Cc: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Re: Failed Build of 'next' x86_64 on GNU/Linux 13 (trixie)
Date: Sun, 14 Sep 2025 12:32:44 +0200	[thread overview]
Message-ID: <10c2da08-b8ce-4221-828a-40a77654e6cc@ipfire.org> (raw)
In-Reply-To: <F7063CE5-9BBB-4E2B-AB1B-FDC83FA2BEB9@ipfire.org>

Hi Michael,

Bad news I am afraid.

On 14/09/2025 11:31, Michael Tremer wrote:
> Hello everyone,
> 
> Thank you for getting back so quickly on this. It would be great if we could sort this problem out as soon as possible.
> 
>> On 13 Sep 2025, at 21:37, Adolf Belka <adolf.belka@ipfire.org> wrote:
>>
>> Hi Michael,
>>
>> On 13/09/2025 21:21, Matthias Fischer wrote:
>>> Hi,
>>> I tried to build 'next' with the other archive - 'Pillow-11.3.0.tar.gz',
>>> but the build fails with same error (ERROR Missing dependencies:
>>> setuptools>=77).
>>> Any ideas?
>>
>> The interesting thing is that the x86_64 nightly build with python3-pillow in it, built without any failure.
> 
> Indeed. But since we have the same sources (checked by checksums) there cannot be any difference there. On the other hand, this could just be chance.
> 
> If you are running multiple builds (or are restarting the same build), does the problem go away? Is there basically a chance that this build is failing and the nightly builds have just been lucky (except riscv64)?
> 
>> Tomorrow I will create a new clone of next and do a build withy no other changes and see if I can reproduce the successful nightly build with next.

I created a new clone of next and ran a straight build, so without any ccache or cache entries.

The build failed at python3-pillow with the same message. So four build attempts I have done have all failed with the same message, and Matthias and Charles also. So the odd one out seems to be the x86_64 builder that is building successfully.

> 
> We should not have a second package of setuptools around. What happens if you manually delete it? Does the build continue?

If you mean the directory entry of setuptools-63.2.0.dist-info that I found, I just tried deleting it in the build_x86_64 tree and re-running build without doing a clean first. The python3-pillow then successfully built.

So the presence of that directory is what is causing the problem but not sure why it is getting built.

Regards,

Adolf.

> 
> -Michael
> 
>>
>> Regards,
>>
>> Adolf.
>>
>>> Best
>>> Matthias
>>> On 13.09.2025 16:12, Matthias Fischer wrote:
>>>> Hi,
>>>>
>>>> I must confess, I don't know how this python building really works - but...
>>>>
>>>> I've found a 'pillow-11.3.0.tar.gz'-archive in the cache directory of my
>>>> 'Devel64-1'. Blake2-Checksum is:
>>>> bde2d91943ca39cef342733f57d5c4b4e1fcb4e20b145fea1606018f255d70311e7f09d02321aede10ea1b0ae73cc86e3932d213718eb081f6961cf36174282f
>>>>
>>>> The archive on the *original website*
>>>> (https://github.com/python-pillow/Pillow/releases/tag/11.3.0) is named
>>>> 'Pillow-11.3.0.tar.gz' and has a different checksum and different
>>>> contents. Note the capitalized "P".
>>>> Blake2-Checksum is:
>>>> 1260c7025e6013c50782024756a0c891d3735bd7d4c1c9d0a89d9eb1c94bd2f762369086f7269d487100e8a0e2678a73012bf29172697c1a1a18e58f9019a9bd
>>>>
>>>> I extracted both archives and compared them with 'WinMerge'. They differ
>>>> significantly - different/missing directories and files.
>>>>
>>>> I don't know where the cached version came from but I'll try a build
>>>> with the original archive and will keep you informed.
>>>>
>>>> HTH
>>>> Matthias
>>>>
>>>> On 13.09.2025 14:48, Michael Tremer wrote:
>>>>> Hello,
>>>>>
>>>>> Could you please check whether the module is there at all. Can it be loaded? Is there a problem loading it?
>>>>>
>>>>> -Michael
>>>>>
>>>>>> On 13 Sep 2025, at 13:47, Matthias Fischer <matthias.fischer@ipfire.org> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I can confirmed - clean build (current 'next') from today shows
>>>>>> identical errors:
>>>>>>
>>>>>> ***SNIP***
>>>>>> python3-pillow (11.3.0)                             [        2 ][ FAIL ]
>>>>>>
>>>>>>     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'
>>>>>>
>>>>>> ERROR: Building python3-pillow                                  [ FAIL ]
>>>>>>     Check /git/ipfire-2.x/log_x86_64/_build.ipfire.log for errors if
>>>>>> applicable
>>>>>> ***SNAP***
>>>>>>
>>>>>> Best
>>>>>> Matthias
>>>>>>
>>>>>> On 13.09.2025 12:36, Michael Tremer wrote:
>>>>>>> Hello Charles,
>>>>>>>
>>>>>>> Can you still reproduce this? The nightly builds seem to have completed okay.
>>>>>>>
>>>>>>> -Michael
>>>>>>>
>>>>>>>> On 8 Sep 2025, at 00:52, Charles Brown <cab_77573@yahoo.com> wrote:
>>>>>>>>
>>>>>>>> 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'
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>
>>
> 



  reply	other threads:[~2025-09-14 10:32 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <91d9cd50-25da-4eb2-8500-88978d759a7b.ref@yahoo.com>
2025-09-07 23:52 ` Charles Brown
2025-09-13 10:36   ` Michael Tremer
2025-09-13 12:47     ` Matthias Fischer
2025-09-13 12:48       ` Michael Tremer
2025-09-13 14:12         ` Matthias Fischer
2025-09-13 15:00           ` Adolf Belka
2025-09-13 15:06             ` Adolf Belka
2025-09-13 15:43               ` Adolf Belka
2025-09-13 15:52                 ` Adolf Belka
2025-09-13 19:21           ` Matthias Fischer
2025-09-13 20:37             ` Adolf Belka
2025-09-14  9:31               ` Michael Tremer
2025-09-14 10:32                 ` Adolf Belka [this message]
2025-09-14 10:48                   ` Michael Tremer
2025-09-14 11:21                     ` Adolf Belka
2025-09-14 11:44                       ` Adolf Belka
2025-09-14 15:47                         ` Adolf Belka
2025-09-14 15:51                           ` Michael Tremer
2025-09-15 10:13                             ` Michael Tremer
2025-09-15 15:29                               ` Adolf Belka
2025-09-15 15:36                                 ` Matthias Fischer
2025-09-15 23:04                                 ` Matthias Fischer
2025-09-13 19:19     ` Charles Brown
     [not found] <e08f7347-f278-44e8-9980-52f975f1202c.ref@yahoo.com>
2025-09-15 21:06 ` Charles Brown
     [not found] <5cd17450-2b6a-48d3-921f-6c6a2c48ee1c.ref@yahoo.com>
2025-09-15 21:19 ` Charles Brown

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=10c2da08-b8ce-4221-828a-40a77654e6cc@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    --cc=michael.tremer@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