From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cpsmtpm-eml110.kpnxchange.com ([195.121.3.14]:64191 "EHLO CPSMTPM-EML110.kpnxchange.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934167Ab0BYW3O convert rfc822-to-8bit (ORCPT ); Thu, 25 Feb 2010 17:29:14 -0500 From: Frans Pop Subject: Re: failure to remove+purge debian package generated by make deb-pkg Date: Thu, 25 Feb 2010 23:29:11 +0100 References: <20100225213610.GA30380@pengutronix.de> In-reply-To: <20100225213610.GA30380@pengutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8BIT Content-Disposition: inline Message-Id: <201002252329.12338.elendil@planet.nl> Sender: linux-kbuild-owner@vger.kernel.org List-ID: To: Uwe =?iso-8859-1?q?Kleine-K=F6nig?= Cc: linux-kbuild@vger.kernel.org, debian-kernel@lists.debian.org Uwe Kleine-König wrote: > I created and successfully installed a custom kernel package using > $(make deb-pkg). > > Then after a failed boot test I removed it and then thought that I > actually want to purge it. > > Cannot delete /boot/initrd.img-2.6.33-rc8-rt, doesn't exist. > run-parts: /etc/kernel/postrm.d/initramfs-tools exited with return code 1 It has nothing to do with the kernel package itself. The problem is in the maintainer scripts that are run as hooks from /etc/kernel/*.d. The kernel package built by deb-pkg does not have any maintainer scripts of itself. All it does is run whatever is in the hooks. As custom kernels may have other requirements than distro ones it's not surprising that the distro hooks can throw errors [1]. Personally I use a set of custom hook scripts with my deb-pkg kernels. Simply because I don't want to have to fix issues that are the result of the distro hook scripts in /etc/kernel. You can simply use custom hook scripts by doing e.g: export KDEB_HOOKDIR=/etc/kernel.custom before calling 'make deb-pkg'. You can then create your own hook scripts in /etc/kernel.custom/{pre,post}{inst,rm}.d/. Cheers, FJP [1] Although in this case I would say that the initrd could also simply be removed using 'rm -f' so it does not fail if it does not exist. You could file a BR against the package that installed that particular hook script, probably initramfs-tools.