Surely portage developers waste many precious neurotransmitters and man-microseconds every day ignoring this error: /usr/bin/install -c -m 644 -o root -g root -t /var/tmp/portage/sys-apps/portage-2.2.01.20389/image//usr/lib/portage/pym/. ././*.py /usr/bin/install: cannot stat `././*.py': No such file or directory Nothing is wrong so there is no need for an error message. Secondly: as this make-target code walks the directories in $S/pym, only errors on the last iteration bubble up and cause a failure (perhaps this disconnect evolved around the limitation that an error always occurred on the first iteration). At least, I'm pretty sure that's right, and also pretty sure this fixes it -- tbh I only tested the non-failing case. Reproducible: Always Steps to Reproduce: 1. ebuild portage-recent.ebuild install Actual Results: "/usr/bin/install: cannot stat `././*.py': No such file or directory" Expected Results: "" Non-beautiful, non-atrocious, patch enclosed (pending bug creation). I promise not to be offended if you don't merge it.
Created attachment 308739 [details, diff] don't generate pointless error message; do handle errors correctly
Looks like the patch is supposed to apply to an older version of the prefix branch, but doesn't apply now.
oh :( sorry about that, I'll port to git if applicable (or close).
Applies to 85b951b73f528a3c97156a7644d7eac16ed835c0 (prefix/HEAD) in git://git.overlays.gentoo.org/proj/portage.git... should I be looking at CVS or something? Sorry for confusion.
Should I assign to Gentoo/Alt Product? Bugzilla shows a slightly ominous-looking confirmation dialog that I don't understand when I try :)
(In reply to comment #4) > Applies to 85b951b73f528a3c97156a7644d7eac16ed835c0 (prefix/HEAD) in > git://git.overlays.gentoo.org/proj/portage.git... should I be looking at CVS > or something? > > Sorry for confusion. Nope, that is the right branch/authoritative code, thanks.
http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commitdiff;h=4025638c00de5e9e21ef419a5b107141525283ca
Next portage release should be more silent. I decided to go for a different approach, since the case of no existing python files should not exist.
this is in 2.2.01.20757