[Engine-devel] oVirt 3.4.0 alpha delayed

Sandro Bonazzola sbonazzo at redhat.com
Fri Jan 10 10:29:39 UTC 2014


Hi,
oVirt 3.4.0 alpha will be delayed due to packages dependencies issue.
Maintainers are already working on this, alpha will be released just after all dependency issues will have been fixed.

Details on dependency missing:

on CentOS 6.5:
[ovirt-3.4.0-alpha]
name=Alpha builds of the oVirt 3.4 project
baseurl=http://resources.ovirt.org/releases/3.4.0-alpha/rpm/EL/$releasever/
enabled=1
skip_if_unavailable=1
gpgcheck=0

# repoclosure -r ovirt-3.4.0-alpha -l ovirt-3.3.2 -l base -l epel -l glusterfs-epel -l updates -l extra -l glusterfs-noarch-epel -l ovirt-stable -n
Reading in repository metadata - please wait....
Checking Dependencies
Repos looked at: 8
   base
   epel
   glusterfs-epel
   glusterfs-noarch-epel
   ovirt-3.3.2
   ovirt-3.4.0-alpha
   ovirt-stable
   updates
Num Packages in Repos: 16581
package: mom-0.3.2-20140101.git2691f25.el6.noarch from ovirt-3.4.0-alpha
  unresolved deps:
     procps-ng
package: otopi-devel-1.2.0-0.0.master.20130910.git4387efb.el6.noarch from ovirt-3.4.0-alpha
  unresolved deps:
     otopi-java = 0:1.2.0-0.0.master.20130910.git4387efb.el6
package: ovirt-engine-sdk-java-3.4.0.1-1.el6.noarch from ovirt-3.4.0-alpha
  unresolved deps:
     httpcomponents-client >= 0:4.2
     apache-commons-logging
     apache-commons-beanutils
package: vdsm-hook-vhostmd-4.14.0-1.git6fdd55f.el6.noarch from ovirt-3.4.0-alpha
  unresolved deps:
     vhostmd


On Fedora 19:
[ovirt-3.4.0-alpha]
name=Alpha builds of the oVirt 3.4 project
baseurl=http://resources.ovirt.org/releases/3.4.0-alpha/rpm/Fedora/$releasever/
enabled=1
skip_if_unavailable=1
gpgcheck=0

# repoclosure -n -r ovirt-3.4.0-alpha -l fedora -l updates -l ovirt-stable
Reading in repository metadata - please wait....
Checking Dependencies
Repos looked at: 4
   fedora
   ovirt-3.4.0-alpha
   ovirt-stable
   updates
Num Packages in Repos: 38832
package: otopi-devel-1.2.0-0.0.master.20130910.git4387efb.fc19.noarch from ovirt-3.4.0-alpha
  unresolved deps:
     otopi-java = 0:1.2.0-0.0.master.20130910.git4387efb.fc19
package: ovirt-engine-3.4.0-0.2.master.20140109103311.git6524789.fc19.noarch from ovirt-3.4.0-alpha
  unresolved deps:
     openstack-java-resteasy-connector >= 0:3.0.2
     openstack-java-quantum-model >= 0:3.0.2
     openstack-java-quantum-client >= 0:3.0.2
     openstack-java-keystone-model >= 0:3.0.2
     openstack-java-keystone-client >= 0:3.0.2
     openstack-java-glance-model >= 0:3.0.2
     openstack-java-glance-client >= 0:3.0.2
     openstack-java-client >= 0:3.0.2
package: ovirt-engine-reports-3.4.0-0.2.master.20140109102135.fc19.noarch from ovirt-3.4.0-alpha
  unresolved deps:
     ovirt-engine-dwh >= 0:3.4.0


On Fedora 20 (ovirt-stable doesn't support Fedora 20):
[ovirt-3.4.0-alpha]
name=Alpha builds of the oVirt 3.4 project
baseurl=http://resources.ovirt.org/releases/3.4.0-alpha/rpm/Fedora/$releasever/
enabled=1
skip_if_unavailable=1
gpgcheck=0

# repoclosure -n -r ovirt-3.4.0-alpha -l fedora -l updates
Reading in repository metadata - please wait....
Checking Dependencies
Repos looked at: 3
   fedora
   ovirt-3.4.0-alpha
   updates
Num Packages in Repos: 38822
package: otopi-devel-1.2.0-0.0.master.20130910.git4387efb.fc19.noarch from ovirt-3.4.0-alpha
  unresolved deps:
     otopi-java = 0:1.2.0-0.0.master.20130910.git4387efb.fc19
package: ovirt-engine-3.4.0-0.2.master.20140109103311.git6524789.fc19.noarch from ovirt-3.4.0-alpha
  unresolved deps:
     openstack-java-resteasy-connector >= 0:3.0.2
     openstack-java-quantum-model >= 0:3.0.2
     openstack-java-quantum-client >= 0:3.0.2
     openstack-java-keystone-model >= 0:3.0.2
     openstack-java-keystone-client >= 0:3.0.2
     openstack-java-glance-model >= 0:3.0.2
     openstack-java-glance-client >= 0:3.0.2
     openstack-java-client >= 0:3.0.2
package: ovirt-engine-reports-3.4.0-0.2.master.20140109102135.fc19.noarch from ovirt-3.4.0-alpha
  unresolved deps:
     ovirt-engine-dwh >= 0:3.4.0

-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com



More information about the Engine-devel mailing list