I haven't been doing any maintenance for a long time now and not only
do I get notified, it also creates a fake impression that all these
packages had at least one maintainer when in practice they had none.
Quoting from the splitString docstring:
NOTE: this function is not performant and should never be used.
This replaces trivial uses of splitString for splitting version
strings with the (potentially builtin) splitVersion.
Sage now by default expects the lcalc library to be named Lfunction
(instead of libLfunction). This could be changed by an environment
variable (https://trac.sagemath.org/ticket/28224), but various distros
seem to agree on this standard
(https://groups.google.com/forum/#!topic/sage-packaging/xvh55IxHTZg) so
it's best just to follow it. The old standard was set by sage anyway and
sage is the only consumer of lcalc in nixpkgs.
There ver very many conflicts, basically all due to
name -> pname+version. Fortunately, almost everything was auto-resolved
by kdiff3, and for now I just fixed up a couple evaluation problems,
as verified by the tarball job. There might be some fallback to these
conflicts, but I believe it should be minimal.
Hydra nixpkgs: ?compare=1538299
Maintenance taken over by debian package maintainer jgmbenoit:
https://trac.sagemath.org/ticket/3360#comment:17
This moves sympow to his fork, since there is no offical
version-controlled source repository from the original author and they
do not seem to maintain sympow anymore. We had already accumulated quite
some patches from debian, who have effectively maintained sympow for a
while now.
This avoids the potential conflict between autoconf flags and the waf
flags. There is some overlap between the two but waf errors when it
doesn’t recognize the flag.
My earlier change mistakenly expected `toString false` to produce '0'
instead of the empty string, leading to unexpected config changes.
Intended to address issue mentioned here and in following discussion:
https://github.com/NixOS/nixpkgs/pull/53972#issuecomment-459981602
Sorry, folks!
(special-case handling of bools here makes this "cleanup" a bit
less of an obvious win but hopefully still preferable overall :))
-----------
makeFlags in resulting derivation, according to this one-liner:
$ nix show-derivation -f . openblas|jq ".[].env.makeFlags"
before:
"BINARY=64 CC=cc CROSS= DYNAMIC_ARCH=1 FC=gfortran HOSTCC=cc INTERFACE64=1 NO_BINARY_MODE= NO_STATIC=1 NUM_THREADS=64 PREFIX=/1rz4g4znpzjwh1xymhjpm42vipw92pr73vdgl6xs1hycac8kf2n9 TARGET=ATHLON USE_OPENMP=1"
after:
"BINARY=64 CC=cc CROSS=0 DYNAMIC_ARCH=1 FC=gfortran HOSTCC=cc INTERFACE64=1 NO_BINARY_MODE=0 NO_STATIC=1 NUM_THREADS=64 PREFIX=/1rz4g4znpzjwh1xymhjpm42vipw92pr73vdgl6xs1hycac8kf2n9 TARGET=ATHLON USE_OPENMP=1"
Without knowing how `placeholder` works, it seems interesting if
entirely unrelated that the `PREFIX` is same for both! :). TIL.
This reverse changes made cfc4313 which broke builds on linux. Still
not sure why this broke Linux, but we can investigate it later.
“buildPackages.stdenv.cc” shouldn’t be put in nativeBuildInputs in
general. Either way, this restores hashes to before that commit.
thanks to @jethrokuan
The openblas script relies on CC=clang for succesfully compiling on
Darwin systems. This seems like bad behavior, but we get things like
https://hydra.nixos.org/build/87657058 otherwise.
Fixes#55536.
Comments on conflicts:
- llvm: d6f401e1 vs. 469ecc70 - docs for 6 and 7 say the default is
to build all targets, so we should be fine
- some pypi hashes: they were equivalent, just base16 vs. base32
* openblas: simplify a bit, fix doCheck so tests are enabled non-cross.
* doCheck should be 'true' in (at least) the non-cross case,
this looks like an inverted check that's largely benign
* doCheck will be set to 'false' in the cross case anyway,
makeDerivation does this IIRC
* targetPrefix can be used without checking, probably by design
Derivation hash does change but no "real" functionality change intended.
* openblas: nix types for config attrs (hash-preserving)
* openblas: more nix-ification, merge in cross attrs, prefer to always set
(but set appropriately for cross and non-cross cases both)
* I'm not sure what NO_BINARY_MODE does,
this change now sets explicitly false in the non-cross scenario
(previously unset unless cross).
* Drop musl NO_AFFINITY case, will be removed in upgrade shortly
* openblas: 0.3.4 -> 0.3.5
Since Intel's default openmp implementation is available in the same src
tarball, we can just include it in the package. This means that `mkl` now "just
works" without any environment variables, fragile setup-hooks, or forced
propagation.
Since the openmp implementation is only needed at runtime (and for test cases),
users can substitute a different one if they prefer by exporting it with
`LD_PRELOAD`, which is how Intel recommends handling this. If they do not do so,
`libiomp.so` lives next to `libmkl_rt.so` and thus will be in the RPATH as a
sane default.
Since this still comes from the same src tarball, we can ship it without losing
the fixed-output derivation; likewise, since Hydra is not building or caching
these, shipping these proprietary packages costs no bandwidth for the nix
community.
Suitesparse libraries would end up containing references to the build
directory. fixDarwinDylibNames appears to not fix this problem. We
manually use intall_name_tool to set the library paths correctly.
The build created libraries with an install_name that points to the
build directory instead of the installation prefix. Causing errors like
this when other packages try to link against it's libraries.
Library not loaded: /private/tmp/nix-build-suitesparse-5.3.0.drv-0/SuiteSparse/lib/libcholmod.3.0.12.dylib
This packags the Intel Math Kernel library on x86-64 platforms, which is a
dependency for many data science and machine learning packages.
Upstream, Intel provides proprietary binary RPMs with a permissive
redistribution license. These have been repackaged in both Debian and Anaconda,
so we are not the first distribution to redistribute.
Since the exposure of the version attribute done in
892a0e8ff4, the OpenBLAS build fails for
i686-linux:
https://nix-cache.s3.amazonaws.com/log/wi79zyfmwdpwx7bm29dzqh4vglx3x550-openblas-0.3.0.drv
According to @edolstra the build slaves of Hydra updated to a new
kernel, which seems to be the real cause for this issue. The latter is
already tracked upstream[1] and a fix[2] is already included in version
0.3.1.
This very update cases 4795 rebuilds across all architectures we
support, so it's still not significant enough to go through staging. In
addition the number of rebuilds doesn't include the amount of builds
that are currently failing.
My original idea was to add a patch just for fixing this on i686-linux
and do the real update via staging, but the amount of rebuilds still is
in an acceptable range IMO and @edolstra agreed on that on IRC.
[1]: https://github.com/xianyi/OpenBLAS/issues/1575
[2]: https://github.com/xianyi/OpenBLAS/pull/1583
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @ttuegel
* treewide: http -> https sources
This updates the source urls of all top-level packages from http to
https where possible.
* buildtorrent: fix url and tab -> spaces
In particular, this contains Firefox-related and libgcrypt updates.
Other larger rebuilds would apparently need lots of time to catch up
on Hydra, due to nontrivial rebuilds in other branches than staging.
ns-3 is a discrete event C++ network simulator developed at www.nsnam.org .
Python bindings & manual building are disabled by default but you can
override it.
Semi-automatic update generated by https://github.com/ryantm/nix-update tools.
This update was made based on information from https://repology.org/metapackage/petsc/versions.
These checks were done:
- built on NixOS
- ran `/nix/store/czmq31v2xa85ql17whbn05774cncbr4a-petsc-3.8.4/bin/saws/getSAWs.bash -h` got 0 exit code
- ran `/nix/store/czmq31v2xa85ql17whbn05774cncbr4a-petsc-3.8.4/bin/saws/getSAWs.bash --help` got 0 exit code
- ran `/nix/store/czmq31v2xa85ql17whbn05774cncbr4a-petsc-3.8.4/bin/saws/getSAWs.bash help` got 0 exit code
- ran `/nix/store/czmq31v2xa85ql17whbn05774cncbr4a-petsc-3.8.4/bin/petscdiff -h` got 0 exit code
- ran `/nix/store/czmq31v2xa85ql17whbn05774cncbr4a-petsc-3.8.4/bin/petscdiff --help` got 0 exit code
- ran `/nix/store/czmq31v2xa85ql17whbn05774cncbr4a-petsc-3.8.4/bin/petscdiff -h` and found version 3.8.4
- ran `/nix/store/czmq31v2xa85ql17whbn05774cncbr4a-petsc-3.8.4/bin/petscdiff --help` and found version 3.8.4
- ran `/nix/store/czmq31v2xa85ql17whbn05774cncbr4a-petsc-3.8.4/bin/update.py -h` got 0 exit code
- ran `/nix/store/czmq31v2xa85ql17whbn05774cncbr4a-petsc-3.8.4/bin/update.py --help` got 0 exit code
- ran `/nix/store/czmq31v2xa85ql17whbn05774cncbr4a-petsc-3.8.4/bin/update.py help` got 0 exit code
- ran `/nix/store/czmq31v2xa85ql17whbn05774cncbr4a-petsc-3.8.4/bin/update.py -V` and found version 3.8.4
- ran `/nix/store/czmq31v2xa85ql17whbn05774cncbr4a-petsc-3.8.4/bin/update.py -v` and found version 3.8.4
- ran `/nix/store/czmq31v2xa85ql17whbn05774cncbr4a-petsc-3.8.4/bin/update.py --version` and found version 3.8.4
- ran `/nix/store/czmq31v2xa85ql17whbn05774cncbr4a-petsc-3.8.4/bin/update.py version` and found version 3.8.4
- ran `/nix/store/czmq31v2xa85ql17whbn05774cncbr4a-petsc-3.8.4/bin/update.py -h` and found version 3.8.4
- ran `/nix/store/czmq31v2xa85ql17whbn05774cncbr4a-petsc-3.8.4/bin/update.py --help` and found version 3.8.4
- ran `/nix/store/czmq31v2xa85ql17whbn05774cncbr4a-petsc-3.8.4/bin/update.py help` and found version 3.8.4
- ran `/nix/store/czmq31v2xa85ql17whbn05774cncbr4a-petsc-3.8.4/bin/sendToJenkins -h` got 0 exit code
- ran `/nix/store/czmq31v2xa85ql17whbn05774cncbr4a-petsc-3.8.4/bin/sendToJenkins --help` got 0 exit code
- ran `/nix/store/czmq31v2xa85ql17whbn05774cncbr4a-petsc-3.8.4/bin/petscnagupgrade.py -h` got 0 exit code
- ran `/nix/store/czmq31v2xa85ql17whbn05774cncbr4a-petsc-3.8.4/bin/petscnagupgrade.py --help` got 0 exit code
- ran `/nix/store/czmq31v2xa85ql17whbn05774cncbr4a-petsc-3.8.4/bin/petscnagupgrade.py help` got 0 exit code
- found 3.8.4 with grep in /nix/store/czmq31v2xa85ql17whbn05774cncbr4a-petsc-3.8.4
- found 3.8.4 in filename of file in /nix/store/czmq31v2xa85ql17whbn05774cncbr4a-petsc-3.8.4
- directory tree listing: https://gist.github.com/da90b8c44c7ed274deb2e1a2c7de8dad
3.10.3 segfaults with glibc 2.27, and since it was fairly recently
added via autoupdate hopefully it's not too strongly needed yet.
This reverts commit 4c28d80be2.
Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:
- built on NixOS
- Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
- found 3.10.3 with grep in /nix/store/79z1zd6ydm6b7x6xbf8b908iirah8hqn-atlas-3.10.3
Semi-automatic update. These checks were done:
- built on NixOS
- Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
- found 0.5.5 with grep in /nix/store/im5hsldagl6la2yf5s8rsnv2w57mb76m-openlibm-0.5.5
- found 0.5.5 in filename of file in /nix/store/im5hsldagl6la2yf5s8rsnv2w57mb76m-openlibm-0.5.5
Semi-automatic update. These checks were performed:
- built on NixOS
- found 3.8.0 in filename of file in /nix/store/6j28cb5b114fxj7x7wpwv8mdbiqxq1fj-blas-3.8.0
Semi-automatic update. These checks were performed:
- built on NixOS
- ran `/nix/store/fgr3yvhrnvfhr0czc4ygx1mnjsrv4f4i-petsc-3.8.3/bin/saws/getSAWs.bash -h` got 0 exit code
- ran `/nix/store/fgr3yvhrnvfhr0czc4ygx1mnjsrv4f4i-petsc-3.8.3/bin/saws/getSAWs.bash --help` got 0 exit code
- ran `/nix/store/fgr3yvhrnvfhr0czc4ygx1mnjsrv4f4i-petsc-3.8.3/bin/saws/getSAWs.bash help` got 0 exit code
- ran `/nix/store/fgr3yvhrnvfhr0czc4ygx1mnjsrv4f4i-petsc-3.8.3/bin/update.py -h` got 0 exit code
- ran `/nix/store/fgr3yvhrnvfhr0czc4ygx1mnjsrv4f4i-petsc-3.8.3/bin/update.py --help` got 0 exit code
- ran `/nix/store/fgr3yvhrnvfhr0czc4ygx1mnjsrv4f4i-petsc-3.8.3/bin/update.py help` got 0 exit code
- ran `/nix/store/fgr3yvhrnvfhr0czc4ygx1mnjsrv4f4i-petsc-3.8.3/bin/update.py -V` and found version 3.8.3
- ran `/nix/store/fgr3yvhrnvfhr0czc4ygx1mnjsrv4f4i-petsc-3.8.3/bin/update.py -v` and found version 3.8.3
- ran `/nix/store/fgr3yvhrnvfhr0czc4ygx1mnjsrv4f4i-petsc-3.8.3/bin/update.py --version` and found version 3.8.3
- ran `/nix/store/fgr3yvhrnvfhr0czc4ygx1mnjsrv4f4i-petsc-3.8.3/bin/update.py version` and found version 3.8.3
- ran `/nix/store/fgr3yvhrnvfhr0czc4ygx1mnjsrv4f4i-petsc-3.8.3/bin/update.py -h` and found version 3.8.3
- ran `/nix/store/fgr3yvhrnvfhr0czc4ygx1mnjsrv4f4i-petsc-3.8.3/bin/update.py --help` and found version 3.8.3
- ran `/nix/store/fgr3yvhrnvfhr0czc4ygx1mnjsrv4f4i-petsc-3.8.3/bin/update.py help` and found version 3.8.3
- ran `/nix/store/fgr3yvhrnvfhr0czc4ygx1mnjsrv4f4i-petsc-3.8.3/bin/petscnagupgrade.py -h` got 0 exit code
- ran `/nix/store/fgr3yvhrnvfhr0czc4ygx1mnjsrv4f4i-petsc-3.8.3/bin/petscnagupgrade.py --help` got 0 exit code
- ran `/nix/store/fgr3yvhrnvfhr0czc4ygx1mnjsrv4f4i-petsc-3.8.3/bin/petscnagupgrade.py help` got 0 exit code
- ran `/nix/store/fgr3yvhrnvfhr0czc4ygx1mnjsrv4f4i-petsc-3.8.3/bin/sendToJenkins -h` got 0 exit code
- ran `/nix/store/fgr3yvhrnvfhr0czc4ygx1mnjsrv4f4i-petsc-3.8.3/bin/sendToJenkins --help` got 0 exit code
- ran `/nix/store/fgr3yvhrnvfhr0czc4ygx1mnjsrv4f4i-petsc-3.8.3/bin/sendToJenkins -h` and found version 3.8.3
- ran `/nix/store/fgr3yvhrnvfhr0czc4ygx1mnjsrv4f4i-petsc-3.8.3/bin/sendToJenkins --help` and found version 3.8.3
- ran `/nix/store/fgr3yvhrnvfhr0czc4ygx1mnjsrv4f4i-petsc-3.8.3/bin/petscdiff -h` got 0 exit code
- ran `/nix/store/fgr3yvhrnvfhr0czc4ygx1mnjsrv4f4i-petsc-3.8.3/bin/petscdiff --help` got 0 exit code
- ran `/nix/store/fgr3yvhrnvfhr0czc4ygx1mnjsrv4f4i-petsc-3.8.3/bin/petscdiff -h` and found version 3.8.3
- ran `/nix/store/fgr3yvhrnvfhr0czc4ygx1mnjsrv4f4i-petsc-3.8.3/bin/petscdiff --help` and found version 3.8.3
- found 3.8.3 with grep in /nix/store/fgr3yvhrnvfhr0czc4ygx1mnjsrv4f4i-petsc-3.8.3
Semi-automatic update. These checks were performed:
- built on NixOS
- found 0.5.3 in filename of file in /nix/store/yqsgs9hw8c3rdia75rswgk98lz3c52ih-openspecfun-0.5.3
cc "@ttuegel"
