That is consistent with the chain of events you described Henk. When libzypp processed the freshly installed product metadata on Dec 16, it instantiated the product-managed repos, Unfortunately, Ilibzypp doesnât appear to reconcile by URL, so you ended up with duplicated repos. I think this does warrant a bug report, though it appears to be a corner case as Iâve not seen it reported elsewhere. Maybe there are others who are blissfully unaware.
I am slowly getting hat you mean and what happened.
The update/patch lead to the re-install of those packages. Which then created those four repo definitions without checking if the corresponding openSUSE-repos-* package is installed or not.
I will try to formulate a bug report based on that. Hoping that a correction will result in people like me not having to check their repo list after each update.
It does look like a âone-offâ type of event. Iâm not sure exactly why you were impacted, and not others running Leap 15.6. Just to clarify, the openSUSE-repos-* packages arenât involved here; this was triggered solely by the release packages installing the product metadata.
Duplicating repo URLs is not an issue. Until those four repos started appearing, I had no âdisabledâ repos, only enabled ones. I manage enabling, and most else, manually via filename changes, deleting the last character, or appending a(n) extra character(s), and expect timestamps to be uniform so as to notice when any change is made that I did not make.
Yes, it looks like something that will only take place once in a few years or so.
But I will post a bug report nevertheless. There are always people that are glad to know these hings and use them for improvement.
Maybe because you have to note this by incident. I did see it only because there was a discussion of repos on some other thread and I just looked at mine. One could e.g. also detect this because the extra refresh done will take extra time. Or by using a zypper se and seeing packages mentioned twice.
But to fact that they werenât there should have signaled that altering the repository list is unwanted on the system.
Why do you believe that? Repos and repo list are not write protected. They can and will be altered by any package. E.g. some external packages like Google Chrome add the Google repo automatically to be able to update the package. Using 1-Click installation will add random reposâŚand so forth.
I see what you mean Henk, but the absence of openSUSE-repos-* isnât what prevents libzypp from instantiating product-managed repos, and libzypp simply enforces what the metadata declares. In other words, itâs a product-management policy issue, not something the presence or absence of openSUSE-repos-* would control.
The openSUSE-repos-*packages are user-visible, pre-created repo files, not tied to /etc/products.d/*.prod.
That may all be fine, but at the user (system manager) I can at least signal that something is not OK here.
On one side it is said: you can choose to manage yourself.
On the other side they do: we litter your repo list regardless of what you want.
I hope someone starts thinking about this controversy.
Why make such a fuss and uprising, when 4 official repos are added by accident by an official openSUSE package. This gets more and more ridiculous. You are wasting your and others time.
The 4 repos do not cause any harm.
Removing the 4 repos is an effort of 5 seconds. Creating a proper bugreport 3 minutes.
Discussing forward and backward since 4 days in the forumâŚ
I am talking here about the standard/official repos only. Products that add there own repo do not interfere directly with those and I hope they document this thus one can check and eventualy change those to oneâs policy.
About the infamous one-click installs I can only say that I may have used them one or two times years (5-10?) ago and if I remember correctly there was an option to add the repo or not. On with I either choose not, or immediate went to disable it (and alter Name and Alias to my liking).
That is what we know now. Not when I started this topic.
I am not wasting your time. While I appreciate your contributions because they are always amongst the better ones here, you are free to answer or not and even to read this or not.
See my ideas about this above in another post.
It is not about the removing (I did that already days ago). It is about understanding what is going on on the systems I manage. And as I only detected this by incident, I am really not convinced that it does not touch others.
I doubt. As @kasi042 uses openSUSErepos-*` package he had them already. Only thing that âhitâ him was the date/time, which maybe confusing when seen, but who will see it?
If I understand correct, then @mrmazda is using a rather blunt way of blocking altering the repo list. (see somewhere above).
I assume you also use the openSUSE-repos-* package (I conclude this from other posts on the forum where you advertise the pros of them), thus you will also not have new repos added because they are already there. But you could check the mtime of them to see if you got the update.
Henk, please, please, please. Take some steps back, take a deep breath, have a coffee or tea and read the answers that you got from different ppl in this thread again. He got the 4 repos the same like you âon topâ. That is why i used that term in one of my answers. He got the 4 unmanaged repo âon topâ of the set of managed repos which are provided by the openSUSE-repos-* service package.
To make it even more obvious. When you use the openSUSE-repos-* package, the repo files have following syntax:
/etc/zypp/repos.d/openSUSE:update-sle.repo
The repo files which got provided by the update have following syntax:
/etc/zypp/repos.d/repo-sle-update.repo
And that is why Deano tried to stress this point already several times and tried to explain it to you. These 4 repos got added to some users system independently if you use openSUSE-repos-* or not.