On Friday, November 28, 2025 8:51:39 PM Mountain Standard Time Seyed Mohamad Amin Modaresi wrote: > Hi Soren. > > But it is good for me, without any error! > Even salsa CI has no error?! It is working for me now, too. I deleted my gxml directory and cloned the repository again and this time it came across clean. I apologize for the static. There are a few lintian tags that we ought to take a look at. I: libgxml-0.20-2.0.2: no-symbols-control-file usr/lib/x86_64-linux-gnu/ libgxml-0.20.so.2 N: N: Although the package includes a shared library, the package does not have a symbols control file. N: N: dpkg can use symbols files in order to generate more accurate library dependencies for applications, based on the symbols from the library that are actually used by the application. N: N: Please refer to the dpkg-gensymbols(1) manual page and https:// wiki.debian.org/UsingSymbolsFiles for details. N: N: Visibility: info N: Show-Always: no N: Check: debian/shlibs There are a few tricks to generating symbols files. Let me know if you have never created one before and I can point you in the right direction. I: libgxml-doc: possible-documentation-but-no-doc-base-registration N: N: The package ships a .html or .pdf file under /usr/share/doc/. Those files are usually documentation, but no files are registered in doc-base. N: N: Files in folders named examples are exempt from this tag. N: N: Please refer to Registering Documents using doc-base (Section 9.10) in the Debian Policy Manual for details. N: N: Visibility: info N: Show-Always: no N: Check: menus Same here. Let me know if you have never done this before and I can point you in the right direction. I: libgxml-0.20 source: superficial-tests [debian/tests/control] N: N: The source package declares tests in the debian/tests/control file but provides only tests with a superficial restriction. N: N: Please provide more meaningful tests. N: N: Please refer to https://lists.debian.org/debian-devel-announce/2019/08/ msg00003.html, Bug#932870, and https://salsa.debian.org/ci-team/autopkgtest/ tree/master/doc/README.package-tests.rst for details. N: N: Visibility: info N: Show-Always: no N: Check: testsuite Upstream contains a bunch of tests. Is there any reason why we aren’t using them. P: libgxml-0.20-dev: example-unusual-interpreter /usr/bin/python [usr/share/ doc/libgxml-0.20-dev/examples/python/example.py] N: N: This package contains an example script for an interpreter that is not shipped in the package and is not known to Lintian. It is possible that there is a typo or the interpreter is not executable. N: N: Visibility: pedantic N: Show-Always: no N: Check: scripts The interpreter needs to be either: #!/usr/bin/env python or #!/usr/bin/python3 Both of these only work if the script is Python 3. Sometimes "#!/usr/bin/ python" was used for scripts that are Python 2 and sometimes people used it with scripts that had been converted to Python 3. In any case, these are the types of issues I usually raise upstream. -- Soren Stoutner soren@debian.org
Attachment:
signature.asc
Description: This is a digitally signed message part.