[gentoo-user] android-sdk-update-manager, wrong permissions?
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
Re: [gentoo-user] android-sdk-update-manager, wrong permissions?
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.
Re: [gentoo-user] android-sdk-update-manager, wrong permissions?
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
[gentoo-user] Android SDK
I noticed there have been a few Android SDK's in portage now for a while - originally android-sdk, now android-sdk-update-manager (http://packages.gentoo.org/package/dev-util/android-sdk-update-manager). I know there is a bug on it - http://bugs.gentoo.org/show_bug.cgi?id=320407 - but that's the only one I can find. Anyone have an idea on when some version might go stable? There's 7 versions in portage and all are testing; the first (version 3) goes back to November 2009. TIA, Ben
Re: [gentoo-user] Android SDK
Apparently, though unproven, at 00:49 on Friday 08 October 2010, BRM did opine thusly: I noticed there have been a few Android SDK's in portage now for a while - originally android-sdk, now android-sdk-update-manager (http://packages.gentoo.org/package/dev-util/android-sdk-update-manager). I know there is a bug on it - http://bugs.gentoo.org/show_bug.cgi?id=320407 - but that's the only one I can find. Anyone have an idea on when some version might go stable? There's 7 versions in portage and all are testing; the first (version 3) goes back to November 2009. You should file a stabilisation request at b.g.o. they are likely not in testing because there's something wrong with them, they are probably in testing because nobody has bothered bumping them to stable. However, considering the speed that Google are releasing Android versions, I think that the usual gentoo arch/~arch methodology is a bit of a joke in this case. If you didn't use the ebuilds, you'd be installing the latest sdk from google anyway, right? All the ebuild does is unpack a binary archive into /opt, nothing magic there, no real compelling need to wait for a stable version. And it doesn't need any ~arch deps either I say just be done with it, keyword the damn thing and install it. -- alan dot mckinnon at gmail dot com
