On 2018-01-25 17:51, Knurpht - Gertjan Lettink wrote:
Op donderdag 25 januari 2018 17:02:22 CET schreef Dave Plater:
On 25/01/2018 17:21, Carlos E. R. wrote:
I found the problem!
I located the YaST log. YaST is looking now "mjpegtools-2.0.0-19.6.x86_64.rpm", whereas the server now has "mjpegtools-2.0.0-19.7.x86_64.rpm"
The server has updated content while I was running the upgrade :-/
And it is impossible to go back in YaST and tell it to refresh.
I usually update from dvd (flash drive) without any repos enabled. My update from 42.2 to 42.3 I changed all repos to 42.3 and did a zypper dup --no-allow-vendor-change and it succeeded without error.
Before booting the install DVD I edited all extra repos to point to the 42.3 versions. This saves time and trouble, when YaST finds installed packages that are not in the OSS repo. The DVD-upgrade procedure does the equivalent of "--no-allow-vendor-change". Remember, it is YaST running from the DVD. This procedure works very well on Leap.
Same experiences here. @Carlos: was the vendor change to Packman *ever* done ?
Yes, of course it was. The problem, as I posted before, was that the packman repository was itself updated while I was running the upgrade, in the half an hour between YaST refreshing the repo data, me ticking the options in YaST, and finally doing the upgrade run. It was not all the packman rpms, only a portion. For example, kodi packages were upgraded without problems, I saw them flash by. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)