On 28/05/2013 21:11, codekick wrote: > On Tue, 28 May 2013 20:49:17 +0200 > fruktopus <frukto...@gmail.com> wrote: > >> Hi, >> >> i just emerged dev-util/android-sdk-update-manager-22 (~x86) >> if I start it, it complains about not being able to create >> >> /opt/android-sdk-update-manager/build-tools >> >> after I created this directory similar problems followed. On a second >> try I changed >> /opt/android-sdk-update-manager/ 's group form 'root' to 'android' and >> made it group writable >> >> drwxrwxr-x 13 root android 4096 28. Mai 12:20 >> android-sdk-update-manager >> >> this solved all problems. Should this be reported as a bug or did i >> screwed it up somehow? >> >> Thanks, frukto >> >> > > I confirm, i had the same issue with 21.1. And i think this is a bug. >
It's probably a bug, you should report it at b.g.o. I had the same problem years ago (back when the first Android phone - the HTC G1 - was all the rage...) The root problem is that Google assumes the sdk will be run in from home directory, not /opt, so the ebuild must take care of proper owner and perms. It's an easy thing for a dv to slip up on. -- Alan McKinnon alan.mckin...@gmail.com
