If a package is installed via tl-setup and the package has a depending package that need an upgrade we will not ask the admin if this is OK. The upgrade will be done nevertheless by zypper. The issue is that the zypper backend does not report this scenario back to tl-setup. I did not find a nice way to reproduce this, the issue was found looking into the parsing code.
Should be fixed now. Tested to install build 2016 on a fresh SLES 12. It successfully installed all packages and dependencies. Tester should make sure that tl-setup works as before when needing to install packages and dependencies. If tester can create a scenario where a package's dependency need to be *upgraded* that would be nice to test but I did not manage to do that.
Tested with build 2029 on a fresh install of SLES 12 and 15, and tl-setup works as before when needing to install packages and dependencies. I was not able to create the scenario where a dependency needed to be upgraded. Here is what I tested: 1. Check what version of cups that tl-setup tries to install (cups-2.2.7-3.26.1). 2. Check what the earliest version of cups is available with command: (For me cups-2.2.7-3.17.1). > zypper search -s cups 3. Install the earlier version of cups with > zypper install cups=2.2.7-3.17.1 4. Run tl-setup. It does not try to upgrade cups. The reason tl-setup doesn't upgrade might be because both cups versions belong to 2.2.7-3, but I didn't find any other package that had more suitable versions available.
