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:
On 2022-12-09 00:23, Stakanov wrote:
In data giovedì 8 dicembre 2022 21:05:17 CET, Carlos E. R. ha scritto:
LC_ALL=en_US.UTF-8 zypper in libKF5ContactEditor.so.5
security repo: was the repo already deactivated for 15.3?? I had it deactivated now to find out if it was related and to lower the number of possible errors.
I can't know when it was deactivated.
Maybe the file "/var/log/zypper.log" has the event registered.
There is a text similar to this:
... alias : Ext_Packman ... name : EXT: Packman Repository ... enabled : 0
that maybe tells when it was deactivated.
You can get the date by "ls -la /etc/zypp/repos.d"
It will have the date last modified.
Like this from my computer:
ls -la /etc/zypp/repos.d total 72 drwxr-xr-x 4 root root 4096 Dec 3 13:03 . drwxr-xr-x 10 root root 4096 Oct 11 13:09 .. -rw-r--r-- 1 root root 97 Jan 16 2021 adobe.repo -rw-r--r-- 1 root root 115 Oct 12 2021 brave-browser.repo -rw-r--r-- 1 root root 124 Dec 4 07:27 mozilla.repo -rw-r--r-- 1 root root 209 Jul 24 16:56 os-repo-backports-update.repo -rw-r--r-- 1 root root 203 Jun 29 15:28 os-repo-non-oss.repo -rw-r--r-- 1 root root 191 Jun 29 15:28 os-repo-oss.repo -rw-r--r-- 1 root root 205 Jul 24 16:57 os-repo-sle-update.repo -rw-r--r-- 1 root root 193 Jul 24 16:57 os-repo-update-non-oss.repo -rw-r--r-- 1 root root 186 Jul 24 16:58 os-repo-update-oss.repo -rw-r--r-- 1 root root 228 Jun 29 17:44 os-repo-virtual.repo -rw-r--r-- 1 root root 178 Jun 9 20:44 packman.repo -rw-r--r-- 1 root root 182 Oct 12 2021 skype-stable.repo -rw-r--r-- 1 root root 233 Jun 9 20:53 teamviewer.repo
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? I thought the 15.3 have not been set to EOL up to now, did not receive a warning. Thanks.