Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/check/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/884zd0n1kqjfm8gkk2ql8rzwshr6ldhl-check-0.12.0/bin/checkmk -h’ got 0 exit code
- ran ‘/nix/store/884zd0n1kqjfm8gkk2ql8rzwshr6ldhl-check-0.12.0/bin/checkmk --help’ got 0 exit code
- found 0.12.0 with grep in /nix/store/884zd0n1kqjfm8gkk2ql8rzwshr6ldhl-check-0.12.0
- directory tree listing: https://gist.github.com/96299205c5d86d2f1eda8b58f2c95588
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/cmark/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/ws8c9r62c7wsas7kj1v0svfs57d53dvv-cmark-0.28.3/bin/cmark -h’ got 0 exit code
- ran ‘/nix/store/ws8c9r62c7wsas7kj1v0svfs57d53dvv-cmark-0.28.3/bin/cmark --help’ got 0 exit code
- found 0.28.3 with grep in /nix/store/ws8c9r62c7wsas7kj1v0svfs57d53dvv-cmark-0.28.3
- directory tree listing: https://gist.github.com/890d356ed9766b2fca77baebee346a0e
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/dbus/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/2fb87ah2lsvnzlah1mkdiwsrv8p01yh6-dbus-1.12.6/bin/dbus-monitor --help’ got 0 exit code
- ran ‘/nix/store/2fb87ah2lsvnzlah1mkdiwsrv8p01yh6-dbus-1.12.6/bin/dbus-cleanup-sockets -h’ got 0 exit code
- ran ‘/nix/store/2fb87ah2lsvnzlah1mkdiwsrv8p01yh6-dbus-1.12.6/bin/dbus-cleanup-sockets --help’ got 0 exit code
- ran ‘/nix/store/2fb87ah2lsvnzlah1mkdiwsrv8p01yh6-dbus-1.12.6/bin/dbus-cleanup-sockets help’ got 0 exit code
- ran ‘/nix/store/2fb87ah2lsvnzlah1mkdiwsrv8p01yh6-dbus-1.12.6/bin/dbus-run-session -h’ got 0 exit code
- ran ‘/nix/store/2fb87ah2lsvnzlah1mkdiwsrv8p01yh6-dbus-1.12.6/bin/dbus-run-session --help’ got 0 exit code
- ran ‘/nix/store/2fb87ah2lsvnzlah1mkdiwsrv8p01yh6-dbus-1.12.6/bin/dbus-uuidgen --help’ got 0 exit code
- ran ‘/nix/store/2fb87ah2lsvnzlah1mkdiwsrv8p01yh6-dbus-1.12.6/bin/dbus-launch -h’ got 0 exit code
- ran ‘/nix/store/2fb87ah2lsvnzlah1mkdiwsrv8p01yh6-dbus-1.12.6/bin/dbus-launch --help’ got 0 exit code
- found 1.12.6 with grep in /nix/store/2fb87ah2lsvnzlah1mkdiwsrv8p01yh6-dbus-1.12.6
- directory tree listing: https://gist.github.com/f7926c86c6572ac1a02dab3468dbbb95
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/gdbm/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/rxca8g769fj1zydp1673w0v09605a5ak-gdbm-1.14.1/bin/gdbmtool -h’ got 0 exit code
- ran ‘/nix/store/rxca8g769fj1zydp1673w0v09605a5ak-gdbm-1.14.1/bin/gdbmtool --help’ got 0 exit code
- ran ‘/nix/store/rxca8g769fj1zydp1673w0v09605a5ak-gdbm-1.14.1/bin/gdbmtool help’ got 0 exit code
- ran ‘/nix/store/rxca8g769fj1zydp1673w0v09605a5ak-gdbm-1.14.1/bin/gdbm_load -h’ got 0 exit code
- ran ‘/nix/store/rxca8g769fj1zydp1673w0v09605a5ak-gdbm-1.14.1/bin/gdbm_load --help’ got 0 exit code
- ran ‘/nix/store/rxca8g769fj1zydp1673w0v09605a5ak-gdbm-1.14.1/bin/gdbm_dump -h’ got 0 exit code
- ran ‘/nix/store/rxca8g769fj1zydp1673w0v09605a5ak-gdbm-1.14.1/bin/gdbm_dump --help’ got 0 exit code
- found 1.14.1 with grep in /nix/store/rxca8g769fj1zydp1673w0v09605a5ak-gdbm-1.14.1
- directory tree listing: https://gist.github.com/fdbeceb9acdfc810ba2c598902e40881
Upstream requested that we remove these packages until the first stable
release. More details are in #38344. This isn't ideal but it seems like
the best solution for now.
Close#38344.
With this patch I remove myself as a maintainer for all packages I
currently maintain.
This is due the fact that I will be basically off the grid from May 2018
until early 2019, as I will be on a trip through north america.
I will revert this patch as soon as I'm back, as I plan to continue
contributing to nixpkgs then.
But as I cannot maintain anything during that time, I'd like to get this
patch merged.
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
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/qpdf/versions.
These checks were done:
- built on NixOS
- ran `/nix/store/ck7mhavin0im813rf4hawqswmrg47pc8-qpdf-8.0.2/bin/fix-qdf --version` and found version 8.0.2
- ran `/nix/store/ck7mhavin0im813rf4hawqswmrg47pc8-qpdf-8.0.2/bin/qpdf --help` got 0 exit code
- ran `/nix/store/ck7mhavin0im813rf4hawqswmrg47pc8-qpdf-8.0.2/bin/qpdf --version` and found version 8.0.2
- found 8.0.2 with grep in /nix/store/ck7mhavin0im813rf4hawqswmrg47pc8-qpdf-8.0.2
- directory tree listing: https://gist.github.com/3d0da50b8418a253f7a33f8df1e1ed7f
https://hydra.nixos.org/build/70700906
I opened an upstream bug, but their bug system is e-mail based and I
haven't got a single reply which contains an web link :(
Since at least d7bddc27b2, we've had a
situation where one should depend on:
- `stdenv.cc.bintools`: for executables at build time
- `libbfd` or `libiberty`: for those libraries
- `targetPackages.cc.bintools`: for exectuables at *run* time
- `binutils`: only for specifically GNU Binutils's executables,
regardless of the host platform, at run time.
and that commit cleaned up this usage to reflect that. This PR flips the
switch so that:
- `binutils` is indeed unconditionally GNU Binutils
- `binutils-raw`, which previously served that role, is gone.
so that the correct usage will be enforced going forward and everything
is simple.
N.B. In a few cases `binutils-unwrapped` (which before and now was
unconditionally actual GNU binutils), rather than `binutils` was used to
replace old `binutils-raw` as it is friendly towards some cross
compilation usage by avoiding a reference to the next bootstrapping
change.
Don't rely on questionable impact of DT_RPATH on dlopen().
This is a bit of a messy subject, but probably the clearest
reference to motivate *not* relying on how dlopen() behaves
in the presence of RPATH or RUNPATH is the following:
https://sourceware.org/ml/libc-hacker/2002-11/msg00011.html
FWIW the dlopen() manpage only mentions the the RPATH
and RUNPATH in the "executable file for the calling program";
no mention of the executable files for libraries--
this has been brought to the attention of the relevant
parties and AFAICT nothing has been done.
The best reference for glibc behavior is
apparently to ... "try it and see".
Luckily a generous soul did exactly that
and reported the findings:
https://www.spinics.net/lists/linux-man/msg02291.html
Qt wrote on the subject a bit when they were bit by this,
linking to the above articles (directly or indirectly).
See:
http://blog.qt.io/blog/2011/10/28/rpath-and-runpath/
--------
Since we know the path of libGL at build-time for libepoxy,
there's a simple solution we can use to avoid all of this:
simply teach libepoxy to explicitly look in the libGL path.
This commit patches libepoxy to accomplish this,
looking to "LIBGL_PATH" as a fallback if it cannot find
the libraries otherwise.
---------
This fixes use of libepoxy w/musl on NixOS!
