It was puzzling indeed, but now I have a reproduction step.
$ sudo apt update
-> no warning
$ sudo apt upgrade
-> to install something to invoke the rsyslog trigger.
Processing triggers for rsyslog (8.2312.0-3ubuntu3) ...
Warning: The unit file, source configuration file or drop-ins of rsyslog.service changed on disk. Run 'systemctl daemon-reload' to reload units.
$ sudo apt update
-> will see the warning.
The warning happens with every systemctl commands so it's not really ubuntu-pro-tools specific issue. However, systemctl warnings are not expected with `apt` commands usually so that's why this could be considered as a surprise. For fixing this properly, the place may not be in pro-tools itself but somewhere else.
It was puzzling indeed, but now I have a reproduction step.
$ sudo apt update
-> no warning
$ sudo apt upgrade
-> to install something to invoke the rsyslog trigger.
Processing triggers for rsyslog (8.2312.0-3ubuntu3) ...
Warning: The unit file, source configuration file or drop-ins of rsyslog.service changed on disk. Run 'systemctl daemon-reload' to reload units.
$ sudo apt update
-> will see the warning.
The warning happens with every systemctl commands so it's not really ubuntu-pro-tools specific issue. However, systemctl warnings are not expected with `apt` commands usually so that's why this could be considered as a surprise. For fixing this properly, the place may not be in pro-tools itself but somewhere else.