I hope I'm not being an idiot, but I'm attempting to install vorbis-1.0
RPMs on a few redhat machines and failing horribly. I'm in dependency
hell.
For starters, libao-0.8.3-1 requires libasound.so.2 (an alsa library?)
which does not seem to be available in any recent redhat releases.
Then vorbis-tools wants libcurl.so.2, which makes redhat 7.2 machines
choke.
Worst of all is that there's a boadload of packages depending on
(since-renamed) vorbis libs:
libvorbisenc.so.0 is needed by kdebase-2.2.2-1
libvorbisfile.so.0 is needed by SDL_mixer-1.2.0-4
libvorbisfile.so.0 is needed by xmms-1.2.5-7
libvorbisfile.so.0 is needed by tuxracer-0.61-5
libvorbisfile.so.0 is needed by kdemultimedia-2.2.2-2
So, my question is: is it possible to upgrade redhat 7.3 machines using
RPMs? The vorbis.com download page seems to imply this is possible. But
it doesn't seem as though I'm going to succeed without forcing a bunch
of
broken dependencies or conflicting packages to coexist.
I'm hoping that a few of the library-version issues could be paranoia
(meaning I can symlink to an older/newer version), or that perhaps I could
tweak the RPM SPEC file to make a less-needy set of binaries (if, for
example, it's possible to not link against libasound.so.2).
I could build from source, but then I'll have a mix of RPM and non-RPM
libraries installed, and I'd rather avoid making too much of a mess on my
systems. Plus I'm sure I'm not the last person who will have these
issues, so I'm willing to go through a few contortions to find the magic
formula so others can benefit.
Any advice?
Eric
--- >8 ----
List archives: http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to
'vorbis-request@xiph.org'
containing only the word 'unsubscribe' in the body. No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.
eric,
i just went through this with rh 7.1, here's my experience:
packages:
vorbis-tools-1.0-1.i386.rpm
libvorbis-1.0-1.i386.rpm
libogg-1.0-1.i386.rpm
curl-7.9.8-1.i386
libalsa0.9-0.9.0beta7-mdk.i586.rpm
libao-0.8.3-1.i386.rpm
openssl-0.9.6b-8.i386.rpm
all packages were fetched from rpmfind.net or vorbis.com
i 'rpm -Uvh' for all packages except for openssl. i had numerous
packages that depended on libssl.so.1, so i couldnt upgrade.
instead, i used 'rpm -ivh --force' for the openssl package.
i dont know about the curl package making rh7.2 choke...
i also upgraded xmms to 1.2.7 (www.xmms.org to get the rpms)
there is a vorbis plugin there too.
good luck,
-matt
On Wed, 2002-07-24 at 13:00, Eric Seppanen wrote:> I hope I'm not being an idiot, but I'm attempting to install
vorbis-1.0
> RPMs on a few redhat machines and failing horribly. I'm in dependency
> hell.
>
> For starters, libao-0.8.3-1 requires libasound.so.2 (an alsa library?)
> which does not seem to be available in any recent redhat releases.
>
> Then vorbis-tools wants libcurl.so.2, which makes redhat 7.2 machines
> choke.
>
> Worst of all is that there's a boadload of packages depending on
> (since-renamed) vorbis libs:
>
> libvorbisenc.so.0 is needed by kdebase-2.2.2-1
> libvorbisfile.so.0 is needed by SDL_mixer-1.2.0-4
> libvorbisfile.so.0 is needed by xmms-1.2.5-7
> libvorbisfile.so.0 is needed by tuxracer-0.61-5
> libvorbisfile.so.0 is needed by kdemultimedia-2.2.2-2
>
> So, my question is: is it possible to upgrade redhat 7.3 machines using
> RPMs? The vorbis.com download page seems to imply this is possible. But
> it doesn't seem as though I'm going to succeed without forcing a
bunch of
> broken dependencies or conflicting packages to coexist.
>
> I'm hoping that a few of the library-version issues could be paranoia
> (meaning I can symlink to an older/newer version), or that perhaps I could
> tweak the RPM SPEC file to make a less-needy set of binaries (if, for
> example, it's possible to not link against libasound.so.2).
>
> I could build from source, but then I'll have a mix of RPM and non-RPM
> libraries installed, and I'd rather avoid making too much of a mess on
my
> systems. Plus I'm sure I'm not the last person who will have these
> issues, so I'm willing to go through a few contortions to find the
magic
> formula so others can benefit.
>
> Any advice?
>
> Eric
>
> --- >8 ----
> List archives: http://www.xiph.org/archives/
> Ogg project homepage: http://www.xiph.org/ogg/
> To unsubscribe from this list, send a message to
'vorbis-request@xiph.org'
> containing only the word 'unsubscribe' in the body. No subject is
needed.
> Unsubscribe messages sent to the list will be ignored/filtered.
<p><p>--- >8 ----
List archives: http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to
'vorbis-request@xiph.org'
containing only the word 'unsubscribe' in the body. No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.
I've made significant progress on making RPMs that are friendlier to a stock redhat system. The libasound dependency in libao can be fixed by editing the libao spec file, building new rpms that don't attempt to interface to ALSA. The libcurl dependency in vorbis-tools (only happens on redhat versions 7.2 or earlier) can be fixed with a simple rpm rebuild. That leaves me with only one remaining issue: there are lots of programs on redhat machines linked against libvorbisenc.so.0 and libvorbisfile.so.0 . The 1.0 version of libvorbis supplies libvorbisenc.so.2 and libvorbisfile.so.3 . So, is there an easy fix to this? Is there a real incompatibility there? Can I make a symlink to point everyone at the new version? Can the old .0 files coexist peacefully with a new libvorbis.so.0 ? The attempt is to make a cleaned-up set of RPMs that will install cleanly on a stock redhat box, without installing mismatched packages from other distributions a la rpmfind. If this issue can be resolved I will have cleaned up spec files and rpms to share. --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
At 01:00 PM 7/24/02 -0500, you wrote:>I hope I'm not being an idiot, but I'm attempting to install vorbis-1.0 >RPMs on a few redhat machines and failing horribly. I'm in dependency >hell. > >For starters, libao-0.8.3-1 requires libasound.so.2 (an alsa library?) >which does not seem to be available in any recent redhat releases.libao does NOT require libasound. This is a false dependency added by the RPM tools, you can and should safely ignore it.> >Then vorbis-tools wants libcurl.so.2, which makes redhat 7.2 machines >choke. > >Worst of all is that there's a boadload of packages depending on >(since-renamed) vorbis libs: > > libvorbisenc.so.0 is needed by kdebase-2.2.2-1 > libvorbisfile.so.0 is needed by SDL_mixer-1.2.0-4 > libvorbisfile.so.0 is needed by xmms-1.2.5-7 > libvorbisfile.so.0 is needed by tuxracer-0.61-5 > libvorbisfile.so.0 is needed by kdemultimedia-2.2.2-2 > >So, my question is: is it possible to upgrade redhat 7.3 machines using >RPMs? The vorbis.com download page seems to imply this is possible. But >it doesn't seem as though I'm going to succeed without forcing a bunch of >broken dependencies or conflicting packages to coexist.Not easily, the reasons for this are complex. If you force it and then symlink libvorbisfile.so.3 to libvorbisfile.so.0, most (all?) of these programs will still work - but some might not. Michael <p>--- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
On Wed, 24 Jul 2002, Eric Seppanen wrote:> I hope I'm not being an idiot, but I'm attempting to install vorbis-1.0 > RPMs on a few redhat machines and failing horribly. I'm in dependency > hell. > > For starters, libao-0.8.3-1 requires libasound.so.2 (an alsa library?) > which does not seem to be available in any recent redhat releases.This is an incorrect install dependency for libao. It is something that seems to pop up a lot because a libao plugin links with libasound, but libasound is not needed for libao to be installed and work. I do not know whether the .spec file is incorrect or if RPM is being overly clever with setting dependencies for the package builder. As a temp fix, you may install the libao RPM with --nodeps safely because libao does not *require* external libraries to be present to do something. (Of course, you may not be happy if those libraries are needed for your preferred audio playback method. However, this is not the case with you.) --- Stan Seibert <p><p>--- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.