New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Staging next #54306
Staging next #54306
Conversation
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/gnutar/versions
* add generic x86_32 support - Add support for i386-i586. - Add `isx86_32` predicate that can replace most uses of `isi686`. - `isi686` is reinterpreted to mean "exactly i686 arch, and not say i585 or i386". - This branch was used to build working i586 kernel running on i586 hardware. * revert `isi[345]86`, remove dead code - Remove changes to dead code in `doubles.nix` and `for-meta.nix`. - Remove `isi[345]86` predicates since other cpu families don't have specific model predicates. * remove i386-linux since linux not supported on that cpu
"Update to iproute2 utility to support new features in Linux 4.20. This release is mostly small fixes but there are several changes related to ip neigh support for offloaded entries." [0] File changes: +share/man/man8/tc-taprio.8.gz nix path-info -S: 4.19.0 42681224 4.20.0 42714224 [0]: https://www.spinics.net/lists/netdev/msg543288.html
libuv: 1.23.2 -> 1.24.1
gmp: don't use uname to detect system features
iproute: 4.19.0 -> 4.20.0
exclude freetype-config
In particular this fixes the libmediaart tests. closes #53701
glib: fix libgio segfaults
gnutar: 1.30 -> 1.31
fixes audio for Audacious, Old School Runescape (yet to be packaged), and a few other packages, see the following issues https://bugs.archlinux.org/task/60591?project=1&string=alsa-lib https://bugzilla.redhat.com/show_bug.cgi?id=1640602 http://git.alsa-project.org/?p=alsa-lib.git;a=commitdiff;h=b420056604f06117c967b65d43d01536c5ffcbc9
libinput: 1.12.4 -> 1.12.5
pythonPackages.pycairo: 1.16.3 -> 1.18.0
Long live... eh, I hope the new KSK won't live as long as the old one. Anyway, it doesn't really matter how fast people update this. https://www.ietf.org/mail-archive/web/dnsop/current/msg24989.html See RFC 5011 for details of the protocol. I re-tested validation with both of these files, to be sure.
freetype: 2.9 -> 2.9.1
This package contains several CMake files used for setting up its provided tools for use in other projects build with CMake. While packaging *ktouch* I found out that the ${_qt5Core_install_prefix} variable doesn't expand at all, rendering the path to the `qmlcachegen` binary useless. As a fix, the command itself is used instead of the path to the binary.
packaging the `ktouch` touch typing tutor. Due to Qt impurities, it needs to be installed in a profile to find it runtime dependencies.
ktouch: init at 18.12.0
ninja sources include re2c's output files, so unless we change the sources by applying a patch, re2c is not even launched anyway, it is not relevant to building docs
We can't run the checkPhase when build != host, so we may as well make the checkInputs native. This signicantly improves the situation of Python packages when enabling strictDeps.
I'm afraid darwin is still in a too bad shape: https://hydra.nixos.org/eval/1503346?filter=darwin&compare=1503325&full=#tabs-now-fail EDIT: it seems largely because of libvdpau. |
Seems to be necessary for some reason. Otherwise we are missing symbols.
@vcunat I pushed a commit to fix libvdpau |
Hydra nixpkgs: ?compare=1503899
It looks like singular puts its headers in a weird location now, which also breaks sage. Not sure why. It is a staging-only problem: https://hydra.nixos.org/api/scmdiff?rev2=379c3899a59df74a2359b34f80604416a25bae05&uri=https%3A%2F%2Fgithub.com%2FNixOS%2Fnixpkgs.git&type=git&branch=&rev1=ab8e72b7bb24d73a588d9783240a1d0154a50ff7 — singular doesn't seem to be mentioned in the diff… |
Hydra nixpkgs: ?compare=1504357
Some was missed: 6ae1cc2 (found via |
The sage problem was also from the same group. @dotlambda: I must say I'm still not really convinced about the advantages of not propagating the |
The advantage is that people only use the Python package when it's really needed. It's also a general scheme people should learn. E.g. pythonPackages.graphviz had the same problem: #52523. There, it makes even more sense not to propagate since the package is also used at runtime. |
I would like to ask to include #54486, which fixes Python's |
@FlorianFranzen: that's a huge rebuild, unfortunately, and the issue seems to be present in master already, so I'd think we leave that to the next iteration (i.e. the usual staging workflow). |
Motivation for this change
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)