Emerging dev-lang/vala-0.14.2 (and possible other versions too) failes with a sandbox violation when git is installed and the directory /.git exists Reproducible: Always
Created attachment 357504 [details] build.log
Created attachment 357506 [details] emerge --info
Try with 0.20 slot
Created attachment 358274 [details] build.log with vala-0.20.1 Same problem with vala:0.20
Maybe this comes from build-aux/git-version-gen, but I don't know why it's being called. Maybe dropping its reference in configure.ac (in the top line), and running eautoreconf after that could help
(In reply to Pacho Ramos from comment #5) > Maybe this comes from build-aux/git-version-gen, but I don't know why it's > being called. Maybe dropping its reference in configure.ac (in the top > line), and running eautoreconf after that could help Did you try dropping that reference?
Created attachment 369762 [details, diff] ebuild and external patch (In reply to Pacho Ramos from comment #6) > Did you try dropping that reference? did not fix the problem
Created attachment 369764 [details, diff] ebuild patch just distract the build system
I see no upstream report yet, could you guys do one and paste the URL here ? It will probably have better chance to get some interest.
(In reply to Michael Weber from comment #7) > Created attachment 369762 [details, diff] [details, diff] > ebuild and external patch > > (In reply to Pacho Ramos from comment #6) > > Did you try dropping that reference? > > did not fix the problem Does this patch work then? Also, is it still needed for 0.26.2? Was this reported? Thanks :)
I can confirm that this bug is still present in version 0.26.2 (removing /.git compiles successfully) The patches didn't get rid of the sandbox violation, though I had to modify them since they were made specifically for an old version of the ebuild (0.22.1)
*** Bug 560308 has been marked as a duplicate of this bug. ***
*** Bug 614728 has been marked as a duplicate of this bug. ***
For what is worth I just hit this with dev-lang/vala-0.36.7. The only way to install the package was by exporting FEATURES="-sandbox -usersandbox" before invoking emerge.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=aa48765f6497dd0443a7bfb747386e7c15e80d90 commit aa48765f6497dd0443a7bfb747386e7c15e80d90 Author: Michael Weber <xmw@gentoo.org> AuthorDate: 2018-01-28 19:49:10 +0000 Commit: Michael Weber <xmw@gentoo.org> CommitDate: 2018-01-28 19:49:28 +0000 dev-lang/vala: Limit errornous git invocation to ${WORKDIR} by exporting GIT_CEILING_DIRECTORIES. Bug: https://bugs.gentoo.org/558556 Closes: https://bugs.gentoo.org/483134 Package-Manager: Portage-2.3.20, Repoman-2.3.6 dev-lang/vala/vala-0.32.1.ebuild | 5 ++++- dev-lang/vala/vala-0.34.9.ebuild | 5 ++++- dev-lang/vala/vala-0.36.7.ebuild | 3 +++ 3 files changed, 11 insertions(+), 2 deletions(-)
Hacks without upstream reports don't constitute a fix.
*** Bug 677772 has been marked as a duplicate of this bug. ***
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9d336568e1ba9cfb5ee04fd70cabc63047377576 commit 9d336568e1ba9cfb5ee04fd70cabc63047377576 Author: Mart Raudsepp <leio@gentoo.org> AuthorDate: 2019-02-16 16:24:04 +0000 Commit: Mart Raudsepp <leio@gentoo.org> CommitDate: 2019-02-16 16:24:49 +0000 dev-lang/vala: remove git ceiling dir hack This was added without maintainer authorization, and doesn't even seem to work these days. If you have a /.git/ or .git/ somewhere between WORKDIR and /, you get to deal with it yourself (or just don't do such odd things). Sorry. Bug: https://bugs.gentoo.org/483134 Package-Manager: Portage-2.3.52, Repoman-2.3.12 Signed-off-by: Mart Raudsepp <leio@gentoo.org> dev-lang/vala/vala-0.32.1.ebuild | 3 --- dev-lang/vala/vala-0.34.16.ebuild | 3 --- dev-lang/vala/vala-0.36.15.ebuild | 3 --- dev-lang/vala/vala-0.36.17.ebuild | 5 +---- dev-lang/vala/vala-0.40.13.ebuild | 3 --- dev-lang/vala/vala-0.42.5.ebuild | 3 --- 6 files changed, 1 insertion(+), 19 deletions(-)
*** Bug 707922 has been marked as a duplicate of this bug. ***
