Bug 707119

Summary: spice-server.spec: remove Obsolete lines
Product: Red Hat Enterprise Linux 6 Reporter: Uri Lublin <uril>
Component: spice-serverAssignee: Uri Lublin <uril>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.1CC: cmeadors, cpelland, dblechte, mkenneth
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: spice-server-0.8.1-2.el6 Doc Type: Bug Fix
Doc Text:
Although old SPICE-related packages (such as cairo-spice) are no longer required to be installed with the spice-server package, they were still needed by a previously installed spice-client or spice-server package. With the "Obsolete" lines in the package spec file, updating spice-server forced an update to spice-client as well, and vice versa. With this update, all "Obsolete" lines have been removed from the spice-server.spec file, thus fixing this bug.
Story Points: ---
Clone Of:
: 707122 707128 (view as bug list) Environment:
Last Closed: 2011-12-06 15:21:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 707122, 707125, 707128, 724984    

Description Uri Lublin 2011-05-24 06:54:51 UTC
Description of problem:
Following rhbz#674171 Obsolete lines were added to spice-server.spec
Following rhbz#675085 Obsolete lines were added to spice-client.spec

A by-product of adding these Obsolete lines is that if a RHEL-6.0 spice-server (and qemu-kvm) is installed on a machine, and spice-client is to be installed on that machine, spice-server (and qemu-kvm) are updated to RHEL-6.1 version.


https://bugzilla.redhat.com/show_bug.cgi?id=674171#c6 and 
https://bugzilla.redhat.com/show_bug.cgi?id=674171#c7 suggest it's better to just remove those Obsolete lines from the spec file.

This bug is for spice-server. Another bug is to be filed for spice-client.

Comment 6 Tomas Capek 2011-09-27 10:07:19 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Although old SPICE-related packages (such as spice-cairo) are no longer required to be installed with the spice-server package, they were still needed by a previously installed spice-client or spice-server package. With the "Obsolete" lines in the package spec file, updating spice-server forced an update to spice-client as well, and vice versa. With this update, all "Obsolete" lines have been removed from the spice-server.spec file, thus fixing this bug.

Comment 7 Uri Lublin 2011-11-30 14:01:11 UTC
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-Although old SPICE-related packages (such as spice-cairo) are no longer required to be installed with the spice-server package, they were still needed by a previously installed spice-client or spice-server package. With the "Obsolete" lines in the package spec file, updating spice-server forced an update to spice-client as well, and vice versa. With this update, all "Obsolete" lines have been removed from the spice-server.spec file, thus fixing this bug.+Although old SPICE-related packages (such as cairo-spice) are no longer required to be installed with the spice-server package, they were still needed by a previously installed spice-client or spice-server package. With the "Obsolete" lines in the package spec file, updating spice-server forced an update to spice-client as well, and vice versa. With this update, all "Obsolete" lines have been removed from the spice-server.spec file, thus fixing this bug.

Comment 8 errata-xmlrpc 2011-12-06 15:21:17 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-2011-1634.html