multiple repositories

Hi. I was looking at my installed repository list and trying to learn how to tweak my multimedia a little more. I discovered some programs are using multiple repositories. When I installed 13.1 I included the basic community repos at installation then went back later to include the others. I used recommendations for Packman support for multimedia. But somehow the oss repo got mixed in there and I have vlc using the packman and oss repos. I noticed some other programs doing the same thing. I have no idea how it happened, but that shouldn’t be should it?
I went to the vendor change info pages to learn how to change to packman but I can’t figure out how. I followed the version change steps but there are dependency problems and I either have to abondon the changes or break the program and I don’t want to do either. I have a hard time understanding how to use the repositories correctly even though I’ve been studying the subject. If I uninstalled the vlc from oss repo would it break anything? Can you help me?


Please can you “show” what you mean. A package like vlc can only be installed from one repo, not from different repos at the same time.

And please do not say only things like: … ncluded the basic community repos …, but show a list of what you hav. We can not answer on assuming what you did:

zypper lr -d

When you doubt you have the multi-media packages installed from Packman, then use YaST > Software > Software management. Choose the Repositories view from the View menu. Then select Packman. You can then click at the right, above the list in the text that says something like: Switch system packages to the versions of this repository. That will switch packages that you have accidently installed from the OSS repo to their Packman version.

IMHO it is a terrible idea to add ALL the community repos. An example is that you really should not have both VLC and Packman. one or the other and Packman is prefered because it supplies lots of other things then VLC stuff. Also heaving all those repos to check out means that every update or any time you install things it will take forever to scan through them. Only add repos that have packages you NEED. Think about this, if it was smart to have all the repos configured and active it would have been done for you. If you go to a restaurant do you order everything on the menu?

Always follow K.I.S.S. principle

After I posted above, it slowly came to my mind that the OP realy could mean with what he said about "included the basic community repos ", that he added a long list (the whole list?) of repos from the community list.

That would indeed mean that a broken system is only something to wait for.

Thank you Henk. I didn’t install ALL the repos. I used the recommendations from the openSUSE:documentation and multimedia sites so some of them shouldn’t show up here:

tony@linux-fkwj:~> zypper lr -d

| Alias | Name | Enabled | Refresh | Priority | Type | URI | Service

1 | | openSUSE BuildService - GNOME:Apps | Yes | Yes | 99 | rpm-md | |
2 | | openSUSE BuildService - Education | Yes | Yes | 99 | rpm-md | |
3 | | openSUSE BuildService - KDE:Extra | Yes | Yes | 99 | rpm-md | |
4 | | openSUSE BuildService - LibreOffice | Yes | Yes | 99 | rpm-md | |
5 | | openSUSE BuildService - Wine CVS Builds | Yes | Yes | 99 | rpm-md | |
6 | | openSUSE BuildService - Database | Yes | Yes | 99 | rpm-md | |
7 | | openSUSE BuildService - filesystems | Yes | Yes | 99 | rpm-md | |
8 | | openSUSE BuildService - Games | Yes | Yes | 99 | rpm-md | |
9 | | openSUSE BuildService - Mozilla | Yes | Yes | 99 | rpm-md | |
10 | | Main Repository (DEBUG) | Yes | Yes | 99 | yast2 | |
11 | | openSUSE BuildService - Java:packages | Yes | Yes | 99 | rpm-md | |
12 | | openSUSE BuildService - devel:languages:python | Yes | Yes | 99 | rpm-md | |
13 | | Packman Repository | Yes | Yes | 99 | rpm-md | |
14 | openSUSE-13.1-1.10 | openSUSE-13.1-1.10 | Yes | No | 99 | yast2 | cd:///?devices=/dev/disk/by-id/ata-hp_CDDVDW_TS-L633N_R3186GFZ786618,/dev/sr0 |
15 | | libdvdcss repository | Yes | Yes | 99 | rpm-md | |
16 | packman-essentials | packman-essentials | Yes | Yes | 99 | rpm-md | |
17 | packman-multimedia | packman-multimedia | Yes | Yes | 99 | rpm-md | |
18 | repo-debug | openSUSE-13.1-Debug | No | Yes | 99 | NONE | |
19 | repo-debug-update | openSUSE-13.1-Update-Debug | No | Yes | 99 | NONE | |
20 | repo-debug-update-non-oss | openSUSE-13.1-Update-Debug-Non-Oss | No | Yes | 99 | NONE | |
21 | repo-non-oss | openSUSE-13.1-Non-Oss | Yes | Yes | 99 | yast2 | |
22 | repo-oss | openSUSE-13.1-Oss | Yes | Yes | 99 | yast2 | |
23 | repo-source | openSUSE-13.1-Source | No | Yes | 99 | NONE | |
24 | repo-update | openSUSE-13.1-Update | Yes | Yes | 99 | rpm-md | |
25 | repo-update-non-oss | openSUSE-13.1-Update-Non-Oss | Yes | Yes | 99 | rpm-md | |

Some of these repos were added along the way. I can’t explain which ones for what reasons but it was for adding some software. I probably have some repos that I don’t need but I don’t know which ones. But I can tell you that the problem I had with VLC not starting or running went away when I completely removed Pulse Audio. 3 libraries were left installed because they had numerous dependency conflicts if uninstalled (over 600 for one, over 800 for another, and more for the 3rd.

I was never able to configure PA like I wanted. But when I removed it other programs started working also: Kmix, Musique, ALSA mixer, and others. If I have repos shown here that I need to get rid of please say. But right now I don’t know of any other problems in my machine. All audio runs through my ext dac and I have complete control over it. I’m still learning.

Happy Linux User

man that is a bit of a mess

a few problems is going to be a understatment

now some repos like mozilla should only have a rather small number of programs
others will REPLACE system files

the first thing it YOU NEED TO SET THE PRIORIES !!!
– yes bold and cap. –
everything is at 99

OpenSUSE is NO DIFFERENT than Fedora,RHEL,Debian

it is very easy to break an install with third party repos

RHEL has “yum- priories”
OpenSUSE /SUSE has the priories setting in yast

0 to 200 with 99 the default

IF one is going to use “packman” then use it and allow VENDER CHANGE
having a mis match of oss and packman WILL CAUSE PROBLEMS

so set packman to a lower number like 50
and place a check in the box " allow vender change "

now this might really take a week or two to straiten out
possibly a month or two
more time than doing a reinstall

after a few updates packman should be used for most multi media
but you might have to use “zypper” and force the vender change
– that WILL take time , doing it one program at a time .

As an example
my repo priories and installed repos

zypper lr -d
#  | Alias                        | Name                               | Enabled | Refresh | Priority | Type   | URI                                                                                   | Service
 1 | Application:Geo              | Application:Geo                    | Yes     | Yes     |   90     | rpm-md |              |        
 2 | OLD-13.1-devel/gcc           | OLD-13.1-devel/gcc                 | Yes     | Yes     |  150     | rpm-md |                    |        
 3 | devel:/gcc                   | devel:/gcc                         | Yes     | Yes     |   95     | rpm-md |                    |        
 4 | | nVidia Graphics Drivers            | No      | No      |  120     | rpm-md |                                             |        
 5 |  | openSUSE BuildService - Games      | Yes     | Yes     |   99     | rpm-md |                        |        
 6 |             | Packman Repository                 | Yes     | Yes     |   95     | rpm-md |                              |        
 7 | multimedia:/color_management | multimedia:/color_management       | Yes     | Yes     |  105     | rpm-md | |        
 8 | openSUSE-13.2-0              | openSUSE-13.2-0                    | Yes     | No      |   99     | yast2  | cd:///?devices=/dev/disk/by-id/ata-HL-DT-ST_DVD+_-RW_GH50N_K1ZA4E31211                |        
 9 |      | libdvdcss repository               | Yes     | Yes     |   99     | rpm-md |                                                  |        
10 | repo-debug                   | openSUSE-13.2-Debug                | No      | Yes     |   99     | NONE   |                        |        
11 | repo-debug-update            | openSUSE-13.2-Update-Debug         | No      | Yes     |   99     | NONE   |                                       |        
12 | repo-debug-update-non-oss    | openSUSE-13.2-Update-Debug-Non-Oss | No      | Yes     |   99     | NONE   |                               |        
13 | repo-non-oss                 | openSUSE-13.2-Non-Oss              | Yes     | Yes     |   99     | yast2  |                          |        
14 | repo-oss                     | openSUSE-13.2-Oss                  | Yes     | Yes     |   99     | yast2  |                              |        
15 | repo-source                  | openSUSE-13.2-Source               | No      | Yes     |   99     | NONE   |                       |        
16 | repo-update                  | openSUSE-13.2-Update               | Yes     | Yes     |   99     | rpm-md |                                             |        
17 | repo-update-non-oss          | openSUSE-13.2-Update-Non-Oss       | Yes     | Yes     |   99     | rpm-md |                                     |        
18 | wine                         | wine                               | Yes     | Yes     |  110     | rpm-md |              |        

On Sat, 03 Jan 2015 02:36:01 +0000, JohnVV wrote:

> after a few updates packman should be used for most multi media but you
> might have to use “zypper” and force the vender change – that WILL take
> time , doing it one program at a time .

Or you can use the YaST software manager, select the repo, and select the
option to “switch installed packages to this repository”.

Or, if you really want to use zypper, you can ‘zypper dup’ with --from to
force the change for multiple packages.

Or you can get a list of the packages and script doing the update.

There’s no reason to do it one by one.


Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at

So you are using 13.1?
Because repos in that list include 13.2 and factory

My suggestion
Keep 13, 15 and 18-25
Remove all the others

zypper dup

Once that is done, you can switch to Packman


I am not realy advocating this.

As long as you have a reasonable amount of repos and once you have switched (and thus installed) packages that are available in several reps to the correct repo (like Packman instead of OSS) the Vendor Stickyness will keep things allright. No need for priority setting IMHO. Almost nobody does use them here.

You should first clean up as caf4926 advises.

Thank you Henk. You are very helpful.

When I installed 13.1 I followed instructions on the Documentation:Repositories link:

I took heed of the note and didn’t duplicate. I installed the repositories listed for 13.1. During installation I let Yast install the repositories it wanted to because I don’t know enough to do it myself manually. Once I got the install done, added the recommended repositories here, and booted to the desktop, I let it sit to pick up any updates or additional programs after installation that it needed and there were some. Before I did anything else like adding programs I set up Firefox, added saved bookmarks and passwords and did some configuration. Before doing anything with audio or video I went to the additional package repositories:

and chose multimedia, packman, NOT VLC, Mozilla, and I think Libre Office at that time. Wine was added months later. That’s all I installed at the time of installation. Over the next several months I added programs that I wanted to learn more about. This may be where the repo problems started. I remember some repos were recommended to be installed to support the programs I wanted. I don’t know how to manage repos so these programs probably added things that shouldn’t have been added. But I don’t know what’s good and what’s not. I did try reading about pachage management and repos but I didn’t understand much about it. I only know of one person from work that knows Linux better than me and he’s always out of touch. So I stumble through it. But I’m still happy learning and making mistakes with Linux. I love flexibility so windows was too stuffy for me. I waited too long to switch but I’m happy that I did.

Of the replies I received about this, I have a sketchy idea of how to fix this. Fixing this one program at a time is not acceptable. Doing a vendor change makies more sense but there must be more to it than outlined here right? I think maybe I should just go ahead and update to 13.2. Wouldn’t that be best? What does zypper dup do all by itself? What about other problems other than the oss/packman mixup? Should I really delete repos except for 13, 15, and 18-25? Johnvv said to set priorities. I don’t know how to choose the priorities. You said that the vendor stickyness will take care of that. I obviously need to learn more to do this. Where can I go to get it?

Thank you for all your help.

Concerning the oss/packman repo problem, looking at the additional package repositories paga again:

the recommendation is to start with just 4 repos: OSS, Non-OSS, Update, Update-Non-OSS, and Packman. If oss and packman shouldn’t be installed together, the problem starts at installation. How do I know not to install those two together when the recommendation is to do so? If the answer is the priority number then I don’t know how to set it correctly. What I’ve read about it left me confuised.

Thanks for everyone’s great help.

The repos I suggested for removal are unnecessary and given your predicament it seemed prudent.

zypper dup = distribution upgrade. It will basically upgrade every package to the newest available in the current repo list, which might actually mean quite a bit of rolling back in your case
I often handle this with yast - software management and the repository switcher, but it’s too tricky to explain. Well let me nutshell it.
I would switch on non-oss, oss, update non-oss, update, then packman (ignore libdvdcss repo for now)
During the process just cancel to ignore and errors and see where you are once you lastly click the switch on packman, hopefully it will be all ok and you can run the process

Repo priorities work this way:
Lower the number = higher priority
99 is default
All mine are 99, I never change this now we have the switcher

Caf’s advise now is to repair what you have.

It does not matter if you add repos using YaST or using zypper ar. The same thing happens

This here below is the general behaviour you should try to follow after you repaired things according to Cafs’ advice.

The general advise is to have active only OSS, non-OSS, their Updates and Packman. You then “switch to Packman”. IMHO most easy to do this with YaST > Software > Software Management; then from the View menu the Repositories View; the select Packman and thenclick above the list at right inn “Switch packages to this repo” (or similar wording. That will install all packages that are in both OSS and Packman anew from Packman. And the Vendor stickyness will garantee that that action will not reverse. No priority needed anymore (that is a thing of the past).

Now for adding more repos.
It could be that you want to use e.g. a stable version of a newer KDE version. That is rather harmless. Add it, switch to it (it will replace your OSS KDE with the newer KDE, but it will possibly also revert some packages from Packman to the new KDE (I am not sure if that is the case). So to be sure re-switch to Packman.

When you want a piece of software from another repo (e.g. for trial, but also for day to day usage) it is not a bad idea to install that software and then, using YaST > Software > Repositories, to Diasable the repo. This to avoid installing packages from it unwanted. Every now and then you can go enable it, look in the Repositories view if there is aa newer vrsion there and update there. For most software I have from such repos, I do that only every few monthes.

You should not forget this disabling after a so called “one click install”. Else your list of active repos will grow and you will get the same mess you have now.

In general, be conservative in adding and using repos. The list must be logical to you. And last but not least, make notes about what you installed extra and from which repos. System Management is a task that involves precise working and documenting.

Thank you for zypper dup. That is helpful but what does this mean:

“I would switch on non-oss, oss, update non-oss, update, then packman (ignore libdvdcss repo for now).”

Switch to what?

In the next sentence do you mean to ignore dependency errors and break the program? I have always never broken anything in yast because I’m thinking something will stop working and would cause problems.

I haven’t taken action on yesterday’s advice yet because I want to make sure I know what to do without getting stuck in the middle of all those changes. I want to outline the steps to take so I can understand what I’m doing and remember for future use. I really want to learn this.


Like I said, it’s tricky and probably going to confuse you.

Switching example:
Use that principle and apply the switch to each repo, you don’t apply anything, just keep toggling each repo and then when you do it finally on Packman, it will be either OK, or very close. If there are errors, you can post the list here
If it’s all OK, just accept it all and let it run

I always wondered if there was anything different between using yast or zypper.

So, I should have only OSS, non-OSS, their updates, and Packman listed as repositories in yast>repositories after installation? And then switch all to Packman? And then leave them that way?

The paragraph on adding more repos I think means to go ahead and get newer programs, switch repos to pick up all needed packages and updates, then switch back to Packman for everyday use. Is that right?

Now I think I know how to switch. In the repository view I pick the desired repo from the scrollable list at the left then click switch at the top of the package listing. I get that now. I thought it worked differently at first, and I’m glad the priority numbers aren’t needed any longer.

I didn’t know to disable repos after installing packages. I thought they were left enabled to get updates etc when they became available. What about needed updates to a program. This cuts them off doesn’t it? Ok I can go there every few months to look but I usually have no clue as to what is or is not needed. How to I sort that out?

Why was apper added? Why have apper and yast doing the same thing? Will using both generate more package updates? I’ve read the criticism on that and tried disabling apper in favor of yast but I don’t know what’s best. Right now they are both working from installation.

I had no idea about disabling a repo after a one-click-install. I’ve done a handful of those and never knew I should disable the repo. This must be another source of my big mess. So I know now why I’ve been getting so many updates in the last few months.

Should I enable auto updating for the repos I need to keep?

Nothing has been said about Packman essentials and Packman multimedia. Should they always both be installed?

You and caf4926 have been very helpful. After I hear from you again to clear up these few things I will start working on this. I’ll delete the unneeded repos first and only keep oss, non-oss, updates, and packman. Then I’ll swith those to packman. Then I’ll wait for the flood of update changes that will probably be coming. I just went to yast>software management>repositories and looked at installed packages. I don’t know how it should look, but the list from oss is tremendously long while the lists from packman essentials and multimedia is very short.

Thanks Again

I’ll have to get back to you as I am off out

But basically. All the switching you have to do is just to get you back to default. Normally we would just switch on Packman. Later…

Yes, a point of confusion has surfaced. You’re telling me to switch each repo. If I click on the packman repo the switch option is to apply all packages to the packman repo. Everybody ia saying to switch repos to packman . What do you mean to switch eech repo? Doesn’t switching to packman do it for all repos? If I now click on say the oss repo, the switch option is to switch all pacages to the oss repo?? Doesn’t that cancel the switch to packman? Your’re right I’m confused now. Why would I have to switch more than one time - highlight packman and switch all packages to packman?

And why are there two more repos at the bottom of the list - packman essentials and packman multimedis?

Are you saying to choose each repo and switch all packages to that repo, then choose the next one and switch all packages to that one, then finally switch all packages to packman? Wouldn’t the order of repos switched make a difference in the installed packages? That just doesn’t make sense to me. Is that what you mean?

That switching should of course be done in the correct sequence!

After removing the repos as told, you should first switch to OSS to install fom OSS all the stuf that may have been installed from those now removed repos. Same for non-OSS.

This of course will also result in removing things you have from Packman and replacing them with the original OSS/non-OSS packages. You then arrive (more or less) in the same situation you are after a clean install. Thus, as last, you should switch to Packman as everybody does after a fresh install.

Thanks Henk. You just tied up the loose ends for me. I never thought you could get back to a clean install because of all those hundreds of packages that have been added. I get the point now. Does this also mean that some packages might be removed completely if they were from another repo but not oss so that I’d have to reinstall them or do they remain installed? If so, no problem. So once I go to the oss repo and switch that will draw all packages from all other repos to oss right?. And this doesn’t have to be done on another repo other than packman? So why did you make the statement: “Same for non-OSS”? So the switch only needs to be done to oss and then to packman and no others? THAT makes sense to me. I’m wondering why I couldn’t think of it myself. And I didn’t know everybody switched to packman after they installed the os. Every time I run into problems and get them fixed whether I did it or had help, I just appreciate Linux all the more. This is good stuff!

Happy New Year