IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
Despite being a known quantity, autotools is so overkill for our needs,
so let's drop it and replace it with a much simpler and easy to customize
system.
Release process doesn't need to be documented in the repo
Dbus interface is basically unused, I've got no problem with having people
look at the code to figure it out if they care that much.
Switch over to use GObject introspection bindings for all python
modules related to GObject/GTK3/etc. It is not possible to mix
and match old pyggtk/pygobject manual bindings with new introspection
based bindings so it must be all changed in one go.
Imports like
import gtk
Change to
from gi.repository import Gtk
The vmmGObject class is changed to always inherit from GObject.GObject
There is no compelling reason to avoid a GObject dep for the
virt-manager TUI & it horribly messed up the code.
Signal declarations are changed from
vmmChooseCD.signal_new(vmmChooseCD, "cdrom-chosen", [object, str])
To
__gsignals__ = {
"cdrom-chosen": (GObject.SignalFlags.RUN_FIRST, None, [object, str])
}
which is required by new GObject bindings
Most of the rest of the change is simply dealing with renamed
constants / classes.
Alot of legacy compat code was removed - ie helpers which
check to see if certain GTK2 methods are available are no
longer required since we're mandating GTK3 only.
The event loop is replaced with LibvirtGLib's event loop.
Still todo
- Rip out all DBus stuff & make vmmEngine class inherit GtkApplication
which provides unique support & DBus method handling
- Switch to use LibvirtGConfig & LibvirtGObject for libvirt interaction
- Possibly switch to Python 3 too ?
- Figure out why GNOME keyring is missing Introspection support
My suggestion is that the standalone GIT repo for virt-install
only live on as a support branch for legacy platforms.
A stable-0.9 branch of virt-manager can be kept for legacy PyGtk2
based virt-manager releases.
The virt-manager master branch should exclusively use GObject
inspection and ideally Python3 and contain both the virt-manager
and virt-install codebases in one since they are intimately
related to each other & using separate GIT repos has needlessly
complicated life for everyone.
crobinso:
Some locking fixes
Misc cleanups and dropping now-useless code
Fix dbus usage
Fix graph cell renderer regression
Fix a couple tooltip issues
If we specify cpu model and apply once, we could not specify empty
cpu model again with following error.
"Error changing VM configuration: internal error Non-empty feature
list specified without CPU model"
That is not useful to restore default cpu model.
This patch fixes above issue.
Signed-off-by: Ken ICHIKAWA <ichikawa.ken@jp.fujitsu.com>
(crobinso: minor cleanup, add Ken to AUTHORS)
If users accidentally add whitespace to the beginning or end of a hostname their connection will fail, so strip it.
Fixes BZ 818438 - Whitespace in remote connection hostname field is not trimmed
(crobinso: Add Dave to AUTHORS)
As discussed in:
https://www.redhat.com/archives/virt-tools-list/2013-February/msg00154.html
There is a bug when creating disk image as qcow2, enable
fully allocating but get the minimal sparse image.
We should give users a notification which describing this.
Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com>
(crobinso: tweak message a bit)
virt-install already supports relabeling, but virt-manager doesn't and
in some cases, this can cause problems, for example when switching to
dynamic labeling with the relabeling turned off. I took the approach
of allowing the user to choose, with safe fallbacks to defaults.
Deals also with this:
https://bugzilla.redhat.com/show_bug.cgi?id=907390
