Bug 22940 – backwards compatibility with bash

Bugzilla will be upgraded to version 5.0 on December 2, 2018. The outage period for the upgrade will start at 0:00 UTC and have a duration of 12 hours

Bug 22940 - backwards compatibility with bash

Summary:	backwards compatibility with bash

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	bash (Show other bugs)
Sub Component:
Version:	7.0J
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Bernhard Rosenkraenzer
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-12-28 09:06 EST by Stefan
Modified:	2008-05-01 11:37 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-12-28 11:00:12 EST
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 Stefan 2000-12-28 09:06:30 EST

Can't do condition statements like the following anymore :
[ $? -eq 0 ] && { echo "Great stuff" }
This used to work in bash but now bash2 requires something like :
[ $? -eq 0 ] && { echo "Great stuff"; }

This caused half the scripts on my machine not to work
anymore after I upgraded to Redhat 7 final, because there
is now only bash2.

Comment 1 Bill Nottingham 2000-12-28 11:00:09 EST

It's an error in the script. bash1 was slightly more lenient.

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