|
Home > Archive > Red Hat Installation > April 2004 > Yum install xine fails; unable to satisfy dependencies
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Yum install xine fails; unable to satisfy dependencies
|
|
|
|
Gathering header information file(s) from server(s)
Server: Fedora Core 1 - i386 - Base
Server: Livna.org Fedora Compatible Packages (stable)
Server: Fedora Core 1 - i386 - Released Updates
Finding updated packages
Downloading needed headers
Resolving dependencies
.......Unable to satisfy dependencies
Package xine-lib needs libaa.so.1, this is not available.
Package xine-lib needs libasound.so.2, this is not available.
Package xine-lib needs libasound.so.2(ALSA_0.9), this is not available.
Package xine-lib needs libasound.so.2(ALSA_0.9.0rc4), this is not available.
Package xine needs libaa.so.1, this is not available.
.... Now what?
I tried to look for the libs in rpmfind.org and discovered
that a zillion dependencies need to be resolved. Libalsa2 needs
libalsa-data. But libalsa-data needs libalsa2. No way to bypass this. What
do I do?
| |
| Andreas Korn 2004-04-19, 5:35 pm |
| PQ wrote:
> Gathering header information file(s) from server(s)
> Server: Fedora Core 1 - i386 - Base
> Server: Livna.org Fedora Compatible Packages (stable)
> Server: Fedora Core 1 - i386 - Released Updates
> Finding updated packages
> Downloading needed headers
> Resolving dependencies
> ......Unable to satisfy dependencies
> Package xine-lib needs libaa.so.1, this is not available.
> Package xine-lib needs libasound.so.2, this is not available.
> Package xine-lib needs libasound.so.2(ALSA_0.9), this is not available.
> Package xine-lib needs libasound.so.2(ALSA_0.9.0rc4), this is not available.
> Package xine needs libaa.so.1, this is not available.
>
> ... Now what?
>
> I tried to look for the libs in rpmfind.org and discovered
> that a zillion dependencies need to be resolved. Libalsa2 needs
> libalsa-data. But libalsa-data needs libalsa2. No way to bypass this. What
> do I do?
Try some additional yum repositories. Here is my yum.conf as an example
[main]
cachedir=/var/cache/yum
debuglevel=2
logfile=/var/log/yum.log
pkgpolicy=newest
distroverpkg=fedora-release
gpgcheck=1
#[os]
#name=Fedora Core 1 os
#baseurl=http://fedora.redhat.com/releases/fedora-core-1
#[updates]
#name=Fedora Core 1 updates
#baseurl=http://fedora.redhat.com/updates/released/fedora-core-1
#[testing]
#name=Fedora Core 1 testing
#baseurl=http://fedora.redhat.com/updates/testing/fedora-core-1
[core]
name=Fedora Linux $releasever - $basearch - core
baseurl=http://ayo.freshrpms.net/fedora/linux/$releasever/$basearch/core
#[extras]
#name=Fedora Linux $releasever - $basearch - extras
#baseurl=http://ayo.freshrpms.net/fedora/linux/$releasever/$basearch/extras
#[alternatives]
#name=Fedora Linux $releasever - $basearch - alternatives
#baseurl=http://ayo.freshrpms.net/fedora/linux/$releasever/$basearch/alternatives
[updates]
name=Fedora Linux $releasever - $basearch - updates
baseurl=http://ayo.freshrpms.net/fedora/linux/$releasever/$basearch/updates
[at-testing]
name=ATrpms for Fedora Core 1 testing
baseurl=http://apt.physik.fu-berlin.de/fedora/1/en/i386/at-testing
[at-bleeding]
name=ATrpms for Fedora Core 1 bleeding
baseurl=http://apt.physik.fu-berlin.de/fedora/1/en/i386/at-bleeding
[newrpms.sunsite.dk]
name=NewRPMS.sunsite.dk for Fedora Core 1
baseurl=http://newrpms.sunsite.dk/apt/redhat/en/i386/fc1
[freshrpms]
name=Fedora Core 1 freshrpms
baseurl=http://ayo.freshrpms.net/fedora/linux/1/i386/freshrpms
[dag]
name=Fedora Core 1 Dag Wieers' repository
baseurl=http://apt.sw.be/redhat/fc1/en/i386/dag
ftp://apt.sw.be/redhat/fc1/en/i386/dag
[dries]
name=Dries repository for Fedora Core 1
baseurl=http://dries.studentenweb.org/yum/fedora/linux/1/i386/dries
#[spc]
#name=spc repository for Fedora Core 1
#baseurl=http://spc.atrpms.net/fedora/linux/1/i386/spc
# http://rpms.subpop.net/fedora/linux/1/i386/spc
#[kde-redhat-fedora-stable-$releasever]
#name=kde-redhat.org (fedora-stable)
#baseurl=http://apt.kde-redhat.org/apt/fedora/$releasever/stable
#[kde-redhat-fedora-stable-all]
#name=kde-redhat.org (fedora-stable)
#baseurl=http://apt.kde-redhat.org/apt/fedora/all/stable
#[kde-redhat-kde-stable-$releasever]
#name=kde-redhat.org (kde-stable)
#baseurl=http://apt.kde-redhat.org/apt/kde-redhat/$releasever/stable
#[kde-redhat-kde-stable-all]
#name=kde-redhat.org (kde-testing)
#baseurl=http://apt.kde-redhat.org/apt/kde-redhat/all/testing
| |
| Markku Kolkka 2004-04-19, 6:35 pm |
| PQ wrote:
> Gathering header information file(s) from server(s)
> Server: Fedora Core 1 - i386 - Base
> Server: Livna.org Fedora Compatible Packages (stable)
So, you didn't notice the bold text in a red box on the
http://rpm.livna.org/ page?
" RPM.Livna.org is not a standalone repository
You must use rpm.livna.org with
Fedora.us repository"
--
Markku Kolkka
markku.kolkka@iki.fi
| |
| HiTech 2004-04-21, 7:37 pm |
| download and install package called apt-get
after it is installed run the command line
apt-get install xine
it will download and install xine and all needed codecs...
good luck.
"PQ" <p@q.com> wrote in message news:pan.2004.04.20.03.23.31.921535@q.com...
>
> Gathering header information file(s) from server(s)
> Server: Fedora Core 1 - i386 - Base
> Server: Livna.org Fedora Compatible Packages (stable)
> Server: Fedora Core 1 - i386 - Released Updates
> Finding updated packages
> Downloading needed headers
> Resolving dependencies
> ......Unable to satisfy dependencies
> Package xine-lib needs libaa.so.1, this is not available.
> Package xine-lib needs libasound.so.2, this is not available.
> Package xine-lib needs libasound.so.2(ALSA_0.9), this is not available.
> Package xine-lib needs libasound.so.2(ALSA_0.9.0rc4), this is not
available.
> Package xine needs libaa.so.1, this is not available.
>
> ... Now what?
>
> I tried to look for the libs in rpmfind.org and discovered
> that a zillion dependencies need to be resolved. Libalsa2 needs
> libalsa-data. But libalsa-data needs libalsa2. No way to bypass this. What
> do I do?
|
|
|
|
|