1 |
On 28/05/2013 21:11, codekick wrote: |
2 |
> On Tue, 28 May 2013 20:49:17 +0200 |
3 |
> fruktopus <fruktopus@×××××.com> wrote: |
4 |
> |
5 |
>> Hi, |
6 |
>> |
7 |
>> i just emerged dev-util/android-sdk-update-manager-22 (~x86) |
8 |
>> if I start it, it complains about not being able to create |
9 |
>> |
10 |
>> /opt/android-sdk-update-manager/build-tools |
11 |
>> |
12 |
>> after I created this directory similar problems followed. On a second |
13 |
>> try I changed |
14 |
>> /opt/android-sdk-update-manager/ 's group form 'root' to 'android' and |
15 |
>> made it group writable |
16 |
>> |
17 |
>> drwxrwxr-x 13 root android 4096 28. Mai 12:20 |
18 |
>> android-sdk-update-manager |
19 |
>> |
20 |
>> this solved all problems. Should this be reported as a bug or did i |
21 |
>> screwed it up somehow? |
22 |
>> |
23 |
>> Thanks, frukto |
24 |
>> |
25 |
>> |
26 |
> |
27 |
> I confirm, i had the same issue with 21.1. And i think this is a bug. |
28 |
> |
29 |
|
30 |
|
31 |
It's probably a bug, you should report it at b.g.o. |
32 |
|
33 |
I had the same problem years ago (back when the first Android phone - |
34 |
the HTC G1 - was all the rage...) The root problem is that Google |
35 |
assumes the sdk will be run in from home directory, not /opt, so the |
36 |
ebuild must take care of proper owner and perms. It's an easy thing for |
37 |
a dv to slip up on. |
38 |
|
39 |
|
40 |
|
41 |
-- |
42 |
Alan McKinnon |
43 |
alan.mckinnon@×××××.com |