From: "Rafael Barrera Oro" <borafael@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] can not emerge KDE-META (ACCESS DENIED chmod: /usr/share/config)
Date: Mon, 3 Nov 2008 12:31:59 -0300 [thread overview]
Message-ID: <a964044f0811030731y6284ca41jf92de00174c3efa0@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2768 bytes --]
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
First i thought it was a portage bug so i did an emerge --sync and found out
that there was an update available, nevertheless, the problem was not fixed.
Some more output:
-- Installing
/var/tmp/portage/kde-base/kdelibs-4.1.2-r1/image/usr/share/doc/HTML/en/sonnet/index.docbook
-- Installing
/var/tmp/portage/kde-base/kdelibs-4.1.2-r1/image/usr/share/man/man7/qtoptions.7
-- Installing
/var/tmp/portage/kde-base/kdelibs-4.1.2-r1/image/usr/share/man/man1/kde4-config.1
ACCESS DENIED chmod: /usr/share/config
chmod: changing permissions of `/usr/share/config': Permission denied
>>> Completed installing kdelibs-4.1.2-r1 into
/var/tmp/portage/kde-base/kdelibs-4.1.2-r1/image/
--------------------------- ACCESS VIOLATION SUMMARY
---------------------------
LOG FILE = "/var/log/sandbox/sandbox-8733.log"
chmod: /usr/share/config
--------------------------------------------------------------------------------
>>> Failed to emerge kde-base/kdelibs-4.1.2-r1, Log file:
>>> '/var/tmp/portage/kde-base/kdelibs-4.1.2-r1/temp/build.log'
* GNU info directory index is up-to-date.
* IMPORTANT: 2 config files in '/etc' need updating.
* See the CONFIGURATION FILES section of the emerge
* man page to learn how to update config files.
!!! existing preserved libs:
>>> package: app-pda/libopensync-0.36
* - /usr/lib64/libopensync.so.0
* - /usr/lib64/libopensync.so.0.0.0
* used by /usr/kde/3.5/bin/kitchensync (kde-base/kitchensync-3.5.9)
* used by /usr/kde/3.5/lib64/kde3/libkitchensyncpart.so
(kde-base/kitchensync-3.5.9)
* used by /usr/kde/3.5/lib64/libkitchensync.so.0.0.0
(kde-base/kitchensync-3.5.9)
* used by 3 other files
* - /usr/lib64/libosengine.so.0
* - /usr/lib64/libosengine.so.0.0.0
* used by /usr/kde/3.5/bin/kitchensync (kde-base/kitchensync-3.5.9)
* used by /usr/kde/3.5/lib64/kde3/libkitchensyncpart.so
(kde-base/kitchensync-3.5.9)
* used by /usr/kde/3.5/lib64/libkitchensync.so.0.0.0
(kde-base/kitchensync-3.5.9)
* used by /usr/kde/3.5/lib64/libqopensync.so.0.0.0
(kde-base/kitchensync-3.5.9)
>>> package: sys-fs/udev-130-r1
* - /lib64/libvolume_id.so.0
* - /lib64/libvolume_id.so.0.75.0
* used by /usr/libexec/hald-probe-storage (sys-apps/hal-0.5.9-r1)
* used by /usr/libexec/hald-probe-volume (sys-apps/hal-0.5.9-r1)
Use emerge @preserved-rebuild to rebuild packages using these libraries
Since the emerge was not completed i do not dare to deal with the preserved
libraries
As usual, thanks in advance
Humbly
Rafael
[-- Attachment #2: Type: text/html, Size: 3503 bytes --]
next reply other threads:[~2008-11-03 15:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 15:31 Rafael Barrera Oro [this message]
2008-11-03 15:37 ` [gentoo-user] can not emerge KDE-META (ACCESS DENIED chmod: /usr/share/config) Alan McKinnon
2008-11-03 15:41 ` Rafael Barrera Oro
2008-11-07 12:39 ` Rafael Barrera Oro
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=a964044f0811030731y6284ca41jf92de00174c3efa0@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