Summary: | dev-lang/vala-0.42.5 - src_prepare(): ACCESS DENIED: open_wr: /.git/index.lock | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Drunkard Zhang <gongfan193> |
Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | flow |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build.log |
Description
Drunkard Zhang
2019-02-12 03:51:51 UTC
Created attachment 564866 [details]
build.log
vala is like the only package where I didn't get around to reverting unauthorized commit that added `export GIT_CEILING_DIRECTORIES="${WORKDIR}"` to supposedly fix this. So it's quite surprising that you get issues with this now. Either way, if you have a /.git, then you get to deal with the results. In this case you'll need to add allowance for it in sandbox configuration. Also, don't do .git at rootfs... *** This bug has been marked as a duplicate of bug 483134 *** Using git sync for portage and vala refuses to compile now >>> Preparing source in /usr/portage/tmp/portage/dev-lang/vala-0.42.7/work/vala-0.42.7 ... * Applying 0.40-Allow-disabling-the-build-of-valadoc.patch ... [ ok ] * Applying 0.40-valadoc-doclets-data-parallel-installable.patch ... [ ok ] * Disabling deprecation warnings ... [ ok ] * ACCESS DENIED: open_wr: /usr/portage/.git/index.lock * Running eautoreconf in '/usr/portage/tmp/portage/dev-lang/vala-0.42.7/work/vala-0.42.7' ... * Running libtoolize --install --copy --force --automake ... * ACCESS DENIED: open_wr: /usr/portage/.git/index.lock * ACCESS DENIED: open_wr: /usr/portage/.git/index.lock * ACCESS DENIED: open_wr: /usr/portage/.git/index.lock * ACCESS DENIED: open_wr: /usr/portage/.git/index.lock * ACCESS DENIED: open_wr: /usr/portage/.git/index.lock * ACCESS DENIED: open_wr: /usr/portage/.git/index.lock * ACCESS DENIED: open_wr: /usr/portage/.git/index.lock [ ok ] * Running aclocal --install -I m4 ... * ACCESS DENIED: open_wr: /usr/portage/.git/index.lock * ACCESS DENIED: open_wr: /usr/portage/.git/index.lock * ACCESS DENIED: open_wr: /usr/portage/.git/index.lock [ ok ] * ACCESS DENIED: open_wr: /usr/portage/.git/index.lock * Running autoconf --force ... * ACCESS DENIED: open_wr: /usr/portage/.git/index.lock [ ok ] * Running autoheader ... [ ok ] * Running automake --add-missing --copy --force-missing ... * ACCESS DENIED: open_wr: /usr/portage/.git/index.lock [ ok ] * Running elibtoolize in: vala-0.42.7/ * Running elibtoolize in: vala-0.42.7/build-aux/ * Applying portage/1.2.0 patch ... * Applying sed/1.5.6 patch ... * Applying as-needed/2.4.3 patch ... >>> Source prepared. * --------------------------- ACCESS VIOLATION SUMMARY --------------------------- * LOG FILE: "/var/log/sandbox/sandbox-4.log" * VERSION 1.0 FORMAT: F - Function called FORMAT: S - Access Status FORMAT: P - Path as passed to function FORMAT: A - Absolute Path (not canonical) FORMAT: R - Canonical Path FORMAT: C - Command Line Caused due to the tmpdir being under the same directory tree? A parent directory of PORTAGE_TMPDIR having a .git/ will trigger this issue, yes. Don't do that or configure sandbox to not trip up on it. For future readers, vala will not build if you have repos.conf configured to use git location = /usr/portage sync-type = git make.conf with PORTAGE_TMPDIR set under the same directory tree PORTAGE_TMPDIR=/usr/portage/tmp |