Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 384881 - sys-fs/udisks-1.0.[2-4] incomplete kernel conf check
Summary: sys-fs/udisks-1.0.[2-4] incomplete kernel conf check
Status: RESOLVED DUPLICATE of bug 356453
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-29 07:27 UTC by Sergey S. Starikoff
Modified: 2011-09-29 07:52 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sergey S. Starikoff 2011-09-29 07:27:05 UTC
Doring configuring automount on my home PC I've read the udisks pacckage, that I need to set up USB_SUSPEND option in my kernel.
And failed to find it by search in menuconfig
Web search said, that I was not only, who failed with it.

Reproducible: Always

Steps to Reproduce:
1. Set up test kernel with disabled PM_RUNTIME and boot with it;
2. emerge -1 udisks (needed and installed);
3. read kernel conf warning;
4. Try to fix kernel configuration.
Actual Results:  
See nothing (no required option, the issue exactly as described in https://bugs.gentoo.org/show_bug.cgi?id=356453 )

It needs PM_RUNTIME too. You would have find this out by hitting / in
menuconfig for search and typing USB_SUSPEND.



Expected Results:  
The udisks ebuild should first check PM_RUNTIME kernel option.
If failed --- report, that PM_RUNTIME and USB_SUSPEND kernel options should be enabled.
If success --- check USB_SUSPEND option.
Comment 1 Samuli Suominen (RETIRED) gentoo-dev 2011-09-29 07:52:32 UTC
udisks only needs CONFIG_USB_SUSPEND and doesn't care about what's the prereqs there are for it, it's clearly visible if you do simple search in menuconfig, so therefore such check doesn't belong to the ebuild

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