This is a hint that mentions the feature #105910 but that is not yet
merged. This is very confusing and since it there is no progress with
that merge we should remove the reference
Reverts NixOS/nixpkgs#269620
- eab0837b68 caused a mass-rebuild on master
- self-merge on a critical package without review and not waiting for the active owner team
Below are the reverts of the commits from that PR
Revert "systemd: migrate to by-name"
This reverts commit 33d2a40d67.
Revert "systemd: add meta.longDescription"
This reverts commit 7c588d141d.
Revert "systemd: cosmetic rewording of code"
This reverts commit d91b8d9fcb.
Revert "systemd: cosmetic rewording of comments"
This reverts commit bc563998c0.
Revert "systemd: remove some redundancy on mesonFlags"
This reverts commit eab0837b68.
Revert "systemd: use lib.meson* functions"
This reverts commit 1129756b1a.
This adds two kernel config settings, one to make MediaTek network
modules visible (so the modules get built) and one to support the
SoC-integrated MT7915E variant in the module.
This gets the MT798X series of SoCs working with a stock NixOS kernel.
This re-introduces the old stable ZFS version we had in the past following
the many predicted issues of ZFS 2.2.x series, that is much more stable
than any further ZFS version at the moment.
I am also removing myself from maintenance of any further ZFS versions as I am
planning to quit ZFS maintenance at some point.
In the meantime, for users like me who depend on ZFS for critical operations, here is a ZFS version
that is known to work for LTS kernels.
The Nixpkgs documentation on the linux kernel builders focused on
using and extending kernels that were already packaged, but never
mentioned that it's possible to also build a kernel almost "from
scratch".
The NixOS documentation went a bit deeper on manual linux kernel
configs, but that information wasn't particularly NixOS-specific.
This commit consolidates the information related to building the
kernel on Nixpkgs's documentation, while keeping any additional
NixOS-specific information on NixOS's documentation.
An additional README.md was created for contributor-facing
documentation.
Fixes the build of pkgsStatic.libcap, as it was trying to link to the
dinamic libc. From libcap-2.69/progs/Makefile:
...
ifeq ($(LIBCSTATIC),yes)
LDFLAGS = --static
DEPS = ../libcap/libcap.a
else
# For this build variant override the LDFLAGS to link statically from
# libraries within the build tree. If you never want this, use make
# DYNAMIC=yes . Note, we can't reliably link statically against glibc
# becasuse of https://sourceware.org/bugzilla/show_bug.cgi?id=12491 .
LDFLAGS = -Wl,-Bstatic
LDFLAGS_SUFFIX = -Wl,-Bdynamic
DEPS = ../libcap/libcap.a
endif
...
https://hydra.nixos.org/build/241116326/nixlog/1
```
build flags: SHELL=/nix/store/x1xxsh1gp6y389hyl40a0i74dkxiprl7-bash-5.2-p15/bin/bash PREFIX=\$\(out\) CC=cc
cc -F/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include -fblocks -c -o CoreSymbolication.o CoreSymbolication.c
In file included from CoreSymbolication.c:1:
./CoreSymbolication.h:393:1: error: type specifier missing, defaults to 'int'; ISO C99 and later do not support implicit int [-Wimplicit-int]
CSSymbolOwnerSetTransientUserData(CSSymbolOwnerRef owner, uint32_t gen);
^
int
1 error generated.
```
Also submitted patch upstream at
https://github.com/matthewbauer/CoreSymbolication/pull/1
ZHF: #265948
stdenv.targetPlatform really shouldn't be used by software that
doesn't generate or manipulate binaries. I reviewed all uses of
targetPlatform outside of pkgs/development/compilers and pkgs/stdenv
and replaced those which weren't involved in something which fits
these criteria.
tags not updated since 2019. updating to last commit puts nixpkgs on par
with debian/ubuntu/Devuan/Kali distributions.
update homepage to github (same as debian) as old page
https://codemonkey.org.uk/projects/trinity/ is not reachable.
