| Summary: | spice-client.spec: remove Obsolete lines | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Uri Lublin <uril> | |
| Component: | spice-client | Assignee: | Uri Lublin <uril> | |
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | urgent | |||
| Version: | 6.1 | CC: | cpelland, dblechte, djasa, lkocman, mkenneth | |
| Target Milestone: | rc | Keywords: | ZStream | |
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | spice-client-0.8.0-3.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-client 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-client forced an update to spice-server as well, and vice versa. With this update, all "Obsolete" lines have been removed from the spice-client.spec file, thus fixing this bug.
|
Story Points: | --- | |
| Clone Of: | 707119 | |||
| : | 707125 (view as bug list) | Environment: | ||
| Last Closed: | 2011-12-06 15:22:23 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: | 707119, 707128 | |||
| Bug Blocks: | 707125, 725103 | |||
|
Description
Uri Lublin
2011-05-24 06:59:00 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
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-client 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-client forced an update to spice-server as well, and vice versa. With this update, all "Obsolete" lines have been removed from the spice-client.spec file, thus fixing this bug.
VERIFIED in spice-client-0.8.2-7
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-client 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-client forced an update to spice-server as well, and vice versa. With this update, all "Obsolete" lines have been removed from the spice-client.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-client 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-client forced an update to spice-server as well, and vice versa. With this update, all "Obsolete" lines have been removed from the spice-client.spec file, thus fixing this bug.
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-1518.html |