@paelzer I've uploaded update-motd adding ubuntu-advantage-tools as a test dependency, because it is accidental that it is already installed on test images.
The apt-file check is not ideal, because it lists packages which are in -proposed but pinning does not allow them to be installed. As a mitigation I've retried all affected tests with ubuntu-advantage-tools also added as a trigger. The apt-file results could be filtered by taking pinning
into consideration, but this would not be perfect easily either, thus I think it is not worth it.
@paelzer I've uploaded update-motd adding ubuntu- advantage- tools as a test dependency, because it is accidental that it is already installed on test images.
The apt-file check is not ideal, because it lists packages which are in -proposed but pinning does not allow them to be installed. As a mitigation I've retried all affected tests with ubuntu- advantage- tools also added as a trigger. The apt-file results could be filtered by taking pinning
into consideration, but this would not be perfect easily either, thus I think it is not worth it.
Yes, SRU-ing a test-only fix is not ideal either. The tests are there to ensure that update-motd scripts can be run as a normal user which is done on WSL: https:/ /balintreczey. hu/blog/ introducing- show-motd- message- of-the- day-for- wsl-and- container- shells/ . An alternative of testing every script by update-motd would be generating similar tests for every package shipping and update-motd script.