yast2 repos management did not work
Hi, i have a strange problem: yast2 software / repositories i like to add a new repo: add / specify url / next repository name: openSUSE_Tumbleweed-home-Herbster0815-androidstudio url: https://download.opensuse.org/repositories/home:/Herbster0815/openSUSE_Tumbl... next emidiatley i am back inside configure software repositorys normalls it shoult download the specific stuff here. i do NOT see the new repo. [OK] / closing yast zypper lr did not show me the repo. inside /etc/zypp/servcices.d/ i have a file service.service contend: [service] enabled=1 autorefresh=1 url = https://download.opensuse.org/repositories/home:/Herbster0815/openSUSE_Tumbl... type = N/A now: yast2 software /repositories error message appears: Errors occurred while restoring the repository configuration. Error refreshing service service (https://download.opensuse.org/repositories/home:/Herbster0815/openSUSE_Tumbl...): [service:openSUSE:Tumbleweed|https://download.opensuse.org/tumbleweed/repo/oss/] Repository already exists. [contignue] now i have a lot of never configured repos installed: 17 | service:KDE:Qt6 | service:KDE:Qt6 | Ja | ( p) Ja | Ja 18 | service:KDE:Unstable:Applications | service:KDE:Unstable:Applications | Ja | ( p) Ja | Ja 19 | service:KDE:Unstable:Extra | service:KDE:Unstable:Extra | Ja | ( p) Ja | Ja 20 | service:KDE:Unstable:Frameworks | service:KDE:Unstable:Frameworks | Ja | ( p) Ja | Ja 21 | service:KDE:Unstable:Qt | service:KDE:Unstable:Qt | Ja | ( p) Ja | Ja 22 | service:home:Herbster0815 | service:home:Herbster0815 | Ja | ( p) Ja | Ja 23 | service:openSUSE:Tumbleweed | service:openSUSE:Tumbleweed | Ja | ( p) Ja | Ja also shown by zypper lr other tumbleweed systems did NOT show this behavior. trying with zypper to remove number 17 (first of this repo) deletes number 16 my normal tumbleweed update repo. whats going on here? i have no idea, i found that there was in end of 2023 start of 2024 a problwm regarding yast softwaremanagement here is the list of updates of this vomputer: 20240826 20240625 20240617 20240613 20240517 20240419 20231001 20230904 because i think it could be possible that somewhere a config file will be not repaired after a bad update? in begin of 2024 there where some problems regarding zypper softwaremanagement. again, other of my systems, updated not equal to this, show absolute normal behavior, and add the repo correct. simoN -- www.becherer.de
OK, i still have no idear why it was working 5 minutes before the second change on a second system, but: this home repo has a directory: /repo inside this is a file repoindex.xml inside this file are all the unwanted repos which where installed at my system. copiing the file /etc/zypp/repos.d/ -rw-r--r-- 1 root root 260 28. Aug 19:17 openSUSE_Tumbleweed-home-Herbster0815-androidstudio.repo from one of my systems to the other, gaves me a "normal" repo and is working fine. again, it must have had something to do with a update at the server that one system has found the "normal" data, and the other a couple of minutes later only the links to "what ever i do not need". ... home repos .... simoN -- www.becherer.de
On 28.08.2024 23:48, Simon Becherer wrote:
OK, i still have no idear why it was working 5 minutes before the second change on a second system,
but:
this home repo has a directory: /repo inside this is a file repoindex.xml inside this file are all the unwanted repos which where installed at my system.
copiing the file /etc/zypp/repos.d/ -rw-r--r-- 1 root root 260 28. Aug 19:17 openSUSE_Tumbleweed-home-Herbster0815-androidstudio.repo from one of my systems to the other, gaves me a "normal" repo and is working fine.
again, it must have had something to do with a update at the server that one system has found the "normal" data, and the other a couple of minutes later only the links to "what ever i do not need".
What makes you think you do not need them? Packages in this project are built against all these repositories and so any package from this project may have packages from any of these repositories as dependencies: <repository name="openSUSE_Tumbleweed"> <path project="KDE:Qt6" repository="openSUSE_Tumbleweed"/> <path project="KDE:Unstable:Qt" repository="openSUSE_Tumbleweed"/> <path project="KDE:Unstable:Frameworks" repository="openSUSE_Factory"/> <path project="KDE:Unstable:Applications" repository="KDE_Unstable_Frameworks_openSUSE_Factory"/> <path project="KDE:Unstable:Extra" repository="KDE_Unstable_Frameworks_openSUSE_Factory"/> <path project="openSUSE:Tumbleweed" repository="standard"/> <arch>x86_64</arch> </repository> It has been the source of confusion in the past. So, if anything, it is a feature. Now, YaST UI could likely be improved.
... home repos ....
It has nothing to do with a repo being "home" or not. Except I am really surprised where this repository type comes from. I do not see it in project configuration. It is possible it has been configured briefly and now this directory is "stuck". Unfortunately changelog for project config apparently does not exist (at least, not exposed in UI or osc).
participants (2)
-
Andrei Borzenkov -
Simon Becherer