When installing app-i18n/man-pages-de-1.3.0 the installation process gets caught in an infinite loop during phase install triggered by po4a-translate (app-text/po4-0.42) . It always happens at the same location. CPU usage goes up to 100%, but memory stays reasonable. Reproducible: Always
Created attachment 358336 [details] Output of ps
Created attachment 358338 [details] output of cave info man-pages-de
Created attachment 358340 [details] 1378577530-install-app-i18n_man-pages-de-1.3:0::gentoo.out
Please test again with sys-apps/portage as PM.
(In reply to Manuel Rüger from comment #4) > Please test again with sys-apps/portage as PM. Same problem here.
Created attachment 359494 [details, diff] temporary patch to make ebuild merge Using the patch I was able to successfully mere the package with paludis being the PM. "-k 0" option essentially means: take all unfinished translations, the default is to drop manpages with a translation completion below 80 percent. Having applied "-k 0" let po4a pass a lot of source files, except groff and console_ioctl - which is why they are excluded explicitely in the patch. Note: This is no real solution, the issues needs further investigation. I have not tried using portage. I suspect an enoding issue / missing env vars or broken perl install being the root cause for this problem. Greetings
Installs without any problems for me with portage-2.2.7 and sys-apps/man-pages-3.51 installed.
I cannot reproduce this either. Can you rerun with MAKEOPTS -j1 so we can single out an offender?
Created attachment 362920 [details] build log of po4a-0.45
(In reply to Markus Oehme from comment #8) > I cannot reproduce this either. Can you rerun with MAKEOPTS -j1 so we can > single out an offender? I tried to iinstall man-pages-de-0.45 again, but this time po4a itself hangs during installation (see above comment for the build log).
(In reply to Christian Apeltauer from comment #10) > I tried to iinstall man-pages-de-0.45 again, but this time po4a itself hangs > during installation (see above comment for the build log). Unfortunately, the build log is not very informative (I tried the build with portage, which worked fine for me and produced a more verbose output). Maybe 'Module::Build was not found in configure_requires!' is a problem, but I don't have any experience with paludis, so that may be a red herring. I've one more guess: maybe your perl-installation got whacky somehow. Maybe try remerging perl and using perl-cleaner.
Same Problems Here
(In reply to Maxr from comment #12) > Same Problems Here First some preliminaries: * Do you use portage? * Did you remerge perl and use perl-cleaner (just to be sure)? * Did you test with latest po4a and man-pages-de? Please provide a build log with MAKEOPTS="-j1". I'll then try to spot a difference to the working merge on this side.
Thank you for your (In reply to Markus Oehme from comment #13) > (In reply to Maxr from comment #12) > > Same Problems Here > > First some preliminaries: > * Do you use portage? I use paludis/cave > * Did you remerge perl and use perl-cleaner (just to be sure)? yes, I have reinstalled perl and updated perl with perl-cleaner -P paludis --all. However, I will do it again to make sure not wasting your time. > * Did you test with latest po4a and man-pages-de? Sorry, I should say I have problem only with app-text/po4a-0.45,I don't need man-pages-de > > Please provide a build log with MAKEOPTS="-j1". I'll then try to spot a > difference to the working merge on this side. Will test and update later.
Created attachment 367882 [details] outputlog of cave resolve po4a -x -1 perl version : v5.16.3 command used : 1: cave resolve perl -1 -x 2: perl-cleaner -P paludis --all 3: cave resolve po4a -x -1 output log
I did some testing and this seems to be a paludis specific thing. I can reproduce the stall with paludis on my machine, while portage does fine on the same setup. I opened a ticket in the paludis bug tracker and will move the discussion there.