So I installed the multi-media codecs by the instructions in this link Multi-media and Restricted Format Installation Guide It seemed to be working alright for a day or two, until my system decided to download updates. During the latest list of packages to update, I run into this particular update:
OpenSUSE-2011-5 – update for pullin-fluendo-mp3.openSUSE_12.1
This update seems to stop the whole update process (in Apper, not from the command line) from continuing. Rather than skipping this package and installing the other updates in the list I get this message:
A package dependency could not be found. More information is available in the detailed report.
upon clicking the detailed report I get:
Patch: openSUSE-2011-5-1.noarch conflicts with
gstreamer-0_10-fluendo-mp3.i586 < 12-1.1 provided by
gstreamer-0_10-fluendo-mp3-0.10.14-43.5.i586
I’m assuming this probably has to do with the vendor switch in the multimedia instructions, but i’m really new opensuse and not sure how to correct this. I know I can command line a zypper update and get around it (which is what I did last time) but it annoys the heck out of me to not have something working right on my system so I would like to know what I should be doing to resolve this. any ideas are welcome. Thanks guys!
i think there is something going wrong with that package. Apper wants to update pullin-fluendo-mp3.openSUSE_12.1 as well though that package is not installed on my system. Therefore the update fails with: couldn’t find package.
Its very amusing, because apper wants to update that everyday. Even blacklisting this package doesn’t help.
Am 21.11.2011 12:26, schrieb Pilgervater:
>
> Hi,
>
> i think there is something going wrong with that package. Apper wants
> to update pullin-fluendo-mp3.openSUSE_12.1 as well though that package
> is not installed on my system. Therefore the update fails with: couldn’t
> find package.
>
> Its very amusing, because apper wants to update that everyday. Even
> blacklisting this package doesn’t help.
>
>
Looks like apper is kpackagekit with a new name but the same old
“features” or was it bugs.
Throw it away and install the yast online update.
–
PC: oS 11.4 (dual boot 12.1) 64 bit | Intel Core i7-2600@3.40GHz | KDE
4.6.0 | GeForce GT 420 | 16GB Ram
Eee PC 1201n: oS 11.4 64 bit | Intel Atom 330@1.60GHz | KDE 4.7.3 |
nVidia ION | 3GB Ram
I confirm that it must be a bug. Getting this conflict every day (have packman installed):
#### YaST2 conflicts list - generated 2011-11-27 19:02:54 ####
patch:openSUSE-2011-5-1.noarch è in conflitto con gstreamer-0_10-fluendo-mp3.x86_64 < 12-6.1 fornito da gstreamer-0_10-fluendo-mp3-0.10.14-43.6.x86_64
] non installare patch:openSUSE-2011-5-1.noarch
] installa gstreamer-0_10-fluendo-mp3-12-8.1.x86_64 (con cambio di fornitore)
http://packman.links2linux.de --> openSUSE
#### YaST2 conflicts list END ###
And of course I do not want a vendor change. So why it nags (even through yast oline update) … I have no pale idea. I would suppose it is not upper but something else is broken.
Sorry, I didn’t get this. You say they claim it is normal? I did not use zypper at all, but I am using yast to do the updates. The message comes from apper applet, so I am unsure what you do mean with the advice about zypper, could you elaborate just a bit more, that would be great, thanks.
I’m tagging a comment here
Partly to explain that sometimes, it might be necessary to wait to update all packages, especially it seems true with gstreamer
This one: gstreamer-0_10-fluendo-mp3
Is also a openSUSE package and strangely, using the switcher doesn’t always seem to have the desired effect.
It may be necessary to do this: http://dl.dropbox.com/u/10573557/Switcher%20Pics/gstreamer_fluendo_mp3_switch.jpeg
But I can add, this doesn’t appear to be a bug. I have 5 systems of both 32 and 64bit and they are updated daily. None have experience any problem with this package.
well, I know you can select it. I did at the time. It installs the packman version, of course. Then the error message comes vice versa…wanting to install the openSUSE patch for fluendo plugin. I am not on that system, but I may have a look if that still happens when I get my hands on it (about a week from now).
I do not have this problem. The version I have is indeed gstreamer-0_10-fluendo-mp3-12-8.1. I think it’s because of the order in which I did the actions. I installed, and then accepted all the online updates available from openSUSE before adding the restricted format archives of packman and libdvdcss. I suspect that if you install, then add the restricted format packages, next update it will want to change gstreamer-0_10-fluendo-mp3 back to the openSUSE version due to openSUSE-2011-5-1.noarch. If I were you, I would try accepting that vendor change. I think the worst that can happen is MP3 playback breaks. But I don’t think it will, since the gstreamer-0_10-fluendo-mp3-12-8.1 plugin from openSUSE works fine. For the first time, an openSUSE release has provided a licensed MP3 player.
There’s one thing I did which you didn’t. I also installed the non-OSS software from the openSUSE-12.1-Addon-NonOss-BiArch-i586-x86_64.iso CD. That contains gstreamer-0_10-fluendo-mp3-12-5.1.1, which then gets updated to gstreamer-0_10-fluendo-mp3-12-8.1 during online update.
update online during install
update online before adding Packman repositry
add Packman
online update (all repos at 99 priority)
switch system packages
online update continues to run (thanks to applet or by hand)
problem arises
change Packman repo priority to 95, openSUSE updates to 90
Help! I finally updated to 12.1 and I’ve got a similar version of this error:
patch:openSUSE-2011-59-1.noarch conflicts with qt4-x11-tools-debuginfo.x86_64 < 4.7.4-19.4.2 provided by qt4-x11-tools-debuginfo-4.6.3-1.4.x86_64
patch:openSUSE-2011-15-1.noarch conflicts with wpa_supplicant-debuginfo.x86_64 < 0.7.3-10.3.1 provided by wpa_supplicant-debuginfo-0.7.1-4.1.x86_64
I have no idea how to fix this and nothing will update. I am trying to update with Apper (apparently that’s what that POS kpackagekit is now). I don’t know enough about the build system to know how to switch vendors, if I even need to, how else to attempt to update, etc.