[Impact]
Because update-notifier does not explicit have the `lsb-release` package as a dependency, users may install the package and rely on `apt-cdrom-check` to work, but it will fail, since it runs
the `lsb_release -sr` command on it.
[Test case]
To reproduce the issue:
1. Launch a xenial container
2. Install update-notifier on it
3. Run apt-cache depends update-notifier-common
4. Verify that lsb-release does not appear
We are only adding a missing dependency to the package. I cannot think of a problem that this might cause to the users of this package.
[Discussion]
We can verify that `apt-cdrom-check` does make use of the `lsb_release` command. Since we don't have that dependency on the package control file, errors can appear when users are executing/relying on that script.
[Impact]
Because update-notifier does not explicit have the `lsb-release` package as a dependency, users may install the package and rely on `apt-cdrom-check` to work, but it will fail, since it runs
the `lsb_release -sr` command on it.
[Test case]
To reproduce the issue:
1. Launch a xenial container notifier- common
2. Install update-notifier on it
3. Run apt-cache depends update-
4. Verify that lsb-release does not appear
To verify that the error is fixed:
1. Install the new update-notifier from this ppa: /launchpad. net/~lamoura/ +archive/ ubuntu/ update- notifier- test-ppa/ notifier- common
https:/
2. Run apt-cache depends update-
3. Verify that lsb-release will now appear as a dependency
[Where problems could occur]
We are only adding a missing dependency to the package. I cannot think of a problem that this might cause to the users of this package.
[Discussion]
We can verify that `apt-cdrom-check` does make use of the `lsb_release` command. Since we don't have that dependency on the package control file, errors can appear when users are executing/relying on that script.