I was confused because the #15 - #18 were never added by me. And they are the same as others in the list.
Thus I went looking at the files these entries represent:
boven:/etc/zypp/repos.d # l
total 88
drwxr-xr-x 2 root root 4096 Jan 3 10:04 ./
drwxr-xr-x 12 root root 4096 Oct 14 08:48 ../
-rw-r--r-- 1 root root 172 Oct 28 2024 backports-debug-update.repo
-rw-r--r-- 1 root root 173 Oct 28 2024 backports-update.repo
-rw-r--r-- 1 root root 139 Oct 28 2024 libdvdcss.repo
-rw-r--r-- 1 root root 173 Oct 28 2024 non-oss-debug-update.repo
-rw-r--r-- 1 root root 170 Oct 28 2024 non-oss-debug.repo
-rw-r--r-- 1 root root 173 Oct 28 2024 non-oss-source.repo
-rw-r--r-- 1 root root 167 Oct 28 2024 non-oss-update.repo
-rw-r--r-- 1 root root 169 Oct 28 2024 non-oss.repo
-rw-r--r-- 1 root root 161 Oct 28 2024 oss-debug-update.repo
-rw-r--r-- 1 root root 158 Oct 28 2024 oss-debug.repo
-rw-r--r-- 1 root root 161 Oct 28 2024 oss-source.repo
-rw-r--r-- 1 root root 154 Oct 28 2024 oss-update.repo
-rw-r--r-- 1 root root 157 Oct 28 2024 oss.repo
-rw-r--r-- 1 root root 152 Oct 28 2024 packman.repo
-rw-r--r-- 1 root root 254 Dec 7 12:47 repo-backports-debug-update.repo
-rw-r--r-- 1 root root 199 Dec 7 12:47 repo-backports-update.repo
-rw-r--r-- 1 root root 234 Dec 7 12:47 repo-sle-debug-update.repo
-rw-r--r-- 1 root root 208 Dec 7 12:47 repo-sle-update.repo
-rw-r--r-- 1 root root 161 Oct 28 2024 sle-debug-update.repo
-rw-r--r-- 1 root root 156 Oct 28 2024 sle-update.repo
boven:/etc/zypp/repos.d #
As can be seen they were added (or changed) at December 7 2025 12:47 (MET). That is on a Sunday. Now the system was running at that moment in time, but I do not do normally system maintenance then.
I went to another system here and:
beneden:/etc/zypp/repos.d # l
total 88
drwxr-xr-x 2 root root 4096 Dec 16 09:10 ./
drwxr-xr-x 10 root root 4096 Oct 14 08:55 ../
-rw-r--r-- 1 root root 172 Nov 16 2024 backports-debug-update.repo
-rw-r--r-- 1 root root 173 Nov 16 2024 backports-update.repo
-rw-r--r-- 1 root root 139 Nov 16 2024 libdvdcss.repo
-rw-r--r-- 1 root root 173 Nov 16 2024 non-oss-debug-update.repo
-rw-r--r-- 1 root root 170 Nov 16 2024 non-oss-debug.repo
-rw-r--r-- 1 root root 173 Nov 16 2024 non-oss-source.repo
-rw-r--r-- 1 root root 167 Nov 16 2024 non-oss-update.repo
-rw-r--r-- 1 root root 169 Nov 16 2024 non-oss.repo
-rw-r--r-- 1 root root 161 Nov 16 2024 oss-debug-update.repo
-rw-r--r-- 1 root root 158 Nov 16 2024 oss-debug.repo
-rw-r--r-- 1 root root 161 Nov 16 2024 oss-source.repo
-rw-r--r-- 1 root root 154 Nov 16 2024 oss-update.repo
-rw-r--r-- 1 root root 157 Nov 16 2024 oss.repo
-rw-r--r-- 1 root root 152 Nov 16 2024 packman.repo
-rw-r--r-- 1 root root 254 Dec 7 12:47 repo-backports-debug-update.repo
-rw-r--r-- 1 root root 199 Dec 7 12:47 repo-backports-update.repo
-rw-r--r-- 1 root root 234 Dec 7 12:47 repo-sle-debug-update.repo
-rw-r--r-- 1 root root 208 Dec 7 12:47 repo-sle-update.repo
-rw-r--r-- 1 root root 162 Nov 16 2024 sle-debug-update.repo
-rw-r--r-- 1 root root 156 Nov 16 2024 sle-update.repo
beneden:/etc/zypp/repos.d #
the same at exactly the same time. Now I am 100% sure that I wasnât doing anything on that system at all.
I have a third system here that wasnât even powered on then and it shows the same!
I may have my senior moments, but I do not understand anything here. Can someone please try to explain what happened here. I want to find out if I am still fit to manage Unix/Linux systems, or that I should give up.
EDIT: I checked my agenda. We were not at home on December 7. Thus the systems were all power off!
Birth and Change time are on Tuesday 16 December 2025 09:09. That is the time where I do my weekly updates. So it came with an update and I would like to know which one. But why is the Modify time set earlier?
The issue is different. As can be seen in Henkâs output, the repo service packages are not involved at all.
You have Nvidia hardware, thus the service packages get installed automatically to ease the driver package managemnt.
It is no âmessâ. Simply remove the old set of repos (beginning with d.o.o) and use the service packages. You will never have again to care about the standard openSUSE repos. As example, the switch to Leap 16 is way more easier, as the repos service packages take care about the completely new repo setup (no dedicated update, backport, SLE repos anymore). Without the repo service packages you need to take care manually when repo changes occur, like with Leap 16.
Ah, sorry, misunderstandable. I just wanted to add I got the same repos at the 7th of December just as Henk did. I only mentioned the openSUSE-repos-Leap for sake of completeness.
BTW, the âmessâ is there, I just didnât want to show it all.
I still think that @kasi042 has a point because having the openSUSE-repos-* packages or not, it is still strange that âsomethingâ sets those dates to 2025-09-07 12:47.
Maybe I should add that I was lready hit much earlier (more then a year ago?) by the introduction of the openSUSE-Leap package (I have no Invidia hardware). It was removed then and the repo list cleaned up, thus I assume it has nothing to do with again messing up my repo list.
I browsed through that article. Somewhere at the beginning I read:
Please be aware that files generated by openSUSE-repos in /etc/zypper/repos.d shall not be edited manually as theyâll be overwritten. Users who want to modify repositories shall uninstall openSUSE-repos and maintain repository definitions manually.
And that is exactly my situation since a long time already (see post #4). Thus I trust that my list of repos is not changed by any update within a stable Leap release.
Also, please tell me where I can find in the article that repo files are predated and why this confusing action is done.
Please note that âThis page was last edited on 23 November 2025, at 09:09â, thus before this falsification of dates took place. Thus the authors may not have been aware of it.
In short, I see no explanation at all in the article. Please correct me if I am wrong with a more precise identification of a paragraph.
The fist line will produce a list of files in the package, the second line will show if the files in the package are changed, see here on what the characters mean.
You can dump (âcatâ) all files in the package and check if the 4 repo*.repo files are listed in these files. If so that explains things.
How should a package, which is not installed on a users system, add files to the system of a user? Again, have a look at Henkâs output. It is the first colum marked âSâ, which clearly shows that the service packages are not installed.
