Description of problem: AFAIK, Spice does not need SDL, we should not install it. [root@master-vds9 ~]# yum remove SDL Loaded plugins: product-id, rhnplugin, subscription-manager Updating certificate-based repositories. Setting up Remove Process Resolving Dependencies --> Running transaction check ---> Package SDL.x86_64 0:1.2.14-2.el6 will be erased --> Finished Dependency Resolution Dependencies Resolved =================================================================================================================================================================================================================== Package Arch Version Repository Size =================================================================================================================================================================================================================== Removing: SDL x86_64 1.2.14-2.el6 @hybrid 469 k Transaction Summary =================================================================================================================================================================================================================== Remove 1 Package(s) Installed size: 469 k Is this ok [y/N]: n Exiting on user Command [root@master-vds9 ~]# rpm -qa |grep spice spice-server-0.8.2-5.el6.x86_64 Version-Release number of selected component (if applicable): 3.1 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Are you sure all past versions all since rhel-5.5, vdsm22, do not need this? Please remember that vdsm-bootstrap is expected to bootstrap all versions of vdsm since first released.
I will rephrase comment#1... from vdsm-bootstrap master of 3.2 we use yum API to install packages, hence not using the explicit dependencies at all. ovirt-host-deploy also uses yum API to achieve the task. So this already resolved in 3.2, the question in comment#1 is for 3.1.z.
(In reply to comment #2) > I will rephrase comment#1... from vdsm-bootstrap master of 3.2 we use yum > API to install packages, hence not using the explicit dependencies at all. This is exactly the problem - we explicitly ask for SDL. I'm pretty sure we don't need it anymore. > > ovirt-host-deploy also uses yum API to achieve the task. > > So this already resolved in 3.2, the question in comment#1 is for 3.1.z. No, not important at all for 3.1.z.
*** This bug has been marked as a duplicate of bug 861575 ***