trunk : Code : Ruby Libvirt Client

Get this branch:: bzr branch lp:ruby-libvirt

Branch merges

This import branch has no branches proposed for merge into it.

No branches dependent on this one.

Related bugs

Link a bug report

Related blueprints

Branch information

Owner:: Brightbox

Project:: Ruby Libvirt Client

Status:: Development

Import details

Import Status: Failed

This branch is an import of the HEAD branch of the Git repository at git://libvirt.org/ruby-libvirt.git.

The import has been suspended because it failed 5 or more times in succession.

Last successful import was on 2020-05-15.

Import started on 2020-05-19 on izar and finished on 2020-05-19 taking 15 seconds — see the log

Import started on 2020-05-17 on alnitak and finished on 2020-05-17 taking 15 seconds — see the log

Import started on 2020-05-16 on izar and finished on 2020-05-16 taking 15 seconds — see the log

Import started on 2020-05-15 on alnitak and finished on 2020-05-15 taking 15 seconds — see the log

Recent revisions

598. By Daniel Berrange on 2020-04-30

gitlab: add CI job for validating DCO signoff

This job uses the shared "check-dco" image to validate that all
commits on a branch in a developer's repo fork have a suitable
Signed-off-by statement present.

Signed-off-by: Daniel P. Berrangé <email address hidden>

597. By Daniel Berrange on 2020-04-07

github: enable lockdown of issues and merge requests

Libvirt uses GitHub as an automated read-only mirror. The goals were to
have a disaster recovery backup for libvirt.org, a way to make it easy
for people to clone their own private copy of libvirt Git, and finally
as a way to interact with apps like Travis.

The project description was set to a message telling people that we
don't respond to pull requests. This was quite a negative message to
potential contributors, and also did not give them any guidance about
the right way to submit to libvirt. Many also missed the description and
submitted issues or pull requests regardless.

It is possible to disable the issue tracker in GitHub, but there is no
way to disable merge requests. Disabling the issue tracker would also
leave the problem of users not being given any positive information
about where they should be reporting instead.

There is a fairly new 3rd party application built for GitHub that
provides a bot which auto-responds to both issues and merge requests,
closing and locking them, with a arbitrary comment:

https://github.com/apps/repo-lockdown

This commit adds a suitable configuration file for libvirt, which
tries to give a positive response to user's issue/pullreq and guide
them to the desired contribution path on GitLab.

Reviewed-by: Andrea Bolognani <email address hidden>
Reviewed-by: Pavel Hrdina <email address hidden>
Reviewed-by: Eric Blake <email address hidden>
Signed-off-by: Daniel P. Berrangé <email address hidden>

596. By Charlie Smurthwaite <email address hidden> on 2020-02-21

Fix cpumap allocation for virDomainGetVcpus and use return value

This patch fixes a bug in which only enough memory for one cpumap is allocated
for virDomainGetVcpus instead of one per virtual CPU. This Fixes an overflow.
Additionally, it uses the return value of virDomainGetVcpus to determine how
many cpuinfo structs were actually populated rather than assuming they all are.
Finally, it uses the logical CPU number from the cpuinfo struct in the retrurn
data instead of assuming CPU numbers are sequential. This should handle cases
where arbitrary CPUs are offline.

Signed-off-by: Charlie Smurthwaite <email address hidden>
Reviewed-by: Charlie Smurthwaite <email address hidden>
Signed-off-by: Ján Tomko <email address hidden>

595. By Stefano Garzarella on 2019-11-23

Fix default values for node_cpu_stats() and node_memory_stats()

ruby_libvirt_value_to_int() returns 0 if the optional value is
not defined, but in node_cpu_stats() and node_memory_stats()
the default value of cpuNum and cellNum is -1.

Reviewed-by: Cole Robinson <email address hidden>
Reported-by: Charlie Smurthwaite <email address hidden>
Signed-off-by: Stefano Garzarella <email address hidden>

594. By Daniel Berrange on 2018-04-24

git: add config file telling git-publish how to send patches

The "git-publish" tool is a useful git extension for sending patch
series for code review. It automatically creates versioned tags
each time code on a branch is sent, so that there is a record of
each version. It also remembers the cover letter so it does not
need re-entering each time the series is reposted.

With this config file present it is now sufficient[1] to run

$ git publish

to send all patches in a branch to the list for review, with the
correct subject prefix added for this non-core libvirt module.

[1] Assuming your $HOME/.gitconfig has an SMTP server listed
at least e.g.

[sendemail]
smtpserver = smtp.example.com

Signed-off-by: Daniel P. Berrangé <email address hidden>

593. By Chris Lalancette on 2018-02-18

Make sure to use our own css everywhere on the site.