Bug 476220 - psprint.conf should be flagged as a config file in openoffice.org2-core RPM
Summary: psprint.conf should be flagged as a config file in openoffice.org2-core RPM
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: openoffice.org
Version: 4.9
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Caolan McNamara
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-12-12 15:37 UTC by Dan Astoorian
Modified: 2009-07-20 12:33 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-07-20 12:33:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Dan Astoorian 2008-12-12 15:37:56 UTC
Description of problem:
The spec file for the openoffice.org2-core RPM does not flag the file /usr/lib/openoffice.org2.0/share/psprint/psprint.conf as a configuration file (like the openoffice.org-1.1.5 RPM does with /usr/lib/ooo-1.1/share/psprint/psprint.conf).  As a result, upgrading the package results in the machine's printer configuration being overwritten.

Version-Release number of selected component (if applicable):
openoffice.org2-core-2.0.4-5.7.0.6.0 and earlier

How reproducible:
Always

Steps to Reproduce:
1. add a global printer to OOo2 (e.g., using /usr/lib/openoffice.org2.0/program/spadmin as root)
2. upgrade or reinstall the openoffice.org2-core RPM

  
Actual results:
The new printer is no longer present, since the file /openoffice.org2.0/share/psprint/psprint.conf is replaced with the file from the new RPM.

Expected results:
The new printer should be preserved.

Additional info:
This defect also applies to Red Hat Enterprise Linux 5.

Comment 1 RHEL Program Management 2008-12-14 15:05:08 UTC
Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.

Comment 2 Dan Astoorian 2008-12-15 16:07:22 UTC
At our site we need to add printers via psprint.conf because we cannot use CUPS for printing due to its lack of support for user authentication.  (The GTK2 CUPS print backend does not work at all when any type of CUPS authentication is enabled.)

Conversely, I don't see a downside to marking psprint.conf as a config file in the RPM.

Comment 3 Caolan McNamara 2009-06-22 11:09:22 UTC
This got done for the RHEL-5 OOo update. The "OOo2" RHEL-4 tech preview is unchanged, and IMO is unlikely to see any non-security updates in the RHEL-4 world


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