With net-analyzer/flow-tools-0.68.5.1-r2 we see during the ebuild, the following warning: >>> Installing (1 of 1) net-analyzer/flow-tools-0.68.5.1-r2 chown: cannot access '/var/run/flows': No such file or directory chmod: cannot access '/var/run/flows': No such file or directory >>> Recording net-analyzer/flow-tools in "world" favorites file... This warning may be a side effect of the fix for this bug: https://bugs.gentoo.org/show_bug.cgi?id=448738 This /var/run/flows file is not actually created in the ebuild itself anymore, and even if it was then that too would be a bug, because /var/run is a tempfs which disappears on system shutdown, therefore storing files of any sort other than .pid files in /var/run is likely not a very wise idea. Certainly storing Netflow files on /var/run would be a pretty crazy thing to do (if that was ever the original intention). The warning is caused by the following statements in the .ebuild file: pkg_postinst() { chown flows:flows /var/run/flows chown flows:flows /var/lib/flows chown flows:flows /var/lib/flows/bin chmod 0755 /var/run/flows chmod 0755 /var/lib/flows chmod 0755 /var/lib/flows/bin flow-capture keeps it's .pid file in /var/run/flowcapture and that's OK, but nothing as far as I can tell should be putting anything in /var/run/flows . I believe the references to this directory are invalid and should be removed. Reproducible: Always
Fixed in -r2. Thanks for reporting!
