Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 454748 - fcaps.eclass - fcaps() sometimes mentions the wrong filesystem type
Summary: fcaps.eclass - fcaps() sometimes mentions the wrong filesystem type
Status: RESOLVED DUPLICATE of bug 454440
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Eclasses (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Constanze Hausner (RETIRED)
URL: http://lists.gnu.org/archive/html/bug...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-30 22:38 UTC by Chris Smith
Modified: 2013-01-31 04:53 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Smith 2013-01-30 22:38:08 UTC 
net-misc/iputils-20121221-r1 throws garbage postinst messages referring to non-existent filesystems

Reproducible: Always

Actual Results:  
WARN: postinst
Could not set caps on '/bin/arping' due to missing filesystem support.
Make sure you enable XATTR support for 'ext2/ext3' in your kernel.   
Could not set caps on '/bin/ping' due to missing filesystem support.
Make sure you enable XATTR support for 'ext2/ext3' in your kernel. 
Could not set caps on '/bin/ping6' due to missing filesystem support. 
Make sure you enable XATTR support for 'ext2/ext3' in your kernel.  
Could not set caps on '/usr/bin/clockdiff' due to missing filesystem support.                                                 
Make sure you enable XATTR support for 'ext2/ext3' in your kernel.

Expected Results:  
As ext2 and ext3 are not being used nor are they compiled in the kernel these messages should not occur.
Comment 1 Jeroen Roovers (RETIRED) gentoo-dev 2013-01-31 04:20:14 UTC 
It runs $(stat -f -c %T "${file}") and that returns "ext2/ext3" in some cases.
Comment 2 SpanKY gentoo-dev 2013-01-31 04:53:59 UTC 

*** This bug has been marked as a duplicate of bug 454440 ***