Currently, we display packaging count for both ESM
and security updates. However, if the package upgrade
comes from ESM, we still count it as a security update.
This can provide confusing messages to users, since
we don't say in that message that security updates contain
both source of packages. To better handle that, we are
now only treating as security updates only security upgrades
that are not related to ESM packages. To further make that
distinction, we are updating the message to show
standard security updates instead of just security updates
Currently, the apt-check script is configured to only handle
package count for ESM Infra. We are now updating the logic
to also handle ESM Apps packages as well.
Furthermore, we are also updating the messaging that
is created in apt-check. We are advertising ESM Apps if the
service is disabled and only messaging about ESM Infra if the
distro is already on ESM mode
The unit tests of package-data-downloader expect 404 failures running
against a SimpleHTTPServer in unit tests for "not-here.txt". This results
in stderr messages to console that look like test errors:
These are not actually test failures, but emitting them in the test
logs leads to confusion when reviewing the test runs.
Unit tests probably shouldn't be running integration testing anyway.
Instead mock subprocess.call on these tests to avoid raising confusing
error messages to console.
d/control d/tests/control: move pep8 dependency into autopkgtest control
pep8 is only referenced by tests/test_pep8.py via subprocess due to the
autopkgtest nosetests3.
The pep8 pkg is removed from Build-Depends because it is not
needed for package build which only runs the following during build:
python3 test_package-data-downloader.py