pre-upload: fix uprev checks with new packages & symlink renames

Handle a few more edge cases:
 - If we're creating a package from scratch, an uprev is not needed.
 - If the user has renamed the existing symlink and modified files/,
   then they don't need to do anything else.
 - If files/ are modified, but the ebuilds haven't been updated, throw
   an error so the uprev is forced.

TEST=created a CL that added an ebuild -> was not rejected
TEST=created a CL that modified an ebuild -> was rejected

Change-Id: I38ea5051d14fd2b68ea04ee97300c40cf604558f
Reviewed-by: Doug Anderson <>
Tested-by: Mike Frysinger <>
2 files changed