When emerging net-mail/razor-2.36-r1 final install step fails with error "unable to find [bunch of Razor2 modules] in @INC". Apparently reason is that before final merge, modules are installed into /var/tmp/portage/.../, which is not in @INC. Reproducible: Always Steps to Reproduce: 1. emerge /usr/portage/net-mail/razor/razor-2.36-r1.ebuild I think adding image directory to @INC for duration of ebuild should be done (probably for all perl modules). As a workaround, I installed razor-agints by hand, and then rerun emerge - it seems it worked just fine.
Here are few last lines from ebuild: Installing /var/tmp/portage/razor-2.36-r1/image/usr/bin/razor-client Writing /var/tmp/portage/razor-2.36-r1/image//usr/lib/perl5/vendor_perl/5.8.0/alphaev6-linux/auto/razor-agents/.packlist Appending installation info to /var/tmp/portage/razor-2.36-r1/image//usr/lib/perl5/vendor_perl/5.8.0/perllocal.pod blib/script/razor-client Can't locate Razor2/Preproc/deHTMLxs.pm in @INC (@INC contains: lib /etc/perl /usr/lib/perl5/site_perl/5.8.0/alphaev6-linux /usr/lib/perl5/site_perl/5.8.0 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.0/alphaev6-linux /usr/lib/perl5/vendor_perl/5.8.0 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.0/alphaev6-linux /usr/lib/perl5/5.8.0 /usr/local/lib/site_perl .) at lib/Razor2/Preproc/Manager.pm line 4. BEGIN failed--compilation aborted at lib/Razor2/Preproc/Manager.pm line 4. Compilation failed in require at lib/Razor2/Client/Agent.pm line 22. BEGIN failed--compilation aborted at lib/Razor2/Client/Agent.pm line 22. Compilation failed in require at blib/script/razor-client line 21. BEGIN failed--compilation aborted at blib/script/razor-client line 21. make: *** [install_razor_agents] Error 2 !!! ERROR: net-mail/razor-2.36-r1 failed. !!! Function perl-module_src_install, Line 102, Exitcode 2 !!! (no error message)
I ran into this same problem, but only on one out of two machines. It seems the install patch is still required in certain cases. I was able to work around the problem by first merging razor-2.36, followed by razor-2.36-r1
Confirmed problem and hack to overcome the problem. However, I noticed the following upon installing the first time: [..snip..] >>> Install razor-2.36 into /mp3/portage/portage/razor-2.36/image/ category net-mail patching file Makefile Hunk #1 FAILED at 275. Hunk #2 succeeded at 736 (offset 53 lines). Hunk #3 FAILED at 764. Hunk #4 FAILED at 777. 3 out of 4 hunks FAILED -- saving rejects to file Makefile.rej make[1]: Entering directory `/mp3/portage/portage/razor-2.36/work/razor-agents-2.36/Razor2-Preproc-deHTMLxs' make[1]: Leaving directory `/mp3/portage/portage/razor-2.36/work/razor-agents-2.36/Razor2-Preproc-deHTMLxs' cp bin/razor-client blib/script/razor-client [..snip..] It finished properly, after which I installed -r1.
got it too with perl 5.8.2, razor 2.36-r1 but i don't have any complain at "unpack" (patching) time. it only breaks after compilation, at install time.
Created attachment 22511 [details, diff] comments out install-razor-agents rule in Makefile This should fix it. razor-client gets run during pkg_postint() in the razor-2.36-r1.ebuild anyway, so this is not needed in the Makefile for us.
I also ran into this problem, so I also did it in this way: ACCEPT_KEYWORDS="~x86" emerge -qD "<razor-2.36-r1" followed by ACCEPT_KEYWORDS="~x86" emerge -qD razor and now it seems to work. Maybe somebody could create a -r2 release, which fixes that!
env ACCEPT_KEYWORDS="~x86" emerge -qD "<razor-2.36-r1"&&env ACCEPT_KEYWORDS="~x86" emerge -qD razor Can confirm this works here as well.
fixed in cvs with the given patch, thanks
*** Bug 39104 has been marked as a duplicate of this bug. ***
