Bug 212526

Summary:	enscript ceased to work: "illegal option: StatesColorModel:"
Product:	[Fedora] Fedora	Reporter:	Pekka Savola <pekkas>
Component:	enscript	Assignee:	Adam Tkac <atkac>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5	CC:	ovasik
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-10-27 11:35:04 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Pekka Savola 2006-10-27 08:40:55 UTC

$ rpm -q enscript
enscript-1.6.4-3.fc5

$ enscript 
enscript:/usr/share/enscript:/usr/local/lib/ps:/usr/lib/ps:128: illegal option:
StatesColorModel:

It seems that the new enscript no longer likes the previous enscript version's
default configuration file, commenting out "StatesColorModel" and
"StatesHighlightLevel" fixes that.

enscript.cfg.rpmnew was created that doesn't have this problem.

Should the user just edit the configuration or is this something that needs to
be addressed at %post scripts or some such?  Did the feature set of enscript
change at the upgrade?


StatesColorModel: blackwhite

Comment 1 Adam Tkac 2006-10-27 11:35:04 UTC

Latest version that supports StatesColorModel option was 1.6.1-31. After that,
StatesColorModel option isn't avaliable. Please see StatesColor,
StatesConfigFile and StatesHighlightStyle options. These options can compensate
removed opts

Comment 2 Pekka Savola 2006-10-30 06:40:08 UTC

To be clear, I don't need those options.  The point was, those options were in
the old enscript.cfg *by default*, which prevented new enscript from running
unless you changed the config file.  Whether this is an issue that would need to
be addressed is another thing...

Comment 3 Adam Tkac 2006-10-31 08:08:17 UTC

If you have a config file (enscript.cfg), and you update package there're many
arguments to not modify old config file.