Re: x11/nvidia-driver build failed at devel/py-importlib-metadata

KIRIYAMA Kazuhiko wrote:
> On Wed, 21 Jun 2023 20:52:20 +0900,
> Charlie Li wrote:
>>
>> [1 Re: x11/nvidia-driver build failed at devel/py-importlib-metadata <multipart/mixed (7bit)>]
>> [1.1  <text/plain; UTF-8 (base64)>]
>> KIRIYAMA Kazuhiko wrote:
>>> Hi, list
>>>
>>> x11/nvidia-driver build failed at devel/py-importlib-metadata:
>>>
>>> Copying importlib_metadata.egg-info to /var/ports/work/var/ports/msrvkx/devel/py-importlib-metadata/work-py39/stage/usr/local/lib/python3.9/site-packages/importlib_metadata-2.0.0-py3.9.egg-info
>>> running install_scripts
>>> writing list of installed files to '/var/ports/work/var/ports/msrvkx/devel/py-importlib-metadata/work-py39/.PLIST.pymodtmp'
>>> ====> Compressing man pages (compress-man)
>>> ===>  Installing for py39-importlib-metadata-2.0.0
>>> ===>  Checking if py39-importlib-metadata is already installed
>>> ===>   Registering installation for py39-importlib-metadata-2.0.0 as automatic
>>> Installing py39-importlib-metadata-2.0.0...
>>> ===>   py39-markdown-3.3.7 depends on package: py39-importlib-metadata>=4.4 - not found
>>> *** Error code 1
>>>
>>> Stop.
>>> make[5]: stopped in /var/ports/msrvkx/textproc/py-markdown
>>> *** Error code 1
>>>
>> Make sure your tree is fully updated, since it appears you have a very
>> old version of importlib-metadata. Partial tree updates are not, will
>> not and never have been supported.
> 
> Could you tell me how to "fully update" ?
> 
You appear to have a weird tree setup so you are on your own there. But 
the root of this particular problem is that the markdown version you are 
building requires a newer importlib-metadata than what your tree has. 
The main ports tree has a much newer importlib-metadata. Figure out how 
to get it.

-- 
Charlie Li
…nope, still don't have an exit line.