Control: tags -1 +moreinfo

Thomas,

Many thanks for addressing some of the issues raised.

One lintian issue remains.

I: luit source: unused-override no-debian-changes  [debian/source/lintian-
overrides:2]
N: 
N:   Your package specifies the named override but there were no tags that
N:   could have been silenced by it.
N:   
N:   Maybe you fixed an underlying condition but forgot to remove the
override.
N:   It is also possible that the Lintian maintainers fixed a false positive.
N:   
N:   If the override is now unused, please remove it.
N:   
N:   This tag is similar to mismatched-override except there a tag could have
N:   been silenced if the context had matched.
N:   
N:   Sometimes, overrides end up not being used because a tag appears only on
N:   some architectures. In that case, overrides can be equipped with an
N:   architecture qualifier.
N: 
N:   Please refer to Architecture specific overrides (Section 2.4.3) in the
N:   Lintian User's Manual for details.
N: 
N:   Visibility: info
N:   Show-Always: yes
N:   Check: lintian
N: 
N: 0 hints overridden; 1 unused override

You can remove 'd/source/lintian-overrides', it is not required for the
current package source tree and will eliminate the only lintian warning.

'd/copyright'. Please add a 'Files: debian/*' section that will inform of
changes related to persons who have made contribution to the debian packaging
related files and directories. Some Debian Developers (DDs) will be hesitant
to sponsor a package without this section being included. For me it is good
for completeness and clarity.

Regards

Phil

-- 

"I play the game for the game’s own sake"

Arthur Conan Doyle - The Adventure of the Bruce-Partington Plans

--

Buy Me A Coffee: https://buymeacoffee.com/kathenasorg

Internet Relay Chat (IRC): kathenas

Matrix: #kathenas:matrix.org

Website: https://kathenas.org

Instagram: https://instagram.com/kathenasorg/

Threads: https://www.threads.net/@kathenasorg

--






Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to