Bug 111713 - preserve configfiles while updating
Summary: preserve configfiles while updating
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: IBMJava2-JRE (Show other bugs)
(Show other bugs)
Version: 2.1
Hardware: i386 Linux
medium
low
Target Milestone: ---
Assignee: Karen Bennet
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-12-09 08:17 UTC by Andreas Piesk
Modified: 2007-11-30 22:06 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-05-05 20:01:52 UTC
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.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2004:145 normal SHIPPED_LIVE New java-1.4.1-ibm packages replace IBMJava2-1.4.1 packages 2004-05-24 04:00:00 UTC

Description Andreas Piesk 2003-12-09 08:17:41 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.5) Gecko/20031027

Description of problem:
the JRE contains several files which are likely to be modified by
users, for instance:

/opt/IBMJava2-131/jre/lib/security/cacerts
/opt/IBMJava2-131/jre/lib/security/java.policy
/opt/IBMJava2-131/jre/lib/security/java.security

these files should be declared as %config(noreplace) in the package,
otherwise the files will be wiped out without any warning.

this applies to the SDK as well.


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


How reproducible:
Always

Steps to Reproduce:
1. install JRE
2. import certificate into keystore
3. update JRE


Additional info:
Comment 2 Suzanne Hillman 2004-05-05 20:01:52 UTC 
Based on looking at the spec file, since there is no previous version
to upgrade from, this looks good. Closing.
Note You need to log in before you can comment on or make changes to this bug.