Bug 15104 – typo in kernel-source post install script

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 15104 - typo in kernel-source post install script

Summary:	typo in kernel-source post install script

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	kernel (Show other bugs)
Sub Component:
Version:	7.0
Hardware:	All Linux

Priority	medium Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Michael K. Johnson
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-08-02 07:09 EDT by bastiaan
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-08-04 16:23:33 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description bastiaan 2000-08-02 07:09:39 EDT

Syptoms:
Installing kernel-source-2.2.16-17.i386.rpm generates the following error
message:
D: running postinstall scripts (if any)
+ cd /usr/src
+ rm -f linux
+ ln -snf linux-2.2.16 linux
var/tmp/rpm-tmp.36107: line 15: syntax error: unexpected end of file
execution of kernel-source-2.2.16-17 script failed, exit status 2

Solution:
The postinstall script in the RPM contains the lines:
if [ 1 -eq 0 ] ; then
        cd /usr/include
        rm -f linux asm
        ln -snf ../src/linux/include/linux linux
        ln -snf ../src/linux/include/asm asm
endif

'endif' is incorrect, replace with 'fi'

Comment 1 Alan Cox 2000-08-02 11:52:11 EDT

One for the next build.

Comment 2 Michael K. Johnson 2000-08-04 16:23:31 EDT

FWIW, that was caused by a change from rpm %foo syntax to shell
syntax, and is fixed in all our current internal incremental
builds.  You will see this error again when the 2.2.16-17 packages
are uninstalled because they exist in the uninstall as well as
install scripts.

Comment 3 Alan Cox 2000-08-05 22:06:24 EDT

The -19 package seems just fine

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