Reference repositories, I typically give Pacman a much higher priority than the rest. For example I give packman 80 or 90. I would give Mozilla possibly 98 (instead of 99) but note that those rpms on Mozilla are cutting edge and have not seen the testing the older OSS/Update Mozilla rpms have seen, and you are risking breakage. I see you have Packman NOT enabled. I recommend you ENABLE it.
I think your “printing” repository is a VERY BAD idea. I recommend you remove it. Printing is too important to risk any breakage, and it can be too difficult to fix when things do break, and when it does break , it always happens at the worst possible time. Don’t mess with printing is my moto However you do have it NOT enabled, so you should be safe.
I would give wine repos a 97 or 98 priority. Maybe same priority as Mozilla.
After installing the program libdvdcss, I recommend you REMOVE the libdvdcss repository.
it’s easy to update all packages from a given repo in Yast. I just click Filter -> Repos, then in repo All in this list -> Update if newer version exists.
Question is if it is possible to do the same with zypper?
I’ll have to start a new thread for me, as I failed.
zypper in multimedia:alsa-docs
zypper up -r multimedia alsa-docs
work to install “alsa-docs” off of repository multimedia when there is older !! version of alsa-docs in the “OSS” repos. The newer version in the “multimedia” repos is ignored. That is true no matter what priority “multimedia” repos has wrt “OSS” repository. Zypper insists that it has the latest rpm installed when it in fact does not.
I wasted 30 minutes on this and I am going to stop. IMHO this is simply not functional or the command is far from obvious. IMHO this is a glaring deficiency in the “man zypper”.
Hmmm … my intention is update/upgrade ONLY specific packages. From what I have read “zypper dup” is NOT for updating specific packages. Hence I do not believe it will do what I am trying to achieve, which is an update of specific alsa applications and not others.
So thank you for the suggestion, but I do NOT believe “zypper dup” will do this.
True, it can not be used package-specific, but only like ‘zypper dup -r multimedia’ to switch everything to the most recent versions of that repository.
On the other hand: usually it doesn’t make much sense to install, for example, the doc-files of a certain package from a different repository than the actual package, as this will most likely result in inconsistencies. I don’t think this would be a needed or even usable feature.
In general, perhaps. In this case it does make sence.
Some time back I exchanged emails with the packager of that repos to get a better idea as to what packages should be installed.
Installing all (with dup) from that repos would be a MAJOR blunder and likely break most users sound. But installing select alsa packages from that repos has helped many dozen users get their sound to function, where otherwise it simply would not work.
Its unfortunate I can not compose a zypper command to do the update of SELECTED packages from that repos.
Okay, but you can not expect a package manager such zypper to perform such a task; one of its major aims is to resolve dependencies without the user having to interact. I suppose you could try rpm itself with some ‘force’ option instead - which would not look so neat, of course, but would show what it actually does: break dependencies.
It wouldn’t be my favoured way of doing things.
Never yet have I had to fiddle with alsa. Sound always just works. And why is it that for some the alsa version released with openSUSE is just behind what is required?