Main Inclusion Report for sourcepackage

Requirements

1. Availability: [http://archive.ubuntu.com/ubuntu/pool/universe/v/virt-manager/virt-manager_0.5.3-0ubuntu8.dsc]; amd64 i386 powerpc

2. Rationale:

   • virt-manager is a graphical console which acts as a front end to libvirt (already in main) locally or remotely, which in our case will be used to manage KVM guests

3. Security:

   • [http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=virt-manager CVE]: none

   • [http://secunia.com/search/?search=virt-manager Secunia history]: none

   • No binaries running as root or suid/sgid nor daemons
   • Network activity: does not open any port or accept any incoming data
   • Does no directly process binary (video, audio, etc) or structured (PDF, etc) data
   • Any source code review performed: soren working actively on it

4. Quality assurance:

   • In what situations does the package not work out of the box without configuration:
     • it requires a local or remote libvirt to work. It provides a sensible error message if someone has not installed it.
   • Does the package ask any debconf questions higher than priority 'medium': no

   • [http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=virt-manager Debian bugs]: No critical bugs

   • [http://packages.qa.debian.org/v/virt-manager.html Maintenance in Debian] is vigorous

   • [http://virt-manager.et.redhat.com/scmrepo.html Upstream] is vigorous

   • [https://bugzilla.redhat.com/buglist.cgi?component=virt-manager&bug_status=NEW&bug_status=ASSIGNED&bug_status=NEEDINFO&bug_status=MODIFIED&bug_status=ON_DEV&bug_status=ON_QA&bug_status=VERIFIED&bug_status=FAILS_QA&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&order=bugs.bug_severity,bugs.bug_status,bugs.priority,map_assigned_to.login_name,bugs.bug_id Upstream bug tracker]: No critical issues

   • Hardware: No special hw requirement directly from it
   • Is there a test suite in the upstream source or packaging ? Is it enabled to run in the build ?

5. Standards compliance:

   • [http://www.pathname.com/fhs/ FHS], [http://www.de.debian.org/doc/debian-policy/ Debian Policy] compliant

   • [http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html Debian library packaging guide] compliant

   • Packaging system: debhelper, cdbs, quilt

6. Dependencies:

   • [http://packages.ubuntu.com/python-gtk2 python-gtk2] in main

   • [http://packages.ubuntu.com/python-glade2 python-glade2] in main

   • [http://packages.ubuntu.com/python-gnome2 python-gnome2] in main

   • [http://packages.ubuntu.com/python-dbus python-dbus] in main

   • [http://packages.ubuntu.com/python-vte python-vte] in main

   • [http://packages.ubuntu.com/librsvg2-common librsvg2-common] in main

   • [http://packages.ubuntu.com/python-libvirt python-libvirt] in universe, see MIR...

   • [http://packages.ubuntu.com/python-virtinst python-virtinst] in universe, see MIR...

   • [http://packages.ubuntu.com/python-gtk-vnc python-gtk-vnc] in universe, see MIR...

   • [http://packages.ubuntu.com/python-urlgrabber python-urlgrabber] in universe, see MIR...

7. Background information:

   • The general purpose and context: very clear
   • What do upstream call this software: virt-manager, has always been called this

Reviewers

MIR bug: [https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/213491]

Report Author: NicolasBarcet Reviewer: