Bug 1015529 - Dependency on libvirt (daemon) isn't required for client bindings
Summary: Dependency on libvirt (daemon) isn't required for client bindings
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: rubygem-ruby-libvirt
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Bohuslav "Slavek" Kabrda
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-04 12:58 UTC by Dominic Cleal
Modified: 2015-02-17 17:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 17:30:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Dominic Cleal 2013-10-04 12:58:13 UTC
Description of problem:
rubygem-ruby-libvirt currently has a dependency on "libvirt", which provides the libvirtd daemon.  The bindings actually appears to link against libvirt-client, which is handled automatically by RPM auto-requires.

This dependency on the daemon could be dropped, as it adds huge installation requirements to a remote client using rubygem-ruby-libvirt.

Version-Release number of selected component (if applicable):
rubygem-ruby-libvirt-0.4.0-4.fc19

How reproducible:
Always

Steps to Reproduce:
1. rpm -q --requires rubygem-ruby-libvirt | grep "libvirt \+"

Actual results:
libvirt

Expected results:
none

Comment 1 Fedora End Of Life 2015-01-09 20:07:03 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2015-02-17 17:30:36 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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