* Carlos E. R. <robin.listas@telefonica.net> [12-09-22 05:41]:
On 2022-12-09 10:20, Stakanov wrote:
In data venerdì 9 dicembre 2022 04:22:15 CET, Larry Len Rainey ha scritto:
On 12/8/22 21:00, Carlos E. R. wrote:
My fault of not being clear. I asked the user after the error appeared to try to deactivate the repo and do zypper up --allow-vendor-change But this might not have been sufficient because if the versions of the security repo are higher then it will still stay on the security ones (which might cause the error). Usual culprits would be a non compatible ClamAv version or a gpg related issue (which would fit with being in use with kontact.
So what would I do as command to make sure that all packages originally stemming from "security" are substituted with the normal repo versions (just to eliminate the source of error, not because I think security is not ok.
What I originally asked was: has (by openSUSE) the repo been already deactivated for 15.3?
Ah.
The command in that case would be "zypper dup --allow-vendor-change". Normally I would say not to do that, but considering the list of repos is limited, it should be no problem.
really not. use "zypper -v dup " and zypper will announce the necessary changes available and <user> can select those appropriate.
I thought the 15.3 have not been set to EOL up to now, did not receive a warning.
Yes, the warning was posted days ago.
-- Cheers / Saludos,
Carlos E. R. (from 15.4 x86_64 at Telcontar)
-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc