testsuite fails on Debian Sid

[Fathi Boudra]

Trying to build the package on Debian Sid, the test suite fails. The same package builds on Oneiric, test suite passed.

python -m testtools.run linaro_image_tools.tests.test_suite
WARNING:linaro_image_tools.hwpack.builder:Local package 'bar' not included
WARNING:linaro_image_tools:Failed to umount bar, but ignoring it because of a previous error
WARNING:linaro_image_tools:Sub process "umount" returned a non-zero value: 1
Tests running...
======================================================================
ERROR: linaro_image_tools.tests.test_utils.TestInstallPackageProviding.test_found_package
----------------------------------------------------------------------
Text attachment: traceback
------------
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/testtools/runtest.py", line 169, in _run_user
    return fn(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 540, in _run_test_method
    return self._get_test_method()()
  File "linaro_image_tools/tests/test_utils.py", line 253, in test_found_package
    install_package_providing('mkfs.vfat')
  File "linaro_image_tools/utils.py", line 132, in install_package_providing
    "Cannot lookup a package which provides %s" % command)
UnableToFindPackageProvidingCommand: Cannot lookup a package which provides mkfs.vfat
------------
Ran 603 tests in 33.909s

FAILED (failures=1)

[Fathi Boudra (fboudra)]

It seems related to command-not-found package in Debian.
The package doesn't come with a database compared to Ubuntu.
You need to run update-command-not-found command.
Though, it doesn't help. Even with a database up-to-date, the test suite fails.

[Georgy Redkozubov (gesha)]

CommandNotFound package couldn't be found by python despite postinstall script that updates python.
The workaround for that is to create a link in /usr/lib/python2.7/dist-packages to the installation of CommandNotFound how it is done in Ubuntu's package.

[Milo Casagrande (milo)]

Due to the age of this issue, we are acknowledging that it will likely not be fixed, is no longer applicable, or was already fixed by an indirect change. If this issue is still important, please add details and reopen it.