changelog.Debian

   1 lvm2 (2.02.168-pve6) unstable; urgency=medium
   2
   3   * update lvmetad disabling to cause less log spam
   4
   5   * update lvmetad disabling to handle missing config key
   6
   7  -- Proxmox Support Team <support@proxmox.com>  Fri, 13 Oct 2017 09:54:53 +0200
   8
   9 lvm2 (2.02.168-pve5) unstable; urgency=medium
  10
  11   * more complete disabling of lvmetad
  12
  13   * don't attempt to enable unused init scripts
  14
  15  -- Proxmox Support Team <support@proxmox.com>  Mon, 9 Oct 2017 12:53:10 +0200
  16
  17 lvm2 (2.02.168-pve4) unstable; urgency=medium
  18
  19   * cherry-pick fixes for dmeventd shutdown behaviour
  20
  21  -- Proxmox Support Team <support@proxmox.com>  Fri, 6 Oct 2017 08:04:34 +0200
  22
  23 lvm2 (2.02.168-pve3) unstable; urgency=medium
  24
  25   * change the use_lvmetad default back to off
  26
  27  -- Proxmox Support Team <support@proxmox.com>  Mon, 24 Jul 2017 09:28:24 +0200
  28
  29 lvm2 (2.02.168-pve2) unstable; urgency=medium
  30
  31   * Update to 2.02.168-2 packaging
  32
  33   * Really apply PVE LVM config changes
  34
  35  -- Proxmox Support Team <support@proxmox.com>  Wed, 19 Apr 2017 11:13:45 +0200
  36
  37 lvm2 (2.02.168-pve1) unstable; urgency=medium
  38
  39   * Refresh PVE patches on top of Debian Stretch package
  40
  41   * Rebuild for PVE 5.0
  42
  43  -- Proxmox Support Team <support@proxmox.com>  Mon, 20 Mar 2017 09:56:27 +0100