Poetry warnings on install

[mjog]

The following was output when installing the package, am reporting it as requested in the output.

mjog@sable:~/myproj$ poetry add --group dev mkdocstrings-python-xref
Using version ^1.6.0.1 for mkdocstrings-python-xref

Updating dependencies
Resolving dependencies... (0.5s)

Package operations: 1 install, 0 updates, 0 removals

  - Installing mkdocstrings-python-xref (1.6.0.1): Installing...
Installing /home/mjog/.cache/pypoetry/virtualenvs/myproj-BvS4MufV-py3.12/lib/python3.12/site-packages/mkdocstrings_handlers/python_xref/VERSION over existing file
Installing /home/mjog/.cache/pypoetry/virtualenvs/myproj-BvS4MufV-py3.12/lib/python3.12/site-packages/mkdocstrings_handlers/python_xref/__init__.py over existing file
Installing /home/mjog/.cache/pypoetry/virtualenvs/myproj-BvS4MufV-py3.12/lib/python3.12/site-packages/mkdocstrings_handlers/python_xref/crossref.py over existing file
Installing /home/mjog/.cache/pypoetry/virtualenvs/myproj-BvS4MufV-py3.12/lib/python3.12/site-packages/mkdocstrings_handlers/python_xref/handler.py over existing file
  - Installing mkdocstrings-python-xref (1.6.0.1)
Warning: Validation of the RECORD file of mkdocstrings_python_xref-1.6.0.1-py3-none-any.whl failed. Please report to the maintainers of that package so they can fix their build process. Details:
In /home/mjog/.cache/pypoetry/artifacts/1a/87/fc/2a6c66dec2103c792ffb781140c7bdb34c948c4e713f21f993dcd192e5/mkdocstrings_python_xref-1.6.0.1-py3-none-any.whl, mkdocstrings_handlers/python_xref/VERSION is not mentioned in RECORD
In /home/mjog/.cache/pypoetry/artifacts/1a/87/fc/2a6c66dec2103c792ffb781140c7bdb34c948c4e713f21f993dcd192e5/mkdocstrings_python_xref-1.6.0.1-py3-none-any.whl, mkdocstrings_handlers/python_xref/__init__.py is not mentioned in RECORD
In /home/mjog/.cache/pypoetry/artifacts/1a/87/fc/2a6c66dec2103c792ffb781140c7bdb34c948c4e713f21f993dcd192e5/mkdocstrings_python_xref-1.6.0.1-py3-none-any.whl, mkdocstrings_handlers/python_xref/crossref.py is not mentioned in RECORD
In /home/mjog/.cache/pypoetry/artifacts/1a/87/fc/2a6c66dec2103c792ffb781140c7bdb34c948c4e713f21f993dcd192e5/mkdocstrings_python_xref-1.6.0.1-py3-none-any.whl, mkdocstrings_handlers/python_xref/handler.py is not mentioned in RECORD
In /home/mjog/.cache/pypoetry/artifacts/1a/87/fc/2a6c66dec2103c792ffb781140c7bdb34c948c4e713f21f993dcd192e5/mkdocstrings_python_xref-1.6.0.1-py3-none-any.whl, mkdocstrings_handlers/python_xref/py.typed is not mentioned in RECORD
Writing lock file

[analog-cbarber]

I think that is might be what you get when you install an sdist that doesn't have a RECORD file because there is no wheel for 1.6.0.1.

I built and uploaded a wheel and sdist for 1.6.1

[ItsDrike]

I still see warnings from version 1.6.2:

Full log:

itsdrike ~/…/GitHub/Public/mcproto mkdocs+ took 1s  $ poetry add --group docs mkdocstrings-python-xref
Using version ^1.6.2 for mkdocstrings-python-xref

Updating dependencies
Resolving dependencies... (0.1s)

Package operations: 1 install, 0 updates, 0 removals

  - Installing mkdocstrings-python-xref (1.6.2): Installing...
Installing /home/itsdrike/Personal/Programming/Python/GitHub/Public/mcproto/.venv/lib/python3.13/site-pac
kages/mkdocstrings_handlers/python_xref/VERSION over existing file
Installing /home/itsdrike/Personal/Programming/Python/GitHub/Public/mcproto/.venv/lib/python3.13/site-pac
kages/mkdocstrings_handlers/python_xref/__init__.py over existing file
Installing /home/itsdrike/Personal/Programming/Python/GitHub/Public/mcproto/.venv/lib/python3.13/site-pac
kages/mkdocstrings_handlers/python_xref/crossref.py over existing file
Installing /home/itsdrike/Personal/Programming/Python/GitHub/Public/mcproto/.venv/lib/python3.13/site-pac
kages/mkdocstrings_handlers/python_xref/handler.py over existing file
Installing /home/itsdrike/Personal/Programming/Python/GitHub/Public/mcproto/.venv/lib/python3.13/site-pac
  - Installing mkdocstrings-python-xref (1.6.2)
Warning: Validation of the RECORD file of mkdocstrings_python_xref-1.6.2-py3-none-any.whl failed. Please 
report to the maintainers of that package so they can fix their build process. Details:
In /home/itsdrike/.cache/pypoetry/artifacts/cf/58/47/8b43ece69d33e9505a38bd4b5f1e8bb870cba8f51b7b930d45d1
da004c/mkdocstrings_python_xref-1.6.2-py3-none-any.whl, mkdocstrings_handlers/python_xref/VERSION is not 
mentioned in RECORD
In /home/itsdrike/.cache/pypoetry/artifacts/cf/58/47/8b43ece69d33e9505a38bd4b5f1e8bb870cba8f51b7b930d45d1
da004c/mkdocstrings_python_xref-1.6.2-py3-none-any.whl, mkdocstrings_handlers/python_xref/__init__.py is 
not mentioned in RECORD
In /home/itsdrike/.cache/pypoetry/artifacts/cf/58/47/8b43ece69d33e9505a38bd4b5f1e8bb870cba8f51b7b930d45d1
da004c/mkdocstrings_python_xref-1.6.2-py3-none-any.whl, mkdocstrings_handlers/python_xref/crossref.py is 
not mentioned in RECORD
In /home/itsdrike/.cache/pypoetry/artifacts/cf/58/47/8b43ece69d33e9505a38bd4b5f1e8bb870cba8f51b7b930d45d1
da004c/mkdocstrings_python_xref-1.6.2-py3-none-any.whl, mkdocstrings_handlers/python_xref/handler.py is n
ot mentioned in RECORD
In /home/itsdrike/.cache/pypoetry/artifacts/cf/58/47/8b43ece69d33e9505a38bd4b5f1e8bb870cba8f51b7b930d45d1
da004c/mkdocstrings_python_xref-1.6.2-py3-none-any.whl, mkdocstrings_handlers/python_xref/py.typed is not
 mentioned in RECORD


Writing lock file

[analog-cbarber]

Seems like there are duplicate entries in the RECORD file in the wheel:

mkdocstrings_handlers/python_xref/VERSION,sha256=otXiaP5wl5yszYlRVrPTO9YaPMfmYKt6WwcGaEmz4kg,6
mkdocstrings_handlers/python_xref/__init__.py,sha256=-mT5ATSmRlmLpuQRceXk-rJJgfsh2hGNwbNSponVynI,756
mkdocstrings_handlers/python_xref/crossref.py,sha256=T9PNsg_Gh1mSddXUfohw4TWy74nVFT5SavSkEL2f6fI,12336
mkdocstrings_handlers/python_xref/handler.py,sha256=FLNtJzmRHQUwwf5KxoWzkjJd9CALK4MvPtoVJXxe6Tk,3137
mkdocstrings_handlers/python_xref/py.typed,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
mkdocstrings_handlers/python_xref/VERSION,sha256=otXiaP5wl5yszYlRVrPTO9YaPMfmYKt6WwcGaEmz4kg,6
mkdocstrings_handlers/python_xref/__init__.py,sha256=-mT5ATSmRlmLpuQRceXk-rJJgfsh2hGNwbNSponVynI,756
mkdocstrings_handlers/python_xref/crossref.py,sha256=T9PNsg_Gh1mSddXUfohw4TWy74nVFT5SavSkEL2f6fI,12336
mkdocstrings_handlers/python_xref/handler.py,sha256=FLNtJzmRHQUwwf5KxoWzkjJd9CALK4MvPtoVJXxe6Tk,3137
mkdocstrings_handlers/python_xref/py.typed,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
mkdocstrings_python_xref-1.6.2.dist-info/METADATA,sha256=HcEZ_eZw6h-GDoDp4fjMyhoFIcjQinUeUzrljTJSGZQ,3653
mkdocstrings_python_xref-1.6.2.dist-info/WHEEL,sha256=1yFddiXMmvYK7QYTqtRNtX66WJ0Mz8PYEiEUoOUUxRY,87
mkdocstrings_python_xref-1.6.2.dist-info/licenses/LICENSE.md,sha256=GqsU1tl1ojrVrhAhoC4dGsk9JOoy9M_KIpuaSYl6bEo,11355
mkdocstrings_python_xref-1.6.2.dist-info/RECORD,,

I don't know why that is happening. Maybe that is what is confusing poetry, but you can see that all of those files are in fact mentioned in the RECORD file.

[analog-cbarber]

This probably is fixed with the most recent release, but I don't have a poetry project to test on right now...