Ubuntu
libvirt package

virtlockd.service shouldn't be installed via dh_systemd_start

Bug #1588006 reported by Chris J Arges on 2016-06-01

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	libvirt (Ubuntu)	Fix Released	Medium	Chris J Arges

Bug Description

Since this is a socket activated service, just install the socket and not the service file as well.

Tags:

Revision history for this message

Chris J Arges (arges) wrote on 2016-06-01:

lp1588006.debdiff Edit (1.3 KiB, text/plain)

Changed in libvirt (Ubuntu):
status:	New → In Progress
importance:	Undecided → Medium
assignee:	nobody → Chris J Arges (arges)
tags:	added: patch

Revision history for this message

Launchpad Janitor (janitor) wrote on 2016-06-02:

This bug was fixed in the package libvirt - 1.3.4-1ubuntu5

---------------
libvirt (1.3.4-1ubuntu5) yakkety; urgency=low

  * Update the correct apparmor profiles to allow AAVMF and qemu-efi
    firmware for aarch64 (1538882)
  * Clean up / refresh various patches to finalize switch from libvirt-bin
    to libvirtd as service name.
    Drop: d/p/ubuntu/libvirt-bin-service-libvirtd-alias.patch
    Refresh+Rename: d/p/ubuntu/libvirt-bin-service-set-notifyaccess.patch ->
                    d/p/ubuntu/libvirtd-service-nolimit.patch
    Rename: d/p/ubuntu/libvirt-bin-service-set-notifyaccess.patch ->
            d/p/ubuntu/libvirtd-service-set-notifyaccess.patch
    Refresh: d/p/ubuntu/libvirtd-service-add-bin-alias.patch
    Add: d/p/ubuntu/libvirtd-init-add-bin-alias.patch
  * Change default profile used by libvirtd.service to /etc/default/libvirtd.
    Drop: d/p/ubuntu/switch-service-files-to-libvirt-bin.patch
  * Drop virtlockd.service from dh_systemd_start in debian/rules as
    the service is socket activated (LP: #1588006).
  * Fix failure to enable libvirtd.service due to lingering libvirt-bin
    alias. This could happen when the upgrade from a version prior 1.3.3-2
    happened before 1.3.4-1ubuntu3 (LP: #1588004).