Bug#576227: insserv: warning: script is corrupt or invalid

On 09/09/2010 12:33 PM, Christian Hofstaedtler wrote: Ola, Do I need to have a kernel with vzevent support for this to test? Chris, this is correct. If so then I must wait until such a kernel appears in Debian... Right. Max Attems informed me yesterday that the kernel will be ready

Bug#513310: [Debian] Re: Bug#513310: vzctl fails to set capabilities, and subsequently fails to start any VE

will backport this fix. I thought I already did that. Thanks! // Ola Quoting Kir Kolyshkin : This is caused by newer kernel headers (in this case on a build system that was used to build this vzctl package), and is fixed in vzctl-3.0.23. See the following git commit: http://git.openvz.org/?p=vz

Bug#513310: [Debian] Re: Bug#513310: vzctl fails to set capabilities, and subsequently fails to start any VE

This is caused by newer kernel headers (in this case on a build system that was used to build this vzctl package), and is fixed in vzctl-3.0.23. See the following git commit: http://git.openvz.org/?p=vzctl;a=commit;h=0d6bfad92c7cb6a193801ce8dac3a0dc64396ca8 So the solution is either to upgrade

Bug#482974: [Debian] Re: Bug#482974: vzctl: vzctl start fails with "Unable to set capability: Invalid argument"

problem on all other platforms than i386. The reason is that they are automatically built. If the kernel information is wrong on the build machine it will get this problem. When is the next release? Best regards, // Ola On Tue, May 27, 2008 at 12:47:50PM +0400, Kir Kolyshkin wrote: It's

Bug#415579: kernel-patch-openvz: Kernel does not compile

It looks like you have not enabled CONFIG_VE (perhaps because of enabled CONFIG_SECURITY). So the way to solve this is disable CONFIG_SECURITY and then enable CONFIG_VE. Konstantin Seiler wrote: Package: kernel-patch-openvz Version: 028.18.1 Severity: grave Justification: renders package unusa

Bug#400675: kernel-patch-openvz: patch still not applying cleanly

Hi Steve, See my comments below. Steve Langasek wrote: If so I need to be prepared as that will probably break this patch. Why is this patch so fragile? If it breaks that easily, it hardly seems releasable -- how do we protect against it being broken by security updates? I suggest that

Bug#400675: kernel-patch-openvz: OpenVZ-Patch does not apply to Debian-Kernel

Could we set up some machinery in order to be notified ASAP about the kernel-patch-openvz rejects? Ola Lundqvist wrote: Hi On Mon, Dec 04, 2006 at 02:40:21PM +0300, Vasily Tarasov wrote: Hi, When I was preparing previous patch only 2.6.18-5 was available from I see. I forgot about t