Bug 161836 - xemacs needs libdb.so.3 which is missing from FC4
xemacs needs libdb.so.3 which is missing from FC4
Product: Fedora
Classification: Fedora
Component: xemacs (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ville Skyttä
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2005-06-27 13:08 EDT by Joshua Rosen
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-06-28 09:01:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Joshua Rosen 2005-06-27 13:08:19 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

Description of problem:
I installed Xemacs with yum, it won't run because you left out libdb.so.3.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. install from yum (it's missing on the CDROMs)
2. xemacs

Actual Results:  xemacs
xemacs: error while loading shared libraries: libdb.so.3: cannot open shared object file: No such file or directory

Additional info:
Comment 1 Jens Petersen 2005-06-27 20:11:07 EDT
XEmacs was moved to Fedora Extras for FC4.

Which version of xemacs do you have installed?

xemacs-21.4.17-3 from extras runs fine for me.

You must be running a rather old xemacs build anyway, since db
support was disabled from our xemacs package a long while ago.
Comment 2 Joshua Rosen 2005-06-27 20:59:29 EDT
Not your fault. The problem is that FC4 put /usr/local/bin into the default path
and the /usr/local/bin had a bunch of old versions of Xemacs in it. When I
changed the path it finds the current version of Xemacs which works.
Comment 3 Ville Skyttä 2005-06-28 09:01:46 EDT
Thanks for the quick followup; setting resolved as NOTABUG because there's 
nothing wrong in the XEmacs package in this respect. 

Note You need to log in before you can comment on or make changes to this bug.