Update conflict

Hi all, hi Wolfi,
today I am having a conflict while updating:

Detected 2 file conflicts:

File /usr/lib64/qt5/plugins/libmarble_part.so
from install of
marble5-15.08.3-83.1.x86_64 (Wolfie-TW-KDE-FW5)
conflicts with file from install of
marble-15.08.3-1.1.x86_64 (repo-oss)

File /usr/lib64/qt5/plugins/plasma_runner_marble.so
from install of
marble5-15.08.3-83.1.x86_64 (Wolfie-TW-KDE-FW5)
conflicts with file from install of
marble-15.08.3-1.1.x86_64 (repo-oss)

These are my repos:

#                    | Alias              | Nome               | Abilitato             | Controllo GPG              | Aggiornamento | Priorità
---------------------+--------------------+--------------------+-----------------------+----------------------------+---------------+----------
 1 | File_Commander     | File Commander     | Sì | ( p) Sì | Sì           |   99
 2 | Insync             | Insync             | Sì | (r ) Sì | Sì           |   99
 3 | Wolfie-TW-KDE-FW5  | Wolfie-TW-KDE-FW5  | Sì | (r ) Sì | Sì           |  100
 4 | packman-essentials | packman-essentials | Sì | (r ) Sì | Sì           |   98
 5 | repo-debug         | repo-debug         | Sì | (r ) Sì | Sì           |   99
 6 | repo-non-oss       | repo-non-oss       | Sì | (r ) Sì | Sì           |   99
 7 | repo-oss           | repo-oss           | Sì | (r ) Sì | Sì           |   99
 8 | repo-update        | repo-update        | Sì | (r ) Sì | Sì           |   99
 9 | vivaldi            | vivaldi            | Sì | ( p) Sì | Sì           |   99
10 | vivaldi-beta       | vivaldi-beta       | Sì | ( p) Sì | Sì           |   99

As you can see, Wolfi’s repo has higher priority, so why the conflict?

T.I.A.

Cris

What does 'zypper dup --from …" give ( use Wolffi’s repo name or number after this one )?

Well, that’s to be expected.
marble 15.08.x is the KF5 version, so it overlaps with my KF5 based marble5.
So either install one or the other, but not both.

If you want to have a KDE4 based marble, I do have marble-15.04.3 in my repo…

As you can see, Wolfi’s repo has higher priority, so why the conflict?

It doesn’t have.
A priority of 100 is lower than 99…

See also “man zypper”:

           -p, --priority positive-integer
               Set priority of the repository. Priority of 1 is the highest,
               the higher the number the lower the priority. Default priority
               is 99. Packages from repositories with higher priority will be
               preferred even in case there is a higher installable version
               available in the repository with a lower priority.

But I am not installing anything. I am only trying to update my system with “zypper dup”.

Yes, you’re right.
So here’s my problem (I think): I have Marble5 installed from your repository.
Now Marble5 is available on the official repository too, and since it has a higher priority it tries to update it from there. But since I have it installed from your repo, it tries to install the update from your repo too.

How would you solve it? Should I set a higher priority on your repo (I am a bit nervous about this)?
Is there a way to tell zypper to switch repo from yours to the official one for that package? I have seen zypper doing this automatically sometimes.

Here is my situation regarding marble:

S | Nome                             | Tipo        | Versione     | Arch   | Repository            
--+----------------------------------+-------------+--------------+--------+-----------------------
i | Marble                           | application |              | noarch | Wolfie-TW-KDE-FW5     
  | libmarblewidget-debugsource      | package     | 15.08.3-1.1  | x86_64 | repo-debug            
  | libmarblewidget-debugsource      | package     | 15.08.3-1.1  | i586   | repo-debug            
  | libmarblewidget-devel            | package     | 15.08.3-1.1  | x86_64 | repo-oss              
  | libmarblewidget-devel            | package     | 15.08.3-1.1  | i586   | repo-oss              
i | libmarblewidget-qt5-22           | package     | 15.08.2-88.1 | x86_64 | (Pacchetti di sistema)
v | libmarblewidget-qt5-22           | package     | 15.08.3-1.1  | x86_64 | repo-oss              
v | libmarblewidget-qt5-22           | package     | 15.08.3-1.1  | i586   | repo-oss              
v | libmarblewidget-qt5-22           | package     | 15.08.3-83.1 | x86_64 | Wolfie-TW-KDE-FW5     
v | libmarblewidget-qt5-22           | package     | 15.08.3-83.1 | i586   | Wolfie-TW-KDE-FW5     
  | libmarblewidget-qt5-22-debuginfo | package     | 15.08.3-1.1  | x86_64 | repo-debug            
  | libmarblewidget-qt5-22-debuginfo | package     | 15.08.3-1.1  | i586   | repo-debug            
  | libmarblewidget-qt5-22-debuginfo | package     | 15.08.3-83.1 | x86_64 | Wolfie-TW-KDE-FW5     
  | libmarblewidget-qt5-22-debuginfo | package     | 15.08.3-83.1 | i586   | Wolfie-TW-KDE-FW5     
i | libmarblewidget20                | package     | 14.12.3-1.2  | x86_64 | (Pacchetti di sistema)
i | libmarblewidget21                | package     | 15.04.3-1.1  | x86_64 | Wolfie-TW-KDE-FW5     
v | libmarblewidget21                | package     | 15.04.3-1.1  | i586   | Wolfie-TW-KDE-FW5     
  | libmarblewidget21-debuginfo      | package     | 15.04.3-1.1  | x86_64 | Wolfie-TW-KDE-FW5     
  | libmarblewidget21-debuginfo      | package     | 15.04.3-1.1  | i586   | Wolfie-TW-KDE-FW5     
i | libmarblewidget22                | package     | 15.08.3-1.1  | x86_64 | repo-oss              
v | libmarblewidget22                | package     | 15.08.3-1.1  | i586   | repo-oss              
  | libmarblewidget22-debuginfo      | package     | 15.08.3-1.1  | x86_64 | repo-debug            
  | libmarblewidget22-debuginfo      | package     | 15.08.3-1.1  | i586   | repo-debug            
  | lmarbles                         | package     | 1.0.8-1.3    | x86_64 | repo-oss              
  | lmarbles                         | package     | 1.0.8-1.3    | i586   | repo-oss              
  | lmarbles-debuginfo               | package     | 1.0.8-1.3    | x86_64 | repo-debug            
  | lmarbles-debuginfo               | package     | 1.0.8-1.3    | i586   | repo-debug            
  | lmarbles-debugsource             | package     | 1.0.8-1.3    | x86_64 | repo-debug            
  | lmarbles-debugsource             | package     | 1.0.8-1.3    | i586   | repo-debug            
v | marble                           | package     | 15.08.3-1.1  | x86_64 | repo-oss              
v | marble                           | package     | 15.08.3-1.1  | i586   | repo-oss              
i | marble                           | package     | 15.04.3-1.1  | x86_64 | Wolfie-TW-KDE-FW5     
v | marble                           | package     | 15.04.3-1.1  | i586   | Wolfie-TW-KDE-FW5     
  | marble                           | srcpackage  | 15.04.3-1.1  | noarch | Wolfie-TW-KDE-FW5     
v | marble-data                      | package     | 15.08.3-1.1  | noarch | repo-oss              
i | marble-data                      | package     | 15.04.3-1.1  | noarch | Wolfie-TW-KDE-FW5     
  | marble-debuginfo                 | package     | 15.08.3-1.1  | x86_64 | repo-debug            
  | marble-debuginfo                 | package     | 15.08.3-1.1  | i586   | repo-debug            
  | marble-debuginfo                 | package     | 15.04.3-1.1  | x86_64 | Wolfie-TW-KDE-FW5     
  | marble-debuginfo                 | package     | 15.04.3-1.1  | i586   | Wolfie-TW-KDE-FW5     
  | marble-debugsource               | package     | 15.04.3-1.1  | x86_64 | Wolfie-TW-KDE-FW5     
  | marble-debugsource               | package     | 15.04.3-1.1  | i586   | Wolfie-TW-KDE-FW5     
  | marble-devel                     | package     | 15.08.3-1.1  | x86_64 | repo-oss              
  | marble-devel                     | package     | 15.08.3-1.1  | i586   | repo-oss              
  | marble-devel                     | package     | 15.04.3-1.1  | x86_64 | Wolfie-TW-KDE-FW5     
  | marble-devel                     | package     | 15.04.3-1.1  | i586   | Wolfie-TW-KDE-FW5     
v | marble-doc                       | package     | 15.08.3-1.1  | noarch | repo-oss
i | marble-doc                       | package     | 15.04.3-1.1  | noarch | Wolfie-TW-KDE-FW5
  | marble-kde                       | package     | 15.08.3-1.1  | x86_64 | repo-oss
  | marble-kde                       | package     | 15.08.3-1.1  | i586   | repo-oss
  | marble-kde-debuginfo             | package     | 15.08.3-1.1  | x86_64 | repo-debug
  | marble-kde-debuginfo             | package     | 15.08.3-1.1  | i586   | repo-debug
  | marble-qt                        | package     | 15.08.3-1.1  | x86_64 | repo-oss
  | marble-qt                        | package     | 15.08.3-1.1  | i586   | repo-oss
  | marble-qt-debuginfo              | package     | 15.08.3-1.1  | x86_64 | repo-debug
  | marble-qt-debuginfo              | package     | 15.08.3-1.1  | i586   | repo-debug
i | marble5                          | package     | 15.08.2-88.1 | x86_64 | (Pacchetti di sistema)
v | marble5                          | package     | 15.08.3-83.1 | x86_64 | Wolfie-TW-KDE-FW5
v | marble5                          | package     | 15.08.3-83.1 | i586   | Wolfie-TW-KDE-FW5
  | marble5                          | srcpackage  | 15.08.3-83.1 | noarch | Wolfie-TW-KDE-FW5
i | marble5-data                     | package     | 15.08.2-88.1 | noarch | (Pacchetti di sistema)
v | marble5-data                     | package     | 15.08.3-83.1 | noarch | Wolfie-TW-KDE-FW5
  | marble5-debuginfo                | package     | 15.08.3-83.1 | x86_64 | Wolfie-TW-KDE-FW5
  | marble5-debuginfo                | package     | 15.08.3-83.1 | i586   | Wolfie-TW-KDE-FW5
  | marble5-devel                    | package     | 15.08.3-83.1 | x86_64 | Wolfie-TW-KDE-FW5
  | marble5-devel                    | package     | 15.08.3-83.1 | i586   | Wolfie-TW-KDE-FW5
i | marble5-doc                      | package     | 15.08.2-88.1 | noarch | (Pacchetti di sistema)
v | marble5-doc                      | package     | 15.08.3-83.1 | noarch | Wolfie-TW-KDE-FW5
i | marble5-kde                      | package     | 15.08.2-88.1 | x86_64 | (Pacchetti di sistema)
v | marble5-kde                      | package     | 15.08.3-83.1 | x86_64 | Wolfie-TW-KDE-FW5
v | marble5-kde                      | package     | 15.08.3-83.1 | i586   | Wolfie-TW-KDE-FW5
  | marble5-kde-debuginfo            | package     | 15.08.3-83.1 | x86_64 | Wolfie-TW-KDE-FW5
  | marble5-kde-debuginfo            | package     | 15.08.3-83.1 | i586   | Wolfie-TW-KDE-FW5
  | marble5-qt                       | package     | 15.08.3-83.1 | x86_64 | Wolfie-TW-KDE-FW5
  | marble5-qt                       | package     | 15.08.3-83.1 | i586   | Wolfie-TW-KDE-FW5
  | marble5-qt-debuginfo             | package     | 15.08.3-83.1 | x86_64 | Wolfie-TW-KDE-FW5
  | marble5-qt-debuginfo             | package     | 15.08.3-83.1 | i586   | Wolfie-TW-KDE-FW5
  | plasma-addons-marble             | package     | 4.14.3-8.1   | x86_64 | Wolfie-TW-KDE-FW5
  | plasma-addons-marble             | package     | 4.14.3-8.1   | i586   | Wolfie-TW-KDE-FW5
  | plasma-addons-marble-debuginfo   | package     | 4.14.3-8.1   | x86_64 | Wolfie-TW-KDE-FW5
  | plasma-addons-marble-debuginfo   | package     | 4.14.3-8.1   | i586   | Wolfie-TW-KDE-FW5

Cris

That’s a contradiction… :wink:
If you update your system you are installing something, by definition (unless there are no updates…).

Yes, you’re right.
So here’s my problem (I think): I have Marble5 installed from your repository.

Yes, and that conflicts on a file level with marble 15.08.3 from the main repo.

Now Marble5 is available on the official repository too

No, it isn’t.
It’s called just marble there, but yes, it’s the same KF5 based version.

and since it has a higher priority it tries to update it from there.
But since I have it installed from your repo, it tries to install the update from your repo too.

Yes and no, it tries to update marble, not marble5.

How would you solve it? Should I set a higher priority on your repo (I am a bit nervous about this)?

Yes, that what you should do.

Is there a way to tell zypper to switch repo from yours to the official one for that package? I have seen zypper doing this automatically sometimes.

“zypper dup” ignores from what repository a package comes from, it just picks the highest available version from the configured repos (or takes the package from the repo with the highest version), it doesn’t respect vendors.
That’s how it is designed.

There is a command line option that has been added recently, to make “zypper dup” respect “vendor stickiness” though: --no-allow-vendor-change

Thank you,
I can confirm that this completely solved my problems.

Cris