Bug 222455 – sys-apps/kexec-tools and net-fs/openafs file collision

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Gautam Iyer 2008-05-17 00:35:52 UTC]

Both sys-apps/kexec-tools-1.101-r4 and net-fs/openafs-1.4.7_pre3 install the file /usr/sbin/kdump, and I get a file collision warning from portage.


Reproducible: Always

Steps to Reproduce:
1. emerge =sys-apps/kexec-tools-1.101-r4
2. emerge =net-fs/openafs-1.4.7_pre3

Actual Results:  
 * Detected file collision(s):
 *
 *      /usr/sbin/kdump

Expected Results:  
No file collisions

[Comment 1 Daniel Drake (RETIRED) 2008-10-31 22:10:03 UTC]

Stefaan, what is kdump in openafs?
I'd say that this tool belongs to kexec-tools, but I know openafs is a much older package and perhaps it's a very central component there too?

[Comment 2 Jeremy Olexa (darkside) (RETIRED) 2009-01-22 23:12:26 UTC]

(In reply to comment #1)
> Stefaan, what is kdump in openafs?
> I'd say that this tool belongs to kexec-tools, but I know openafs is a much
> older package and perhaps it's a very central component there too?
> 

From http://lse.sourceforge.net/kdump/ :

Kdump is a kexec based crash dumping mechansim for Linux. Kdump functionality is broken mainly in two components, user space and kernel space. Kernel space patches are already part of main line kernel tree. User space component is nothing but a patch on top of existing kexec tools. 

[Comment 3 Lari Korpi 2009-04-05 22:05:32 UTC]

And what is kdump doing in openafs?

It seems openafs has several old things that are now implemented elsewhere.
http://bugs.gentoo.org/show_bug.cgi?id=200674

[Comment 4 Chris Reffett (RETIRED) 2010-06-12 18:54:47 UTC]

Why not just remove the binary? I mean, this has happened before with openafs (where it installs compile_et, which is also installed by e2fsprogs-libs) and the fix for that in the ebuild is to rm the binary during src_install. Why not do the same here?

[Comment 5 SpanKY 2010-06-21 23:08:11 UTC]

openafs-1.4.12.1 ebuild punts kdump files