text:
nixos-21.11.336103.40ef692a55b: linuxPackages_rt_5_10 fails to build

Describe the bug
Real-time kernel fails to build with the latest release (2022-02-22T13:35:20Z) of “nixos” channel:
https://releases.nixos.org/nixos/21.11/nixos-21.11.336103.40ef692a55b
GOT: make[1]: Leaving directory '/build/linux-5.10.78/build'
GOT: make: Leaving directory '/build/linux-5.10.78'
error: unused option: BPF_UNPRIV_DEFAULT_OFF
warning: unused option: DEBUG_STACKOVERFLOW
warning: unused option: EXT4_ENCRYPTION
warning: unused option: F2FS_FS_ENCRYPTION
warning: unused option: RCU_PERF_TEST
warning: unused option: RT_GROUP_SCHED
warning: unused option: TRANSPARENT_HUGEPAGE
warning: unused option: TRANSPARENT_HUGEPAGE_ALWAYS
warning: unused option: TRANSPARENT_HUGEPAGE_MADVISE
warning: unused option: XEN_SCRUB_PAGES
warning: unused option: XEN_SELFBALLOONING
warning: unused option: XEN_STUB
warning: unused option: XEN_TMEM
builder for '/nix/store/h19rqc84lw3dkc5al9vih30fg31cbkak-linux-config-5.10.78-rt55.drv' failed with exit code 255
cannot build derivation '/nix/store/9yhc7mjhhrxvik00jkqsd8qr3b54h56m-linux-5.10.78-rt55.drv': 1 dependencies couldn't be built

A clear and concise description of what the bug is.
Steps To Reproduce

Set nixos channel to https://releases.nixos.org/nixos/21.11/nixos-21.11.336103.40ef692a55b (latest release at this moment)
boot.kernelPackages = lib.mkForce pkgs.linuxPackages_rt_5_10
nixos-rebuild

Expected behavior
Real-time kernel builds and boots successfully.
Additional context
My config where this real-time kernel is used (just in case): https://github.com/unclechu/nixos-config/blob/e739f03cadd43076255c9e004c19d8fc2fa7c9ff/configuration-audio.nix
Notify maintainers
@TredwellGit
@ma27
@nequissimus
@alyssais
@thoughtpolice
Metadata
$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.16.5, NixOS, 21.11 (Porcupine)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.16`
 - channels(root): `"nixos, nixos-unstable"`
 - channels(wenzel): `""`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

https://github.com/NixOS/nixpkgs/pull/161287

https://github.com/NixOS/nixpkgs/pull/161592

authors: TredwellGit unclechu


text:
Kitty: EGL: failed to get EGL display: Success

Describe the bug
Running attempting to run kitty in sway the following error is returned

I'm assuming this is an error in the kitty or sway it packaged
Additional context
Currently running in QEMU using the QXL video driver
Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[will@qemu:~]$ nix-shell -p nix-info --run "nix-info -m"

usually a reboot fixes it for me

usually a reboot fixes it for me

This persist after multiple reboots, I've tried installing the glfw-wayland and egl-wayland packages and it doesn't seem to solve it.

It appears it was an issue with the vm I was in not having proper opengl support.

For me this tool solved my issue with the exact same error message. Seems like a Nix OpenGL Issue https://github.com/guibou/nixGL

Having the same issue after updating my nixos, though OpenGL seems to be installed completely fine. Problem persists after a reboot.

+1

yeah running into this now as well on Arch w/ Hyprland on an intel Arc. Haven't had time to attempt to resolve just yet

Thanks @igorgue. I use AMD's integrated graphics and simply downgraded the mesa package using the pacman cache.

@Hariss-Gills I solved this later by installing Kitty from the arch repos instead of their official binary, with that I was able to update.

source: gharchive/issue

authors: Arroquw Hariss-Gills WilliamBehrens igorgue keydon kstaniek rjohnsondev teto

repo: NixOS/nixpkgs

license: MIT

license_type: permissive

license_source: github-api


text:
vim won't build on OSX

vim directly or indirectly depends on clang, which means the wrong cc is in scope. useChroot doesn't help.
installing `vim-7.4.131'
these derivations will be built:
  /nix/store/5b3i76s5zf3w9b7kn4lklvxjrvk90rv7-vim-7.4.131.drv
building path(s) `/nix/store/vchr56qb7sv746l4phdspid70701a895-vim-7.4.131'
building /nix/store/vchr56qb7sv746l4phdspid70701a895-vim-7.4.131
unpacking sources
unpacking source archive /nix/store/zmsdkkipckqk5ddhllz9pxk1cvcq77q5-hg-archive
source root is hg-archive
patching sources
configuring
configure flags: --prefix=/nix/store/vchr56qb7sv746l4phdspid70701a895-vim-7.4.131 --enable-multibyte --enable-nls
configure: creating cache auto/config.cache
checking whether make sets $(MAKE)... yes
checking for gcc... no
checking for cc... cc
checking whether the C compiler works... no
configure: error: in `/private/var/folders/fl/sv20mnl95w7114pq00w2y74r0000gp/T/nix-build-vim-7.4.131.drv-3/hg-archive/src':
configure: error: C compiler cannot create executables
See `config.log' for more details.
note: keeping build directory `/private/var/folders/fl/sv20mnl95w7114pq00w2y74r0000gp/T/nix-build-vim-7.4.131.drv-3'
builder for `/nix/store/5b3i76s5zf3w9b7kn4lklvxjrvk90rv7-vim-7.4.131.drv' failed with exit code 77
error: build of `/nix/store/5b3i76s5zf3w9b7kn4lklvxjrvk90rv7-vim-7.4.131.drv' failed

config.log:
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by configure, which was
generated by GNU Autoconf 2.65.  Invocation command line was

  $ auto/configure --prefix=/nix/store/vchr56qb7sv746l4phdspid70701a895-vim-7.4.131 --enable-multibyte --enable-nls --srcdir=. --cache-file=auto/config.cache

## --------- ##
## Platform. ##
## --------- ##

hostname = Toothless
uname -m = x86_64
uname -r = 13.2.0
uname -s = Darwin
uname -v = Darwin Kernel Version 13.2.0: Thu Apr 17 23:03:13 PDT 2014; root:xnu-2422.100.13~1/RELEASE_X86_64

/usr/bin/uname -p = i386
/bin/uname -X     = unknown

/bin/arch              = unknown
/usr/bin/arch -k       = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo      = Mach kernel version:
	 Darwin Kernel Version 13.2.0: Thu Apr 17 23:03:13 PDT 2014; root:xnu-2422.100.13~1/RELEASE_X86_64
Kernel configured for up to 8 processors.
4 processors are physically available.
8 processors are logically available.
Processor type: i486 (Intel 80486)
Processors active: 0 1 2 3 4 5 6 7
Primary memory available: 8.00 gigabytes
Default processor set: 247 tasks, 1223 threads, 8 processors
Load average: 2.43, Mach factor: 5.56
/bin/machine           = unknown
/usr/bin/oslevel       = unknown
/bin/universe          = unknown

PATH: /nix/store/5scg4nx9nq9b1a46iqkvvm4x9bivqsda-gettext-0.18.2/bin
PATH: /nix/store/1rgpg53kqa698bvyna5x2fr9r5rvnyzn-ncurses-5.9/bin
PATH: /nix/store/nhk3j4xcr7iqvla5h57b6dc2i5xcsd9f-pkg-config-0.23/bin
PATH: /nix/store/v19iawd8phiwxn59b00164g386jg1i48-clang-wrapper-wrapper-3.3/bin
PATH: /nix/store/akdgfdaff3sqvfwhbnh8ba8xazminwrs-coreutils-8.21/bin
PATH: /nix/store/p8sjbl93y3ir0svwvm92wxrfnh5axcjw-findutils-4.4.2/bin
PATH: /nix/store/ljc2d177lznaip0i7n2fwqgcb2v4iqk7-diffutils-3.3/bin
PATH: /nix/store/3gwzx8fyxqyxhj5xl5sskxnlgvc55kpj-gnused-4.2.2/bin
PATH: /nix/store/s17iksifwg0sggbh110f2p2hgwbv4zx3-gnugrep-2.14/bin
PATH: /nix/store/ywsg6qw2kpyhiz71mlqxr1sbacvyjmmh-gawk-4.1.0/bin
PATH: /nix/store/1bix04wrkbv5vwgkgwkmdncdcb6wkcdz-gnutar-1.27.1/bin
PATH: /nix/store/k4cd2ya7fhk4lg9hbxaqnx5qy3vk8nq8-gzip-1.6/bin
PATH: /nix/store/xqlw8lnly0s27ijyn5zd8s2j5s16n516-bzip2-1.0.6/bin
PATH: /nix/store/wa1ixqf3k40v2cjhm0xxjs1czyj4bprd-gnumake-3.82/bin
PATH: /nix/store/85h1r887x7raf97l1invbm9zg1c1sfxr-bash-4.2-p45/bin
PATH: /nix/store/ar2xaivm56y7g4vhc0k1bx18awnp6dp3-patch-2.7.1/bin
PATH: /nix/store/y2lsw31p99nyxqzs2cb6hb97x7dp2pnq-xz-5.0.5/bin
PATH: /nix/store/2a1rqajz3g5jqqxbhdapha26pgg4izhs-clang-wrapper-3.3/bin
PATH: /nix/store/v0lrjkxx44x763g4qngdmgrqca6cmzdw-native-darwin-cctools-wrapper/bin
PATH: /nix/store/akdgfdaff3sqvfwhbnh8ba8xazminwrs-coreutils-8.21/bin

## ----------- ##
## Core tests. ##
## ----------- ##

configure:2490: creating cache auto/config.cache
configure:2568: checking whether make sets $(MAKE)
configure:2590: result: yes
configure:2648: checking for gcc
configure:2678: result: no
configure:2741: checking for cc
configure:2762: found /nix/store/v19iawd8phiwxn59b00164g386jg1i48-clang-wrapper-wrapper-3.3/bin/cc
configure:2785: result: cc
configure:2904: checking for C compiler version
configure:2913: cc --version >&5
clang version 3.3 (tags/RELEASE_33/final)
Target: x86_64-apple-darwin13.2.0
Thread model: posix
configure:2924: $? = 0
configure:2913: cc -v >&5
clang version 3.3 (tags/RELEASE_33/final)
Target: x86_64-apple-darwin13.2.0
Thread model: posix
configure:2924: $? = 0
configure:2913: cc -V >&5
clang-3.3: error: unsupported option '-V -B/nix/store/h36hbxyv22gnh2pldv1wahx3dhn3r98l-gcc-apple-4.2.1.5666.3/lib/gcc/x86_64-apple-darwin10/4.2.1'
clang-3.3: error: no input files
configure:2924: $? = 1
configure:2913: cc -qversion >&5
clang-3.3: error: no input files
configure:2924: $? = 1
configure:2944: checking whether the C compiler works
configure:2966: cc    conftest.c  >&5
impure path `/var/empty' used in link
clang-3.3: error: linker command failed with exit code 1 (use -v to see invocation)
configure:2970: $? = 1
configure:3008: result: no
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE_URL ""
| #define UNIX 1
| /* end confdefs.h.  */
|
| int
| main ()
| {
|
|   ;
|   return 0;
| }
configure:3013: error: in `/private/var/folders/fl/sv20mnl95w7114pq00w2y74r0000gp/T/nix-build-vim-7.4.131.drv-3/hg-archive/src':
configure:3017: error: C compiler cannot create executables
See `config.log' for more details.

## ---------------- ##
## Cache variables. ##
## ---------------- ##

ac_cv_env_CC_set=
ac_cv_env_CC_value=
ac_cv_env_CFLAGS_set=
ac_cv_env_CFLAGS_value=
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_LIBS_set=
ac_cv_env_LIBS_value=
ac_cv_env_XMKMF_set=
ac_cv_env_XMKMF_value=
ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_prog_CC=cc
ac_cv_prog_make_make_set=yes

## ----------------- ##
## Output variables. ##
## ----------------- ##

AWK=''
CC='cc'
CFLAGS=''
CPP=''
CPPFLAGS=''
CPP_MM=''
DEFS=''
DEPEND_CFLAGS_FILTER=''
ECHO_C='\c'
ECHO_N=''
ECHO_T=''
EGREP=''
EXEEXT=''
EXNAME=''
GNOME_INCLUDEDIR=''
GNOME_LIBDIR=''
GNOME_LIBS=''
GREP=''
GTK_CFLAGS=''
GTK_LIBNAME=''
GTK_LIBS=''
GUITYPE=''
GUI_INC_LOC=''
GUI_LIB_LOC=''
GUI_X_LIBS=''
HANGULIN_OBJ=''
HANGULIN_SRC=''
INSTALL_LANGS=''
INSTALL_TOOL_LANGS=''
LDFLAGS=''
LIBOBJS=''
LIBS=''
LINK_AS_NEEDED=''
LTLIBOBJS=''
LUA_CFLAGS=''
LUA_LIBS=''
LUA_OBJ=''
LUA_PRO=''
LUA_SRC=''
MAKEMO=''
MOTIF_LIBNAME=''
MSGFMT=''
MZSCHEME_CFLAGS=''
MZSCHEME_EXTRA=''
MZSCHEME_LIBS=''
MZSCHEME_MZC=''
MZSCHEME_OBJ=''
MZSCHEME_PRO=''
MZSCHEME_SRC=''
NARROW_PROTO=''
NETBEANS_OBJ=''
NETBEANS_SRC=''
OBJEXT=''
OS_EXTRA_OBJ=''
OS_EXTRA_SRC=''
PACKAGE_BUGREPORT=''
PACKAGE_NAME=''
PACKAGE_STRING=''
PACKAGE_TARNAME=''
PACKAGE_URL=''
PACKAGE_VERSION=''
PATH_SEPARATOR=':'
PERL_CFLAGS=''
PERL_LIBS=''
PERL_OBJ=''
PERL_PRO=''
PERL_SRC=''
PKG_CONFIG=''
PYTHON3_CFLAGS=''
PYTHON3_CONFDIR=''
PYTHON3_LIBS=''
PYTHON3_OBJ=''
PYTHON3_SRC=''
PYTHON_CFLAGS=''
PYTHON_CONFDIR=''
PYTHON_GETPATH_CFLAGS=''
PYTHON_LIBS=''
PYTHON_OBJ=''
PYTHON_SRC=''
QUOTESED=''
RUBY_CFLAGS=''
RUBY_LIBS=''
RUBY_OBJ=''
RUBY_PRO=''
RUBY_SRC=''
SET_MAKE=''
SHELL='/bin/sh'
SNIFF_OBJ=''
SNIFF_SRC=''
STRIP=''
TAGPRG=''
TCL_CFLAGS=''
TCL_LIBS=''
TCL_OBJ=''
TCL_PRO=''
TCL_SRC=''
VIEWNAME=''
VIMNAME=''
WORKSHOP_OBJ=''
WORKSHOP_SRC=''
XCODE_SELECT=''
XMKMF=''
X_CFLAGS=''
X_EXTRA_LIBS=''
X_LIB=''
X_LIBS=''
X_PRE_LIBS=''
ac_ct_CC=''
bindir='${exec_prefix}/bin'
build_alias=''
compiledby=''
datadir='${datarootdir}'
datarootdir='${prefix}/share'
docdir='${datarootdir}/doc/${PACKAGE}'
dogvimdiff=''
dovimdiff=''
dvidir='${docdir}'
exec_prefix='NONE'
host_alias=''
htmldir='${docdir}'
includedir='${prefix}/include'
infodir='${datarootdir}/info'
libdir='${exec_prefix}/lib'
libexecdir='${exec_prefix}/libexec'
line_break=''
localedir='${datarootdir}/locale'
localstatedir='${prefix}/var'
mandir='${datarootdir}/man'
oldincludedir='/usr/include'
pdfdir='${docdir}'
prefix='/nix/store/vchr56qb7sv746l4phdspid70701a895-vim-7.4.131'
program_transform_name='s,x,x,'
psdir='${docdir}'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
shrpenv=''
sysconfdir='${prefix}/etc'
target_alias=''
vi_cv_path_lua=''
vi_cv_path_luajit=''
vi_cv_path_mzscheme=''
vi_cv_path_perl=''
vi_cv_path_plain_lua=''
vi_cv_path_python3=''
vi_cv_path_python=''
vi_cv_path_ruby=''
vi_cv_path_tcl=''
vi_cv_perllib=''
xmkmfpath=''

## ----------- ##
## confdefs.h. ##
## ----------- ##

/* confdefs.h */
#define PACKAGE_NAME ""
#define PACKAGE_TARNAME ""
#define PACKAGE_VERSION ""
#define PACKAGE_STRING ""
#define PACKAGE_BUGREPORT ""
#define PACKAGE_URL ""
#define UNIX 1

configure: exit 77

vim builds again on master.

authors: gridaphobe joelteon


text:
docker-17.06.0-ce broken build (w/o sandbox)

Issue description
The build is broken if sandboxing is disabled: it attempts to access /tmp when generating the manpages.
See the nix-build output for the exact error message.
Breaking commit: ec570448a036095e181b33b978d71dfc61e56202 by @vdemeester
Note that enabling sandboxing system-wide does allow the build to succeed.
Steps to reproduce
Run nix-build -A docker on unstable (or nixos-rebuild switch with the docker service enabled and an older version of docker).
Technical details

System: 17.09.git.823fd92 (Hummingbird)
Nix version: nix-env (Nix) 1.11.12
Nixpkgs version: "17.09.git.823fd928e6"
Sandboxing enabled: no

@calvertvl arf I shouldn't have use go install there.. will fix 👼

authors: calvertvl vdemeester


text:
Plymouth suddenly omits key-presses on password entry

Describe the bug
For a few days, when booting my amd computer with plymouth enabled I can't enter my passphrase anymore.
Pushing keys multiple times eventually end up in one key-press being accepted. Booting with nosplash instead of splash suddenly has no more issues with keyboard entries.
Steps To Reproduce
Steps to reproduce the behavior:
NixOS Unstable

Setting to initrd.systemd.enable = true; and plymouth.enable = true;

  boot = {
	  consoleLogLevel = 0;
	  initrd.compressor = "zstd";
          initrd.systemd = {
            enable = true;
            network.enable = true;
          };
          loader.systemd-boot = {
            enable = true;
            configurationLimit = 32;
          };
	  initrd.verbose = false;
	  kernelParams = [ "udev.log_level=3" ];
	  plymouth.enable = true;
	  plymouth.theme = "solar";
  };

Rebooting with a LUKS/ZFS Passphrase
Key-presses are omitted

Expected behavior
Every key I hit will be used.

@cillianderoiste @dasj19 @lilyinstarlight ?@K900?
Metadata

system: "x86_64-linux"
host os: Linux 6.6.10, NixOS, 24.05 (Uakari), 24.05pre567746.317484b1ead8
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.18.1
channels(pl): "nixos"
channels(root): "nixos"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Add a :+1: reaction to issues you find important.

Upstream bug report https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/236


text:
Update request: zotero 7.0.0 → 7.0.3

Package name: zotero
Latest released version: 7.0.3

Current version on the unstable channel: 7.0.0
Current version on the stable/release channel: 6.0.35

[x] Checked the nixpkgs pull requests

Notify maintainers

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

Closing because #338458 was merged.

authors: sstubbs toonn


text:
In 18.03 (beta), a terminal is spawn at startup with lightdm

Issue description
When using the lightdm display manager without a desktop manager, a xterm terminal is spawn at startup.
In 18.03:
       ├─lightdm─┬─X───5*[{X}]
        │         ├─lightdm─┬─9mf28jw5dzqbg7h─┬─.xterm-wrapped───zsh
        │         │         │                 ├─9mf28jw5dzqbg7h───tee
        │         │         │                 ├─taffybar-linux-───5*[{taffybar-linux-}]
        │         │         │                 └─xmonad-x86_64-l─┬─.albert-wrapped───73*[{.albert-wrapped}]
        │         │         │                                   ├─.emacsclient-wr
        │         │         │                                   ├─.termite-wrappe─┬─zsh───pstree
        │         │         │                                   │                 └─{.termite-wrappe}
        │         │         │                                   └─stalonetray
        │         │         └─2*[{lightdm}]
        │         └─2*[{lightdm}]

The exact same configuration with 17.09 would give:
        ├─lightdm─┬─X───5*[{X}]
        │         ├─lightdm─┬─2d597d9iv29z0al─┬─taffybar-linux-───5*[{taffybar-linux-}]
        │         │         │                 └─xmonad-x86_64-l─┬─.albert-wrapped───16*[{.albert-wrapped}]
        │         │         │                                   ├─.termite-wrappe─┬─zsh───pstree
        │         │         │                                   │                 └─2*[{.termite-wrappe}]
        │         │         │                                   └─stalonetray
        │         │         └─2*[{lightdm}]
        │         └─2*[{lightdm}]

Steps to reproduce
Install nixos 18.03 (beta)
Using this configuration:
# desktop ui configuration
{ ... }:

{
  services.xserver = {
    displayManager = {
      lightdm = {
        enable = true;
        autoLogin.user= "vagrant";
        autoLogin.enable= true;
      };
      sessionCommands = ''
      '';
     };
  };
  services.xserver.desktopManager.default = "none";
  services.xserver.windowManager = {
    xmonad.enable = true;
    xmonad.extraPackages = hpkgs: [
      hpkgs.xmonad-contrib
      hpkgs.xmonad-extras
    ];
    default = "xmonad";
  };
}

Important note
This configuration services.xserver.desktopManager.default = "none"; was necessary in 17.09 to avoid this exact same issue. So if I remove that line, I have got the same problem in 17.09.
In 18.03 the line does not seem to make any difference anymore.
Technical details
λ ~ → nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 4.14.24, NixOS, 18.03pre130932.cc4677c36ee (Impala)`
 - multi-user?: `yes`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.0`
 - channels(root): `"nixos"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs`

Possible culprit
https://github.com/NixOS/nixpkgs/commit/6b9a99e55d537c27c5b384d58c997839a0519df9#diff-137f2d57afcbbbda7a486ad228be43de

@ElvishJerricco do you think your commit could be the cause of the change in behavior from 17.09 to 18.03 ?

Possibly related - https://github.com/NixOS/nixpkgs/pull/31268, specifically see this comment https://github.com/NixOS/nixpkgs/pull/31268#issuecomment-347080036

@pbogdan Thanks ! Indeed after disabling  xterm with services.xserver.desktopManager.xterm.enable = false; it works as expected.
Shall I close this issue ?

@PierreR in fact I think my change was supposed to prevent this :P My change only affects the first login, making its default session whatever you've listed in services.xserver.desktopManger.default and services.xserver.windowManager.default.

authors: ElvishJerricco PierreR pbogdan


text:
Is it possible to add / mount writable directory to package?

Issue description
Because it isn't possible to get VirtualBox extension packages working when using the unstable channel I thought about adding a writable directory to the VirtualBox package. When trying to manually install the extension pack (via settings) it tries to write to a relative path in the nix-store, but that fails because it is read-only. Is something like this possible? Or is there any fix for building VirtualBox  and Extension Pack from the unstable channel? I really want to switch to NixOS as primary distro, but VirtualBox and the Extension Pack, which is needed for USB 3.0 are holding me back (I need to run Windows for a few things).

/nix/store is read only. (AFAIK Nix removes write permission when it finalizes a store path.) You should be able to hack around this by creating a symlink from your package that leads outside /nix/store, and edit that out of store location.
If VirtualBox can not install extensions because it tries to write into /nix/store, we may have to wrap it with a script that makes it write someplace else. (At the moment I can not test this. Are you saying that there is a problem with the way VirtualBox is packaged, and this problem exists in the unstable channel and does not exist in 18.03?)

@orivej Seems so. I don't know why, but when I added the virtualbox and extension options, it worked fine in 18.03. But changing the channel to unstable and upgrading, the Extension Pack is ignored somehow. Also when choosing 4.17 kernel instead of the default one.

The best thing would be to have an option to create this symlink to a writable directory, so that you can just use the extpack download and install it like on other platforms too, no wasted energy to compile everything again.

@jlelse Can we close this in favour of https://github.com/NixOS/nixpkgs/issues/34796#issuecomment-406372825 ?

authors: flokli jlelse orivej


text:
Vulnerability roundup 65: libraw-0.18.12: 1 advisory

search, files

[ ] CVE-2018-5817 (nixos-18.09)

Scanned versions: nixos-18.09: 40e716b92a7. May contain false positives.

Closing as 18.09 is no longer supported.

authors: Ekleog ckauhaus


text:
Graphics state is broken after resume from suspend-to-RAM

Suspend-to-RAM is unusably broken for me with NixOS. When booting into Ubuntu 14.04 from a live USB on the same hardware, suspend-to-RAM works perfectly.
CONFIGURATION
I am running on a 3rd generation Lenovo X1 Carbon. My configuration.nix is here https://gist.github.com/anderspapitto/1454c0dc54a3eea69b60, and my hardware-configuration.nix is here https://gist.github.com/anderspapitto/04bf411c2c919bc89617. I am on nixpkgs-unstable, at a commit described by
[root@gurney:~]# cat /root/.nix-defexpr/channels/manifest.nix
[ { meta = { }; name = "nixos-15.05pre58357.a869c83"; out = { outPath = "/nix/store/0fq4hfpq3pxcakal4bcpn1znbyawp1w3-nixos-15.05pre58357.a869c83"; }; outPath = "/nix/store/0fq4hfpq3pxcakal4bcpn1znbyawp1w3-nixos-15.05pre58357.a869c83"; outputs = [ "out" ]; system = "x86_64-linux"; type = "derivation"; } ]

PROBLEM DESCRIPTION
When I suspend (using systemctl suspend, either as my unprivileged user or as root), and then resume by pressing the power button, it appears that something is broken in the graphics state. My display manager (slim) shows up correctly, except that when I enter my password, I don't see dots appear in the password box, and there is no cursor. After logging in, my status bar is missing, there is some pixelated garbage in the top left corner of the screen, and many operations don't work. I can switch workspaces, but can't launch programs or interact with running windows.
Interestingly, restarting the X server (with sudo systemctl restart display-manager) does NOT fix this issue. At the same time, all vttys other than the one with X running in it are unaffected. Even more interestingly, if I turn off X (sudo systemctl stop display-manager), suspend and resume, and then start X afterwards, it displays the same symptoms. Only a reboot helps.
LOGS
I have tried looking in journalctl output, but I don't see anything useful. I see some errors and warnings, but these are the same when first booting as when resuming from suspend or when restarting display-manager. Here is the output of journalctl -b -1
https://gist.github.com/anderspapitto/3841395e3c95b167dcab
I'm happy to gather any more information and try out suggestions, but I'm not sure how to continue investigating this on my own.

Duplicate of #6617

@codyopel #6617 isn't related (It's about configuring the resumeDevice for hibernation).
@anderspapitto I don't see any mention of services.xserver.videoDrivers, did you try setting that correctly? I guess it has an intel GPU? Otherwise, have you found reports of this issue on other distros?

I would expect that something around the graphic driver stack is causing it. I see a potentially problematic message during suspend:
[drm:stop_ring [i915]] *ERROR* render ring : timed out trying to stop ring

/var/log/X.0.log might show more interesting things, and I also suspect that setting services.xserver.videoDrivers = [ "intel" ]; might get you a better X driver and solve this.

I have an integrated intel gpu (Intel HD Graphics 5500). Setting services.xserver.videoDrivers does not fix the issue - it looks like "intel" is in the default list, so it was probably being used already.
I don't see anything relevant in the X logs. Here is an example
https://gist.github.com/anderspapitto/a5d1e6207226634b3137
@vcunat it seems like that error has been seen related to similar issues. I'll try following this discussion
http://markmail.org/thread/nnibszsh3pcca7gg#query:+page:1+mid:jaiyfhwxzhp52loa+state:results

It looks the workaround from that thread (run glxgears before suspending) works for me, and the fix is already upstream in the 4.0 kernel, so I'll close this for now. Thanks!

authors: anderspapitto cillianderoiste codyopel vcunat


text:
lmms 1.2.0-rc7 is crashing (not starting at all)

Describe the bug
lmms does not seem to work anymore.
To Reproduce
$ nix-shell -p lmms --run lmms
qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in ""
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

/tmp/nix-shell-24710-0/rc: line 1: 24727 Aborted                 (core dumped) lmms

Metadata
Please run nix run nixpkgs.nix-info -c nix-info -m and paste the result.
error: attribute 'nixpkgs' in selection path 'nixpkgs.nix-info' not found

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
  - lmms

cc @yegortimoshenko
Here is an issue I found which sounds similar : #21668

This must be relevant to #65399

authors: mrVanDalo veprbl


text:
amdgpu-pro not usable

Describe the bug
I try to use OpenCL on a Radeon RX 480 GPU. It don't work with amdgpu driver, so i wanted to try amdgpu-pro. But nixos-rebuild fails:
[root@gaming:~]# nixos-rebuild switch
building Nix...
building the system configuration...
error: unsupported xorg abiCompat 1.19 for xorg-server-1.20.8
(use '--show-trace' to show detailed location information)

There where ABI incompatibilities before. Maybe that helps: https://github.com/NixOS/nixpkgs/blob/b0ccd6dd16909c8639c2d9bee7dd2a2a0ac74c30/nixos/doc/manual/release-notes/rl-1703.xml#L48-L50
To Reproduce
Steps to reproduce the behavior:

select amdgpu-pro driver

  services.xserver.videoDrivers = [ "amdgpu-pro" ];
  nixpkgs.config.allowUnfree = true;

nixos-rebuild switch

Expected behavior
usable driver
Notify maintainers
for amdgpu-pro: @corngood
for xorg: ?
Metadata

system: "x86_64-linux"
host os: Linux 5.6.13, NixOS, 20.03.1879.91cdcf31357 (Markhor)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.4
channels(root): "nixos-20.03.1879.91cdcf31357, nixos-hardware, nixos-unstable-20.09pre225931.32b8ed73809"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

Duplicate of https://github.com/NixOS/nixpkgs/issues/78031.


text:
Package request: timeshift (System restore tool for Linux)

Project description
System restore tool for Linux
This program takes snapshots for the root directory periodically or when told to using either rsync or btrfs, and allow the user restore them if need be. It is capable to do cross-distribution restore, or
to work from a live CD/USB.

Not sure if snapshots are important for NixOS, but it saves the day when you need to restore another distribution to the previous state inside NixOS, or if you are using nix package manager on other distributions.
Metadata

homepage URL: https://github.com/teejee2008/timeshift
source URL: https://github.com/teejee2008/timeshift
license: gpl3
platforms: linux

Not sure if snapshots are important for NixOS

from their readme:

It is designed to protect only system files and settings. User files such as documents, pictures and music are excluded.

that is not really usefull since nixos already allows rollbacks

It could be useful with Nix on non-NixOS Linux but you might as well use the native package manager to install Timeshift then.
Being able to offline timeshift non-NixOS distros from your NixOS installation seems like the most sensible use-case.

Being able to offline timeshift non-NixOS distros from your NixOS installation seems like the most sensible use-case.

Actually, my original motivation is to rescue my Debian Testing in the laptop.
It crashed after the system partition was filled up suddenly (probably by the inflating system logs).
I have a working NixOS installation in a USB stick (it  is one of the very distros that can be installed onto a removable storage device, making it boot able elsewhere and not affecting the local boot loader at the same time.), and it seems to be a good idea to rescue it from the USB stick.
It's probably a bit user-specific. :sweat_smile:
BTW, what is the Nixy way to deal with the trouble if something similar (something fills up the disk space suddenly) happen to a NixOS installation?
Thanks you very much for answering, and for this wonderful distro!

BTW, what is the Nixy way to deal with the trouble if something similar (something fills up the disk space suddenly) happen to a NixOS installation?

Delete older generations, run garbage collection and optimise the store. Preferably in that order.

Oh and getting rid of stray gcroots can also help a ton. I had one that kept an old 19.09 system closure  around for months.

It might not be needed by most of the NixOS users. But the project itself seems to be easy to build (with well-written make files and simple dependencies). I can write one when I have time.

I hope it's still relevant.

I think this is going to help those who want to upgrade from a previous system's version.

AFAIK, this snapshot tool is commonly seen in Debian-based distros, and is enabled by default on Ubuntu and Linux Mint.
Remaining issues:

The "periodic snapshot" functionality requires crontab access from superuser. This is not enabled by deafult, and can be disabled at run time. If we want to have it on NixOS, it may require special patches and a NixOS module.

timeshift-gtk expects /etc/timeshift/timeshift.json to exist before it starts. I'm not sure how other packages manage that.

authors: Atemu ShamrockLee cicildihar davidak


text:
libseccomp does not cross compile

Describe the bug
Tried cross compiling libseccomp for the raspberry pi. Didn't work.
To Reproduce

nix-shell -p pkgsCross.raspberryPi.libseccomp

[…]
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking whether make supports nested variables... (cached) yes
checking for linux/seccomp.h... yes
checking for cython3... no
checking for cython... no
checking for armv6l-unknown-linux-gnueabihf-gperf... no
checking for gperf... no
configure: error: please install gperf
builder for '/nix/store/3v5likmzzdkjn5q7zszh0g64klrmxj41-libseccomp-2.5.0-armv6l-unknown-linux-gnueabihf.drv' failed with exit code 1

Expected behavior
gperf must be declared as nativeBuildInput. Therefore, nix-shell -p pkgsCross.raspberryPi.libseccomp.overrideAttrs(old: {nativeBuildInputs = [gperf]}) works.
Notify maintainers
@thoughtpolice
Metadata

system: "x86_64-linux"
host os: Linux 5.8.5-arch1-1, Arch Linux, noversion
multi-user?: no
sandbox: yes
version: nix-env (Nix) 2.3.3
channels(piegames): "home-manager, nixpkgs-20.09pre241765.7bc3a08d3a4"
nixpkgs: /home/piegames/.nix-defexpr/channels/nixpkgs

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

Looks like fix landed in 0730d80e40f4fcb8d0b1bcfa6711f87c33777027

authors: piegamesde sorki


text:
geogebra: 5-0-593-0 -> 5-0-609-0, geogebra6: 6-0-600-0 -> 6-0-609-0

Motivation for this change

geogebra: 5-0-593-0 -> 5-0-609-0, enable on darwin
geogebra6: 6-0-600-0 -> 6-0-609-0, enable on darwin

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

did you test darwin @sikmir ? I had some strange bug, where the window wouldnt get any input, because it wont gain focus.

Yes, it works for me on my macOS High Sierra.

did you test darwin @sikmir ? I had some strange bug, where the window wouldnt get any input, because it wont gain focus.

Yes, it works for me on my macOS High Sierra.

source: gharchive/pull-request


text:
Add aarch64-linux support to resilio-sync pkgs

Motivation for this change
I want to support arm64 so that I can run resilio-sync on a Raspberry Pi.
Official documentation states that aarch64-linux is supported.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS Raspberry Pi
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@ofborg build resilio-sync

To comply with CONTRIBUTING.md please have the commit message name be of the format
<pkg-name>: <subject-line>

for more examples, please look at https://github.com/NixOS/nixpkgs/blob/master/.github/CONTRIBUTING.md#submitting-changes
in your case, the commit message should be:
resilio-sync: add aarch64 support

done

authors: jonringer rhoriguchi


text:
wasabiwallet: 1.1.12.2 -> 1.1.12.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/zkSNACKs/WalletWasabi/releases.
meta.description for wasabiwallet is: "Privacy focused Bitcoin wallet"
meta.homepage for wasabiwallet is: "https://wasabiwallet.io/"
meta.changelog for wasabiwallet is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 1.1.12.3 with grep in /nix/store/1qmhk5sg6wk74zgpnai3zhqzlv0l7sg7-wasabiwallet-1.1.12.3

directory tree listing: https://gist.github.com/c42589ffee5faa24f8ee5725386fd246

du listing: https://gist.github.com/65eb3d5cf2cfea2a589fa683d8eddd63

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
0 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
0 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
wasabiwallet

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1qmhk5sg6wk74zgpnai3zhqzlv0l7sg7-wasabiwallet-1.1.12.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A wasabiwallet https://github.com/r-ryantm/nixpkgs/archive/0f94a01a9fb2517bb6959aac8097fb4c7b1ad487.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1qmhk5sg6wk74zgpnai3zhqzlv0l7sg7-wasabiwallet-1.1.12.3
ls -la /nix/store/1qmhk5sg6wk74zgpnai3zhqzlv0l7sg7-wasabiwallet-1.1.12.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

1 package built:

wasabiwallet

Maintainer pings
cc @mmahut for testing.

Result of nixpkgs-review pr 106632 run on x86_64-linux 1

1 package built:

wasabiwallet

authors: RaghavSood r-ryantm


text:
bottom: 0.5.4 -> 0.5.6

Motivation for this change
Update https://github.com/ClementTsang/bottom
Changes since 0.5.4:

Fixed temperature sensors not working on non-Linux platforms.
Fixed CPU graph colours not matching the legend in the "all" state.

Update done automatically with nix run 'nixpkgs#nix-update' -- --version 0.5.6 bottom
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Tested on NixOS x86_64-linux and NixOS aarch64-linux. It didn't work on aarch64-linux, but that's unrelated and I'll open another PR to fix it.

authors: berbiche petabyteboy


text:
containerd: misc fixes

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

diff lGTM

Result of nixpkgs-review pr 107778 run on x86_64-linux 1

14 packages built:

charliecloud
containerd
disnix
disnixos
docker (docker-edge ,docker_19_03)
docker-gc
docker_18_09
dydisnix
dysnomia
out-of-tree
pipework
python37Packages.jupyter-repo2docker
python38Packages.jupyter-repo2docker
python39Packages.jupyter-repo2docker


text:
tortoisehg: 5.2.1 -> 5.6

Motivation for this change
Fixes #108740. tortoisehg 5.2.1 used a URL that does not exist and version 5.2.1 never existed as a released version. Additionally, package was out of date/buggy.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 108742 run on x86_64-linux 1

1 package built:

tortoisehg

Result of nixpkgs-review pr 108742 run on x86_64-linux 1

1 package built:

tortoisehg

Should we just backport it?

Should we just backport it?

Yes i think so. @Mic92  if we backport, would we want 5.6 or 5.4.2?

Yes i think so. @Mic92  if we backport, would we want 5.6 or 5.4.2?

Yes i think so. @Mic92 if we backport, would we want 5.6 or 5.4.2?

5.6 sounds easier right now.

Yes i think so. @Mic92 if we backport, would we want 5.6 or 5.4.2?

5.6 sounds easier right now.


text:
treewide: fix double quoted strings in one-liners

Motivation for this change
Prior discussion: #108099
Authored by @kvtb
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@SuperSandro2000 please run nixpkgs-review, bam has a hash change

@SuperSandro2000 please run nixpkgs-review, bam has a hash change

This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 110670 run on x86_64-linux 1

1 package failed to build and are new build failure:

bam: log https://termbin.com/l40xj

This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 110670 run on x86_64-linux 1

1 package failed to build and are new build failure:

bam: log https://termbin.com/l40xj

do not commit, there are more bugs.
I will rerun the script

do not commit, there are more bugs.
I will rerun the script

https://github.com/nixos/nixpkgs/commit/00ec1f7b62a052878904eedec097e389962c10eb.patch

https://github.com/nixos/nixpkgs/commit/00ec1f7b62a052878904eedec097e389962c10eb.patch

By the way, how are you pushing these patches?

By the way, how are you pushing these patches?

By the way, how are you pushing these patches?

There is @volth's Nix parser in Scala. Apparently, it has some bugs when processing double-quoted strings

By the way, how are you pushing these patches?

There is @volth's Nix parser in Scala. Apparently, it has some bugs when processing double-quoted strings

There is @volth's Nix parser in Scala. Apparently, it has some bugs when processing double-quoted strings

Oh I mean pushing the patches under NixOS/nixpkgs directly, do you email or run a command etc.?

There is @volth's Nix parser in Scala. Apparently, it has some bugs when processing double-quoted strings

Oh I mean pushing the patches under NixOS/nixpkgs directly, do you email or run a command etc.?

There is @volth's Nix parser in Scala. Apparently, it has some bugs when processing double-quoted strings

Oh I mean pushing the patches under NixOS/nixpkgs directly, do you email or run a command etc.?

all patches are visible under NixOS/nixpkgs
yours too: https://github.com/nixos/nixpkgs/commit/b228182734ac783882249391d2b232b7ae9689cd.patch

There is @volth's Nix parser in Scala. Apparently, it has some bugs when processing double-quoted strings

Oh I mean pushing the patches under NixOS/nixpkgs directly, do you email or run a command etc.?

all patches are visible under NixOS/nixpkgs
yours too: https://github.com/nixos/nixpkgs/commit/b228182734ac783882249391d2b232b7ae9689cd.patch

authors: SuperSandro2000 kvtb siraben


text:
[20.09] nginx module: fix typo in proxyWebsockets description

Motivation for this change
Backport of #111485.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Thanks!

authors: Luflosi roberth


text:
tor-browser-bundle-bin: 10.0.9 -> 10.0.12

Update to latest release
https://blog.torproject.org/new-release-tor-browser-10012

Result of nixpkgs-review pr 114209 run on x86_64-linux 1

1 package built:

torbrowser (tor-browser-bundle-bin)

Thanks!
Backport to stable in https://github.com/NixOS/nixpkgs/pull/114699

authors: nicbk prusnak ronthecookie


text:
klayout: 0.26.9 -> 0.26.10

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/KLayout/klayout/releases.
meta.description for klayout is: "High performance layout viewer and editor with support for GDS and OASIS"
meta.homepage for klayout is: "https://www.klayout.de/"
meta.changelog for klayout is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.26.10 with grep in /nix/store/prix1l7d9vf176kab8d6xdbjjb3rhzav-klayout-0.26.10

directory tree listing: https://gist.github.com/faaab2ae4af3f0de33de36df43cfd366

du listing: https://gist.github.com/35b248ee13f63e675c2c5125aa975604

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
klayout

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/prix1l7d9vf176kab8d6xdbjjb3rhzav-klayout-0.26.10 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A klayout https://github.com/r-ryantm/nixpkgs/archive/e0828f85cbd8dfa6030a5a7901bf71afcf7ce45a.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/prix1l7d9vf176kab8d6xdbjjb3rhzav-klayout-0.26.10
ls -la /nix/store/prix1l7d9vf176kab8d6xdbjjb3rhzav-klayout-0.26.10/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

klayout

Maintainer pings
cc @knedlsepp for testing.

Result of nixpkgs-review pr 114666 run on x86_64-linux 1

1 package built:

klayout

authors: r-ryantm tomberek


text:
bitwig-studio: 3.3.3 -> 3.3.6

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 117795 at d1599260 run on x86_64-linux 1

1 package built successfully:

bitwig-studio (bitwig-studio3)

1 suggestion:

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/applications/audio/bitwig-studio/bitwig-studio3.nix:36:3:
   |
36 |   installPhase = ''
   |   ^

authors: bfortz r-rmcgibbo


text:
sphinx-material: init at 0.0.32

Motivation for this change
sphinx-material was not part of nixpkgs
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 120057 at 81508237 run on aarch64-linux 1

4 packages built successfully:

python38Packages.css-html-js-minify
python38Packages.sphinx-material
python39Packages.css-html-js-minify
python39Packages.sphinx-material

2 suggestions:

warning: unclear-gpl
lgpl3 is a deprecated license, please check if project uses lgpl3Plus or lgpl3Only and change meta.license accordingly.
Near pkgs/development/python-modules/css-html-js-minify/default.nix:19:5:
   |
19 |     license = with licenses; [ gpl3 lgpl3 ];
   |     ^

warning: unclear-gpl
gpl3 is a deprecated license, please check if project uses gpl3Plus or gpl3Only and change meta.license accordingly.
Near pkgs/development/python-modules/css-html-js-minify/default.nix:19:5:
   |
19 |     license = with licenses; [ gpl3 lgpl3 ];
   |     ^

Fix change proposed by @r-rmcgibbo.

@SuperSandro2000 Thank you for the feedback, that is indeed a bit clear.

authors: FlorianFranzen r-rmcgibbo


text:
terra: 1.0.0pre1175_ef6a75f -> 1.0.0-beta3

Motivation for this change
ZHF: #122042
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

I've just found https://github.com/terralang/terra/pull/495.
@seylerius any comments?

Result of nixpkgs-review pr 122665 at d7bb2331 run on x86_64-linux 1

1 package built successfully:

terra

5 suggestions:

warning: unnecessary-parallel-building
Meson, CMake and qmake already set enableParallelBuilding = true by default so it is not necessary.
Near pkgs/development/compilers/terra/default.nix:34:3:
   |
34 |   enableParallelBuilding = true;
   |   ^

warning: missing-patch-comment
Consider adding a comment explaining the purpose of this patch on the line preceeding.
Near pkgs/development/compilers/terra/default.nix:39:5:
   |
39 |     ./nix-llvm-install-prefix.patch
   |     ^

warning: missing-patch-comment
Consider adding a comment explaining the purpose of this patch on the line preceeding.
Near pkgs/development/compilers/terra/default.nix:40:5:
   |
40 |     ./nix-cflags.patch
   |     ^

warning: missing-patch-comment
Consider adding a comment explaining the purpose of this patch on the line preceeding.
Near pkgs/development/compilers/terra/default.nix:41:5:
   |
41 |     ./disable-luajit-file-download.patch
   |     ^

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/development/compilers/terra/default.nix:56:3:
   |
56 |   installPhase = ''
   |   ^

sorry for doing this via email I don't have access to my github at this time.
On Tue, May 11, 2021 at 10:42:55PM -0300, J. Neto wrote:

+diff --git a/cmake/Modules/FindClang.cmake b/cmake/Modules/FindClang.cmake
+index c0bafdf..6ab263e 100644
+-set(CLANG_RESOURCE_DIR ${LLVM_INSTALL_PREFIX}/lib/clang/${LLVM_PACKAGE_VERSION})
++set(CLANG_RESOURCE_DIR @LLVM_INSTALL_PREFIX@/lib/clang/${LLVM_PACKAGE_VERSION})

do we need a patch here? can cmake get LLVM_INSTALL_PREFIX from the
environment or from a pass variable somehow?

I've tried set an environment variable without success.
I don't know how cmake gets LLVM_INSTALL_PREFIX but terralang expects llvm and clang to be in the same place - not true for nixpkgs.
Check how seylerius do it: https://github.com/terralang/terra/blob/b924f9d043f93ad2cbf2506d2fe0f71ad75cd9cb/default.nix#L35-L38
I could substituteInPlace too; cleaner than my patch solution.

On Wed, May 12, 2021 at 08:01:41AM -0700, jnetod wrote:

I've tried set an environment variable without success.
I don't know how cmake gets LLVM_INSTALL_PREFIX but terralang expects llvm and clang to be in the same place - not true for nixpkgs.
Check how seylerius do it: https://github.com/terralang/terra/blob/b924f9d043f93ad2cbf2506d2fe0f71ad75cd9cb/default.nix#L35-L38
I could substituteInPlace too; cleaner than my patch solution.

substituteInPlace would be ideal, less patches the better.

Hi, good to hear from y'all. I am currently working on fixing some serious issues in the resulting built Terra (if you get tests turned on properly, they reveal weirdness is afoot). I'll also be 90% of the way to a flake when I get the current stage done, so I'll probably do that as well. Would not mind collabing on fixing this.
How thoroughly are you running the tests, currently?

Okay, on further examination you're fully running the tests, and it looks like you're running into the -frandom-seed issue. That's largely caused by some foolishness in how Terra selects a linker for compilation, and is something my team has a fix for. You should grab all our changes from tcompiler.cpp, honestly. There's another thing in there, as well, adding an ugly workaround for a game-breaking issue with CPU detection sometimes failing.
We'll have it into Terra's master as soon as I clean up the current problems arising from standardizing how LuaJIT is fetched, rather than using the current manual download-and-build.

@seylerius Thanks! I've cherry-picked all changes made on tcompiler.cpp.

authors: jb55 jnetod r-rmcgibbo seylerius


text:
linux-kernel: Enable BTF

Motivation for this change
BTF is a new, lightweight debug information format tailored specifically
for the needs of eBPF, allowing eBPF programs to be portable across
various kernel versions, configurations and distributions. This is used
by bpftrace and lots of new eBPF-based tooling to avoid a dependency
on LLVM on the host.
BTF debug information is enabled on all major distributions: Fedora 31+,
RHEL 8.2+, Ubuntu 20.10, Debian 11 and ArchLinux all have enabled it.
Enabling BTF debug information requires adding two new dependencies to
the kernel build: Python3 and pahole. Those will be used to generate the
BTF debugging information.

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

@ofborg build linux_xanmod

@ofborg test latestKernel.login kernel-latest

Please target staging, this causes a ton of rebuilds which most users won't directly benefit from any time soon.

/rebase-staging

How should I do that? Just change the target branch in github's ui?

How should I do that? Just change the target branch in github's ui?

I'm not sure that works. For me I do:
git fetch --all
git checkout $myBranch
git rebase -i origin/staging
git push --force

You may or may not fiddle with GH's UI as well, not sure.

No, don't do that. That way you'd try to merge staging into master and ping pretty much all codeowners.
Just change the base (or target) branch in the GH UI. You only need to rebase if there's a merge conflict between your branch and staging; after you changed the target branch that is.

Done, and no conflicts!

Hi, what else needs to be done for this PR to get approvals and get merged? Having BTF info in the kernel is very useful for software packages that make use of eBPF and for eBPF development.

If someone resolves the conflict and pings me I will merge this.

Very sorry for the ping, I accidentally rebased on master :sweat_smile: .
@lovesegfault I fixed the merge conflict. I'm still not 100% sure that the zlib.dev dependency is correct though. I'm not familiar enough with the kernel build system or nix to know for sure.

Alright, I added zlib in buildInputs, and locally verified that the build works.

Linux 5.10 and linux 5.12 fail to configure with this option.
Please have a look.
error: builder for '/nix/store/dn8bf57symyrsna58kvz6nlml76jn3c3-linux-config-5.10.57.drv' failed with exit code 255;
       last 10 log lines:
       > warning: unused option: INET_RAW_DIAG
       > warning: unused option: INET_TCP_DIAG
       > warning: unused option: INET_UDP_DIAG
       > warning: unused option: RCU_PERF_TEST
       > warning: unused option: SECURITY_WRITABLE_HOOKS
       > warning: option not set correctly: STRICT_DEVMEM (wanted 'y', got 'n')
       > warning: unused option: XEN_SCRUB_PAGES
       > warning: unused option: XEN_SELFBALLOONING
       > warning: unused option: XEN_STUB
       > warning: unused option: XEN_TMEM
       For full logs, run 'nix log /nix/store/dn8bf57symyrsna58kvz6nlml76jn3c3-linux-config-5.10.57.drv'.
error: builder for '/nix/store/jgaja973qf0jbs9myjwl29k5r3jh3i2z-linux-config-5.12.19.drv' failed with exit code 255;
       last 10 log lines:
       > warning: unused option: INET_RAW_DIAG
       > warning: unused option: INET_TCP_DIAG
       > warning: unused option: INET_UDP_DIAG
       > warning: unused option: RCU_PERF_TEST
       > warning: unused option: SECURITY_WRITABLE_HOOKS
       > warning: option not set correctly: STRICT_DEVMEM (wanted 'y', got 'n')
       > warning: unused option: XEN_SCRUB_PAGES
       > warning: unused option: XEN_SELFBALLOONING
       > warning: unused option: XEN_STUB
       > warning: unused option: XEN_TMEM
       For full logs, run 'nix log /nix/store/jgaja973qf0jbs9myjwl29k5r3jh3i2z-linux-config-5.12.19.drv'.

Well, that shux. It works on my machine, and I tested kernel 5.10 and 5.12. To test, I use a flake.nix system that looks like this:
{
    inputs.nixpkgs.url = "github:roblabla/nixpkgs/enable-btf";
    packages.x86_64-linux.kernel = nixpkgs.legacyPackages.x86_64-linux.linuxPackages_5_10.kernel;
    packages.x86_64-linux.configfile = nixpkgs.legacyPackages.x86_64-linux.linuxPackages_5_10.kernel.configfile;
  };
}

and then just run nix build '.#configfile'. The lockfile pins commit 34150f86c0a6b9d452bab09157896c3b85b103d1 now.
@Mic92 Could you provide the full logs so I can figure out what went wrong?

I think it's only linuxPackages_5_10_hardened.kernel now which is sort of broken anyway.

zlib needs to be in nativeBuildInputs, otherwise the kernel fails to cross-compile. zlib appears to only be used for a build system tool, so this makes sense.

With this PR error build kernel:
  LD [M]  drivers/net/wireless/intersil/hostap/hostap_pci.ko
  LD [M]  drivers/net/wireless/intel/iwlwifi/iwlwifi.ko
  LD [M]  drivers/net/wireless/intersil/orinoco/orinoco.ko
/nix/store/fp2h123793bxln4cjxy0mz08sf4nx2m3-binutils-2.35.1/bin/ld: drivers/net/wireless/intel/ipw2x00/ipw2100.ko: final close failed: No space left on device
/nix/store/fp2h123793bxln4cjxy0mz08sf4nx2m3-binutils-2.35.1/bin/ld: drivers/net/wireless/ath/wil6210/wil6210.ko: final close failed: No space left on device
/nix/store/fp2h123793bxln4cjxy0mz08sf4nx2m3-binutils-2.35.1/bin/ld: final link failed: No space left on device
make[3]: *** [../scripts/Makefile.modfinal:78: drivers/net/wireless/intel/ipw2x00/ipw2100.ko] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: *** [../scripts/Makefile.modfinal:78: drivers/net/wireless/ath/wil6210/wil6210.ko] Error 1
make[3]: *** [../scripts/Makefile.modfinal:78: drivers/net/wireless/broadcom/b43legacy/b43legacy.ko] Error 1
/nix/store/qfb4j7w2fjjq953nd9xncz5mymj5n0kb-bash-5.1-p8/bin/bash: line 1: printf: write error: No space left on device
make[3]: *** [../scripts/Makefile.modfinal:78: drivers/net/wireless/cisco/airo_cs.ko] Error 1
make[3]: *** Deleting file 'drivers/net/wireless/cisco/airo_cs.ko'
/nix/store/fp2h123793bxln4cjxy0mz08sf4nx2m3-binutils-2.35.1/bin/ld: final link failed: No space left on device
/nix/store/fp2h123793bxln4cjxy0mz08sf4nx2m3-binutils-2.35.1/bin/ld: final link failed: No space left on device
/nix/store/fp2h123793bxln4cjxy0mz08sf4nx2m3-binutils-2.35.1/bin/ld: final link failed: No space left on device
make[3]: *** [../scripts/Makefile.modfinal:78: drivers/net/wireless/intel/ipw2x00/ipw2200.ko] Error 1
make[3]: *** [../scripts/Makefile.modfinal:78: drivers/net/wireless/cisco/airo.ko] Error 1
make[3]: *** [../scripts/Makefile.modfinal:78: drivers/net/wireless/broadcom/brcm80211/brcmsmac/brcmsmac.ko] Error 1
/nix/store/fp2h123793bxln4cjxy0mz08sf4nx2m3-binutils-2.35.1/bin/ld: final link failed: No space left on device
/nix/store/fp2h123793bxln4cjxy0mz08sf4nx2m3-binutils-2.35.1/bin/ld: final link failed: No space left on device
make[3]: *** [../scripts/Makefile.modfinal:78: drivers/net/wireless/intel/iwlegacy/iwl3945.ko] Error 1
/nix/store/fp2h123793bxln4cjxy0mz08sf4nx2m3-binutils-2.35.1/bin/ld: final link failed: No space left on device
make[3]: *** [../scripts/Makefile.modfinal:78: drivers/net/wireless/intel/ipw2x00/libipw.ko] Error 1
/nix/store/fp2h123793bxln4cjxy0mz08sf4nx2m3-binutils-2.35.1/bin/ld: final link failed: No space left on device
make[3]: *** [../scripts/Makefile.modfinal:78: drivers/net/wireless/broadcom/brcm80211/brcmfmac/brcmfmac.ko] Error 1
make[3]: *** [../scripts/Makefile.modfinal:78: drivers/net/wireless/broadcom/b43/b43.ko] Error 1
/nix/store/fp2h123793bxln4cjxy0mz08sf4nx2m3-binutils-2.35.1/bin/ld: drivers/net/wireless/ath/ath9k/ath9k_htc.ko: final close failed: No space left on device
make[3]: *** [../scripts/Makefile.modfinal:78: drivers/net/wireless/ath/ath9k/ath9k_htc.ko] Error 1
/nix/store/fp2h123793bxln4cjxy0mz08sf4nx2m3-binutils-2.35.1/bin/ld: final link failed: No space left on device
make[3]: *** [../scripts/Makefile.modfinal:78: drivers/net/wireless/intersil/hostap/hostap_cs.ko] Error 1
/nix/store/fp2h123793bxln4cjxy0mz08sf4nx2m3-binutils-2.35.1/bin/ld: final link failed: No space left on device
make[3]: *** [../scripts/Makefile.modfinal:78: drivers/net/wireless/ath/ath9k/ath9k_hw.ko] Error 1
/nix/store/fp2h123793bxln4cjxy0mz08sf4nx2m3-binutils-2.35.1/bin/ld/nix/store/fp2h123793bxln4cjxy0mz08sf4nx2m3-binutils-2.35.1/bin/ld: : drivers/net/wireless/intersil/hostap/hostap.kodrivers/net/wireless/intersil/orinoco/orinoco.ko: final close failed: : final close failed: No space left on deviceNo space left on device

make[3]: *** [../scripts/Makefile.modfinal:78: drivers/net/wireless/intersil/hostap/hostap.ko] Error 1
make[3]: *** [../scripts/Makefile.modfinal:78: drivers/net/wireless/intersil/orinoco/orinoco.ko] Error 1
/nix/store/fp2h123793bxln4cjxy0mz08sf4nx2m3-binutils-2.35.1/bin/ld: final link failed: No space left on device
make[3]: *** [../scripts/Makefile.modfinal:78: drivers/net/wireless/intel/iwlwifi/mvm/iwlmvm.ko] Error 1
/nix/store/fp2h123793bxln4cjxy0mz08sf4nx2m3-binutils-2.35.1/bin/ld: final link failed: No space left on device
make[3]: *** [../scripts/Makefile.modfinal:78: drivers/net/wireless/intel/iwlwifi/iwlwifi.ko] Error 1
make[2]: *** [../scripts/Makefile.modpost:152: __modpost] Error 2
make[1]: *** [/tmp/nix-build-linux-5.12.19.drv-0/linux-5.12.19/Makefile:1450: modules] Error 2
make: *** [../Makefile:215: __sub-make] Error 2
builder for '/nix/store/rjxmmqq2rmp8g2pm8zw05mjji47c1m3q-linux-5.12.19.drv' failed with exit code 2
note: build failure may have been caused by lack of free disk space
error: build of '/nix/store/rjxmmqq2rmp8g2pm8zw05mjji47c1m3q-linux-5.12.19.drv' failed

@Izorkin  your error looks like you run out of disk-space. Make sure TMPDIR is not pointing to a tmpfs.

@lopsided98 see https://github.com/NixOS/nixpkgs/pull/139710

I checked this variant yesterday - error build.
There is enough free space on /tmp.
df -h /tmp
Filesystem      Size  Used Avail Use% Mounted on
tmpfs            16G  4.0K   16G   1% /tmp

The error message clearly indicates no space left errors though:
make[3]: *** [../scripts/Makefile.modfinal:78: drivers/net/wireless/intel/iwlegacy/iwl3945.ko] Error 1
/nix/store/fp2h123793bxln4cjxy0mz08sf4nx2m3-binutils-2.35.1/bin/ld: final link failed: No space left on device
make[3]: *** [../scripts/Makefile.modfinal:78: drivers/net/wireless/intel/ipw2x00/libipw.ko] Error 1
/nix/store/fp2h123793bxln4cjxy0mz08sf4nx2m3-binutils-2.35.1/bin/ld: final link failed: No space left on device
make[3]: *** [../scripts/Makefile.modfinal:78: drivers/net/wireless/broadcom/brcm80211/brcmfmac/brcmfmac.ko] Error 1
make[3]: *** [../scripts/Makefile.modfinal:78: drivers/net/wireless/broadcom/b43/b43.ko] Error 1
/nix/store/fp2h123793bxln4cjxy0mz08sf4nx2m3-binutils-2.35.1/bin/ld: drivers/net/wireless/ath/ath9k/ath9k_htc.ko: final close failed: No space left on device
make[3]: *** [../scripts/Makefile.modfinal:78: drivers/net/wireless/ath/ath9k/ath9k_htc.ko] Error 1
/nix/store/fp2h123793bxln4cjxy0mz08sf4nx2m3-binutils-2.35.1/bin/ld: final link failed: No space left on device
make[3]: *** [../scripts/Makefile.modfinal:78: drivers/net/wireless/intersil/hostap/hostap_cs.ko] Error 1
/nix/store/fp2h123793bxln4cjxy0mz08sf4nx2m3-binutils-2.35.1/bin/ld: final link failed: No space left on device

Notice that if TMPDIR can also point to /run/user/$UID if you are in a nix-shell, which can be surprising.

Checked it out. The build uses all 16GB of memory.
Without etnable BTF - 3,5GB.

Maybe but don't build it on tmpfs than.

I don't think we should be enabling these by default. People who want it can set options.debug like before.

Those should definitely be enabled by default, as they enable eBPF CO-RE functionality: https://facebookmicrosites.github.io/bpf/blog/2020/02/19/bpf-portability-and-co-re.html
This is very important for a bunch of bpf-based tools. It's enabled by default on many distribs, like Fedora, Ubuntu and Debian for this reason.

This ballooned the size of zfs.ko.xz ten-fold for me, from 881K to 9.4M.  Other modules from ZFS are also affected, and the combined size increase means my initramfs no longer fits on my boot partition.  But it didn't increase the size of Linux itself at all, so presumably there's some change we can make to the ZFS package to fix this?
I do agree it makes sense for this to be enabled by default.

Kernel without btf:
$ wc -c bzImage
6360032

Kernel with btf
$ wc -c ./result/bzImage
7280640 ./result/bzImage

So it's a 14% increase for the kernel image.

https://github.com/NixOS/nixpkgs/pull/141284

authors: Atemu Izorkin Mic92 alyssais fortuneteller2k lopsided98 lovesegfault markpash roblabla


text:
seafile-shared: update source hash, seafile-client: update source hash

Motivation for this change
It looks like the tags have been modified
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 129111 run on x86_64-linux 1

2 packages built:

seafile-client
seafile-shared

Result of nixpkgs-review pr 129111 at 1a4c9851 run on aarch64-linux 1

2 packages built successfully:

seafile-client
seafile-shared

Backport would have required merging https://github.com/NixOS/nixpkgs/pull/129057 first, but it failed to build due to the outdated hashes. I will create a PR with both backports.

authors: eduardosm r-rmcgibbo


text:
treewide: fix redirected URLs

Using the script in maintainers/scripts/update-redirected-urls.sh

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 132233 run on x86_64-linux 1

Result of nixpkgs-review pr 132233 run on x86_64-darwin 1


text:
cobalt: 0.16.5 -> 0.17.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/cobalt-org/cobalt.rs/releases.
meta.description for cobalt is: "Static site generator written in Rust"
meta.homepage for cobalt is: "https://github.com/cobalt-org/cobalt.rs/"
meta.changelog for cobalt is: ""
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/kiqs19h08nxfj0sfmh95i6czhrl3hawn-cobalt-0.17.0/bin/cobalt passed the binary check.

1 of 1 passed binary check by having a zero exit code.

1 of 1 passed binary check by having the new version present in output.

found 0.17.0 with grep in /nix/store/kiqs19h08nxfj0sfmh95i6czhrl3hawn-cobalt-0.17.0

found 0.17.0 in filename of file in /nix/store/kiqs19h08nxfj0sfmh95i6czhrl3hawn-cobalt-0.17.0

directory tree listing: https://gist.github.com/bcdf3ee43f78a2d31771ec099c1891df

du listing: https://gist.github.com/6780349ef2e15cccb5650864d2dd8787

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
cobalt

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/kiqs19h08nxfj0sfmh95i6czhrl3hawn-cobalt-0.17.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cobalt https://github.com/r-ryantm/nixpkgs/archive/ae2196daa645de14adfee07e2e10e0424dafe551.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/kiqs19h08nxfj0sfmh95i6czhrl3hawn-cobalt-0.17.0
ls -la /nix/store/kiqs19h08nxfj0sfmh95i6czhrl3hawn-cobalt-0.17.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

cobalt

Maintainer pings
cc @ethancedwards8 for testing.

LGTM.


text:
python38Packages.jupyterlab: 3.1.17 -> 3.1.18

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python38Packages.jupyterlab is: "Jupyter lab environment notebook server extension."
meta.homepage for python38Packages.jupyterlab is: "https://jupyter.org/"
meta.changelog for python38Packages.jupyterlab is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

/nix/store/qk75mr0apy98z6bnc1d567mj7pd1vvmv-python3.8-jupyterlab-3.1.18/bin/jlpm passed the binary check.

/nix/store/qk75mr0apy98z6bnc1d567mj7pd1vvmv-python3.8-jupyterlab-3.1.18/bin/jupyter-lab passed the binary check.

/nix/store/qk75mr0apy98z6bnc1d567mj7pd1vvmv-python3.8-jupyterlab-3.1.18/bin/jupyter-labextension passed the binary check.

/nix/store/qk75mr0apy98z6bnc1d567mj7pd1vvmv-python3.8-jupyterlab-3.1.18/bin/jupyter-labhub passed the binary check.

/nix/store/qk75mr0apy98z6bnc1d567mj7pd1vvmv-python3.8-jupyterlab-3.1.18/bin/.jlpm-wrapped passed the binary check.

/nix/store/qk75mr0apy98z6bnc1d567mj7pd1vvmv-python3.8-jupyterlab-3.1.18/bin/.jupyter-lab-wrapped passed the binary check.

/nix/store/qk75mr0apy98z6bnc1d567mj7pd1vvmv-python3.8-jupyterlab-3.1.18/bin/.jupyter-labextension-wrapped passed the binary check.

/nix/store/qk75mr0apy98z6bnc1d567mj7pd1vvmv-python3.8-jupyterlab-3.1.18/bin/.jupyter-labhub-wrapped passed the binary check.

4 of 8 passed binary check by having a zero exit code.

8 of 8 passed binary check by having the new version present in output.

found 3.1.18 with grep in /nix/store/qk75mr0apy98z6bnc1d567mj7pd1vvmv-python3.8-jupyterlab-3.1.18

found 3.1.18 in filename of file in /nix/store/qk75mr0apy98z6bnc1d567mj7pd1vvmv-python3.8-jupyterlab-3.1.18

directory tree listing: https://gist.github.com/5f9946fdb60e8d03f18aebb6dd962eb2

du listing: https://gist.github.com/7ce5a64e8028957547da109d1faddf5d

Rebuild report (if merged into master) (click to expand)

12 total rebuild path(s)

4 package rebuild(s)

4 x86_64-linux rebuild(s)
4 i686-linux rebuild(s)
4 x86_64-darwin rebuild(s)
0 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
python38Packages.jupyterlab
python38Packages.jupytext
python39Packages.jupyterlab
python39Packages.jupytext

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qk75mr0apy98z6bnc1d567mj7pd1vvmv-python3.8-jupyterlab-3.1.18 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python38Packages.jupyterlab https://github.com/r-ryantm/nixpkgs/archive/9ae2f3f9e68116253540cf7f5fed1bc4783a6efd.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qk75mr0apy98z6bnc1d567mj7pd1vvmv-python3.8-jupyterlab-3.1.18
ls -la /nix/store/qk75mr0apy98z6bnc1d567mj7pd1vvmv-python3.8-jupyterlab-3.1.18/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

4 packages built:

python38Packages.jupyterlab
python38Packages.jupytext
python39Packages.jupyterlab
python39Packages.jupytext

Maintainer pings
cc @zimbatm @costrouc for testing.

3.1.18 already in master, see https://github.com/NixOS/nixpkgs/commit/169d8a74e3a85a45b4095082dce92c79e42a01f2


text:
Haskell: Init haskell.lib.composable

Supersedes https://github.com/NixOS/nixpkgs/pull/100732
Basically, makes the drv argument to everything in haskell.lib the last argument. Some discussion in the above PR

I think my main suggestion would be to split this into at least two pull requests:

One pull request to introduce the composable versions of the functions
Another pull request to switch existing uses over to the new version

Also take into account lib.pipe, which makes code like this possible:
lib.pipe drv [
 hlib.doCheck
 (drv: hlib.removeConfigureFlag drv "flag")
 …
]

This will make the nesting problem cause of the flipped arguments less problematic.

I think that we all agree that this is the right way to go. The question is can we go in this direction and if so, how? Infinitely maintaining two versions of the library would be very unsatisfying.

I don’t think it’s so big an annoyance that breaking all backwards compat is justified, and maybe not even big enough to split the ecosystem even further? I don’t see any good way to solve this initial misdesign now that so much code depends on it :(

Well in a world where markUnbroken and unmarkBroken both already exist, I think there is room to argue that a few more functions won’t really hurt?

I think my main suggestion would be to split this into at least two pull requests:

Done: https://github.com/NixOS/nixpkgs/pull/144705

This will make the nesting problem cause of the flipped arguments less problematic.

Was this referring to the use of lib.pipe to make using the current functions nicer, or the fact that this change itself solves the nasty nesting problem? I agree with both, but the best solution overall is lib.pipe with these flipped functions.

hahah, I just noticed that lib.pipe itself has the weird argument order where the element being transformed comes first...

I don’t think it’s so big an annoyance that breaking all backwards compat is justified, and maybe not even big enough to split the ecosystem even further? I don’t see any good way to solve this initial misdesign now that so much code depends on it :(

well, the previous functions are still available under .lib. I definitely prefer the case of having both sets in nixpkgs than just the old ones. In terms of eventually removing and replacing the old set (i.e. having haskell.lib = haskell.lib.composable) maybe that's something we can tackle down the line, or just leave forever.
I suppose I was definitely aiming for replacing the old set when putting the deprecation warning in, but I'd be very happy to compromise that away.

* don’t deprecate the old module functions

* call it `.compose` instead of `composable` (just less typing and same content)

* Maybe add some documentation to the non-compose module header and the nixpkgs haskell documentation that `compose` is preferred.

done done done, https://github.com/NixOS/cabal2nix/pull/528

* Define everything in `compose` in terms of the old definitions, don’t duplicate any implementation as it does right now (single source of truth).

The old lib has always been defined in terms of compose, I hope this is OK.

Other than that I’m looking forward to using these functions in the future.

Me too!

The old lib has always been defined in terms of compose, I hope this is OK.

Ah, I didn’t see that. It has the disadvantage that the history gets a bit mangled, but personally I don’t care which way around it is.


text:
ibus-cangjie init at 2.4

Motivation for this change
An Ibus framework for users of Cangjie and Quick input methods.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Adding to NixOS system config as one does other ibus engines results in a selectable, but not fully functional, experience. I am still trying to figure out what gtk dependencies are required since the preferences menu does not open and to me that is the likely culprit given how other ibus engines are packaged.
The input method does not seem to be active most of the time when it is selected, but I once had it kick into action for no reason.


text:
gnome.gnome-desktop: 41.1 -> 41.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for gnome.gnome-desktop is: "Library with common API for various GNOME modules"
meta.homepage for gnome.gnome-desktop is: "https://gitlab.gnome.org/GNOME/gnome-desktop"
meta.changelog for gnome.gnome-desktop is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 41.2 with grep in /nix/store/hgdp3r5dn8p6jabflsmyy8yfqnyjhgp4-gnome-desktop-41.2

found 41.2 in filename of file in /nix/store/hgdp3r5dn8p6jabflsmyy8yfqnyjhgp4-gnome-desktop-41.2

Rebuild report (if merged into master) (click to expand)

113 total rebuild path(s)

107 package rebuild(s)

107 x86_64-linux rebuild(s)
6 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
adapta-gtk-theme
almanah
chrome-gnome-shell
contrast
denemo
docbookrx
dropbox-cli
empathy
eolie
epiphany
evince
evolution
evolution-ews
evolutionWithPlugins
fractal
glom
gnome.cheese
gnome.empathy
gnome.eog
gnome.epiphany
gnome.evince
gnome.file-roller
gnome.gnome-applets
gnome.gnome-books
gnome.gnome-characters
gnome.gnome-clocks
gnome.gnome-contacts
gnome.gnome-control-center
gnome.gnome-desktop
gnome.gnome-disk-utility
gnome.gnome-documents
gnome.gnome-flashback
gnome.gnome-font-viewer
gnome.gnome-initial-setup
gnome.gnome-panel
gnome.gnome-session
gnome.gnome-settings-daemon
gnome.gnome-settings-daemon338
gnome.gnome-shell
gnome.gnome-software
gnome.gnome-terminal
gnome.gnome-tweak-tool
gnome.gnome-tweaks
gnome.gnome-user-share
gnome.gnome-weather
gnome.gnome_control_center
gnome.gnome_desktop
gnome.gnome_session
gnome.gnome_settings_daemon
gnome.gnome_shell

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/hgdp3r5dn8p6jabflsmyy8yfqnyjhgp4-gnome-desktop-41.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A gnome.gnome-desktop https://github.com/r-ryantm/nixpkgs/archive/ea1fb3f051ccb6dd0af8418177e1984a20c0aae2.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/hgdp3r5dn8p6jabflsmyy8yfqnyjhgp4-gnome-desktop-41.2
ls -la /nix/store/hgdp3r5dn8p6jabflsmyy8yfqnyjhgp4-gnome-desktop-41.2/bin

Pre-merge build results
NixPkgs review skipped

Maintainer pings
cc @hedning @jtojnar @dasj19 @maxeaubrey for testing.

Should be merged once all the other GNOME packages are.

authors: jtojnar r-ryantm


text:
python3Packages.types-pytz: 2021.3.1 -> 2021.3.2

Motivation for this change
Update to latest upstream rrelease 2021.3.2
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 149866 run on x86_64-linux 1

1 package failed to build:

home-assistant

6 packages built:

python38Packages.aioridwell
python38Packages.simplisafe-python
python38Packages.types-pytz
python39Packages.aioridwell
python39Packages.simplisafe-python
python39Packages.types-pytz


text:
pifi: remove

Motivation for this change
This upstream repository has been archived.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Please also add a throw in pkgs/top-level/aliases.nix :-)


text:
tree-sitter: 0.20.2 -> 0.20.4 and updater script fixes

Motivation for this change
Upstream update and update script errors.
Closes #156292 (commit included)

Fix update script bug introduced in https://github.com/NixOS/nixpkgs/pull/154753 (due to script options used, unbound variable error is thrown when token env variable is not set)
Handle "bad credentials" error
Output { lib }: at the top of the generated nix file
Grammar updates

This fixed https://github.com/nvim-treesitter/nvim-treesitter/issues/2295 in my neovim setup
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

cc @Profpatsch

@rvolosatovs curious that this seems to fix that for you, as you should still be on the old lua parser. I would have expected https://github.com/NixOS/nixpkgs/pull/156535 to at least be required.

@rvolosatovs curious that this seems to fix that for you, as you should still be on the old lua parser. I would have expected #156535 to at least be required.

I only really tested with Rust, everything is handled via Nix

Bisect claims 15e1696532ef874befb555cde22d7a240f5669df tree-sitter: update grammars broke difftastic in master: https://hydra.nixos.org/build/165602918. Noticed during review of https://github.com/NixOS/nixpkgs/pull/157184#issuecomment-1024969270

authors: gravndal rvolosatovs trofi


text:
graalvm11-ce: 21.3.0 -> 22.0.0.2

graalvm17-ce: 21.3.0 -> 22.0.0.2

Motivation for this change
Bump graalvm to latest
Things done
Ran update script

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

@ofborg build babashka

Result of nixpkgs-review pr 156918 run on x86_64-linux 1

2 packages failed to build:

clojure-lsp
vscode-extensions.betterthantomorrow.calva

10 packages built:

HentaiAtHome
babashka
clj-kondo
dapl-native
dbqn-native
graalvm11-ce
graalvm17-ce
jet
neil
zprint

The clojure-lsp failure seems related to SVM, I think it is caused by Datalevin again? Since you're the maintainer @ericdallo, if you want to follow with this merge knowing this will break the clojure-lsp package (since I imagine you will need to fix this in clojure-lsp/dataelvin first), I can merge this.
vscode-extensions.betterthantomorrow.calva depends on clojure-lsp too, so once fixed it is fixed this also should be fixed.

BTW, I want to see if this new version fixed aarch64-linux or introduced aarch64-darwin. But I will probably do this in a separate PR.

@thiagokokada no problem, I removed datalevin from clojure-lsp replaced by transit :) Next release will already avoid lots of graalvm issues, and I'll probably need to change the derivation so I'm ok with merging this

@thiagokokada no problem, I removed datalevin from clojure-lsp replaced by transit :) Next release will already avoid lots of graalvm issues, and I'll probably need to change the derivation so I'm ok with merging this

You may want to bump clojure-lsp first maybe them, since once datalevin is removed clojure-lsp should build with either version of GraalVM.
But your call. I am waiting just for the x86_64-darwin checks.

Thanks @ericdallo.

authors: ericdallo thiagokokada