Improve dep-8 testing of DKMS modules
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dahdi-linux (Ubuntu) |
Fix Released
|
Low
|
Stefan Bader | ||
Trusty |
Fix Released
|
Low
|
Unassigned |
Bug Description
Currently the dahdi-dkms modules are tested through auto-testing only by the generic DKMS package test. This does an install and checks whether this is successful. For dahdi-dkms this can be improved by actually loading the dahdi_dummy module.
Also, though this is more specifically and issue with Trusty (hence the nomination), there used to be an inconsistency with the echo (noise cancellation) module. For quite a while now this is provided by the kernel itself and at a version level which the same as the DKMS sources contain. For recent packaging we prevent the DKMS package from building that module, but back in Trusty it is done but not installed by DKMS. Which then results in a warning text in the output of "dkms status". This seems to cause a test failure for the generic test case.
So for Trusty I would also backport the dep-8 testcase (which seems less intrusive than doing anything to the build itself) get the improved testing and have the status test ignore the additional warning.
This bug was fixed in the package dahdi-linux - 1:2.10. 0.1~dfsg- 1ubuntu4
--------------- 0.1~dfsg- 1ubuntu4) wily; urgency=low
dahdi-linux (1:2.10.
* Improve dep-8 testing by supplying individual test case (which will
also test-load the dummy module) (LP: #1497982)
-- Stefan Bader <email address hidden> Mon, 21 Sep 2015 08:57:25 -0500