Restricted Formats

English Multimedia
#1

Hi!
I’m a linux newbie. I’ve been using it for a month.I followed your Multi-media and Restricted Format Installation Guide for 11.3 .
I’ve got the following repositories:

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

–±------------------------------------±------------------------------------±--------±--------±---------±-------±---------------------------------------------------------------±-------
1 | Updates for openSUSE 11.3 11.3-1.82 | Updates for openSUSE 11.3 11.3-1.82 | Yes | Yes | 99 | rpm-md | Index of /update/11.3 |
2 | openSUSE-11.3 11.3-1.82 | openSUSE-11.3 11.3-1.82 | Yes | No | 99 | yast2 | cd:///?devices=/dev/sr0 |
3 | packman | packman | Yes | Yes | 99 | rpm-md | Index of /pub/linux/misc/packman/suse/11.3 |
4 | repo-debug | openSUSE-11.3-Debug | No | Yes | 99 | NONE | Index of /debug/distribution/11.3/repo/oss |
5 | repo-non-oss | openSUSE-11.3-Non-Oss | Yes | Yes | 99 | yast2 | Index of /distribution/11.3/repo/non-oss |
6 | repo-oss | openSUSE-11.3-Oss | Yes | Yes | 99 | yast2 | Index of /distribution/11.3/repo/oss |

Then I proceeded to “Check your multimedia problem in ten steps”. Here is the output

SUSE:~ # LC_ALL=C zypper ve
Loading repository data…
Reading installed packages…

Dependencies of all installed packages are satisfied.

SUSE:~ # rpm -qa --queryformat '%{NAME} → %{VENDOR}
’ | grep -i VideoLAN
libdvdcss → VideoLAN Project (VideoLAN - VLC: Free streaming and multimedia solutions for all OS!)

SUSE:~ # rpm --verify --query --all ‘libav*’ ‘libpostproc*’ ‘libswscale*’

SUSE:~ # rpm --query --queryformat '%{NAME}-%{VERSION}-%{RELEASE}-%{ARCH} → %{VENDOR}
’ libxine1 libxine1-codecs
libxine1-1.1.18.1-2.pm.41.2-i586 → PackMan :: Startseite
libxine1-codecs-1.1.18.1-2.pm.41.2-i586 → PackMan :: Startseite

SUSE:~ # rpm --verify --query --all ‘xine’

SUSE:~ # rpm --query --queryformat '%{NAME}-%{VERSION}-%{RELEASE}-%{ARCH} → %{VENDOR}
’ gstreamer-0_10-ffmpeg gstreamer-0_10-fluendo-mp3 gstreamer-0_10-fluendo-mpegdemux gstreamer-0_10-fluendo-mpegmux gstreamer-0_10-plugins-bad gstreamer-0_10-plugins-base gstreamer-0_10-plugins-good gstreamer-0_10-plugins-good-extra
package gstreamer-0_10-ffmpeg is not installed
gstreamer-0_10-fluendo-mp3-2-106.2-i586 → openSUSE
package gstreamer-0_10-fluendo-mpegdemux is not installed
package gstreamer-0_10-fluendo-mpegmux is not installed
gstreamer-0_10-plugins-bad-0.10.18-6.2-i586 → openSUSE
gstreamer-0_10-plugins-base-0.10.29-1.9-i586 → openSUSE
gstreamer-0_10-plugins-good-0.10.22-1.16-i586 → openSUSE
package gstreamer-0_10-plugins-good-extra is not installed

SUSE:~ # rpm --verify --query --all ‘gst’

SUSE:~ # rpm --verify MPlayer

SUSE:~ # rpm --verify --query --all ‘vlc’

SUSE:~ # rpm --verify w32codec-all
SUSE:~ #

I noticed that I’ve got some gstreamer packages from openSUSE repository and not from Packman.I tried to update them unconditionally
just like caf4926 advised but in vain. They are still openSUSE.

Finally when I wanted to switch system packages to the versions in Packman repository I got the following warning dialog box

YaST2 conflicts list - generated 2010-07-25 23:27:44

transmission-common-1.93-1.9.noarch requires transmission-ui = 1.93, but this requirement cannot be provided
uninstallable providers: transmission-1.93-1.9.i586[repo-oss]
transmission-qt-1.93-1.9.i586[repo-oss]
] keep obsolete transmission-gtk-1.93-1.9.i586

 ] break transmission-common by ignoring some of its dependencies

 ] install transmission-1.93-1.9.i586 from excluded repository

 ] install transmission-qt-1.93-1.9.i586 from excluded repository

 ] deinstallation of transmission-common-1.93-1.9.noarch

YaST2 conflicts list END

Any suggestions would be greatly appreciated.

#2

Using the switcher on Packman, when the error box comes up, just cancel to close the box.
Go to transmission-gtk in the package list and use the radio button to get it from packman
http://thumbnails24.imagebam.com/9022/2a293690215313.jpg](http://www.imagebam.com/image/2a293690215313)

Some gstreamer packages in Packman are not 64 bit, so I have some from openSUSE too

#3

Thanks for your quick reply caf4926. I changed transmission-gtk to Packman but still error box comes up.

YaST2 conflicts list - generated 2010-07-26 18:59:58

transmission-common-1.93-1.9.noarch requires transmission-ui = 1.93, but this requirement cannot be provided
uninstallable providers: transmission-gtk-1.93-1.9.i586[openSUSE-11.3 11.3-1.82]
transmission-1.93-1.9.i586[repo-oss]
transmission-gtk-1.93-1.9.i586[repo-oss]
] Following actions will be done:
install transmission-gtk-1.93-1.9.i586 from excluded repository
downgrade of transmission-gtk-2.03-0.pm.3.1.i586 to transmission-gtk-1.93-1.9.i586
install transmission-gtk-1.93-1.9.i586 (with vendor change)
PackMan :: Startseite → openSUSE
] keep obsolete transmission-qt-1.93-1.9.i586

 ] Following actions will be done:

install transmission-1.93-1.9.i586 from excluded repository
downgrade of transmission-2.03-0.pm.3.1.i586 to transmission-1.93-1.9.i586
install transmission-1.93-1.9.i586 (with vendor change)
PackMan :: Startseite → openSUSE
] break transmission-common by ignoring some of its dependencies

 ] deinstallation of transmission-common-1.93-1.9.noarch

YaST2 conflicts list END

#4

] deinstallation of transmission-common-1.93-1.9.noarch

See the pic I gave you earlier. I only have 1 package under transmission
ImageBam - Fast, Free Image Hosting and Photo Sharing

#5

caf4926 can you explain me what is actually the reason of shifting from oss repository ( supported by openSUSE and containing tested packages) to Packman. I noticed that some packages are updated to newer versions but some of them are changed to a previous versions. I mean what’s the reason of doing a rollback. For instance Amarok package in oss repo is newer that the one in Packman.

#6

The reason is to have a harmony of packaging for multi-media
Actually you could keep transmission from OSS, but it may not support DHT (I’m unsure, but this is true for ktorrent)

Amarok is not in Packman

#7

Once again I’d like to help you for your help caf4926. I think I’ll call it a day.Linux can be really daunting. I’m going to give it a try tomorrow.

#8

No problem.Take your time over it.

#9

Sorry for the typo. It was supposed to be “thank you for your help…”

#10

I figured that one :wink:

#11

On 2010-07-26 18:06 GMT Linioman wrote:

>
> caf4926 can you explain me what is actually the reason of shifting
> from oss repository ( supported by openSUSE and containing tested
> packages) to Packman. I noticed that some packages are updated to
> newer versions but some of them are changed to a previous versions. I
> mean what’s the reason of doing a rollback. For instance Amarok
> package in oss repo is newer that the one in Packman.

The main reason for using packman is because it provides versions of
some packages that in the oss repo have some features dissabled for
legal reasons.

However, I understand that, being the release date so recent, the
packman repo (and perhaps most repos, except oss and non-oss) are still
not completely ready. Thus you may get errors. It is still too early.

–
Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” GM (Elessar))