Bug 97089

Summary: upgrading foomatic overwrites cups config files
Product: [Retired] Red Hat Linux Reporter: Ivo <ivo>
Component: redhat-config-printerAssignee: Tim Waugh <twaugh>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 9CC: james
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 0.6.72-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-08-29 16:04:10 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 Ivo 2003-06-10 08:48:27 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030530

Description of problem:
the %post scection of foomatic runs a
   /usr/sbin/printconf-backend --force-rebuild
this will destroy any hand edited changes to /etc/cups/cupsd.conf
/etc/cups/printers.conf and custom edited ppd files in /etc/cups/ppd.
There's not even a backup of the original files.

We've been using cups since before its inclusion in redhat, thus all our cups
config files are hand written. For some printers we're using custom ppd files.
I've now deinstalled reshat-config-printer to ward against this happening again.

Possibly this bug should have been filed against redhat-config-printer or alchemist.



Version-Release number of selected component (if applicable):
foomatic-2.0.2-15.1

How reproducible:
Always

Steps to Reproduce:
1. Upgrade foomatic: rpm -U foomatic-2.0.2-15.1.i386.rpm


    

Actual Results:  all changes to cups configuration files destroyed.
/etc/cupsd.conf and /etc/cups/printers.conf replaced by defaults. Extra ppd
files in /etc/cups/ppd deleted

Expected Results:  cups config files not generated by redhat-config-printer
should be left untouched. At the very least a backup of the origiinal config
file should have been generated.

Additional info:

Comment 1 Tim Waugh 2003-08-29 13:48:30 UTC
It ought to make a backup file I guess.