Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 537124 - sys-apps/paludis: paludisbuild doesn't have write access to /var/log/sandbox
Summary: sys-apps/paludis: paludisbuild doesn't have write access to /var/log/sandbox
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Michał Górny
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-20 12:00 UTC by cmuelle8
Modified: 2018-09-19 11:42 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description cmuelle8 2015-01-20 12:00:28 UTC
SYMPTOM/TESTCASE:
sudo -u paludisbuild sandbox bash
paludisbuild@coltrane /etc/sandbox.d $ echo 1 > /proc/mtrr
 * ACCESS DENIED:  open_wr:      /proc/mtrr
 * ISE:write_logfile: unable to append logfile: /var/log/sandbox/sandbox-16870.log
 * ../../sandbox-2.6/libsandbox/libsandbox.c:check_syscall():879: failure (Ungültiger Dateideskriptor):
 * ISE:
	abs_path: /proc/mtrr
	res_path: /proc/mtrr
/usr/lib64/libsandbox.so(+0xa252)[0x7f863fa76252]
/usr/lib64/libsandbox.so(+0xa368)[0x7f863fa76368]
/usr/lib64/libsandbox.so(+0x46e3)[0x7f863fa706e3]
/usr/lib64/libsandbox.so(open+0x6c)[0x7f863fa74bcc]
bash[0x47a552]
bash(do_redirections+0x52)[0x450ab2]
bash[0x451abd]
bash(execute_command_internal+0xc5e)[0x452c7e]
bash(execute_command+0x4e)[0x45450e]
bash(reader_loop+0x202)[0x479602]
/proc/16871/cmdline: bash 

Sandboxed process killed by signal: Aborted


CURE:
If paludis is used, packages are compiled using an unprivileged user ("paludisbuild").  This user NEEDS write access to /var/log/sandbox

If the sandbox cannot write log files, it will be aborted together with the sanboxed process, effectively failing the packages install.

Reproducible: Always
Comment 1 SpanKY gentoo-dev 2015-02-21 19:55:42 UTC
the sandbox ebuild already grants write access to the portage group.  if that isn't sufficient, you can set the SANDBOX_LOG env var to point somewhere else.
Comment 2 cmuelle8 2015-02-22 17:38:46 UTC
(In reply to SpanKY from comment #1)
> the sandbox ebuild already grants write access to the portage group.  if
> that isn't sufficient, you can set the SANDBOX_LOG env var to point
> somewhere else.

This is not enough.  Either gentoo supports multiple PM, or it does not.  If it does not, then drop alternative PM from the main tree.  To tinker around with it 'until it works' is no solution.  These are integral system parts that need to work 'out of the box'.

Also, since sandbox is not exactly a part of PM, than why should the location to put its logfiles into differ from one to the next?  This seems very artificial.  

You may have a point however in suggesting that this ought to be fixed by each PM-ebuild individually, and not by the sandbox ebuild (from a modular pov it's not quite understandable why it prefers a specific PM in the first place).
Comment 3 Mikle Kolyada (RETIRED) archtester Gentoo Infrastructure gentoo-dev Security 2018-09-19 11:42:06 UTC
Paludis has been removed from the tee.