
Upstream software project
ruby-fog-libvirt
Module for the 'fog' gem to support libvirt
About ruby-fog-libvirt
Module for the 'fog' gem to support libvirt
This project links 4 native package records across 3 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.
These are catalog observations, not a guarantee of installation, compatibility, or upstream support.
Project pictures and package coverage
Project identity
- Project
- ruby-fog-libvirt
- Publisher
- Not authoritatively mapped
- Native package records
- 4
- Operating systems
- debian-12, debian-13, opensuse-leap-15-6
- License expression
- MIT
- Metadata completeness
- 100/100 (not a software quality rating)
- Homepage
- Visit upstream site
- Source repository
- Open source repository
Source-reported description
The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.
Packages by operating system
Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.
Debian 12 (Bookworm)
- ruby-fog-libvirt0.11.0-1
Debian 12 (Bookworm) / ruby
Module for the 'fog' gem to support libvirt
allbookworm
Debian 13 (Trixie)
- ruby-fog-libvirt0.13.2-1
Debian 13 (Trixie) / ruby
Module for the 'fog' gem to support libvirt
alltrixie
openSUSE Leap 15.6
- ruby2.5-rubygem-fog-libvirt0.7.0-bp156.3.1
openSUSE Leap 15.6 / Development/Languages/Ruby / source rubygem-fog-libvirt
Module for the 'fog' gem to support libvirt
aarch64ppc64les390xx86_64leap-15.6 - ruby2.5-rubygem-fog-libvirt-doc0.7.0-bp156.3.1
openSUSE Leap 15.6 / Development/Languages/Ruby / source rubygem-fog-libvirt
RDoc documentation for fog-libvirt
aarch64ppc64les390xx86_64leap-15.6
Project resources and further reading
Mapping provenance
Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.
No field-level source record is published yet.