**argon:~/bin #** zypper dup --no-allow-vendor-change
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Loading repository data...
Reading installed packages...
Computing distribution upgrade...
Problem: problem with installed package liba52-0-0.7.5+svn613-1.27.x86_64
Solution 1: install liba52-0-0.7.5+svn613-1.1.x86_64 (with vendor change)
http://packman.links2linux.de --> openSUSE
**Choose the above solution using '1' or cancel using 'c' [1/c] (c): **c
**argon:~/bin #**
This is since about a week, because I wanted to wait and see if maybe packman just had to catch-up, but this remains.
What’s now best to do? Allow the vendorchange? Will that haunt me forever? Or wait any longer?
I have the packman repo set to a priority of 98. That gives it preference over the other repos.
I just do “zypper dup”. I don’t use the “–no-allow-vendor-change”
My reasoning: for full multimedia support, we are supposed to switch applications to packman. By giving packman a better priority, that should normally happen automatically, unless blocked by some requirement.
If I were using outside repos, I would use “–no-all-vendor-change”. But that does not seem necessary if I am only using the standard repos plus packman.
And yes, I do sometimes see vendor changes. They have not caused any problems (yet). But then I mainly use 42.2, so my testing for problems on Tumbleweed might be imperfect.
I could be that this is only a shortcut of telling us about your Packman usage, but just “with Packman” is a bit unclear.
This is why and how to use Packman.
When you want to have full multimedia support, you need several packages from Packman instead of from the OSS repo (because of legal reasons).
To do this you first have to add the Packman repo to your repo list (which you have done) And then you have to do the “vendor switch to Packman” of which I am not sure you did it, because you do not say so explicitly. To do the switch in your case:
zypper dup --from packman
When you install more multimedia players, repeat this after such an installation to be sure that all libraries (codecs) that were drawn in (and maybe even the player itself) are from Packman.
Please first do this vendor switch to Packman and then repeat your
zypper dup --no-allow-vendor-change
And come back when the error (or any other problem) is still there.
liba52 has been removed from Packman as it is part of the distribution now.
As it doesn’t exist in Packman any more, “zypper dup --no-allow-vendorchange” will ask you to allow to switch to the available one from the standard repo. (“zypper dup” would just do the switch without asking)
Well, openSUSE is open as the name implies.
All packages are available to everyone (also the source code), everyone can have an account on the build service (actually it’s the same account as here in the forums ), and everyone can inspect everything.
Of course it helped that I happen to know there are efforts going on to get more multimedia packages into openSUSE itself because patents expired.
That’s the case with libac52 and some mp3 packages soon (hopefully).
I follow this, because it will also help with KDE packaging (see below), because we will be able to enable (e.g. mp3) support in the standard packages, kwave and k3b in particular.
And it does not make much sense to provide things in Packman any more that are (uncrippled) in the standard repos.
Especially in regards to multimedia, Packman is actually just a “workaround” to avoid legal problems.
Of course it will probably never be possible to provide full codec support in the standard distribution. (or not soon at all at least…)
So at least ffmpeg will stay in Packman for a long time I suppose…
(but at least having a crippled version in the standard repos helps a lot already for packaging other things)
and am I happy to talk to one?
Yes, to some degree.
I do contribute (KDE mostly, I’m member of openSUSE’s KDE team and also have a developer account upstream at KDE).
Other than that, it’s mainly because I use (open)SUSE since about 14 years…
), and everyone can inspect everything.
