)[0x2b49730e39e0]
/proc/13606/cmdline:
../../coreconf/nsinstall/Linux2.6_x86_64_x86_64-pc-linux-gnu-gcc_glibc_PTH_64_OPT.OBJ/nsinstall
-D ../../dist public dbm
I would try it with sandbox disabled.
FEATURES=-*sandbox* your emerge command here
It may work. Certainly worth a shot I guess.
Dale
:-) :-)
are
(supposed to) play in the same sandbox. This means the behaviors of
different packages and their dependencies and interactions with each
other are somewhat predictable, and when problems occur, they are easier
to debug and solve because everyone's playing in the same sandbox.
When you
tries to write files outside the sandbox
which is not allowed.
Tamer you can try if pycrypto installs fine with setuptools 0.7.3. If
yes you should open a bug about the pycrypto-2.6-r2 sandbox issue
with setuptools 0.6.30-r1
--
Regards
Daniel
of having a group of volunteer guinea pigs
(anybody running ~arch) is demonstrated. That said, masking big
changes and calling for volunteers among the volunteers doesn't hurt.
Seems like we need to be more careful with code that runs outside the
sandbox. Config protection is nice
the sandbox feature used by emerge.
After removing the NET_RAW capability from /usr/bin/python2.7 the
sandbox errors went away.
So now it's back to running my Python apps as root when all they
really need is raw sockets...
--
Grant Edwards grant.b.edwardsYow! Sign my PETITION
: /var/log/sandbox/sandbox-29464.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
F: open_wr
S: deny
P: /proc/self/coredump_filter
portage:portage during the fetching of package
sources.
userpriv
Allow portage to drop root privileges and compile
packages as portage:portage without a sandbox
(
> Ebuilding this packages dies of a Sandbox Violation:
>
Post the full build log and ebuild? I was able to get the new version
to
compile and install after using "sed" to loosen the sphinx dependency,
sed -i "s/1\.5/2.0/" setup.py || die
Hi Michael,
this 'sed' helped me
d code wants to speculatively execute
a memcpy(), then the sandbox would need to call it on behalf of the
untrusted code. But if the sandbox is protected, the memcpy() call would
never be made speculatively, since retpoline will trap it. So memcpy()
itself doesn't need protection. If memcpy() ends up
devel/libtool-2.4.6-r3)
>
> * Error: The above package list contains packages which cannot be
> * installed at the same time on the same system.
> --
> I did not switch to new profile "17" yet. I was trying to rebuild
> "sys-devel/libtool" first, but go
On 2019.01.21 13:41, Jacques Montier wrote:
Le lun. 21 janv. 2019 à 19:19, Jack
a
écrit :
>
> I have a suspicion that this really might be sandbox related.
> /dev/fd/whatever are all in the live system, and if I understand
> correctly, emerge works within the sandbox, s
So this is the real error - portage can't (pre)load libsandbox.so.
> 1) When is the last time you did a full upgrade? I'm now wondering if
> you have inconsistent versions of different packages installed.
> 2) Try re-emerging sys-apps/sandbox.
>
- I just did a full upgrade by
gt; "Allow portage to drop root privileges and compile packages as
> portage:portage without a sandbox"
According to my emerge --info output I have sandbox, usersandbox and userpriv,
all set. The owner of my portage directory and all files therein is
root:root. Should the ownership be por
reads. But:
>>
>> $ grep -e '\-j' -e distcc /etc/portage/make.conf
>> EMERGE_DEFAULT_OPTS="--jobs=18 --load-average=30 --backtrack=200 --
>> autounmask=n --keep-going --nospinner"
>> FEATURES="distcc userfetch buildpkg network-sandbox parallel-install s
[5] x86_64-pc-linux-gnu-3.4.6-hardenednossp
[6] x86_64-pc-linux-gnu-4.1.1 *
[snip]
$ ../sandbox-1.2.17//configure --prefix=/usr
--host=i686-pc-linux-gnu --mandir=/usr/share/man
--infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc
--localstatedir=/var/lib --libdir=/usr/lib32
-r1
* Repository: gentoo
* Maintainer: syst...@gentoo.org print...@gentoo.org
* USE: abi_x86_64 amd64 elibc_glibc kernel_linux userland_GNU
* FEATURES: network-sandbox preserve-libs sandbox userpriv usersandbox
>>> Unpacking source...
>>> Source unpacked in /var/tmp/portage/ac
3.9.0_beta1::gentoo
dev-util/cmake: 3.17.3::gentoo
dev-util/pkgconfig: 0.29.2::gentoo
sys-apps/baselayout: 2.7-r1::gentoo
sys-apps/openrc: 0.41.2::gentoo
sys-apps/sandbox: 2.20::gentoo
sys-devel/autoconf: 2.13-r1::gentoo, 2.69-r5::gentoo
sys-devel/automake:
sys-apps/openrc: 0.53.1::gentoo
sys-apps/sandbox: 2.38::gentoo
sys-devel/binutils: 2.42-r1::gentoo
sys-devel/binutils-config: 5.5::gentoo
sys-devel/clang: 17.0.6::gentoo, 18.1.2::gentoo
sys-devel/gcc: 13.2.1_p20240210::gentoo
sys-devel/gcc-config
/work/anope-_build'
* S: '/var/tmp/portage/net-irc/anope-/work/anope-'
* --- ACCESS VIOLATION SUMMARY
---
* LOG FILE: /var/log/sandbox/sandbox-7388.log
*
VERSION 1.0
FORMAT: F - Function called
FORMAT: S - Access Status
FORMAT
: 2.0.1-r6
sys-apps/baselayout: 1.12.9-r2
sys-apps/sandbox:1.2.18.1-r2
sys-devel/autoconf: 2.13, 2.61-r1
sys-devel/automake: 1.6.3, 1.7.9-r1, 1.9.6-r2, 1.10
sys-devel/binutils: 2.18-r1
sys-devel/gcc-config: 1.3.16
sys-devel/libtool: 1.5.24
virtual/os-headers: 2.6.22-r2
ACCEPT_KEYWORDS=x86
the sandbox feature didn't lead to success.
Thanks a lot for your help!
Hi Max,
You don't say if you got unixODBC working with the gui again or not. I
suppose though that resolving those later issues you had fixed unixODBC
as well ?
--
Alan McKinnon
alan dot mckinnon at gmail dot com
to make a note of this too. Pst, you see this?
FEATURES=buildsyspkg sandbox fixpackages parallel-fetch
I like the buildsyspkg part. At least I will have the system packages
and can boot up.
Once I even merged busybox to the root filesystem. It overwrites all the
Unix tools with symlinks
Hi,
I try to update a system.
I try to start by updating portage, but ...
emerge -vp sys-apps/portage
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild U ] sys-apps/sandbox-1.2.20_alpha2-r1 [1.2.17] 272 kB
[ebuild U ] sys-apps/portage
On Tuesday 15 April 2008, Helmut Jarausch wrote:
Hi,
I try to update a system.
I try to start by updating portage, but ...
emerge -vp sys-apps/portage
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild U ] sys-apps/sandbox-1.2.20_alpha2
, in order:
Calculating dependencies... done!
[ebuild U ] sys-apps/sandbox-1.2.18.1-r2 [1.2.17]
[ebuild U ] dev-python/pycrypto-2.0.1-r6 [2.0.1-r5]
[ebuild U ] sys-apps/portage-2.1.4.4 [2.1.2.2]
*** Portage will stop merging at this point and reload itself,
then resume the merge
Hello,
I'm not sure in which mailing list this one belongs, so I hope I
picked the right one.
I was trying to make an ebuild for a small MUD client (tinyfugue). But
it doesn't seem to work correct. When I try to compile it I get an
ACCESS VIOLATION SUMMARY ERROR from sandbox because I tried
from sandbox because I tried to access
/usr/bin.
ACCESS DENIED open_wr: /usr/bin/tf
Could someone tell my how I can give my ebuild the rights to access
/usr/bin? The script looks like this one:
Normally in the src_install stage the files are installed to
${PORTAGE_TMPDIR}/portage/${PF
/sandbox:1.2.18.1
--
... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
Felix Finch: scarecrow repairman rocket surgeon / [EMAIL PROTECTED]
GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see
=135688
https://bugs.gentoo.org/show_bug.cgi?id=182361#c21
Thanks. Sandbox has now recompiled, and one package has recompiled.
I'll see if everything ele recompiles next.
--
... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
Felix Finch: scarecrow repairman rocket surgeon
-
consuming job.
The Nouveau project has developed an special sandbox for the
binary drivers, which us allows sniff it's communication with
the chip. Several test programs send specific commands to the
driver and record what's send to the chip. This way, spare CPU
time can be used for collecting
config for it, consisting of
lines like cruft name, cruft src uri and a few more lines if you'll
need to pass some extra parameters to configure/make/install.
It'll build the package in a sandbox, then transfer it to destination,
memorizing every change it did and preventing collisions and config
to pass some extra parameters to configure/make/install.
It'll build the package in a sandbox, then transfer it to destination,
memorizing every change it did and preventing collisions and config
overwrites.
Just put that config script into an ebuild file and use portage to
build it - as simple
if you'll
need to pass some extra parameters to configure/make/install.
It'll build the package in a sandbox, then transfer it to destination,
memorizing every change it did and preventing collisions and config
overwrites.
Just put that config script into an ebuild file and use portage
parameters to configure/make/install.
It'll build the package in a sandbox, then transfer it to destination,
memorizing every change it did and preventing collisions and config
overwrites.
Just put that config script into an ebuild file and use portage to
build it - as simple as it gets ;)
I
it!)
- if it does not have a remove, usually if you install it inside
/home/${username}/whatever, then removing that is fine.
Best thing though is to write an ebuild and then Portage will sandbox
the build so it knows every file that has been installed.
The package knows where to link to when it goes
it!)
- if it does not have a remove, usually if you install it inside
/home/${username}/whatever, then removing that is fine.
Best thing though is to write an ebuild and then Portage will sandbox
the build so it knows every file that has been installed.
The package knows where to link to when
, you'll need to write a short config for it, consisting of
lines like cruft name, cruft src uri and a few more lines if you'll
need to pass some extra parameters to configure/make/install.
It'll build the package in a sandbox, then transfer it to destination,
memorizing every change it did
]
[ebuild U ] dev-python/pycrypto-2.0.1-r6 [2.0.1-r5]
[ebuild U ] sys-apps/sandbox-1.6-r2 [1.2.17]
[ebuild N] app-arch/lzma-utils-4.32.7 USE=-nocxx
[ebuild N] app-admin/eselect-news-20080320
[ebuild U ] app-admin/eselect-1.0.11-r1 [1.0.7] USE=-vim-syntax%
[ebuild U ] app
for next time. I did however
notice that although python is in the system set, it is not saving a
copy for some reason. Anybody know why this setting is not working?
FEATURES=--keep-going buildsyspkg sandbox fixpackages
Is the buildsyspkg option not valid anymore?
Dale
:-) :-)
Dale wrote:
You may want to look into that setting for next time. I did however
notice that although python is in the system set, it is not saving a
copy for some reason. Anybody know why this setting is not working?
FEATURES=--keep-going buildsyspkg sandbox fixpackages
John covici schrieb:
On my laptop, I did emerge sync and it said to emerge portage,
however when I tried to do this I got the following:
These are the packages that would be merged, in order:
Calculating dependencies . ..... done!
[ebuild U ] sys-apps/sandbox-1.2.18.1-r2 [1.2.17
. ..... done!
[ebuild U ] sys-apps/sandbox-1.2.18.1-r2 [1.2.17] 232 kB
[ebuild U ] dev-python/pycrypto-2.0.1-r6 [2.0.1-r5] USE=-bindist -gmp
-test 151 kB
[ebuild U ] sys-apps/portage-2.1.4.4 [2.1.2.7] USE=doc* -build
-epydoc (-selinux) LINGUAS=-pl 368
:
These are the packages that would be merged, in order:
Calculating dependencies . ..... done!
[ebuild U ] sys-apps/sandbox-1.2.18.1-r2 [1.2.17] 232 kB
[ebuild U ] dev-python/pycrypto-2.0.1-r6 [2.0.1-r5]
USE=-bindist -gmp -test 151 kB
[ebuild U
for about 5 or 6 years now. It works. My settings:
FEATURES=buildsyspkg sandbox fixpackages
Mine only keeps system packages but it can be set up several different ways.
Dale
: /usr/share/config
chmod: changing permissions of `/usr/share/config': Permission denied
You are running emerge in a sandbox and the ebuild is trying to chmod a
directory with these permissions:
$ ls -ald /usr/share/config
drwxr-xr-x 4 root root 208 Oct 23 15:39 /usr/share/config
in a sandbox and the ebuild is trying to chmod a
directory with these permissions:
$ ls -ald /usr/share/config
drwxr-xr-x 4 root root 208 Oct 23 15:39 /usr/share/config
which of course will never work. This is a bug, so report it at bgo unless
someone else has already done so.
--
alan dot
around) and madwifi-old is completely unsupported (sandbox violations,
should be removed from portage).
- Grant
On 5/7/05, Ciaran McCreesh [EMAIL PROTECTED] wrote:
On Sat, 7 May 2005 01:23:04 +0200 krzaq [EMAIL PROTECTED] wrote:
| If src_install ( ) is simply
| make DESTDIR=${D} install || die
| then i have to emerge it with -sandbox. Otherwise it dies on access
| voliation when trying
| to install
---
LOG FILE = /tmp/sandbox-net-print_-_foomatic-db-engine-3.0.2-14466.log
open_wr: /dev/fd/3 (symlink to /proc/14865/fd/3)
I have no idea why this happens; it's true there is no /dev/fd/3 but who
---
LOG FILE = /tmp/sandbox-net-print_-_foomatic-db-engine-3.0.2-14466.log
open_wr: /dev/fd/3 (symlink to /proc/14865/fd/3)
I have no idea why this happens; it's true there is no /dev/fd/3 but who
should
}/environment /dev/null
doesn't work.
No idea, but strange things happen in Portage's sandbox.
(By the way, /dev/null is a pasto? Here it is .)
But have you tried updating the kernel? See the thread on random
emerge failures. Yours aren't random, but worth trying an update.
And if that doesn't help
Grant,
On 6/7/05, Grant [EMAIL PROTECTED] wrote:
When I try to emerge gthumb, I get this at the end:
Completed installing gthumb-2.6.3 into
/var/tmp/portage/gthumb-2.6.3/image/
--- ACCESS VIOLATION SUMMARY
---
LOG FILE = /tmp/sandbox
When I try to emerge gthumb, I get this at the end:
Completed installing gthumb-2.6.3 into
/var/tmp/portage/gthumb-2.6.3/image/
--- ACCESS VIOLATION SUMMARY
---
LOG FILE = /tmp/sandbox-media-gfx_-_gthumb-2.6.3
)
[blocks B ] dev-php/php (is blocking dev-php/PEAR-PEAR-1.3.6)
[ebuild U ] sys-apps/sandbox-1.2.13 [1.2.12]
[ebuild U ] sys-devel/autoconf-wrapper-3.2 [3.1]
(...)
So, it seems dev-php/mod_php and dev-php/php are blocking some packages.
However, I have unmerged both of them already. Why
USE flags to include
these and other settings that I plan to use but didn't have in before.
And since my USE flags changed, I'm in the middle of doing the
emerge --newuse --emptytree world (it's actually going quite well;
out of 417 packages, only scotty failed due to some sandbox violations
(via the sensible route)there is no way im kidding my self that this install is going to last...
since this is not a production machinemore like my sandbox to try stuff out...
I have an Athlon XP 2200+ and 512MB ram, so not really a super-charged setup, though
naturally much faster
remove a program, library, or
something else, how will I know that there will be no affected
dependencies.
Also is there something which will reveal that an executable or library
has never been used or infrequently used.
I have not installed many packages outside the portage sandbox. Most
, but the worst thing I can imagine is a crash of
the program.
Anyway, I did not notice any such problem and I do update while the
computer is in use. It may be caused by the fact that the program is
replaced quite fast - the only dangerous time could be when the new one
is copied from sandbox to the real
is in use. It may be caused by the fact that the program is
replaced quite fast - the only dangerous time could be when the new one
is copied from sandbox to the real system.
As for it - I would not dare it on a mission critical server, but
anywhere else yes.
--
This message has optimized support
-- for whatever reason. The environment is probably
modified at that point (e.g. by portages sandbox), so it doesn't work
with a forwarded X connection.
Maybe you can temporarily overcome that by using e.g. Xnest (since you
already have X forwarding running) or Xvnc.
-hwh
--
[EMAIL PROTECTED
Hi Daevid,
Am Mittwoch, 20. Jun 2007, 15:11:22 -0700 schrieb Daevid Vincent:
Emerging (16 of 29) dev-ruby/rake-0.7.3 to /
[...]
Install rake-0.7.3 into /var/tmp/portage/dev-ruby/rake-0.7.3/image/
category dev-ruby
Exiting on signal 2
sandbox: Signal already caught and busy
@lists.gentoo.org
Subject: Re: [gentoo-user] dev-ruby/rake-0.7.3 seems to hang?
Emerging (16 of 29) dev-ruby/rake-0.7.3 to /
[...]
Install rake-0.7.3 into
/var/tmp/portage/dev-ruby/rake-0.7.3/image/
category dev-ruby
Exiting on signal 2
sandbox: Signal already
build breaks on pilot-link, which
can be simply fixed with 'FEATURES=-sandbox emerge pilot-link'. Problem is,
I can't do a resume after this as the emerge list from the world build has
been blatted when I emerged pilot-link. So, is there any way I can preserve
the state of the world build, so
-on setting for the
emerge
# flag of the same name. It causes binary packages to be created
of all
# packages that are merged.
FEATURES=buildpkg ccache sandbox
It sort of helps me in case I screw up. It happens sometimes, usually
when we least expect it too.
I'll have to look into that. It's
Hum, because of your post, I began to believe it is not only my
problem. And voila! A bug has been filed for it:
http://bugs.gentoo.org/show_bug.cgi?id=99823
It is caused by a change in behaviour in sandbox such that the file
/tmp/sandboxpids.tmp, which genlop uses to determine if a emerge
darren kirby wrote:
Also, I have rebuilt the glibc several times through this ordeal,
and at 5-6 hours per pop it is getting tedious to try new things.
Glibc _was_ built correctly, so is there anyway I can manually
copy the rest of the files from the portage sandbox to the live
filesystem
problems is Grub. When I try to emerge it in the hardened chroot the
config script bombs out with an error 'C compiler cannot create
executables'. One suggested solution was to disable sandbox in
features and try again, no such luck. My next thought was to build a
second chroot with a regular
On 7/3/06, Philip Webb [EMAIL PROTECTED] wrote:
FEATURES=autoconfig confcache distlocks metadata-transfer sandbox sfperms strict
userpriv
Hrm, confcache has also been known to cause strange problems, and in
fact is currently package.mask'ed.
Can you try FEATURES=-confcache emerge --oneshot
as portage:portage without a sandbox (unless
usersandbox is also used).
===
So, you've got it wrong.
Because of the minus, -userpriv means _forbid_ portage to drop root
privileges or in other words use root privileges. Well, mysql
build doesn't want to run tests as root (which
that folder??
The short answer is to edit make.conf and create a new directory. For
example, here is a copy from my make.conf of the relevant location
(sorry for the line numbers):
FEATURES=collision-protect sandbox ccache userpriv usersandbox buildpkg
# features for the cowboy in you
#FEATURES
create that folder??
The short answer is to edit make.conf and create a new directory. For
example, here is a copy from my make.conf of the relevant location
(sorry for the line numbers):
FEATURES=collision-protect sandbox ccache userpriv usersandbox buildpkg
# features for the cowboy
On Sun, Nov 8, 2009 at 5:14 AM, Florian Philipp
li...@f_philipp.fastmail.net wrote:
James schrieb:
All,
I'm trying to set up a DNS server here for a lab environment.
- hijacking a TLD (linux.com let's say, as an example)
- trying to point several Linux boxen in a sandbox with no internet
either AMD64 with just a couple of ~AMD64 packages,
or full ~AMD64. I haven't seen this problem on either system. However
I do run ~AMD64 portage, sandbox, gentoolkit, eix and a few other
installation things on all my systems so possibly that's part of it.
Good luck,
Mark
I had upgraded from
suggestions would be welcome
any updates on this? I'm having exactly the same problem!
I don't have a clue about this, but I'm left wondering. What is the
actual problem or error printout?
Is it a sandbox violation like in bug #257116?
Have you successfully run python-updater after switching
upgraded udev to the latest which only
works with kernels 2.6.25 or higher, and the last working kernel on
that machine is 2.6.24 (grr!). Wondering if I can download a binary
package of udev-149 from somewhere (or can I build it on another
machine in a sandbox and package it with quickpkg?). Im kind
}
MAKEOPTS=-j6
FEATURES=buildpkg sandbox fixpackages parallel-fetch --keep-going
EMERGE_DEFAULT_OPTS=--with-bdeps y --backtrack=30
That works very well here for me. Rig, AMD 4 core CPU at 3.2Ghz, 4Gbs
of ram at DDR3 1600 and SATA 3.0Gbs/sec. Your mileage may vary tho.
Dale
:-) :-)
Dale rdalek1967 at gmail.com writes:
Besides gcc, what is a good list
of critical software to use guickpkg
as to keep backup binaries?
FEATURES=buildpkg sandbox fixpackages parallel-fetch --keep-going
I saw this (FEATURES=buildpkg) googling around.
1. What is a good list of software
Am Fri, 25 Feb 2011 01:29:29 + (UTC)
schrieb James wirel...@tampabay.rr.com:
Dale rdalek1967 at gmail.com writes:
Besides gcc, what is a good list
of critical software to use guickpkg
as to keep backup binaries?
FEATURES=buildpkg sandbox fixpackages parallel-fetch --keep
of the Gentoo devs.
Diego didn't mask it because webmin itself modified config files; of
course that is what it is supposed to do. Rather, it was masked
because the ebuild itself was dodging the sandbox protection.
See Diego's blog for more info:
http://blog.flameeyes.eu/2010/08/20/there-s-something-about
to be recovered; it was mostly portage, var/tmp, some
extra sandbox stuff, kind of things.
Glad to hear that.
--
Joost
, it's already in FEATURES by default :)
[nelz@yooden ~ 0]% grep fixlafiles /etc/make.conf
[nelz@yooden ~ 1]% emerge --info | grep fixlafiles
FEATURES=assume-digests binpkg-logs buildpkg distlocks fixlafiles
fixpackages news parallel-fetch preserve-libs protect-owned sandbox
sfperms strict unknown
On 06/22/2011 06:55 AM, Dale wrote:
I just did my updates and ran into this:
* Maintainer: s...@gentoo.org
* USE: amd64 consolekit elibc_glibc kernel_linux multilib policykit
userland_GNU
* FEATURES: preserve-libs sandbox
* Please install currently selected gcc version with USE=fortran
preserve-libs protect-owned sandbox sfperms strict
unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv
usersandbox usersync
You're not alone. It's not shown here either.
--
Regards,
Mick
signature.asc
Description: This is a digitally signed message part.
-owned sandbox sfperms strict
unknown-features-warn unmerge-logs unmerge-orphans userfetch
FEATURES!
It seems to be enabled by default
[nelz@yooden ~ 0]% grep parallel /etc/make.conf
[nelz@yooden ~ 1]% emerge --info | grep parallel
FEATURES=assume-digests binpkg-logs buildpkg distlocks ebuild-locks
fixlafiles news parallel-fetch preserve-libs protect-owned sandbox
sfperms strict unknown
. Mostly stable, kernel from gentoo-sources 3.3.2.
CFLAGS=-march=amdfam10 -mcx16 -msahf -mpopcnt -mabm -O2 -pipe
CXXFLAGS=${CFLAGS}
CHOST=x86_64-pc-linux-gnu
#MAKEOPTS=-j1
MAKEOPTS=-j4
#FEATURES=ccache parallel-fetch buildsyspkg distcc
FEATURES=-sandbox ccache parallel-fetch buildsyspkg
LINGUAS=en
yesterday, bugs happen. Wait a day. They get fixed.
This sandbox violation seems to show up maybe once a year? Don't know
why but it gets fixed fast.
Cheers,
Mark
it? It is
setuptools/pycrypto which tries to write files outside the sandbox
which is not allowed.
Because it could be that something first checks the existence of that file
and only if it exists, tries to remove or use it.
Helmut
No ebuild should mess with the live system!!!
The problem
/setuptools-2.2/work/setuptools-2.2-python2_7/build/PasteDeploy.egg-info',
511) {}
I also tried disabling sandoxing in FEATURES, but the error still occurs:
FEATURES=parallel-fetch parallel-install -userpriv -usersandbox -sandbox
-strict
I tried other versions but the behaivour was the same.
Any
for sandbox to work
* Please check to make sure these options are set correctly.
* Failure to do so may cause unexpected problems.
which doesn't even advise where to find USER_NS, or will chromium no longer
work as it did in the past?
--
Regards,
Mick
signature.asc
Description
it there. The usual reason is that upstream has said their code
requires an option to be set.
Where would you have gotten the idea that ignoring it is good advice?
* Messages for package www-client/chromium-43.0.2357.65:
[27/1984]
* USER_NS is required for sandbox to work
e (name)'
> > failed
> >
> > (gst-plugin-scanner:3783): Clutter-CRITICAL **: Unable to initialize
> > Clutter: Could not initialize Gdk
> > ** Message: pygobject_register_sinkfunc is deprecated (GstObject)
> > Warning: Unable to extract the base list for
> > t
bject_register_sinkfunc is deprecated (GstObject)
> Warning: Unable to extract the base list for
> twisted.trial.unittest.TestDecorator: Bad dotted name
> Warning: Module gobject._gobject is shadowed by a variable with the same
> name.
> Warning: 18 markup errors were found while processing do
e (name)'
> > failed
> >
> > (gst-plugin-scanner:3783): Clutter-CRITICAL **: Unable to initialize
> > Clutter: Could not initialize Gdk
> > ** Message: pygobject_register_sinkfunc is deprecated (GstObject)
> > Warning: Unable to extract the base list for
> > t
needed
to configure the features list I'm using, it's been ages since I've
messed with it...
##
EMERGE_DEFAULT_OPTS="--jobs=1 --quiet-build=n --verbose"
FEATURES="sandbox distlocks nostrip parallel-fetch userfetch userpriv
usersandbox spli
On Fri, 09 Dec 2016 16:49:48 +0100
Nils Freydank <nils.freyd...@posteo.de> wrote:
> would need to migrate to an multilib profile - and I don’t know how awful
> this
> would become.
I try and this make me more pain. I stopped. GCC, GLIBC and sandbox not
want compile. Something w
to an multilib profile - and I don’t know how awful
>> > this
>> > would become.
>>
>> I try and this make me more pain. I stopped. GCC, GLIBC and sandbox not
>> want compile. Something with blabla.32.h is missing. I find nothing in
>> documentation
have a four core
>> CPU.
>>
>> FEATURES="-usersync -userpriv -usersandbox buildpkg sandbox parallel-fetch"
>>
>> MAKEOPTS="-j5"
>
> There is some controversy over setting MAKEOPTS=${number of threads}
> possibly being better than MAKEOPTS=
ecure, but choices made in the interest of
security don't really seem to relate to it. The last big extension
update was like that. There was some easy way to get around the
sandbox that Mozilla made for Firefox.
This update will break my favorite extension, Vimperator. I am already
looking at replac
-going -v -j5
> --quiet-build=n -1 --unordered-display"
>
> FEATURES="-usersync userpriv usersandbox buildpkg sandbox parallel-fetch"
>
> Each of those were added as I noticed I needed them more often than
> not. The backtrack option started out at 50 but sometimes
301 - 400 of 1472 matches
Mail list logo
