Bug 842356 - Rebase usbredir to latest upstream
Rebase usbredir to latest upstream
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: usbredir (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Hans de Goede
Desktop QE
: Rebase
Depends On:
  Show dependency treegraph
Reported: 2012-07-23 10:42 EDT by Hans de Goede
Modified: 2013-02-21 03:50 EST (History)
2 users (show)

See Also:
Fixed In Version: usbredir-0.5.1-1.el6
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-02-21 03:50:37 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0346 normal SHIPPED_LIVE usbredir bug fix and enhancement update 2013-02-20 15:53:45 EST

  None (edit)
Description Hans de Goede 2012-07-23 10:42:39 EDT
Almost all Spice features being developed upstream are coming from RHEL/RHEV RFE-s, backporting all the necessary changes from upstream to the RHEL-6 packages, will result in backporting aprox. 90% of all changes, leading to almost identical yet subtle different source trees (with subtle different behavior and/or bugs) for RHEL-6 and upstream/Fedora/what will be in RHEL. Therefor we would like to rebase the spice packages to the latest upstream.

These changes are needed for support for seamless migration and USB live migration.
Comment 2 Hans de Goede 2012-09-21 03:37:17 EDT
This is fixed by usbredir-0.5.1-1.el6, moving to modified.
Comment 6 errata-xmlrpc 2013-02-21 03:50:37 EST
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.


Note You need to log in before you can comment on or make changes to this bug.