-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2018-02-26 a las 09:50 -0000, Richmond escribió:
I received a security update for Lame, but it wouldn't install due to vendor change. I decided to remove Packman as I only use it for playing MP3 and it doesn't seem to be necessary for that anymore.
So I went into yast2 sw_single and selected the repository view, and selected Packman and then selected Delete all packages in this list. I had to resolve dependencies which I did by selecting downgrade or de-installation in every case. One of the things it removed was Chromium.
I then disabled Packman, and re-installed Chromium. But this seemed to re-install libmp3lame from Packman even though it was disabled. So I removed it again and then removed Packman, then re-installed Chromium. This time it installed libmp3lame0 from openSUSE-Leap-42.3-Update. So what is the correct procedure for doing this, and why does yast2 install software from disabled repositories?
Huh. The first move is to, on the packman repo view, "disable switch to this repo" if it appears. Next is disable the packman repo. (If something was reinstalled from packman, it means you did not disable it, or that you have it twice. YaST can not enable itself a repo) So the after pacman is disabled, go to the oss repo and click "switch system packages to this repo". Then go to to the @system repo, select the unmaintained packages view, then force all of those to update even if it means repository change. Find any package that came from packman and upgrade or delete it, solving any dep in the road. - -- Cheers Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlqUE+EACgkQja8UbcUWM1ytQAEAhLiQ4ebhw+BnzZkMf23Qsozr Zlgqeil4V76GKBHGVs8A/iPqqD5MGdyxEcTzecLTbwbwgC2ArFJszfRay5KuZ5xA =6dlU -----END PGP SIGNATURE-----