texlive/bin: remove unnecessary parentheses #225035

python310Packages.sphinx-autodoc-typehints: 1.23.4 -> 1.22

…d empty meta.maintainers, misc cleanup

roc-toolkit: 0.2.1 -> 0.2.3

iana-etc: 20221107 -> 20230316

https://github.com/ijl/orjson/releases/tag/3.8.9 ijl/orjson@3.8.6...3.8.9

Diff: rust-lang/rust@1.68.1...1.68.2 Changelog: https://blog.rust-lang.org/2023/03/28/Rust-1.68.2.html

...into staging

Announcement: https://sourceware.org/pipermail/libc-alpha/2022-August/141193.html Announcement: https://sourceware.org/pipermail/libc-alpha/2023-February/145190.html

Failing Hydra build: https://hydra.nixos.org/build/189053872

Previously, builds such as `cmake` would fail with errors like this: In file included from /nix/store/injyphmxqgi028skp28fsmdvbdb57nvl-glibc-2.36-48-dev/include/linux/fs.h:19, from /build/cmake-3.24.2/Utilities/cmlibarchive/libarchive/archive_read_disk_posix.c:56: /nix/store/injyphmxqgi028skp28fsmdvbdb57nvl-glibc-2.36-48-dev/include/linux/mount.h:95:6: error: redeclaration of 'enum fsconfig_command' 95 | enum fsconfig_command { | ^~~~~~~~~~~~~~~~ The reason behind that is that the kernel exports `linux/mount.h` via kernel headers APIs that are also defined in `sys/mount.h` from glibc. To avoid clashes, safeguards were implemented in glibc to prevent this from happening[1][2]. However, these `#ifndef`-safeguards are removed by `fixincludes` during gcc's build and the (broken) result is subsequently copied into `include-fixed/sys/mount.h` which is added to each build via the cc-wrapper. To work around this, I decided to simply drop the file: it also exists in glibc's output and our gcc12 doesn't seem to expose this anymore anyways. [1] Commit bb1e8b0ca99b5cbedfae3e6245528a87d95ff3e2 [2] Commit 3bd3c612e98a53ce60ed972f5cd2b90628b3cba5

Failing Hydra build: https://hydra.nixos.org/build/193327405 Same fix as for gcc11.

Failing Hydra build: https://hydra.nixos.org/build/193342322 Patch from gcc11 requires some minor adjustments to properly apply.

Failing Hydra build: https://hydra.nixos.org/build/193370420

Failing Hydra build: https://hydra.nixos.org/build/193340626

Failing Hydra build: https://hydra.nixos.org/build/193371579

Failing Hydra build: https://hydra.nixos.org/build/193330218

Failing Hydra build: https://hydra.nixos.org/build/193374680

Failing Hydra build: https://hydra.nixos.org/build/193338640 We don't need the `meson.build` fixes because (1) lxc4 doesn't use meson and (2) it contains some fixes to make sure it works both with newer and older glibc versions. Since we only ship glibc 2.36 from now on, we can skip that.

Failing Hydra build: https://hydra.nixos.org/build/193347368

Failing Hydra build: https://hydra.nixos.org/build/193339001

Failing Hydra build: https://hydra.nixos.org/build/193332774

The functions pidfd_open & pidfd_send_signal are now part of `glibc`, but defined in the header `sys/pidfd.h` which is not included in `bindings.c`. Failing Hydra build: https://hydra.nixos.org/build/193376808

Failing Hydra build: https://hydra.nixos.org/build/193323749

Failing Hydra build: https://hydra.nixos.org/build/193810432

Set the executable bit before running the check phase, so that the check phase can run the script to test its behaviour. This aligns with what `concatTextFile` is doing. Also use explicit `if` statements so that we don't silently ignore `chmod` failures.

Fixes #223583 This strips the exe files when testpath is used on non-windows platforms.

…ges-staging-reland opencv: misc CUDA-related updates and fixes; add enableLto

bundler: 2.4.9 -> 2.4.10

maturin: 0.14.15 -> 0.14.16

Changelog: https://www.sqlite.org/releaselog/3_41_2.html

wayland: build libraries on darwin

systemd/systemd-stable@v253.1...v253.2 Commits: 81 Files changed: 113

tk: propagate frameworks

The script requires a python3 shebang with an environment that includes python3Packages.pefile at runtime.

freeipa: init at 4.10.1

sratom: 0.6.8 -> 0.6.14

Avoid aliases

libidn2: 2.3.2 -> 2.3.4

https://mm.icann.org/pipermail/tz-announce/2023-March/000079.html > This release's code and data are identical to 2023a. In other words, > this release reverts all changes made in 2023b other than commentary, > as that appears to be the best of a bad set of short-notice choices > for modeling this week's daylight saving chaos in Lebanon.

To correctly find the implementation of `pidfd_open` - which was introduced in glibc 2.36 - an additional `#include` is needed. The newly introduced patch adds that. Failing Hydra build: https://hydra.nixos.org/build/214432977

Failing Hydra build: https://hydra.nixos.org/build/214419156 Relevant upstream thread: https://lore.kernel.org/qemu-devel/20230110174901.2580297-1-berrange@redhat.com/

No functional changes for the other TLS backend but it is now possible to build curl with `rustls-ffi`. ``` > ./result-bin/bin/curl --version curl 8.0.1 (x86_64-pc-linux-gnu) libcurl/8.0.1 rustls-ffi/0.9.2/rustls/0.20.8 zlib/1.2.13 brotli/1.0.9 zstd/1.5.4 libidn2/2.3.2 libssh2/1.10.0 nghttp2/1.51.0 Release-Date: 2023-03-20 Protocols: dict file ftp ftps gopher gophers http https imap imaps mqtt pop3 pop3s rtsp scp sftp smtp smtps telnet tftp Features: alt-svc AsynchDNS brotli GSS-API HSTS HTTP2 HTTPS-proxy IDN IPv6 Kerberos Largefile libz SPNEGO SSL threadsafe UnixSockets zstd ```

The command ``` nix-build -A tests.trivial-builders.references --show-trace ``` fails eval with ``` in job ‘nixpkgs.tests.trivial-builders.references’: error: The option `meta.description' does not exist. Definition values: - In `makeTest parameters': "Run the Nixpkgs trivial builders tests" ``` because `meta.description` and `meta.license` are not valid for `nixosTest`s (they are valid for `mkDerivation` of course). This has been causing Hydra eval failures: https://hydra.nixos.org/jobset/nixos/pr-209870-gcc-external-bootstrap#tabs-errors Let's fix eval by removing these attributes.

The command at the top of this file fails to evaluate: ``` $ nix-build -A tests.pkg-config.defaultPkgConfigPackages in job ‘nixpkgs.tests.pkg-config.defaultPkgConfigPackages.tests-combined.x86_64-linux’: error: pkg-config module `recurseForDerivations` is not defined to be a derivation. Please check the attribute value for `recurseForDerivations` in `pkgs/top-level/pkg-config-packages.nix` in Nixpkgs. ``` This is also causing eval errors on Hydra: https://hydra.nixos.org/jobset/nixos/pr-209870-gcc-external-bootstrap#tabs-errors Let's filter out `recurseForDerivations=true` from the attrset, since it exists mainly as a flag to signal special handling when recursing.

When wrapping `clang` and using a `gccForLibs` whose `libgcc` is in its own output (rather than the `lib` output), this commit will adds `-L${gccForLibs.libgcc}/lib` to `cc-ldflags`. If that flag is not added, `firefox` will fail to compile because it invokes `clang-wrapper` with `-fuse-ld=lld` and passes `-lgcc_s` to `lld`, but does not tell `lld` where to find `libgcc_s.so`. In that situation, firefox will fail to link.

The Nix-driven bootstrap of gcc expects that `stdenv.cc.cc` has a `version` attribute, except if `stdenv.cc` is the `bootstrapFiles`. This commit causes `ccache-links`'s `cc-wrapper` to `inherit version` in order to satisfy that requirement. Without this commit, ofborg CI will fail. Co-authored-by: Sandro <sandro.jaeckel@gmail.com>

This commit has no effect on eval. It simply factors out a common subexpression.

This commit has no effect on eval. It simply reorganizes the `gcc11` and `gcc12` expressions so they apply a list of `overrideAttrs`. The list is currently empty.

python310Packages.orjson: 3.8.6 -> 3.8.9

https://github.com/cython/cython/blob/0.29.34/CHANGES.rst

Lots of python packages seem to ship their source distributions with generated code. In recent cython versions there is a way to force a regeneration of these files and using it sounds generally sounds like a good thing. If it turns out, that this causes problems on individual packages, setting `dontForceRegenCython` will prevent the regeneration. Added in 3.0.0a11 and backported to 2.9.34, so both cython versions we ship right now support this flag.

@Ericson2314

#### Summary By default, when you type `make`, GCC will compile itself three times. This PR inhibits that behavior by configuring GCC with `--disable-bootstrap`, and reimplements the triple-rebuild using Nix rather than `make`/`sh`. #### Immediate Benefits - Allow `gcc11` and `gcc12` on `aarch64` (without needing new `bootstrapFiles`) - Faster stdenv rebuilds: the third compilation of gcc (i.e. stageCompare) is no longer a `drvInput` of the final stdenv. This allows Nix to build stageCompare in parallel with the rest of nixpkgs instead of in series. - No more copying `libgcc_s` out of the bootstrap-files or other derivations - No more Frankenstein compiler: the final gcc and the libraries it links against (mpfr, mpc, isl, glibc) are all built by the same compiler (xgcc) instead of a mixture of the bootstrapFiles' compiler and xgcc. - No more [static lib{mpfr,mpc,gmp,isl}.a hack] - Many other small `stdenv` hacks eliminated - `gcc` and `clang` share the same codepath for more of `cc-wrapper`. #### Future Benefits - This should allow using a [foreign] `bootstrap-files` so long as `hostPlatform.canExecute bootstrapFiles`. - This should allow each of the libraries that ship with `gcc` (lib{backtrace, atomic, cc1, decnumber, ffi, gomp, iberty, offloadatomic, quadmath, sanitizer, ssp, stdc++-v3, vtv}) to be built in separate (one-liner) derivations which `inherit src;` from `gcc`, much like #132343 #### Incorporates - #210004 - #36948 (unreverted) - #210325 - #210118 - #210132 - #210109 - #213909 - #216136 - #216237 - #210019 - #216232 - #216016 - #217977 - #217995 #### Closes - Closes #108305 - Closes #108111 - Closes #201254 - Closes #208412 #### Credits This project was made possible by three important insights, none of which were mine: 1. @Ericson2314 was the first to advocate for this change, and probably the first to appreciate its advantages. Nix-driven (external) bootstrap is "cross by default". 2. @trofi has figured out a lot about how to get gcc to not mix up the copy of `libstdc++` that it depends on with the copy that it builds, by moving the `bootstrapFiles`' `libstdc++` into a [versioned directory]. This allows a Nix-driven bootstrap of gcc without the final gcc would still having references to the `bootstrapFiles`. 3. Using the undocumented variable [`user-defined-trusted-dirs`] when building glibc. When glibc `dlopen()`s `libgcc_s.so`, it uses a completely different and totally special set of rules for finding `libgcc_s.so`. This trick is the only way we can put `libgcc_s.so` in its own separate outpath without creating circular dependencies or dependencies on the bootstrapFiles. I would never have guessed to use this (or that it existed!) if it were not for a [comment in guix] which @Mic92 [mentioned]. My own role in this PR was basically: being available to go on a coding binge at an opportune moment, so we wouldn't waste a [crisis]. [aarch64-compare-ofborg]: https://github.com/NixOS/nixpkgs/pull/209870/checks?check_run_id=10662822938 [amd64-compare-ofborg]: https://github.com/NixOS/nixpkgs/pull/209870/checks?check_run_id=10662825857 [nonexistent sysroot]: #210004 [versioned directory]: #209054 [`user-defined-trusted-dirs`]: https://sourceware.org/legacy-ml/libc-help/2013-11/msg00026.html [comment in guix]: https://github.com/guix-mirror/guix/blob/5e4ec8218142eee8e6e148e787381a5ef891c5b1/gnu/packages/gcc.scm#L253 [mentioned]: #210112 (comment) [crisis]: #108305 [foreign]: #170857 (comment) [static lib{mpfr,mpc,gmp,isl}.a hack]: https://github.com/NixOS/nixpkgs/blob/2f1948af9c984ebb82dfd618e67dc949755823e2/pkgs/stdenv/linux/default.nix#L380

Now that we've dropped the gcc-links-statically-to-lib{isl,mpfr,mpc,gmp} hack, our gcc needs libisl.so. Let's add it to the bootstrap-files.

We do not want to preserve the symlinks from libgcc_s, since they point to another outpath. We want to copy from that outpath rather than link to it.

…ibstdc++} Our bootstrap-files unpacker has always relied on a lot of unstated assumptions, one of them being that every library has a DT_NEEDED for librt.so, so patchelf'ing something into the RUNPATH into librt.so means that it will be searched for every library load in all of the bootstrap-files. Unfortunately that assumption is not true for libgcc. This causes problems, because patchelf links against libgcc (and against libstdc++, which links against libgcc). So we can't use patchelf on libgcc, because it needs libgcc, so patchelf doesn't work until libgcc is patchelfed. The robust solution here is to use static linking for the copy of patchelf that is shipped with the bootstrap-files. We don't have to go all the way to a statically linked libc; just -static-libgcc and -static-libstdc++ are enough to break the circular dependency.

This commit adds `gcc/common/checksum.nix`, which contains code common to both gcc11 and gcc12, implementing the `enableChecksum` feature. When gcc's built-in bootstrap (`--enable-bootstrap`) is used, gcc compiles itself three times and compares a hash of the unlinked `.o` files from the second and third compilation. The `enableChecksum=true` parameter performs the same comparison as part of the `postInstall` phase. Notably, `enableChecksum=true` can be used with `enableBootstrap=false`. Co-authored-by: Sandro <sandro.jaeckel@gmail.com>

This commit adds a derivation `gcc-stageCompare` to `pkgs/test/stdenv/default.nix`. It is important to always build this derivation whenever building `stdenv`! Because we are using a Nix-driven bootstrap instead of gcc's built-in `--enable-bootstrap`, the `gcc` derivation no longer performs the post-self-compilation sanity check. You must build this derivation in order to perform that sanity check. The major benefit of this new approach is that the sanity check (which involves a third compilation of gcc) can be performed *concurrently* with all packages that depend on `stdenv`, rather than serially. Since `stdenv` has very little derivation-level parallelism it cannot take advantage of more than one or perhaps two builders. If you have three or more builders this commit will reduce the time-to-rebuild-stdenv by around 20% (one of three gcc rebuilds is removed from the critical path, and stdenv's build time is dominated by roughly 3*gcc + 1*binutils + 1*bison-test-suite). Co-authored-by: Sandro <sandro.jaeckel@gmail.com>

The Nix-driven bootstrap of gcc resulted in some changes to the structure of the `libgccjit` outpaths, and also added an additional output (`libgcc`) to `gcc`. This commit makes the corresponding changes in the `emacs` derivation in order to not break emacs. Emacs is the only user of `libgccjit` in nixpkgs at the moment.

...into staging

As a result of 8f45423 ("libpcap: build with libnl"), the static build started to fail, because iptables didn't know to link with libnl. The patch makes iptables use pkg-config to find libpcap, which means it knows about other libraries that need to be linked when doing a static build.

Release for Vulkan SDK 1.3.243

…cc-bootstrap

...into staging

https://github.com/django/asgiref/blob/3.6.0/CHANGELOG.txt

https://docs.djangoproject.com/en/4.2/releases/4.2/

Tests still fail on darwin because of missing timezone information, no idea how to resolve that. TZDIR does work on Linux.

This was previously propagated by asgiref, which is not the case anymore with version 3.6.0.

Fixes infinite recursions on apps that override django to django_4.

Breaks nixpkgs usage when aliases are disabled.

freeipa: Don't use alias for python-ldap

...into staging

…rrect input ...into staging

...into staging

I hope r-ryantm will link this correctly next time. Their tags/releases on GitHub don't have the information.

...into staging

In GitHub issue #221592 I found that virt-manager was not showing PCI info. Tracking the issue down points to this library, which is consumed by libvirt. libpciaccess was reading from the default path of /usr/share/hwdata/pci.ids, which will likely not exist on NixOS. Instead of using the hard-coded path, change the libpciaccess package to depend on hwdata at runtime and to be configured with the hwdata share path. Updated the generation script, as well as committed the newly generated changes.

python3Packages.pytest-rerunfailures: 11.1.1 → 11.1.2

python310Packages.cython: 0.29.33 -> 0.29.34; Add setup hook to force regeneration of generated code in sdists

python310Packages.certbot: 2.3.0 -> 2.4.0

python310Packages.asgiref: 3.5.2 -> 3.6.0; python310Packages.django: 4.1.7 -> 4.7.0 and enable tests

harfbuzz: 7.0.1 -> 7.1.0

curl: add support for Rustls backend

qt5: regularly scheduled patchset update

…roducibility python3Packages.testpath: fix build reproducibility

dates are embedded arch does the same thing https://github.com/archlinux/svntogit-community/blob/4858f1493d6eaf5357df10a768d41adc116991b7/trunk/PKGBUILD#L22

python310Packages.distlib: remove unnecessary and unreproducible exe's

vulkan-sdk: 1.3.239 -> 1.3.243

fixes #223776

Changelog: https://go.dev/doc/devel/release#go1.20

Without the change when I attempt to built `nixpkgs` with weekly `gcc-13` (it pulls in `flex` as a build input`) I am getting build failure related to glibc mix caused by glibc loading: ...-binutils-patchelfed-ld-2.40/bin/ld: ...-xgcc-13.0.0/libexec/gcc/x86_64-unknown-linux-gnu/13.0.1/liblto_plugin.so: error loading plugin: ...-bootstrap-tools/lib/libpthread.so.0: undefined symbol: __libc_vfork, version GLIBC_PRIVATE The change disables LTO plugin entirely to avoid loading of `glibc` mix.

…fixup python3Packages.testpath: fixup optional -> optionalString

xgcc: avoid libc.so mix between gcc and binutils-ld linker plugin

qt5/qtwayland: drop merged patch

Currently zink can't find libvulkan.so, so it won't work when you try to use it, you can verify that using strace, patching RPATH fixes this. closes #187791

https://cryptography.io/en/latest/changelog/#v40-0-1

wayland: hotfix

…ksum output on Darwin

The build system generates the file "hitables.c" with the program "./himktables" that is also compiled by the build system. This does not work when cross-compiling since this program is built for the wrong architecture. We already use a natively built copy of texlive.bin.core for various other tools (like tangle, weave), so this change just adds himktables to the this native copy and uses this program in the cross build.

The stage before `xgcc` creates the first compiled patchelf (i.e. not from bootstrapFiles). The `xgcc` stage was inadvertently switching *back* to using the patchelf *from* the bootstrapFiles. The first commit in this PR adds self-checking comments (assertions) to make it clear where each stage's patchelf comes from. The second commit fixes the bug, and updates the self-checking comments.

texlive.bin.core{,-big}: fix cross compilation

...into staging-next

…idity gcc: do not --disable-bootstrap, create libgcc output, or create checksum output on Darwin

...into staging-next

/cc PR #223238

mpg123: 1.31.2 -> 1.31.3

I broke `pkgsMusl` with #209870. Something odd is happening with `xgcc` (the temporary compiler that should be used only to compile `gcc`, although we are using it to compile a temporary `patchelf` too) and `libstdc++`. The temporary fix in this commit is to use `-static-libstdc++` for the ephemeral `patchelf` built by `xgcc`. It isn't pretty, but it appears to work. Incorporates: - #224945

python310Packages.cryptography: 39.0.1 -> 40.0.1

python310Packages.{aiohttp,anyio,passlib}: speed test up with pytest-xdist

…gsMusl

> unable to copy file #224962 (comment)

As suggested here: #223303 (review) These parentheses are unnecessary. No change to eval.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

texlive/bin: remove unnecessary parentheses #225035

texlive/bin: remove unnecessary parentheses #225035

Commits on Mar 27, 2023

Commits on Mar 28, 2023

Commits on Mar 29, 2023

Commits on Mar 30, 2023

Commits on Mar 31, 2023

Commits on Apr 1, 2023

Commits on Apr 2, 2023

Commits on Apr 3, 2023

Commits on Apr 4, 2023

Commits on Apr 5, 2023

Commits on Apr 6, 2023