Bug#892193: lvm2: Debian 9 fails to boot from the LV on a multipath device

Package: lvm2 Version: 2.02.168-2 Severity: important Dear Maintainer, there is a problem with booting Debian Stretch from LV on a multipath device (I have multipath-tools-boot installed). At initramfs, logical volumes are activated by udev as soon as the disks appear, so lvm complains that there

Bug#876459: needrestart: Non-interactive mode not being detected properly

Package: needrestart Version: 2.11-3 Severity: important Tags: upstream patch Dear Maintainer, the problem described in the archived bug #803249 still exists in 2.11-3 (Debian 9.1). When needrestart is run without a tty AND with DEBIAN_FRONTEND=noninteractive, it still tries to work

Bug#876452: needrestart: Unnamed block devices (like for OpenVZ's simfs) not being detected properly

Package: needrestart Version: 2.11-3 Severity: important Tags: patch upstream Dear Maintainer, needrestart does not work properly on some OpenVZ containers - it always claims that everything needs to be restarted. There was a bug report about that in the upstream:

Bug#778303: chef: Memory leak

the issue and the solution is here: https://github.com/chef/chef/pull/754 Please let me know if it is possible to apply it together with the forked runs (technically it is), or should I open another issue. -- Greetings, Piotr Pańczyk Asseco Business Solutions S.A

Bug#778303: chef: Memory leak

. If you decide to backport the package, I would suggest to add one small feature (from newer versions) by chance - I really miss the file_edited? method in Chef::Util::FileEdit. It's just one getter, the diff is also attached. -- Greetings, Piotr Pańczyk Asseco

Bug#778303: chef: Memory leak

of virtual machines. If you manage to apply the commits related to the forking behaviour, I can test the package for you. On 22.02.2015 03:16, Antonio Terceiro wrote: Hello Piotr, On Fri, Feb 13, 2015 at 03:56:38PM +0100, Piotr Pańczyk wrote: Hello Antonio, On 13.02.2015 14:29, Antonio Terceiro wrote

Bug#778303: chef: Memory leak

Hello Antonio, On 13.02.2015 14:29, Antonio Terceiro wrote: Would you by any chance be able to identify the upstream commit that introduced the fix? If so, I can try backporting that and releasing a stable update. I think this is it: https://github.com/chef/chef/pull/291 -- Greetings, Piotr

Bug#773698: chef-server-api: Error 500 returned by Chef Server

Package: chef-server-api Version: 10.12.0-1 Severity: normal Dear Maintainer, I'm getting error 500 (Net::HTTPFatalError: 500 Internal Server Error) from Chef Server when running the client, probably due to big amount of data returned by Ohai. I tried connecting the same node to newer version of