glen martin wrote:
> I'm still puzzled, though, that I can call chown by hand and it
> works fine. That
> is, I type
> chown portage:portage /tmp/foo
> which works. but the emerge log says
> /usr/lib/portage/bin/ebuild.sh: line 1882: 16369 Segmentation
> fault chown portage:portage "${T}/environment" >&/dev/null
> doesn't work.
No idea, but strange things happen in Portage's sandbox.
(By the way, ">&/dev/null" is a pasto? Here it is "&>".)
But have you tried updating the kernel? See the thread on "random
emerge failures". Yours aren't random, but worth trying an update.
And if that doesn't help, how about using a default profile?
> I'm starting to wonder about other possibilities:
> 1) Could the error report be erroneous? That is, not chmod/chown
> at all? Perhaps line number mismatching?
Maybe. Have you looked at /usr/lib/portage/bin/ebuild.sh?
Because here the chown is on line 1880. Portage 2.0.51.19.
Perhaps try reemerging portage?
Benno
--
[email protected] mailing list
