I am unable to emerge dev-perl/perl-tk-800.025-r1, as I get some strange behavior during the patch phase where the ebuild attempt to access Perforce. Reproducible: Always Steps to Reproduce: 1. emerge perl-tk Actual Results: When emerging dev-perl/perl-tk-800.025-r1 I get the output+error: Calculating dependencies ...done! >>> emerge (1 of 4) dev-perl/perl-tk-800.025-r1 to / >>> md5 src_uri ;-) Tk800.025.tar.gz >>> Unpacking source... >>> Unpacking Tk800.025.tar.gz to /opt/portage/portage/perl-tk-800.025-r1/work * Applying perl-tk-800.025-dirtarget.patch... * A dry-run of patch command succeeded, but actually * applying the patch failed! * Failed Patch: perl-tk-800.025-dirtarget.patch! * * Include in your bugreport the contents of: * * /opt/portage/portage/perl-tk-800.025-r1/temp/perl-tk-800.025-dirtarget.patch-400.out !!! ERROR: dev-perl/perl-tk-800.025-r1 failed. !!! Function epatch, Line 354, Exitcode 0 !!! Failed Patch: perl-tk-800.025-dirtarget.patch! And the referenced output file: ***** perl-tk-800.025-dirtarget.patch ***** =========================================== PATCH COMMAND: patch -p0 < /usr/portage/dev-perl/perl-tk/files/perl-tk-800.025-dirtarget.patch =========================================== Get file pTk/Makefile.PL from Perforce with lock? [y] patching file pTk/Makefile.PL =========================================== ACTUALLY APPLYING perl-tk-800.025-dirtarget.patch... =========================================== Get file pTk/Makefile.PL from Perforce with lock? [y] Path '/opt/portage/portage/perl-tk-800.025-r1/work/Tk800.025/pTk/Makefile.PL' is not under client's root '/home/scotte/p4'. patch: **** Can't get file pTk/Makefile.PL from Perforce As you can see, for some reason it is attempting access Perforce, even though that has nothing to do with this at all! I can emerge dev-perl/perl-tk-800.025 just fine, and have not had this problem in emerging several hundred other packages, even though the ebuild for this doesn't look particularly strange... I moved the p4 binaries out of the way, which resulted in: ***** perl-tk-800.025-dirtarget.patch ***** =========================================== PATCH COMMAND: patch -p0 < /usr/portage/dev-perl/perl-tk/files/perl-tk-800.025-dirtarget.patch =========================================== Get file pTk/Makefile.PL from Perforce with lock? [y] patching file pTk/Makefile.PL =========================================== ACTUALLY APPLYING perl-tk-800.025-dirtarget.patch... =========================================== Get file pTk/Makefile.PL from Perforce with lock? [y] sh: line 1: p4: command not found patch: **** Can't get file pTk/Makefile.PL from Perforce r
Which variables have you reset in your make.conf? It almost looks like there is a conflict between what you've set as your PORTAGE_* vars (I see that it is running the ebuild out of /opt/portage/protage, and that it is attempting to build in /home/scotte/p4).
Interesting... The problem has gone away. The ebuild does not appear to have been updated (Jan 10), and my make.conf has not changed (posted here), nor my use of perforce, but somehow it magically built OK. OK to close this, I guess. Bizzare!
This is odd indeed. I'm going to tentatively close this bug. Please reopen if the problem resurfaces. Thanks for the report.
