Bug 11841 - a2ps upgrade fails, leaves config files in the wrong place
a2ps upgrade fails, leaves config files in the wrong place
Status: CLOSED RAWHIDE
Product: Red Hat Powertools
Classification: Retired
Component: a2ps (Show other bugs)
5.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Powers
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-06-01 22:51 EDT by Jonathan Kamens
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-06-19 17:25:43 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)

  None (edit)
Description Jonathan Kamens 2000-06-01 22:51:02 EDT
Here's what I saw when I tried to upgrade a2ps-4.12-7 to a2ps-4.13-1:

	warning: /etc/a2ps-site.cfg created as /etc/a2ps-site.cfg.rpmnew
	Looking for the afm files read by a2ps...
	a2ps: cannot open file `/usr/etc/a2ps.cfg': No such file or directory
	a2ps: cannot find file `level1.ppd': No such file or directory
	Extracting font names...
	Sorting entries...
	sort: fonts.map.new: No such file or directory
	execution of script failed

Afterwards, "rpm -q a2ps" shows that both 4.12-7 and 4.13-1 are supposedly
installed.  Furthermore, it appears that the upgrade created configuration
files in /etc even though a2ps is now expecting to find them in /usr/etc. 
I had to copy my config files from /etc to /usr/etc to get a2ps 4.13-1 to
work.
Comment 1 Tim Powers 2000-06-19 17:25:42 EDT
This should be fixed now. We switched to %conlfigure in the spec file and
--sysconfir=/etc wasn't defined by RPM at the time. It should be fixed in 4.13-4
now.

Tim

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