stable

rubygem-fog-libvirt-0.0.3-3.fc24 and rubygem-ruby-libvirt-0.7.0-1.fc24

FEDORA-2016-69519948a5 created by clalance 9 years ago for Fedora 24

Update ruby-libvirt to upstream 0.7.0 release. This requires to relax dependency in fog-libvirt.

How to install

Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:

sudo dnf upgrade --refresh --advisory=FEDORA-2016-69519948a5

This update has been submitted for testing by clalance.

9 years ago

This update has been pushed to testing.

9 years ago

This update has reached 14 days in testing and can be pushed to stable now if the maintainer wishes

9 years ago
User Icon bowlofeggs commented & provided feedback 9 years ago
karma

When I do a dnf upgrade --enablerepo updates-testing, I see this:

Skipping packages with broken dependencies: rubygem-ruby-libvirt x86_64 0.7.0-1.fc24 updates-testing 87 k

User Icon bit4man commented & provided feedback 9 years ago
karma

Works for me

User Icon bex commented & provided feedback 9 years ago
karma

+1

vondruch edited this update.

9 years ago
User Icon domcleal commented & provided feedback 9 years ago
karma

rubygem-fog-libvirt also needs updating to 0.3.0, as it currently depends on rubygem(ruby-libvirt) < 0.7.0 preventing this update from being installed.

$ rpm -q rubygem-fog-libvirt
rubygem-fog-libvirt-0.0.3-2.fc24.noarch
$ rpm -qR rubygem-fog-libvirt | grep ruby-libvirt
rubygem(ruby-libvirt) >= 0.5.0
rubygem(ruby-libvirt) < 0.7.0
User Icon bowlofeggs commented & provided feedback 9 years ago
karma

dnf still will not install this package, claiming it has broken dependencies.

This update has been unpushed.

Better to unpush this as long as nobody is going to fix it ...

Yeah, I agree. I think we need to actually update fog so that it accepts any version of ruby-libvirt, not tied to a specific one. vondruch, any chance you can track that down and get it done?

vondruch already removed the maximum version in fog-libvirt@5b04ed3, it's just that Fedora 24 has a much older fog-libvirt 0.0.3 with the limit still in place. F25+ are fixed.

This [1] was the real source of issues as far as I remember. I'll bump the fog-libvirt dependency to the latest ruby-libvirt and add this to this update, but I hope you guys will test it, because I don't have an energy to spend on testing this.

[1] https://github.com/vagrant-libvirt/vagrant-libvirt/issues/568#issuecomment-193448091

Can somebody test this scratch build of rubygem-fog-libvirt prior I commit it?

https://koji.fedoraproject.org/koji/taskinfo?taskID=18520272

vondruch: installation with this rubygem-ruby-libvirt update and basic fog-libvirt functionality works for me.

vondruch edited this update.

New build(s):

  • rubygem-fog-libvirt-0.0.3-3.fc24
9 years ago

This update has been submitted for testing by vondruch.

9 years ago

So lets see how this will work ... I did precisely 0 testing, so it is up to you guys. Autokarma is disabled ...

This update has been pushed to testing.

9 years ago
User Icon domcleal commented & provided feedback 9 years ago
karma

vagrant-libvirt and basic fog-libvirt usage appears to work.

User Icon pvalena commented & provided feedback 9 years ago
karma

vagrant up|halt|ssh commands work as expected

This update has been submitted for stable by vondruch.

9 years ago

Ok, one month in updates-testing and two positive responses. I pushed this into stable.

This update has been pushed to stable.

9 years ago

Please log in to add feedback.

Metadata
Type
enhancement
Karma
2
Signed
Content Type
RPM
Test Gating
Autopush Settings
Unstable by Karma
-3
Stable by Karma
disabled
Stable by Time
disabled
Dates
submitted
9 years ago
in testing
9 years ago
in stable
9 years ago
modified
9 years ago

Automated Test Results