Bug 16241 - upgrade: script execution failed
Summary: upgrade: script execution failed
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: apache
Version: 7.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact:
: 16419 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2000-08-15 14:54 UTC by Brock Organ
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2000-08-31 15:12:22 UTC

Attachments (Terms of Use)

Description Red Hat Bugzilla 2000-08-15 14:54:38 UTC
Here is an error message from an anaconda upgrade (/tmp/upgrade.log)
showing an error upgrading apache:

Upgrading apache.                                                          
/bin/linuxconf: error while loading shared libraries: libncurses.so.4:
cannot open shared object file: No    such file or directory               
warning: /etc/httpd/conf/httpd.conf saved as
execution of linuxconf-1.17r2-6 script failed, exit status 127             
Upgrading apache-devel.                                                    

Comment 1 Red Hat Bugzilla 2000-08-15 22:13:56 UTC
That's unfortunate.  The trigger which dies, however, isn't an important one,
and all of the packages involved still function correctly after the upgrade.

Comment 2 Red Hat Bugzilla 2000-08-17 15:03:58 UTC
The trigger is also gone from the package in the build tree, so we're looking at
a bug in the old version of the package that turned out to be harmless.

Comment 3 Red Hat Bugzilla 2000-08-17 15:05:00 UTC
*** Bug 16419 has been marked as a duplicate of this bug. ***

Comment 4 Red Hat Bugzilla 2000-08-27 15:26:44 UTC
Upgrading 6.2 to RC2 gives the same problem. 
For some reason, the fix is to install db2 (or db1, don't remember; anyway, it's the one
containing the missing lib for apache).

Comment 5 Red Hat Bugzilla 2000-08-31 15:12:20 UTC
the issues resolution would require an errata to linuxconf for 6.2 (purely for
the purpose of removing this message, as core functionality is not affected)...

This is a lower priority issue ... and as such we will defer to the next release

Comment 6 Red Hat Bugzilla 2000-09-06 18:53:35 UTC
The fact that apache is not upgraded does not look low priority to me.
Am I missing something (perhaps wrt internal cuts)  ?

Comment 7 Red Hat Bugzilla 2000-09-22 01:39:34 UTC
Why not make apache require linuxconf? If linuxconf gets upgraded
first, will this problem go away?

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