Concerns on Updating My Tumbleweed Installation Due to Several Problems and File Conflicts

[ExesCarnival0891]

Thanks for the information everyone, I did not realize my system was becoming a mess.

@knurpht

@ExesCarnival0891 The only thing that might save your system, is to:

• sudo zypper install -f opensuse-repos-tumbleweed, next
• remove all non-Tumbleweed repos
• also remove the ones below

 2 | hardware                 | Hardware tools (openSUSE_Tumbleweed)                 | Yes     | (r ) Yes  | No      | -    |   99     | rpm-md | https://download.opensuse.org/repositories/hardware/openSUSE_Tumbleweed/            | 
 3 | home_RN_asusctl          | asusctl (openSUSE_Tumbleweed)                        | Yes     | (r ) Yes  | No      | -    |   99     | rpm-md | https://download.opensuse.org/repositories/home:/RN:/asusctl/openSUSE_Tumbleweed/   | 
 4 | network_im_signal        | Signal Messaging Devel Project (openSUSE_Tumbleweed) | Yes     | (r ) Yes  | No      | -    |   99     | rpm-md | https://download.opensuse.org/repositories/network:/im:/signal/openSUSE_Tumbleweed/ | 

I’ll do that then and update how it went, thanks.

@knurpht

If you have installed and used opi, remove it and do not use it again until
– you fully understand the implications of using it and solving what ever conflicts it causes
– opi gets fixed so that it will never ever add home: or devel repos. As it is now it is the perfect tool for breaking system consistence.

Double checked, and I can confirm that I did not have opi installed, much less used it. I typically just did zypper addrepo.

@hui

Repo 2, 4 and 11 are factory/developement repos.
Repo 3 is a home repo.
Repo 12 is a developement repo (for a package which is not in the distribution yet).
They do not add themself. The user must add them.

The issues from your first post are created by packages which you installed from the factory/developement repos (can be seen at the versions)

Can you elaborate on how you can tell a repo is a factory/slowroll/home repo? I genuinely did not know those repos were of that type, since the links did not say so (outside of the ones that mention they were slowroll/tumbleweed).

@hcvv

That is a good one. When one disables autorefresh for some repos, I assume that is for a reason. When one then always does a zyyper ref just before doing anything else with zypper, the question is: what is that reason?

I was just paranoid of modifying the repo beyond just adding them. I never disabled autorefresh in any of the repos, its just the ones I added did not have autorefresh on by default.

@hcvv

The typing of this is not needed when you copy/paste the line with the command together with the output (only one line more). And that way of posting is preferred by most people here because they see then in one code snippet all they need: prompt, command and output exactly the same as you saw it on the screen.

Noted, will include the command when pasting the output in the future.

Before I go ahead and do what knurpht recommended, I should probably explain how I added all these repos:

2 | hardware                 | Hardware tools (openSUSE_Tumbleweed)                 | Yes     | (r ) Yes  | No

I added this repo to install solaar. I looked it up and found a page on the Open Build Service to install it.

3 | home_RN_asusctl          | asusctl (openSUSE_Tumbleweed)                        | Yes     | (r ) Yes  | No      | https://download.opensuse.org/repositories/home:/RN:/asusctl/openSUSE_Tumbleweed/

I use a ASUS G14 Laptop, and wanted to install the community ran software for ROG laptops that would act as an alternative to Armoury Crate/GHelper on Windows. You can follow my journey to that in Repository Unknown in KDE Discover & Glitchy Application Window Movement & Installing asusctl + supergfxctl for ASUS ROG Laptops. I am bit hesitant to remove them, but I can always try out Switcheroo Control for graphics switching and CoolerControl to control fans.

 4 | network_im_signal        | Signal Messaging Devel Project (openSUSE_Tumbleweed) | Yes     | (r ) Yes  | No

Since there is no official package compatible with OpenSUSE, I was conflicted on where to get Signal from. I eventually decided to use the repo and found out about the repo through the forum topic Error installing signal-desktop.

11 | security                 | Security tools (openSUSE_Tumbleweed)                 | Yes     | (r ) Yes  | No

I wanted to install the GUI version of Veracrypt. Their .rpm package did not install for me due to some conflicts if I remember correctly. The appimage had some weird bugs, such as auto-mounting all devices leading to a loop of me repeatedly entering my user account password, and the app acting as if I got it wrong even after multiple attempts of getting it right. I eventually found the repo in Veracrypt not installing. That was when I started to use the mount option instead of auto-mount devices, and in retrospect I should’ve tried it out in the appimage version first before installing something else.

12 | snappy                   | snappy                                               | Yes     | (r ) Yes  | Yes

I was trying to install Lunacy, and the only options they had for linux was a .deb package, and an ARM version of the .deb, and from the Snap Store. I installed Lunacy following the Snap instructions, which involved adding that repo. The Lunacy developers do seem to officially carry a flatpak, but as of now, don’t seem to advertising it on their main page, so I got confused. This seems to be a very recent addition when looking at their backlog, so they will probably announce it in the near future.

Again, thanks for the help everyone. In the future I’ll try to stick to flatpaks, appimages, and the base repos installed more often.