Bug 173685 - update-alternatives --install should not remove non-symlinks
Summary: update-alternatives --install should not remove non-symlinks
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: chkconfig (Show other bugs)
(Show other bugs)
Version: rawhide
Hardware: All Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Ben Levenson
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-11-18 21:54 UTC by Thomas Fitzsimmons
Modified: 2014-03-17 02:56 UTC (History)
1 user (show)

Fixed In Version: 1.3.24-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-11-18 21:57:07 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.)

Description Thomas Fitzsimmons 2005-11-18 21:54:03 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4

Description of problem:
update-alternatives --install removes slaves if they're in its database but are no longer slaves of the master being installed, even if slave has been changed to something other than a symlink.  This behaviour causes legitimate files to be removed during upgrades that change a file from an alternative symlink to a normal file.


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


How reproducible:
Always

Steps to Reproduce:
1. build and install java-1.4.2-gcj-compat-1.4.2.0-40jpp_51rh
2. build and install java-1.4.2-gcj-compat-1.4.2.0-40jpp_52rh


Actual Results:  /usr/bin/rebuild-gcj-db does not exist:

$ rpm -qV java-1.4.2-gcj-compat
..?......   /etc/java/security/security.d/1000-gnu.java.security.provider.Gnu
missing     /usr/bin/rebuild-gcj-db


Expected Results:  Smooth upgrade.


Additional info:
Comment 1 Bill Nottingham 2005-11-18 21:57:07 UTC 
Fixed in 1.3.24-1, in theory.
Note You need to log in before you can comment on or make changes to this bug.