[raring-meta] Update linux-crashdump dependencies

Tim Gardner tim.gardner at canonical.com
Wed Feb 6 14:37:19 UTC 2013


On 02/06/2013 07:19 AM, Bouchard Louis wrote:
> Hi,
> 
> Le 06/02/2013 15:02, Stefan Bader a écrit :
>> Currently there is one complicating factor: kdump-tools is produced
>> by the makedumpfile source package (which is in main) but the
>> binary package kdump-tools is not (yet).
>> 
>> Louis is looking into that. Though it seems not a too big issue 
>> given that the makedumpfile source and binary package are already 
>> in main.
>> 
>> But after this change, the meta package may get stuck. Not sure 
>> whether it is better to wait for kdump-tools to be in main or go
>> ahead and push for it through having the meta package held back by
>> it.
>> 
>> -Stefan
>> 
>> ---
>> 
> 
> What I was told by the #ubuntu-devel crowd is that kdump-tools would
> get into main by the simple fact of having a main package with a
> dependancy toward kdump-tools. My verification with Martin Pitt this
> morning lead to believe that once crashdump-tools would depend on it,
> it would make its way into main automagically.
> 
> I don't know of any other package in main that would depend on 
> kdump-tools, as makedumpfile has no dependency toward kdump-tools
> but rather the opposite.
> 
> Kind regards,
> 
> ...Louis
> 
>> From 028e8d62d24a71f3329100f05f0aa9543f40572a Mon Sep 17 00:00:00
>> 2001 From: Stefan Bader <stefan.bader at canonical.com> Date: Wed, 6
>> Feb 2013 14:48:37 +0100 Subject: [PATCH] UBUNTU: Update
>> linux-crashdump dependencies
>> 
>> We were using some additional scripts in kexec-tools to produce 
>> kernel dumps via kexec. Though upstream and Debian got tools to
>> create those dumps packaged as kdump-tools. We want to reduce the
>> deviation from Debian, so changing the meta package to depend on
>> kdump-tools. The kdump-tools package depends on kexec-tools and
>> makedumpfile, so those two can be dropped from the dependencies.
>> 
>> Signed-off-by: Stefan Bader <stefan.bader at canonical.com> --- 
>> meta-source/debian/control.common |    2 +- 1 file changed, 1
>> insertion(+), 1 deletion(-)
>> 
>> diff --git a/meta-source/debian/control.common
>> b/meta-source/debian/control.common index 7cdbe0b..95afa6e 100644 
>> --- a/meta-source/debian/control.common +++
>> b/meta-source/debian/control.common @@ -36,7 +36,7 @@ Description:
>> Generic Linux kernel image. Package: linux-crashdump Architecture:
>> i386 amd64 Section: devel -Depends: ${misc:Depends}, kexec-tools,
>> makedumpfile, grub-pc (>= 1.96+20090611-1ubuntu2) | grub-efi-ia32 |
>> grub-efi-amd64 | grub (>= 0.97-29ubuntu24) +Depends:
>> ${misc:Depends}, kdump-tools, grub-pc (>= 1.96+20090611-1ubuntu2) |
>> grub-efi-ia32 | grub-efi-amd64 | grub (>= 0.97-29ubuntu24) 
>> Recommends: apport Suggests: crash Description: Linux kernel
>> crashdump setup for the latest generic kernel
>> 
> 
> 

I believe you should go through the Main Inclusion Request formality for
kdump-tools first. This gives the security team a chance to look at the
package to make sure its not going to disclose any sensitive
information, a particularly important action given the nature of this
package.

rtg
-- 
Tim Gardner tim.gardner at canonical.com




More information about the kernel-team mailing list