Am 16.05.22 um 11:10 Uhr schrieb Dario Faggioli:
Hello!
I'd be curious if I'm the only one running into the following, when doing, for instance, `transactional-update dup`, or similar):
[zypper downloading and installing packages] There are running programs which still use files and libraries deleted or updated by recent upgrades. They should be restarted to benefit from the latest updates. Run 'zypper ps -s' to list these programs.
Since the last system boot core libraries or services have been updated. Reboot is suggested to ensure that your system benefits from these updates. 2022-05-16 10:23:35 Application returned with exit status 107. ERROR: zypper --no-cd dup on /.snapshots/269/snapshot failed with exit code 107! [...] Basically, the dup went well, but zypper is informing us that some service reload and/or a reboot is necessary.
Now, this is of course not particularly useful as a message, on a t-u based system, as we're going to reboot anyway. But the real problem seems to me to be that zypper itself returns 107, when printing that message.
As Thorsten said already: return code 107 is ZYPPER_EXIT_INF_RPM_SCRIPT_FAILED, so that's a real error condition. What you are thinking about are 102 and 103 (ZYPPER_EXIT_INF_REBOOT_NEEDED / ZYPPER_EXIT_INF_RESTART_NEEDED), and these are ignored as expected. Cheers, Ignaz