Hi, last night two of my Tumbleweed machines said that there are no repos at all when I tried to update them or install software. I opened the Yast repo window and they were there, just all disabled. I enabled them and then things went back to normal. What can cause this?
I update one of them with zypper dup, the other with transactional-update dup. The previous update a day before seemed to go normally.
In two other Tumbleweeds on my LAN this problem did not appear, yet.
I do not understand either. But as you did this apparently unattended and also enabled them already, you destroyed any evidence I am afraid. E.g. the change timestamps of the repo files could have suggested us at least when the disabling happened.
I re-read your first post and I am now not sure you did it unattended. But I guess the same is true: no investigation of status and contents of the repo files (they are at /etc/zypp/repos.d ).
You can still wait if others here have a similar experience.
I had the same effect on various TW machines throughout the last weeks. And annoying Discover spam on available updates, which I disabled (settings for Discover pop-up), just to have them back the next day.
I uninstalled Discover6 on all my TW installs in the meantime and now watch if repos get disabled again in the future. tbc…
You are right, I indeed disabled the updates in Discover, because I do the updating with a script and Discover locks the database while it checks for the updates.
I think this is it.
I need no notifications, but this is a small problem. At least I was not hacked in sinister ways.
For my taste this Discover is over the top. I have a free will to decide from which source I want my updates, therefore I configure the mirrors manually.
Even worse is this package drawn in e.g. with NVIDIA driver install setting all repos to opensuse CDN, it’s another nightmare to me. Linux was made to have a choice. Not let others make decisions over your head.
Some decisions surely need to be made about the defaults, but they will not work for everyone.
I did not follow it but the repo management seems to show traces of some struggles in the past about how to make it work for most people. Nvidia is not trivial.
I use nomodeset=0 in my server to stay out of trouble.