Installing Umbrello in Argon: KDE Vendor change

As the title says, I’m trying to install Umbrello using openSUSE Argon and I get:

>>> sudo zypper in umbrello                                                                                ±[master] ✓ 
[sudo] password for root: 
Retrieving repository 'Main Update Repository' metadata ..........................................................[done]
Building repository 'Main Update Repository' cache ...............................................................[done]
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: umbrello-19.11.90-lp151.3.1.x86_64 requires libQt5Core.so.5(Qt_5.13)(64bit), but this requirement cannot be provided
  not installable providers: libQt5Core5-5.13.1-lp151.2.1.x86_64[http-download.opensuse.org-ec71d4c5]
 Solution 1: Following actions will be done:
  install libQt5Core5-5.13.1-lp151.2.1.x86_64 (with vendor change)
    openSUSE  -->  obs://build.opensuse.org/KDE
  install libQt5DBus5-5.13.1-lp151.2.1.x86_64 (with vendor change)
    openSUSE  -->  obs://build.opensuse.org/KDE
  install libQt5Gui5-5.13.1-lp151.2.1.x86_64 (with vendor change)
    openSUSE  -->  obs://build.opensuse.org/KDE
  install libQt5Location5-5.13.1-lp151.1.1.x86_64 (with vendor change)
    openSUSE  -->  obs://build.opensuse.org/KDE
  install libQt5Multimedia5-5.13.1-lp151.2.1.x86_64 (with vendor change)
    openSUSE  -->  obs://build.opensuse.org/KDE
  install libQt5Network5-5.13.1-lp151.2.1.x86_64 (with vendor change)
    openSUSE  -->  obs://build.opensuse.org/KDE
  install libQt5NetworkAuth5-5.13.1-lp151.1.1.x86_64 (with vendor change)
    openSUSE  -->  obs://build.opensuse.org/KDE

and so on and so on… I guess I shouldn’t proceed?

I can’t tell you what to do, because it is your system.

You have chosen to use Argon. You should expect some of the newer versions of software to require a vendor change to the unstable repos used with Argon.

If I were in your position, I would probably go with the vendor changes. Maybe make notes, so that you can undo it in case of problems. Or use “/var/log/zypp/history” as a guide to undoing it. If you are using “btrfs”, you could probably undo it with a rollback to an earlier snapshot.

I’m guessing that the proposed solution 1 will probably work out.

Vendor changes don’t (or haven’t) unexpectedly happen on Tumbleweed which is still my main OS. I accidentally discovered Argon the other day and it sounded like KDE Neon but with a Leap base so I thought it would stay in the same repo. I think I installed using btrfs, and certainly did if that was the default.

I suppose, I should stop being a coward and ask myself, “what’s the worst that could happen?”

It turns out that it’s everything crashing! You’ve got to love btrfs and snapper. Argon might not be what I thought it was going to be.

[QUOTE=MyNameIsRichard;2921501]It turns out that it’s everything crashing!</blockquote>
I have avoided Argon.

The problem comes when an application uses an incompatible library version. It should be possible for it all to work, but you need to be careful with keeping the various parts compatible. If you really need the latest versions, it is probably safer to go with Tumbleweed.

You’ve got to love btrfs and snapper.

I’m glad those rollbacks helped you out.