(cherry picked from commit 63fffe7)

This reverts commit a1eacb9.

Adding dev outputs to python packages means they can't be included in
a Python environment created with python3.withPackages, because
makePythonPath will include the dev output, which is empty apart from
nix-support, rather than the out output, which contains all the Python
code.

cppunit: 1.14.0 -> 1.15.0

libinput: 1.14.3 -> 1.15.0

kdeFrameworks: 5.64.0 -> 5.65.0

Also remove obsolete `let .. in ..`

Reduce closure gnome-shell closure

 http://www.wavpack.com/changelog.txt

Upstream announcement:
https://lists.gnu.org/archive/html/info-gnu/2020-01/msg00002.html

For the lazy:

> * Noteworthy changes in release 4.8 (2020-01-14) [stable]
>
> ** Bug fixes
>
>   "sed -i" now creates temporary files with correct umask (limited to u=rwx).
>   Previously sed would incorrectly set umask on temporary files, resulting
>   in problems under certain fuse-like file systems.
>   [bug introduced in sed 4.2.1]
>
> ** Release
>
>   distribute gzip-compressed tarballs once again
>
> ** Improvements
>
>   a year's worth of gnulib development, including improved DFA performance

Signed-off-by: Matthias Beyer <mail@beyermatthias.de>

Revert "Re-revert "awscli: Get rid of runtime -dev dependencies""

libde265: 1.0.4 -> 1.0.5

Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/libdvdnav/versions

- - nixpkgs now with full darwin support

poppler: 0.83.0 -> 0.84.0

graalvm8: 19.1.1 -> 19.2.1

cups: 2.3.0 -> 2.3.1

…VE-2019-9433

backports sourced from debian package 1.7.0-3+deb10u1, included in-repo
as file is not available on sources.debian.org or salsa.debian.org

(cherry picked from commit 9bcc760)

This reverts commit f14a4d6, and thus
applying 558af6f.

This was an oversight, and unnecessary in the .pc file.

"Most of the fixes have been related to single (and json) formatting.
Thank you to Aya, Jakub, Jiri, and Ron for the work to get devlink
improved." [0]

File changes (additions/removals):
None

nix path-info -S:
5.4.0 46705272
5.5.0 46726136

[0]: https://marc.info/?l=linux-netdev&m=158013364425477

In the sandbox built for https://nixbuild.net, the coreutils build fails
because a failure in the df skip-rootfs test. The test failure is triggered by
the existance of a rootfs file system. However, I think that the test is faulty,
and I have reported it upstream in
https://lists.gnu.org/archive/html/bug-coreutils/2019-12/msg00000.html.

Disabling the test makes the coreutils build work in the nixbuild.net sandbox,
and I can't think of any negative impact disabling it can have. In normal nix
setups and in the normal nix sandbox, this test is not exercised anyway, since
there is no rootfs visible.

x264: fix on ARM