[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#997662: lintian: Incorrect tag: package-contains-python-dot-directory for .egg-info directories



Control: affects -1 asciidoc

Hi lintian devs,

Am 24.10.21 um 00:04 schrieb Stefano Rivera:
Package: lintian
Version: 2.110.0
Severity: normal

Hi, I see lintian 2.110 is now emitting a
package-contains-python-dot-directory tag for .egg-info directories in
binary packages.

We do not want to encourage package maintainers to remove .egg-info
directories from their Python binary packages. Tools inspect these to
know which Python modules are available on the system, as well as many
other things.

I would consider all of these tags to be incorrect:
W: python3-bs4: package-contains-python-dot-directory usr/lib/python3/dist-packages/beautifulsoup4-4.10.0.egg-info/
W: python3-bs4: package-contains-python-dot-directory usr/lib/python3/dist-packages/beautifulsoup4-4.10.0.egg-info/PKG-INFO
W: python3-bs4: package-contains-python-dot-directory usr/lib/python3/dist-packages/beautifulsoup4-4.10.0.egg-info/dependency_links.txt
W: python3-bs4: package-contains-python-dot-directory usr/lib/python3/dist-packages/beautifulsoup4-4.10.0.egg-info/requires.txt
W: python3-bs4: package-contains-python-dot-directory usr/lib/python3/dist-packages/beautifulsoup4-4.10.0.egg-info/top_level.txt

I've tried to package a new version of KiCad and that failed due a nasty issue I faced while dh_auto_configure was running to configure the documentation that is build by asciidoc later.

CMake Error at /usr/share/cmake-3.21/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
  Could NOT find ASCIIDOC (missing: ASCIIDOC_COMMAND)
Call Stack (most recent call first):
  /usr/share/cmake-3.21/Modules/FindPackageHandleStandardArgs.cmake:594 (_FPHSA_FAILURE_MESSAGE)
  CMakeModules/FindASCIIDOC.cmake:72 (find_package_handle_standard_args)
  CMakeLists.txt:72 (find_package)

It did cost me an hour to narrow down the real culprit.

The KiCad documentation is doing some wrapping inside it's CMake files to detect asciidoc. Basically it is calling 'asciidoc --version' to detect the underlying version.

https://gitlab.com/kicad/services/kicad-doc/-/blob/master/CMakeModules/FindASCIIDOC.cmake#L20

For the current version of asciidoc in testing calling 'asciidoc --version' is working as expected.

$ asciidoc --version asciidoc 9.0.0rc2

Doing the same in unstable isn't working anymore, but due this the configuration of the KiCad documentation can't run successfully.

root@i5:/build/kicad-5.99.0+really5.1.11+dfsg1/doc/build# asciidoc --version
Traceback (most recent call last):
  File "/usr/bin/asciidoc", line 33, in <module>
    sys.exit(load_entry_point('asciidoc==10.0.1', 'console_scripts', 'asciidoc')())
  File "/usr/bin/asciidoc", line 22, in importlib_load_entry_point
    for entry_point in distribution(dist_name).entry_points
  File "/usr/lib/python3.9/importlib/metadata.py", line 524, in distribution
    return Distribution.from_name(distribution_name)
  File "/usr/lib/python3.9/importlib/metadata.py", line 187, in from_name
    raise PackageNotFoundError(name)
importlib.metadata.PackageNotFoundError: asciidoc

Searching for similar issues I've found #998114 which describes that deleting the entry points within the asciidoc package isn't a good idea to me.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998114

--
Regards
Carsten


Reply to: