Emerging less-457 ran into file locking contention. Moved the files and emerged smooth. Posting files for QA purposes. Forgive typos, imputing longhand /etc/env.d.70less /usr/bin/code2color /usr/bin/less /usr/bin/lessecho /usr/bin/lesskey /usr/bin/lesspipe /usr/lib/debug/usr/bin/less.debug /usr/lib/debug/usr/bin/lessecho.debug /usr/lib/debug/usr/bin/lesskey.debug /usr/share/doc/less-457.NEWS.bz2 /usr/share/doc/less-457.README.bz2 /usr/share/doc/less-457.README.Gentoo.bz2 /usr/share/man/man1/less.1.bz2 /usr/share/man/man1/lessecho.1.bz2 /usr/share/man/man1/lesskey.1.bz2 Reproducible: Always Was able to move the files manually and emerge successfully
1) Please post your `emerge --info' in a comment. 2) Please attach the entire (failing?) build log to this bug report.
Sorry, I didn't save it, just wrote the locked files down. The build didn't fail, it was only on the install portion where it in countered the locked files. Would you like a completed build log? Apologizes
It isn't even clear what you mean by locked files.
(In reply to comment #3) > It isn't even clear what you mean by locked files. Am I that vague? When the install portion executes after a complete build emerge moves the complete build from sandbox to the actual location(s) in /etc & /usr. Those files I specified were 'LOCKED' and were held read-only. Thus the install was incomplete and portage complained listing the files I posted below as owned by other installations. * PLEASE FILE A QA NOTICE IF YOU CAN CONFIRM THAT THOSE FILES ARE NOT OWNED BY ANOTHER PROGRAM. You've never seen file contention before? QA - Quality assurance... ? I was able to remove posted files and emerge the less-457 ebuild with out any error. Figured it was just errata, easy fix, something in the ebuild syntax. My system is stock and I didn't rice. So it's legitimate. ? - is there a qa.gentoo.org - ? - Should I be posting this there - ? If so then my apologizes
