| Commit message (Collapse) | Author | Age |
| |
|
|\
| |
| | |
Fix R
|
| |
| |
| |
| |
| |
| | |
I believe this test is currently incorrect on aarch64 and expects a
warning about loss of precision with much smaller numbers than the
platform's long doubles can handle.
|
| | |
|
|/ |
|
| |
|
|\ |
|
| | |
|
|/ |
|
|\ |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Naive concatenation of $LD_LIBRARY_PATH can result in an empty
colon-delimited segment; this tells glibc to load libraries from the
current directory, which is definitely wrong, and may be a security
vulnerability if the current directory is untrusted. (See #67234, for
example.) Fix this throughout the tree.
Signed-off-by: Anders Kaseorg <andersk@mit.edu>
|
|\| |
|
| |
| |
| |
| | |
Fixes #77590.
|
|/ |
|
|\
| |
| | |
gmsh: 4.4.1 -> 4.5.1
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Sage needs some doctest changes. The patch was included upstream.
Modelled after https://trac.sagemath.org/ticket/28911.
|
|
|
|
| |
Closes https://github.com/NixOS/nixpkgs/pull/75587.
|
|
|
|
|
|
|
|
| |
The pybrial package is a bit awkward. It doesn't have its own top-level
attribute, since it has a cyclic dependency with sage. That's one of the
reasons why it rarely gets updated. Its distributed along with brial, so
its best to keep the versions synchronized. The easiest way to do this
is to just re-use the source of brial.
|
|\ |
|
| | |
|
| | |
|
|/
|
|
| |
remove libGLU_combined package and replace with libGL and libGLU
|
|\
| |
| | |
sage: disable test timeout
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I already did that once in 359bf7f1e31ff5615974266e55993aff0a52ddf0.
That change mysteriously got lost somehow (presumably in some merge
commit).
Nix has its own timeout settings, so there is no risk in running
forever. At the same time, some tests can exceed the default timeout
(30minutes per file for --long tests) when run on many weak cores (like
the aarch64 community builder or some hydra builders).
|
| | |
|
|\| |
|
| |
| |
| |
| |
| | |
Permanent redirects on homepages and/or source URLs
as reported by Repology
|
|/ |
|
| |
|
|\
| |
| | |
R: enable tcltk on darwin
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
python.pkgs.pkgconfig raises an exception on missing packages since
version 1.5.0. Previously those errors were just silently ignored. That
worked fine, since the packages are only missing at runtime (when they
are not really needed) but present at buildtime.
Since this fails the tests now, we just add the packages to
PKG_CONFIG_PATH at runtime. This does not add additional runtime
dependencies. Still, it would be nicer if the sage testssuite would not
test the buildsystem at runtime in the first place.
The breakage was originally caused by the pkgconfig update in
1efa71616fadd5c7f852173445b2db824534b99b.
|
| | |
|
| |
| |
| |
| |
| |
| | |
Needs to be fixed upstream (by werkzeug, twisted). Doesn't impact the
functionality and the tests are soon to be removed with the py3 update
anyway.
|
|/ |
|
| |
|
| |
|
|\
| |
| | |
sage: ignore attrs deprecation warning
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
cmp is deprecated since attrs 19.2.0:
http://www.attrs.org/en/19.2.0/changelog.html
The deprecation warning breaks the doctests. Fortunately they have a
rather long deprecation window, so we can just wait until upstream(s)
fix this.
|
|/
|
|
| |
R's autoconf does not use the normal configure flags for that.
|
|
|
|
|
|
|
| |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/nauty/versions
|
|
|
|
|
|
|
| |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/ginac/versions
|
|\
| |
| | |
clp: 1.17.2 -> 1.17.3
|