public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Rafael Barrera Oro" <borafael@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] can not emerge KDE-META (ACCESS DENIED chmod: /usr/share/config)
Date: Fri, 7 Nov 2008 09:39:40 -0300	[thread overview]
Message-ID: <a964044f0811070439sa238b2cl7e94e7efc5b2fe2b@mail.gmail.com> (raw)
In-Reply-To: <a964044f0811030741k4d22c47dl4c2eff9d2c52ddfb@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 989 bytes --]

There, i submited a bug:

http://bugs.gentoo.org/show_bug.cgi?id=245420

This is the first bug i submit, it feels good...

2008/11/3 Rafael Barrera Oro <borafael@gmail.com>

> Will do
>
> thanks for the explanation
>
> 2008/11/3 Alan McKinnon <alan.mckinnon@gmail.com>
>
> On Monday 03 November 2008 17:31:59 Rafael Barrera Oro wrote:
>> > Whenever i try to emerge KDE-META-4.1.2-r1, everything goes fine until
>> the
>> > process suddenly dies with the following epitaph:
>> >
>> > ACCESS DENIED  chmod:     /usr/share/config
>> > chmod: changing permissions of `/usr/share/config': Permission denied
>>
>> You are running emerge in a sandbox and the ebuild is trying to chmod a
>> directory with these permissions:
>>
>>  $ ls -ald /usr/share/config
>> drwxr-xr-x 4 root root 208 Oct 23 15:39 /usr/share/config
>>
>> which of course will never work. This is a bug, so report it at bgo unless
>> someone else has already done so.
>>
>>
>> --
>> alan dot mckinnon at gmail dot com
>>
>>
>

[-- Attachment #2: Type: text/html, Size: 1739 bytes --]

      reply	other threads:[~2008-11-07 12:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-03 15:31 [gentoo-user] can not emerge KDE-META (ACCESS DENIED chmod: /usr/share/config) Rafael Barrera Oro
2008-11-03 15:37 ` Alan McKinnon
2008-11-03 15:41   ` Rafael Barrera Oro
2008-11-07 12:39     ` Rafael Barrera Oro [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=a964044f0811070439sa238b2cl7e94e7efc5b2fe2b@mail.gmail.com \
    --to=borafael@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