This regex should match files ending in `.git`, not any character and `git` after that.

https://lists.x.org/archives/xorg-announce/2021-February/003072.html
https://lists.x.org/archives/xorg-announce/2021-February/003073.html

Changelog:

https://github.com/PyO3/setuptools-rust/releases/tag/v0.12.1
https://github.com/PyO3/setuptools-rust/releases/tag/v0.12.0

The build wanted to create a Cargo.lock in the top-level source
directory (presumably because it is also a Cargo project), since we
were crating the lock file in sourceRoot (which was set to the example
project). This failed because the sources are read-only. Change the
test to create the lock file in the top-level crate directory, which
is Cargo's default behavior.

The passthru test used python3Packages, mixing different Python
version when testing on a Python version different that the python3
alias.

This fixes CVE-2021-23336:
https://www.djangoproject.com/weblog/2021/feb/19/security-releases/

networkmanager: 1.30.0 -> 1.30.2

[staging] python3Packages.django_2: 2.2.18 -> 2.2.19

xorg.xorgproto: 2020.1 -> 2021.3

fetchgit: escape dot in regex

Changelog: https://github.com/ImageMagick/ImageMagick/blob/7.0.11-4/ChangeLog

imagemagick: 7.0.11-3 -> 7.0.11-4

When, after patching, `configure.ac` is newer than `configure`, the
Makefile will try to regenerate `configure` from `configure.ac`.

While that might usually be desirable, in this case we want to keep
bootstrapping simple and directly use the `configure` from the package
so we can avoid a dependency on automake.

Previously, we used the `-T` parameter to automake to make sure the
timestamps were okay. However, this is brittle when we update: when the
timestamp of the original file changes, and no longer matches the
timestamp of the original file in the patch, `patch` will show a warning
but otherwise continue without updating the timestamp.

This PR changes things so we only patch `configure`, so that will always
have a newer timestamp.

Refs #115177

ntfs3g: add darwin build

The applied patch contains the changes from this PR:
OpenMathLib/OpenBLAS#3060

This patch prevents gcc from reordering instructions in a way
that can cause crashes with SIGILL on aarch64.

This issue crashes python when importing numpy on aarch64:
numpy/numpy#18131

Get rid of non-absolute RPATH reference to CoreFoundation

python3Packages.setuptools-rust: 0.11.6 -> 0.12.1

Signed-off-by: Pamplemousse <xav.maso@gmail.com>

ocamlPackages.ocaml: 4.10.0 -> 4.10.2

ocamlPackages.findlib: 1.8.1 -> 1.9.1

Currently there is only one line difference regarding bootstrapped-pip,
but this will change in the future with the whole Python world moving
towards PEP 517.

gnome-usage: 3.38.0 -> 3.38.1