Hide Forgot
Description of problem: libvirt is being rebased in 6.1, and to keep the stack updated, and fix some serious error handling problems in libvirt-java the cleanest is to rebase that component too Version-Release number of selected component (if applicable): libvirt-java-0.4.6-1.el6 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
The upstream release was made by Bryan Kearney yesterday: https://www.redhat.com/archives/libvirt-users/2011-February/msg00014.html Fixing: - Only throw errors on real errors. - Remote non thread safe error reporting - BZ 600819 Incorrect scheduler parameter value passed to native API. Daniel
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: Libvirt-java is being rebased on 6.1 to math the libvirt rebase and pick the bug fixes done upstream especially the ones in the error handling APIs.
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,2 +1,2 @@ -Libvirt-java is being rebased on 6.1 to math the libvirt rebase and pick the bug fixes done upstream especially +Libvirt-java is being rebased on 6.1 to match the libvirt rebase and pick the bug fixes done upstream especially the ones in the error handling APIs.
libvirt-java-0.4.7-1.el6 is built into RHEL-6-candidate and should fix the issue, Daniel
Verified. Passed. Checked the brewweb (https://brewweb.devel.redhat.com/packageinfo?packageID=15012) libvirt-java-0.4.7-1.el6 for RHEL-6.1 was built successfully. The package can be install correctly. -------------- # rpm -qa|grep libvirt-java libvirt-java-0.4.7-1.el6.noarch libvirt-java-javadoc-0.4.7-1.el6.noarch libvirt-java-devel-0.4.7-1.el6.noarch
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0761.html