[MacPorts] #70265: py-pyicu: all subports fail to build on case-sensitive filesystems, due to directory name case mismatch

[MacPorts]

#70265: py-pyicu: all subports fail to build on case-sensitive filesystems, due to
directory name case mismatch
-----------------------+------------------------
  Reporter:  mascguy   |      Owner:  reneeotten
      Type:  defect    |     Status:  assigned
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:  2.9.3
Resolution:            |   Keywords:
      Port:  py-pyicu  |
-----------------------+------------------------
Description changed by mascguy:

Old description:

> With the latest update to this port, committed yesterday, all subports
> now fail to build on case-sensitive filesystems - including our buildbots
> - with the following error:
>
> [Note: path to macports work directory truncated, for readability.]
>
> {{{
> ERROR Source .../py310-pyicu/work/PyICU-2.13.1 does not appear to be a
> Python project: no pyproject.toml or setup.py
>
> Command failed:  cd ".../py310-pyicu/work/PyICU-2.13.1" &&
> /opt/local/Library/Frameworks/Python.framework/Versions/3.10/bin/python3.10
> -m build --no-isolation --wheel --outdir .../py310-pyicu/work
> }}}
>
> That is due to all files residing under directory `py310-pyicu`, rather
> than `PyICU-2.13.1`:
>
> {{{
> $ cd $(port work py312-pyicu)
>
> $ ls -l
> drwxr-xr-x  2 macports  wheel  -   68 Jun 20 18:28:33 2024 PyICU-2.13.1
> drwxr-xr-x  5 macports  wheel  - 2652 Apr 29 16:17:30 2024 pyicu-2.13.1
>
> $ gfind PyICU-2.13.1
> PyICU-2.13.1
>
> $ gfind pyicu-2.13.1
> pyicu-2.13.1
> pyicu-2.13.1/CHANGES
> pyicu-2.13.1/CREDITS
> pyicu-2.13.1/LICENSE
> pyicu-2.13.1/MANIFEST.in
> pyicu-2.13.1/PKG-INFO
> pyicu-2.13.1/README.md
> [...etc...]
> }}}
>
> The fix may be as simple as eliminating the mixed-case `python.rootname`
> declaration in the portfile, assuming nothing else needs to be done...?

New description:

 With the latest update to this port, committed yesterday, all subports now
 fail to build on case-sensitive filesystems - including our buildbots -
 with the following error:

 //[Note: path to macports work directory truncated, for readability.]//

 {{{
 ERROR Source .../py310-pyicu/work/PyICU-2.13.1 does not appear to be a
 Python project: no pyproject.toml or setup.py

 Command failed:  cd ".../py310-pyicu/work/PyICU-2.13.1" &&
 /opt/local/Library/Frameworks/Python.framework/Versions/3.10/bin/python3.10
 -m build --no-isolation --wheel --outdir .../py310-pyicu/work
 }}}

 That is due to all files residing under directory `pyicu-2.13.1`, rather
 than `PyICU-2.13.1`:

 {{{
 $ cd $(port work py312-pyicu)

 $ ls -l
 drwxr-xr-x  2 macports  wheel  -   68 Jun 20 18:28:33 2024 PyICU-2.13.1
 drwxr-xr-x  5 macports  wheel  - 2652 Apr 29 16:17:30 2024 pyicu-2.13.1

 $ gfind PyICU-2.13.1
 PyICU-2.13.1

 $ gfind pyicu-2.13.1
 pyicu-2.13.1
 pyicu-2.13.1/CHANGES
 pyicu-2.13.1/CREDITS
 pyicu-2.13.1/LICENSE
 pyicu-2.13.1/MANIFEST.in
 pyicu-2.13.1/PKG-INFO
 [...etc...]
 }}}

 The fix may be as simple as eliminating the mixed-case `python.rootname`
 declaration in the portfile, assuming nothing else needs to be done...?

--

-- 
Ticket URL: <https://trac.macports.org/ticket/70265#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS