--- Begin Message ---
Subject: |
Unable to reconfigure: "suspicious ownership or permission" and "guix system: error: build failed" |
Date: |
Wed, 4 May 2016 21:02:39 +0200 |
Hi!
When I try to reconfigure my Guix SD system from a git checkout (e.g. from
commit 8c15e084fe5fd9492f61128c9995bb1741d225e3) the following happens:
> [...]
> grafting '/gnu/store/pm1043sf438anc08xzw2sgc89rrjiir2-clutter-1.24.2'
> -> '/gnu/store/72cp43sqala9j0hn3fsy5bcsc8whgjqb-clutter-1.24.2'...
> suspicious ownership or permission on
> `/gnu/store/72cp43sqala9j0hn3fsy5bcsc8whgjqb-clutter-1.24.2';
> rejecting
> this build output cannot build derivation
> `/gnu/store/wq8g2g5pnncyv0dsw1kc1ibrib5gsa0a-gnome-control-center-3.18.2.drv':
> 1 dependencies couldn't be built cannot build derivation
> `/gnu/store/xcjpfvjl7xvwd917lf0f6vlk634wwpbp-gnome-shell-3.18.3.drv':
> 1
> dependencies couldn't be built cannot build derivation
> `/gnu/store/3gih89s3bh8hfjhvf4fsim6sz1pyfkvn-totem-3.18.1.drv': 1
> dependencies couldn't be built cannot build derivation
> `/gnu/store/wx3s477dhp9yvgjpsk964bzg378mhivp-profile.drv': 1
> dependencies couldn't be built cannot build derivation
> `/gnu/store/cisc729wjyw5ichh8xr4gjhk9gvjzsxw-system.drv': 1
> dependencies couldn't be built guix system: error: build failed: build
> of `/gnu/store/cisc729wjyw5ichh8xr4gjhk9gvjzsxw-system.drv' failed
This is the output of `ls -l /gnu/store | grep rwx`:
-r--r--r-- 2 root root 3415 1 jan 1970
2apcn0jh6hd3vcn85bq49dj9r41rwxbz-grilo-0.2.14-guile-builder
-r--r--r-- 2 root root 1002 1 jan 1970
2hv3lmx86vg3k6qdifmhzfdgnjhrwxq7-bash43-022.drv
-r--r--r-- 2 root root 4353 1 jan 1970
2x4792z417ynwrwx2f510gszmbqcmc63-python-pygobject-3.18.0.drv
-r--r--r-- 2 root guixbuild 4831 1 jan 1970
54f2qgyz20pkhws2k2psk7frwxp96x6y-shepherd.conf
dr-xr-xr-x 6 root root 4096 1 jan 1970
5hazsfjrwx39ikzy6s5a19mwad9h2gzw-tumbler-0.1.31/
-r--r--r-- 2 root root 2681 1 jan 1970
5i3z9vllkxnssps3ynl2mh446k43crwx-isl-0.11.1-guile-builder
-r--r--r-- 2 root root 3343 1 jan 1970
6qadrdrwxdvqxp9b1ry440702cz0qznp-libxdamage-1.1.4.drv
drwxrwxrwx 5 guixbuilder01 guixbuild 4096 4 maj 20.27
72cp43sqala9j0hn3fsy5bcsc8whgjqb-clutter-1.24.2/
-r--r--r-- 2 root root 1068 1 jan 1970
c7xs8wfdpwrnhrwx2bhln3pgzd7cg2qx-gnome-bluetooth-3.18.1.tar.xz.drv
-r--r--r-- 2 root root 3572 1 jan 1970
hsaqbkh9x95lpv0gyrwx4c8ccz59mv57-gdk-pixbuf-2.32.3.drv
-r--r--r-- 2 root root 3038 1 jan 1970
isc838rhgavs4vxmlcynzgcgr2prwxc5-libxkbfile-1.0.9.drv
dr-xr-xr-x 4 root guixbuild 4096 1 jan 1970
j8pbczvgni7w0rlwnq8rwxphx57gd43k-gtk-xfce-engine-2.10.1/
-r--r--r-- 2 root root 1821 1 jan 1970
mafg4xrwxdar8fd2fgv1ls7mmnhc9fap-expat-2.1.0.drv
-r--r--r-- 2 root root 1040 1 jan 1970
mwcrwxjwb3li9yb8fj2w1v023pky7j6p-fontsproto-2.1.3.tar.bz2.drv
dr-xr-xr-x 6 root root 4096 1 jan 1970
nszhvmlvhsfvky43sk3y2f5rpazrwxhb-ntp-4.2.8p6/
-r--r--r-- 2 root root 10387 1 jan 1970
p2rwxj55il5d0ywnnbb5953g1kb3miwp-gtk-icon-themes-builder
-r--r--r-- 2 root root 2325 1 jan 1970
w9znxd69rwx5n9zla2jgislpk5hqbw24-file-5.25.drv
Output of `ls -la /gnu/store/72cp43sqala9j0hn3fsy5bcsc8whgjqb-clutter-1.24.2`:
totalt 1652
drwxrwxrwx 5 guixbuilder01 guixbuild 4096 4 maj 20.27 ./
drwxrwxr-t 2329 root guixbuild 1671168 4 maj 20.27 ../
drwxrwxrwx 3 guixbuilder01 guixbuild 4096 4 maj 20.27 include/
drwxrwxrwx 4 guixbuilder01 guixbuild 4096 4 maj 20.27 lib/
drwxrwxrwx 4 guixbuilder01 guixbuild 4096 4 maj 20.27 share/
Any ideas?
Best regards,
Albin
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#22954: Suspicious ownership or permission on harfbuzz-1.0.6-bin |
Date: |
Mon, 10 Oct 2016 22:21:38 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) |
Hello!
Jeffrey Serio <address@hidden> skribis:
> The build failed with the error message "Suspicious ownership or
> permission on /gnu/store/...-harfbuzz-1.0.6-bin".
I’m happy to report that this is finally fixed!
Commit d72267863382041b84a9712eea354882be72ef55.
The root problem was that libguile’s ‘mkdir’ was playing dirty tricks
with umask(2), as explained at <http://bugs.gnu.org/24659>. Our
multithreaded grafting code triggered the issue described in that bug.
Thanks,
Ludo’.
--- End Message ---