Summary: | app-portage/eix-0.31.9: eix-test-obsolete repeats "invalid line" message many times | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Daniel Gulotta <dgulotta> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED UPSTREAM | ||
Severity: | minor | CC: | martin |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Daniel Gulotta
2016-09-14 16:30:50 UTC
eix-test-obsolete is just a wrapper for eix which, roughly speaking, calls first eix -te and then eix -Te several times with successively various REDUNDANT_IF_* tests disabled. Of course, eix does not know that it was called previously, and just will spit the warning every time. If you use "eix-test-obsolete quick" (or simply eix -tTe), then eix is called only twice (or once), and you see the warning also only twice (once), but of course the output has correspondingly less information. There is not much which can be changed in this structure (unless one would code a completely independent "obsolete" test). I added the option --nowarn which suppresses certain warnings and added it to all calls of eix in eix-test-obsolte (except for the first call eix -t). There can still be some duplicate output from eix -t, because files are read twice: Once to get the portage config and once to check for -t redundancy. It would be unnatural to suppress warnings, because they can be disjoint, depending on your configuration. The fix is in the git master branch on github (>=eix-0.31.10). A live ebuild for eix is in the mv overlay. I slept it over and decided to even avoid duplicate output: Warnings are now cached and printed only once. |