287565 – sys-process/iotop-0.3.2 should die instead of simply warn when CONFIG_* is not ok

Bug 287565 - sys-process/iotop-0.3.2 should die instead of simply warn when CONFIG_* is not ok

Summary: sys-process/iotop-0.3.2 should die instead of simply warn when CONFIG_* is no...

Status:	RESOLVED WONTFIX

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	High trivial
Assignee:	Jeremy Olexa (darkside) (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2009-10-03 20:26 UTC by Pacho Ramos
Modified:	2009-10-05 21:16 UTC (History)
CC List:	0 users

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 Pacho Ramos gentoo-dev

2009-10-03 20:26:41 UTC

Currently the following is being used:
CONFIG_CHECK="~TASK_IO_ACCOUNTING ~TASKSTATS"

But "~" should be dropped as, currently, iotop is installed but it doesn't work:
$ iotop 
Could not run iotop as some of the requirements are not met:
- Python >= 2.5 for AF_NETLINK support: Found
- Linux >= 2.6.20 with I/O accounting support (CONFIG_TASKSTATS, CONFIG_TASK_DELAY_ACCT, CONFIG_TASK_IO_ACCOUNTING): Not found

Thanks

Reproducible: Always

Comment 1 Justin Lecher (RETIRED) gentoo-dev

2009-10-05 19:44:58 UTC

As it is not fatal to the system, but not fuctional, I don't think that we need to force the die.
Nevertheless I assign to maintainer.

Comment 2 Jeremy Olexa (darkside) (RETIRED) archtester

2009-10-05 20:07:30 UTC

dieing is too harsh. Think of cross-compiling or compiling binpkgs for another host.

Comment 3 Pacho Ramos gentoo-dev

2009-10-05 21:16:42 UTC

I didn't think in that cases, sorry