-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2017-03-05 23:30, Richard Werth wrote:
Am Sonntag, 5. März 2017, 22:40:17 CET schrieb Carlos E. R.:
On 2017-03-05 18:49, Frans de Boer wrote:
And no, I did not use zypper dup --no-allow-v at any given time. I always use the yast2 interface.
Well, I don't think yast2 is adequate for updating TW.
Please can you give any hints where to look for the differences between updating with YAST (not allow vendor change) and updating with zypper dup - not-allow-vendor-change?
I think both are working along the priorities.
YaST simply has no equivalent to "zypper dup". I think there is a "factory update" module, but I have never used it. I'm unsure if it is maintained. The best approximation would be, in YaST to select view by repository, choose one, then on the right panel select "update all with newer version", then browse down to find packages in red, then update unconditionally those if appropriate. - -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAli8mg0ACgkQja8UbcUWM1zUoAEAmAzmRBfL8wzEaYN0fTGNretm vrdN3yecuRTxX7dwS1sA/R9lEUA7/B27qFBbE3lVaTCfuE5Gn+GfBDvnQyyDVDqW =sa4Y -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org