#16736: sagenb: SandboxViolation in webassets
-------------------------------------+-------------------------------------
Reporter: vbraun | Owner:
Type: defect | Status: needs_review
Priority: major | Milestone: sage-6.3
Component: packages: | Resolution:
standard | Merged in:
Keywords: | Reviewers:
Authors: Volker Braun | Work issues:
Report Upstream: N/A | Commit:
Branch: | a487a0d673527ab9a9b57c36edf9c5ed0a7ac483
u/vbraun/sagenb__sandboxviolation_in_webassets| Stopgaps:
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by strogdon):
This is very curious. I merged #16733 and this ticket w/o the
{{{sandbox.patch}}} (the patch was removed and the change was committed
with {{{git commit -a}}}). The following sequence did not give a
{{{SandboxViolation}}} in webassets:
* ./sage -f docutils
* ./sage -f setuptools
* ./sage -f sagenb
But the following sequence did yield the violation (new docutils
installed)
* ./sage -f pillow
* ./sage -f setuptools
* ./sage -f sagenb
Then adding the sandbox patch in and doing
* ./sage -f setuptools
* ./sage -f sagenb
seemed to resolve things. So where is the real problem? Maybe it doesn't
matter. The sandbox patch does work.
--
Ticket URL: <http://trac.sagemath.org/ticket/16736#comment:14>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
