lua-say: bump debhelper compatibility level
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lua-say (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
lua-say is blocking dh-lua/27 migration at the moment:
This is the important part:
autopkgtest [09:19:35]: test dh-lua-tests: - - - - - - - - - - results - - - - - - - - - -
dh-lua-tests FAIL stderr: dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
autopkgtest [09:19:35]: test dh-lua-tests: - - - - - - - - - - stderr - - - - - - - - - -
dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 9 in use)
The fix is straightforward: 1) we could bump debhelper compatibility level to something greater than 9; or 2) we could add the allow-stderr restriction to d/t/control.
I filed this bug in Debian:
https:/
In Debian, I recommend 1) but, in Ubuntu, my proposed solution is 2) because bumping debhelper version might have some side effects we do not want to have at this point of feature freeze.
With the attached debdiff applied autopkgtest is happy again:
autopkgtest [09:24:30]: test dh-lua-tests: - - - - - - - - - - results - - - - - - - - - -
dh-lua-tests PASS
autopkgtest [09:24:31]: @@@@@@@
dh-lua-tests PASS
summary: |
- lua-say: autopkgtest failure blocking dh-lua + lua-say: bump debhelper compatibility level |
tags: | added: patch |
The bottom line is that this dep8 test flagged a real issue and is an opportunity to improve this package. Adding allow-stderr is a workadound, and one I'm afraid will likely remain there forever. The correct fix is to bump the dh level.
I suggest to rephrase this bug to indicate the dh level needs to be bumped, and leave it open even after the allow-stderr workaround is applied.