On Thu, 2002-08-01 at 08:03, Matt Fahrner wrote: > We have a locally generated RPM that is complaining about missing > libraries (dependancies) that exist: > > %1 rpm -i bcf-isp-jdk-1.0-2.i386.rpm > libodbcinst.so is needed by bcf-isp-jdk-1.0-2 > libodbc.so is needed by bcf-isp-jdk-1.0-2 > %2 ls -l /usr/lib/libodbcinst.so /usr/lib/libodbc.so > lrwxrwxrwx 1 root root 20 Nov 21 2001 > /usr/lib/libodbcinst.so -> libodbcinst.so.1.0.0* > lrwxrwxrwx 1 root root 16 Nov 21 2001 > /usr/lib/libodbc.so -> libodbc.so.1.0.0* > %3 rpm -qf /usr/lib/libodbcinst.so /usr/lib/libodbc.so > unixODBC-devel-2.0.7-3 > unixODBC-devel-2.0.7-3 > %4 rpm -ql unixODBC-devel-2.0.7-3 | egrep > '/usr/lib/libodbcinst.so|/usr/lib/libodbc.so' > /usr/lib/libodbc.so > /usr/lib/libodbcinst.so > > Does anyone have a clue why this would happen? This RPM was generated > on the same machine that we are trying to do the install (though > ultimately we have the same problem on other machines - which is > actually the whole point of its generation). Yes. The /usr/lib/libodbc.so and libodbcinst.so probably aren't actually part of unixODBC-devel package, but are symlinks created by 'ldconfig'. If you run 'rpm -qf /usr/lib/libodbc.so' it'll probably tell you it's not owned by any package. > I ask this in part because I've seen this before with other RPMs (ones > we did not generate) and could not seem resolve the issue. Note that > we DO NOT want to use "--force" or "--nodeps" (I have seen "--nodeps" > not work either for these sorts of things anyway for some reason). > > Please also note this dependancy was generated automatically by the > RPM build - we did not ask for it. It would be nice if you could turn > off such build dependancy checking along with the automatic "strip" > etc. The strip for instance can add a lot of unnecessary time to a > build of a large package. There is a way to disable at least the automatic dependency generation, I think, but I can't find it at the moment. I'm sure someone else here will know or you can ask on the rpm-list. > As a final note, this RPM will install just fine as part of a > kickstart but when manually installed it will not. Clearly some > different logic exists between the two. Anaconda actually does something akin to '--force --nodeps' when it installs packages, because stopping and having the user resolve them manually isn't an option then. Wil -- Wil Cooley wcooley@xxxxxxxxxxx Naked Ape Consulting http://nakedape.cc * * * * Linux, UNIX, Networking and Security Solutions * * * * QCSNet http://www.qcsn.com * * * * T1, Frame Relay, DSL, Dial-up, and Web Hosting * * * *
Attachment:
signature.asc
Description: This is a digitally signed message part
