It seems that PProcM depends on IO-Pipely during runtime for people who are on the testing branch. IO-Pipely is a new package and still on testing, so I guess it provides some functionality that was split from a pre-existing package. Until recently, PProcM was working fine without it. Reproducible: Always Steps to Reproduce: 1. On a testing system without IO-Pipely installed, emerge app-admin/pprocm. 2. Run PProcM 3. Actual Results: $ PProcM Can't locate IO/Pipely.pm in @INC (@INC contains: /etc/perl /usr/local/lib64/perl5/5.16.3/x86_64-linux-thread-multi /usr/local/lib64/perl5/5.16.3 /usr/lib64/perl5/vendor_perl/5.16.3/x86_64-linux-thread-multi /usr/lib64/perl5/vendor_perl/5.16.3 /usr/local/lib64/perl5 /usr/lib64/perl5/vendor_perl/5.16.0 /usr/lib64/perl5/vendor_perl /usr/lib64/perl5/5.16.3/x86_64-linux-thread-multi /usr/lib64/perl5/5.16.3 .) at /usr/lib64/perl5/vendor_perl/5.16.3/POE/Pipe.pm line 11. BEGIN failed--compilation aborted at /usr/lib64/perl5/vendor_perl/5.16.3/POE/Pipe.pm line 11. Compilation failed in require at (eval 4) line 2. ...propagated at /usr/lib64/perl5/5.16.3/base.pm line 84. BEGIN failed--compilation aborted at /usr/lib64/perl5/vendor_perl/5.16.3/POE/Pipe/OneWay.pm line 8. Compilation failed in require at /usr/lib64/perl5/vendor_perl/5.16.3/POE/Resource/Clock.pm line 12. BEGIN failed--compilation aborted at /usr/lib64/perl5/vendor_perl/5.16.3/POE/Resource/Clock.pm line 12. Compilation failed in require at /usr/lib64/perl5/vendor_perl/5.16.3/POE.pm line 11. BEGIN failed--compilation aborted at /usr/lib64/perl5/vendor_perl/5.16.3/POE.pm line 11. Compilation failed in require at /usr/bin/PProcM line 11. BEGIN failed--compilation aborted at /usr/bin/PProcM line 11. What happened after you performed the steps above? Expected Results: Show current read/write speed for each block device.
+ 17 Dec 2013; Mikle Kolyada <zlogene@gentoo.org> pprocm-1.0-r1.ebuild: + Add missing RDEPEND on dev-perl/IO-Pipely wrt bug #490132 +