Bug #192341 - When the chflags command does not exit successfully,
authorZac Medico <zmedico@gentoo.org>
Wed, 26 Sep 2007 17:03:18 +0000 (17:03 -0000)
committerZac Medico <zmedico@gentoo.org>
Wed, 26 Sep 2007 17:03:18 +0000 (17:03 -0000)
commit432d0a083f8e8ba27687f177393cbb38bbc7d54d
tree397e11d4b200b2a045039fd1826876a7c111f527
parentc90c13bbbb1f6a4d7262c922b1413dadbf09eb5b
Bug #192341 - When the chflags command does not exit successfully,
try to generate an informative error. First, use stat or lstat to
try and generate an ENOENT error.  It the path exists, verify that
the chflags binary exists and raise CommandNotFound if necessary.
Finally, simply generate an EPERM OSError with the output of the
command since we're not sure exactly why it failed or what the
real errno was.

svn path=/main/trunk/; revision=7834
pym/portage/__init__.py