android-sdk-update-manager-3 calls "enewgroup android" in pkg_preinst(). It also runs "chgrp android <list>" in src_install(). pkg_preinst() runs after src_install() with the result that the android is not created yet wehn needed and chgrp fails. The installed dirs {platforms,add-ons,docs,temp} are then owned by the root group and users cannot update their sdk using the android GUI tool. "chgrp android <list>" should probably be called early in src_install(). Alternatively, drop the android group entirely and elog the user that SDK updates must be one as root. Reproducible: Always Steps to Reproduce: 1. emerge -avC android-sdk-update-manager 2. groupdel android 3. emerge -av android-sdk-update-manager 4. gpasswd -a <USER> android 5. run android as user Actual Results: SDK updates fail Expected Results: SDK updates should succeed Snipped output from emerge showing echo's inserted in each ebuild phase: >>> Install android-sdk-update-manager-3 into /var/tmp/portage/dev-util/android-sdk-update-manager-3/image/ category dev-util src_install() running now chgrp: invalid group: `android' >>> Completed installing android-sdk-update-manager-3 into /var/tmp/portage/dev-util/android-sdk-update-manager-3/image/ >>> Installing (1 of 1) dev-util/android-sdk-update-manager-3 * checking 57 files for package collisions pkg_preinst() running now * Adding group 'android' to your system ... * - Groupid: next available
Fixed in -r1. Bug filed for devmanual. :)
