From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] android-sdk-update-manager, wrong permissions?
Date: Tue, 28 May 2013 23:19:30 +0200 [thread overview]
Message-ID: <51A51F62.1030200@gmail.com> (raw)
In-Reply-To: <20130529011142.3da41748@codekick-hp>
On 28/05/2013 21:11, codekick wrote:
> On Tue, 28 May 2013 20:49:17 +0200
> fruktopus <fruktopus@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.mckinnon@gmail.com
prev parent reply other threads:[~2013-05-28 21:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 18:49 [gentoo-user] android-sdk-update-manager, wrong permissions? fruktopus
2013-05-28 19:11 ` codekick
2013-05-28 21:19 ` Alan McKinnon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51A51F62.1030200@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox