Bug 862240

Summary: Bacula-storage-common wrongly removes alternatives for bcopy during update.
Product: Red Hat Enterprise Linux 6 Reporter: Lukáš Nykrýn <lnykryn>
Component: baculaAssignee: Lukáš Nykrýn <lnykryn>
Status: CLOSED ERRATA QA Contact: Tomas Dolezal <todoleza>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.3CC: azelinka, ovasik, todoleza
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: bacula-5.0.0-12.el6 Doc Type: Bug Fix
Doc Text:
Cause: Post scriptlet in bacula-storage-common do /usr/sbin/alternatives --remove bacula-sd. Consequence: Link to bcopy.{mysql,sqlite,postgresql} does not exist after update. Fix: Do not remove these links in storage-common package, but in storage-{mysql,sqlite,postgresql} Result: Link to bcopy.{mysql,sqlite,postgresql} does not disappear after update.
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-11-19 04:15:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Patch for spec file none

Description Lukáš Nykrýn 2012-10-02 12:06:01 UTC
Description of problem:
Post scriptlet in bacula-storage-common do /usr/sbin/alternatives --remove bacula-sd.

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

Steps to Reproduce:
1. update bacula-sd
2. /usr/sbin/alternatives --display bacula-sd
  
Actual results:
link does not exist

Expected results:
link should exist

Additional info:
Missing link can lead to problems during package removal.
Workaround for this issue is to manually add link before uninstall, for example:
/usr/sbin/alternatives --install /usr/sbin/bcopy bacula-sd /usr/sbin/bcopy.sqlite 40

Comment 1 Lukáš Nykrýn 2012-10-02 12:08:35 UTC
Created attachment 620258 [details]
Patch for spec file

Comment 10 errata-xmlrpc 2012-11-19 04:15:29 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-1469.html