Accidentally added leap repos to tumbleweed

Hi, I am new to Tumbleweed and just learning the package management system. I’d like to know if and how badly I screwed up my system; I can’t tell.

I accidentally ran the following lines suggested at SDB:KDE repositories - openSUSE Wiki for Leap even though I am on Tumbleweed.

zypper ar -fp 75 '$releasever' KDE-Qt5 
zypper ar -fp 75 '$releasever' KDE-Qt6 
zypper ar -fp 75 '$releasever' KDE-Frameworks 
zypper ar -fp 75 '$releasever' KDE-Frameworks5 
zypper ar -fp 75 '$releasever' KDE-Applications 
zypper ar -fp 75 '$releasever' KDE-Extra 
zypper -v dup --allow-vendor-change

Then I accepted what I thought was a fairly minor change to existing system. 6 new packages and 5 removed which were changes from 5 to 6 (I think it’s qt?).

But now that I realized my error, I scrolled up to save the terminal output. So I see that >100 packages were upgraded. But many of them have nothing to do with kde. Lots of command line applications such as tmux, vim, btop. 3 packages changed vendor. And ‘openSUSE Tumbleweed 20240221-0 → 20240222-0’

I also see that there were errors adding a few of the KDE repos although they still show up in the repo list. So not sure if they were added in the first place.

I just installed this system in the past couple of days. Of course first order of business with a new install is refresh the repos and apply needed upgrades. Then installed many of the packages which have now been upgraded today.

I’m confused if the >100 upgraded packages and tumbleweed version change had to do with the addition of the Leap KDE repo or if they were just a coincidence?

I now have disabled the Leap repos. And will switch the 3 vendor changed packages back to correct repo. Is there anything else to do? Do I have to do something to fix the >100 other packages?

And is there some sort of safeguard that I can enable to prevent myself from doing something like this in the future? It seems like an extra layer of errorchecking that would look for wrong distro names in the URL prior to adding would be smart. Cause I am not smart but I use linux anyway.

I did not read all your details. But the general idea when you added wrong reo(s) and installed already from them is to remove them again and do a zypper dup to the standard repo. In the Tumbleweed case, just a

zypper dup --allow-vendor-change

When you did the vendor switch to Packman earlier, just must repeat that cation then after this.

On Tumbleweed $releasever should be snapshot date (something like 20240221) and such repositories simply do not exist. Show full output of

zypper lr -d


zypper dup --allow-vendor-change

after having disable the “wrong” repositories. This assumes you have only the standard ones.

You just accept that Linux is for those who use there brains. You should make yourself reasonable aware of what you are goinf to do. If it is the crossing of the street or the usage of RPMs and repositories with zypper and/or YaST > Software.

It most cases it is useless to build in more “do your really want to …” layers. It will irritate most system managers to the utmost. And will loose usefulness very soon, because the extra click on “yes” or the hit of Return will be done automatic within a short time. And that is not only for system managers, but for all man-computer interfaces.

The safeguard here is that you have to be root and thus are at the toes of your carefulness.

1 Like
zypper lr -d
#  | Alias                            | Name                                   | Enabled | GPG Check | Refresh | Priority | Type   | URI                                                                  | Service
 1 | KDE-Applications                 | KDE-Applications                       | No      | ----      | ----    |   75     | N/A    | |
 2 | KDE-Extra                        | KDE-Extra                              | No      | ----      | ----    |   75     | N/A    |       |
 3 | KDE-Frameworks                   | KDE-Frameworks                         | Yes     | (r ) Yes  | Yes     |   74     | rpm-md |                      |
 4 | KDE-Frameworks5                  | KDE-Frameworks5                        | No      | ----      | ----    |   75     | N/A    |                  |
 5 | KDE-Qt5                          | KDE-Qt5                                | No      | ----      | ----    |   75     | N/A    |                          |
 6 | KDE-Qt6                          | KDE-Qt6                                | No      | ----      | ----    |   75     | N/A    |                          |
 7 | M17N:fonts                       | M17N:fonts                             | Yes     | (r ) Yes  | Yes     |   80     | rpm-md |                          |
 8 | X11:xfce                         | X11:xfce                               | Yes     | (r ) Yes  | Yes     |   80     | rpm-md |                            |
 9 |    | Main Repository (NON-OSS)              | Yes     | (r ) Yes  | Yes     |   99     | rpm-md |                                               |
10 |        | Main Repository (OSS)                  | Yes     | (r ) Yes  | Yes     |   99     | rpm-md |                                                   |
11 | | Main Update Repository                 | Yes     | (r ) Yes  | Yes     |   99     | rpm-md |                                                     |
12 | repo-debug                       | openSUSE-Tumbleweed-Debug              | No      | ----      | ----    |   99     | rpm-md |                                             |
13 | repo-openh264                    | Open H.264 Codec (openSUSE Tumbleweed) | Yes     | (r ) Yes  | Yes     |   99     | rpm-md |                                             |
14 | repo-source                      | openSUSE-Tumbleweed-Source             | No      | ----      | ----    |   99     | N/A    |                                            |

Thanks! I did it anyway even though I have a few extra repos as per above.

I had already reverted the 3 vendor-changed packages to main tumbleweed repo. When I run this command there are 3 upgrades, 3 vendor changes, 2 new and 1 removed packages. All seem to be related to the removed/added/vendor-changed packages from the original error.

I think it is to do with the KDE-Frameworks repo. And probably OK? If I understand it, I probably should have reverted them to the Frameworks repo instead of the main repo, if I am going to have Frameworks enabled?

I guess it’s a philosophical difference because I think linux should be accessible to all kinds of people not just the elite who already understands it.

Crossing the street is a very apt example. There is actually a tonne of thought, structure and engineering put into street crossing so that the average person can be protected. Traffic laws and enforcement, education, signage, lights, audio cues, paint, structural elements like boulevards and islands, municipal decisions like one-way streets, traffic calming, accessibility like bumpy surfaces to indicate to blind people where the crossing is, speeding cameras, speed bumps… etc etc etc. All put in place so that errors in judgement are less likely to happen and less dangerous when they do.

Yes, and Linux has a very steep learning curve for the system manager (not for the user though, (s)he can be a happy desktop user without too much hassle). Most people will admit that. And as one hasn’t the same amount of time as being trained in road traffic (from being only a few years old), there will be much falling and struggling. That is how it is.


This (and other) repositories does not exist, so whatever happened could not be due to these non-existent repositories.

I like how sysadmin is such a loaded word, this sweet guy decided to call them a system manager to not scare people away :joy:


You just accept that Linux is for those who use there brains. 

It would be even better for Linux users if they used their brains.

tom kosvic

1 Like

:rofl: :joy:

Couldn’t resist the chance for the ping. Nothing serious. Just for fun.

tom kosvic

I think it’s important to note, though, that Linux is approachable by any user willing to learn. That doesn’t mean we can’t put guardrails in place, though.

We shouldn’t be pushing people away because they have an idea or suggestion, so let’s keep on track here.

With that said…

There isn’t, because there may be situations where using something from a different version can be done safely or makes sense (though I am blanking on such a situation that I’ve run across - the closest is probably using the official Zoom RPM, which is advertised as being for Leap 15.5, but works just fine on Tumbleweed - but that’s not delivered through a repo).

Advanced users will occasionally run into situations where doing things a different way makes sense.

That said, it does seem that it’s a good lesson to pay attention to the URLs for the repos you add - as others may have said, it’s generally best not to add additional repos unless you know what you’re doing and why you’re doing it - and to avoid one-click repos just in general.

Especially those that come from a home: repository - those are not official, but are places where individual users are playing around with package building. They may or may not work anywhere but on that user’s system, and the user may or may not be willing to support it.

But in general, if a repo is not for the distro you’re using (and the URI will be the definitive source of infromation on that), then at the very least, stop and ask a question before proceeding. :slight_smile:

Actually now that I see better what happened, there basically is a guardrail. If the Leap copy/paste lines all have $releasever, then they will never resolve on the the TW version. If the convention is consistent then it will work just fine.

And the other good news is that there don’t seem to be too many additional repos from what I can see. Limited opportunity to make this mistake again.

I know that every distribution, including those with extensive additional repos, counsel their users to stick with the mainline repos. But I never met one that was even close to satisfactory. And these things exist people people want them to. I love the diversity and complexity of tasks I can accomplish on my linux computer. 10 years ago I couldn’t even have imagined it. But some niche packages are required.

In the fresh TW I absolutely had to add the xfce4 extra repo, because the mainline one is sadly incomplete lacking multiple key packages. Even the extra repo doesn’t have everything related that I want. But it’s a big improvement.

I’m guessing not too much xfce users around here? From how sparse the packaging is and the very QTiness of the yast2 applications. (Which are otherwise fantastic! Tools that I have been thinking “why doesn’t this exists??” for years.)

Since nobody addressed my main question of the >100 other packages, I am guessing there was just a coincidental release of packages at the same time. They are not at all implicated.

stop and ask a question before proceeding. :slight_smile:

I will!

1 Like

I think this topic has run it’s course and that the original question is answered.
Related topics can of course be started when needed.
This one will be closed.

1 Like