text:
Build failure: ceph (cython failure)

Steps To Reproduce
I am seeing cython errors building ceph on staging. Running nix-build -E 'with import /path/to/nixpkgs {}; ceph.
Build log
https://gist.github.com/danielbarter/ee6dfb258427a3f9fdab64745876ee26
...
Error compiling Cython file:
------------------------------------------------------------
...
        """
        name = cstr(name, 'name')
        cdef:
            rados_ioctx_t _ioctx = convert_ioctx(ioctx)
            char *_name = name
            librbd_progress_fn_t _prog_cb = &no_op_progress_callback
                                            ^
------------------------------------------------------------

rbd.pyx:760:44: Cannot assign type 'int (*)(uint64_t, uint64_t, void *) except? -1' to 'librbd_progress_fn_t' (alias of 'int (*)(uint64_t, uint64_t, void *) noexcept'). Exception values are incompatible. Suggest adding 'noexcept' to the type of the value being assigned.

Error compiling Cython file:
------------------------------------------------------------
...
            rados_ioctx_t _ioctx = convert_ioctx(ioctx)
            char *_name = name
            librbd_progress_fn_t _prog_cb = &no_op_progress_callback
            void *_prog_arg = NULL
        if on_progress:
            _prog_cb = &progress_callback
                       ^
------------------------------------------------------------

rbd.pyx:763:23: Cannot assign type 'int (*)(uint64_t, uint64_t, void *) except? -1 nogil' to 'librbd_progress_fn_t' (alias of 'int (*)(uint64_t, uint64_t, void *) noexcept'). Exception values are incompatible. Suggest adding 'noexcept' to the type of the value being assigned.

Error compiling Cython file:
------------------------------------------------------------
...
        image_id = cstr(image_id, 'image_id')
        cdef:
            rados_ioctx_t _ioctx = convert_ioctx(ioctx)
            char *_image_id = image_id
            int _force = force
            librbd_progress_fn_t _prog_cb = &no_op_progress_callback
                                            ^
------------------------------------------------------------

rbd.pyx:868:44: Cannot assign type 'int (*)(uint64_t, uint64_t, void *) except? -1' to 'librbd_progress_fn_t' (alias of 'int (*)(uint64_t, uint64_t, void *) noexcept'). Exception values are incompatible. Suggest adding 'noexcept' to the type of the value being assigned.

Error compiling Cython file:
------------------------------------------------------------
...
            char *_image_id = image_id
            int _force = force
            librbd_progress_fn_t _prog_cb = &no_op_progress_callback
            void *_prog_arg = NULL
        if on_progress:
            _prog_cb = &progress_callback
                       ^
------------------------------------------------------------

rbd.pyx:871:23: Cannot assign type 'int (*)(uint64_t, uint64_t, void *) except? -1 nogil' to 'librbd_progress_fn_t' (alias of 'int (*)(uint64_t, uint64_t, void *) noexcept'). Exception values are incompatible. Suggest adding 'noexcept' to the type of the value being assigned.

Error compiling Cython file:
------------------------------------------------------------
...
        """
        image_name = cstr(image_name, 'image_name')
        cdef:
            rados_ioctx_t _ioctx = convert_ioctx(ioctx)
            char *_image_name = image_name
            librbd_progress_fn_t _prog_cb = &no_op_progress_callback
                                            ^
------------------------------------------------------------

rbd.pyx:1097:44: Cannot assign type 'int (*)(uint64_t, uint64_t, void *) except? -1' to 'librbd_progress_fn_t' (alias of 'int (*)(uint64_t, uint64_t, void *) noexcept'). Exception values are incompatible. Suggest adding 'noexcept' to the type of the value being assigned.

Error compiling Cython file:
------------------------------------------------------------
...
            rados_ioctx_t _ioctx = convert_ioctx(ioctx)
            char *_image_name = image_name
            librbd_progress_fn_t _prog_cb = &no_op_progress_callback
            void *_prog_arg = NULL
        if on_progress:
            _prog_cb = &progress_callback
                       ^
------------------------------------------------------------

rbd.pyx:1100:23: Cannot assign type 'int (*)(uint64_t, uint64_t, void *) except? -1 nogil' to 'librbd_progress_fn_t' (alias of 'int (*)(uint64_t, uint64_t, void *) noexcept'). Exception values are incompatible. Suggest adding 'noexcept' to the type of the value being assigned.

Error compiling Cython file:
------------------------------------------------------------
...
        """
        image_name = cstr(image_name, 'image_name')
        cdef:
            rados_ioctx_t _ioctx = convert_ioctx(ioctx)
            char *_image_name = image_name
            librbd_progress_fn_t _prog_cb = &no_op_progress_callback
                                            ^
------------------------------------------------------------

rbd.pyx:1124:44: Cannot assign type 'int (*)(uint64_t, uint64_t, void *) except? -1' to 'librbd_progress_fn_t' (alias of 'int (*)(uint64_t, uint64_t, void *) noexcept'). Exception values are incompatible. Suggest adding 'noexcept' to the type of the value being assigned.

Error compiling Cython file:
------------------------------------------------------------
...
            rados_ioctx_t _ioctx = convert_ioctx(ioctx)
            char *_image_name = image_name
            librbd_progress_fn_t _prog_cb = &no_op_progress_callback
            void *_prog_arg = NULL
        if on_progress:
            _prog_cb = &progress_callback
                       ^
------------------------------------------------------------

rbd.pyx:1127:23: Cannot assign type 'int (*)(uint64_t, uint64_t, void *) except? -1 nogil' to 'librbd_progress_fn_t' (alias of 'int (*)(uint64_t, uint64_t, void *) noexcept'). Exception values are incompatible. Suggest adding 'noexcept' to the type of the value being assigned.

Error compiling Cython file:
------------------------------------------------------------
...
        """
        image_name = cstr(image_name, 'image_name')
        cdef:
            rados_ioctx_t _ioctx = convert_ioctx(ioctx)
            char *_image_name = image_name
            librbd_progress_fn_t _prog_cb = &no_op_progress_callback
                                            ^
------------------------------------------------------------

rbd.pyx:1151:44: Cannot assign type 'int (*)(uint64_t, uint64_t, void *) except? -1' to 'librbd_progress_fn_t' (alias of 'int (*)(uint64_t, uint64_t, void *) noexcept'). Exception values are incompatible. Suggest adding 'noexcept' to the type of the value being assigned.

Error compiling Cython file:
------------------------------------------------------------
...
            rados_ioctx_t _ioctx = convert_ioctx(ioctx)
            char *_image_name = image_name
            librbd_progress_fn_t _prog_cb = &no_op_progress_callback
            void *_prog_arg = NULL
        if on_progress:
            _prog_cb = &progress_callback
                       ^
------------------------------------------------------------

rbd.pyx:1154:23: Cannot assign type 'int (*)(uint64_t, uint64_t, void *) except? -1 nogil' to 'librbd_progress_fn_t' (alias of 'int (*)(uint64_t, uint64_t, void *) noexcept'). Exception values are incompatible. Suggest adding 'noexcept' to the type of the value being assigned.

Error compiling Cython file:
------------------------------------------------------------
...
        cdef:
            rbd_completion_t completion
            PyObject* p_completion_obj= <PyObject*>completion_obj

        with nogil:
            ret = rbd_aio_create_completion(p_completion_obj, __aio_complete_cb,
                                                              ^
------------------------------------------------------------

rbd.pyx:2929:62: Cannot assign type 'void (rbd_completion_t, void *) except * nogil' to 'rbd_callback_t' (alias of 'void (*)(rbd_completion_t, void *) noexcept nogil'). Exception values are incompatible. Suggest adding 'noexcept' to the type of '__aio_complete_cb'.

Error compiling Cython file:
------------------------------------------------------------
...
        if not allow_shrink and old_size > size:
            raise InvalidArgument("error allow_shrink is False but old_size > new_size")
        cdef:
            uint64_t _size = size
            bint _allow_shrink = allow_shrink
            librbd_progress_fn_t prog_cb = &no_op_progress_callback
                                           ^
------------------------------------------------------------

rbd.pyx:3009:43: Cannot assign type 'int (*)(uint64_t, uint64_t, void *) except? -1' to 'librbd_progress_fn_t' (alias of 'int (*)(uint64_t, uint64_t, void *) noexcept'). Exception values are incompatible. Suggest adding 'noexcept' to the type of the value being assigned.

Error compiling Cython file:
------------------------------------------------------------
...
        """
        name = cstr(name, 'name')
        cdef:
            char *_name = name
            uint32_t _flags = flags
            librbd_progress_fn_t prog_cb = &no_op_progress_callback
                                           ^
------------------------------------------------------------

rbd.pyx:3517:43: Cannot assign type 'int (*)(uint64_t, uint64_t, void *) except? -1' to 'librbd_progress_fn_t' (alias of 'int (*)(uint64_t, uint64_t, void *) noexcept'). Exception values are incompatible. Suggest adding 'noexcept' to the type of the value being assigned.

Error compiling Cython file:
------------------------------------------------------------
...

        name = cstr(name, 'name')
        cdef:
            char *_name = name
            uint32_t _flags = flags
            librbd_progress_fn_t prog_cb = &no_op_progress_callback
                                           ^
------------------------------------------------------------

rbd.pyx:3576:43: Cannot assign type 'int (*)(uint64_t, uint64_t, void *) except? -1' to 'librbd_progress_fn_t' (alias of 'int (*)(uint64_t, uint64_t, void *) noexcept'). Exception values are incompatible. Suggest adding 'noexcept' to the type of the value being assigned.

Error compiling Cython file:
------------------------------------------------------------
...
        Flatten clone image (copy all blocks from parent to child)
        :param on_progress: optional progress callback function
        :type on_progress: callback function
        """
        cdef:
            librbd_progress_fn_t _prog_cb = &no_op_progress_callback
                                            ^
------------------------------------------------------------

rbd.pyx:4091:44: Cannot assign type 'int (*)(uint64_t, uint64_t, void *) except? -1' to 'librbd_progress_fn_t' (alias of 'int (*)(uint64_t, uint64_t, void *) noexcept'). Exception values are incompatible. Suggest adding 'noexcept' to the type of the value being assigned.

Error compiling Cython file:
------------------------------------------------------------
...
        """
        cdef:
            librbd_progress_fn_t _prog_cb = &no_op_progress_callback
            void *_prog_arg = NULL
        if on_progress:
            _prog_cb = &progress_callback
                       ^
------------------------------------------------------------

rbd.pyx:4094:23: Cannot assign type 'int (*)(uint64_t, uint64_t, void *) except? -1 nogil' to 'librbd_progress_fn_t' (alias of 'int (*)(uint64_t, uint64_t, void *) noexcept'). Exception values are incompatible. Suggest adding 'noexcept' to the type of the value being assigned.

Error compiling Cython file:
------------------------------------------------------------
...
    @requires_not_closed
    def rebuild_object_map(self):
        """
        Rebuild the object map for the image HEAD or currently set snapshot
        """
        cdef librbd_progress_fn_t prog_cb = &no_op_progress_callback
                                            ^
------------------------------------------------------------

rbd.pyx:4118:44: Cannot assign type 'int (*)(uint64_t, uint64_t, void *) except? -1' to 'librbd_progress_fn_t' (alias of 'int (*)(uint64_t, uint64_t, void *) noexcept'). Exception values are incompatible. Suggest adding 'noexcept' to the type of the value being assigned.
Traceback (most recent call last):
  File "/build/ceph-18.2.1/src/pybind/rbd/setup.py", line 192, in <module>
    ext_modules=cythonize(
  File "/nix/store/c55ks8c5p3qpvqy9azc5h05hij6d3fcf-python3-3.10.14-env/lib/python3.10/site-packages/Cython/Build/Dependencies.py", line 1154, in cythonize
    cythonize_one(*args)
  File "/nix/store/c55ks8c5p3qpvqy9azc5h05hij6d3fcf-python3-3.10.14-env/lib/python3.10/site-packages/Cython/Build/Dependencies.py", line 1321, in cythonize_one
    raise CompileError(None, pyx_file)
Cython.Compiler.Errors.CompileError: rbd.pyx
make[2]: *** [src/pybind/rbd/CMakeFiles/cython_rbd.dir/build.make:74: lib/cython_modules/lib.3/rbd.cpython-310-x86_64-linux-gnu.so] Error 1
make[1]: *** [CMakeFiles/Makefile2:5126: src/pybind/rbd/CMakeFiles/cython_rbd.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
...

Notify maintainers
@johanot @krav
Metadata
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.82, NixOS, 23.11 (Tapir), 23.11.20240326.4473351`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - nixpkgs: `/nix/store/b2hxgkvh0jrkxfv312xcrmrr3qyz50c1-source`

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

Relevent warning before:
warning: c_rbd.pxd:596:48: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
warning: ../rados/rados.pxd:7:0: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310

so seems like this may be an upstream cython compatiblity issue

last hydra build: https://cache.nixos.org/log/14ld094d4rq3y17zb74xi5i5j3wx0p64-ceph-18.2.1.drv
Comparing to my gist, the last successful hyra build seems to be getting cython 0.2.9, but my build is getting cython 3.0?

fix here: https://github.com/NixOS/nixpkgs/pull/302358

This doesn't sound like https://tracker.ceph.com/issues/63591. Please open an upstream issue.

@dotlambda: I am getting a 404 when I try and create an account on their issue tracker. Does anyone reading have an existing account?

Closing since fix was merged into staging-next

authors: danielbarter dotlambda


text:
washed out colors on nixos-unstable starting from  33d1e75

Describe the bug
My laptop display's colors are washed out/brighter since 33d1e75. The previous hydra build 2057814 is still working.
colord seems to be starting normally. Gnome Settings also shows the color profile in the color management section.
I would be happy to narrow the issue down to a specific commit, but I haven't figured out how to pin the flake input to a nixpkgs commit which hasn't a hydra build.
Steps To Reproduce
Steps to reproduce the behavior:

Log into gnome
colors are washed out, especially greens.

Expected behavior
The colors should look the same after upgrading.
Additional context
I'm using a Lenovo Yoga running Gnome 46 on wayland. The bug is also present on X11.
Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
Console output from the working rev:

[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.8.9, NixOS, 24.05 (Uakari), 24.05.20240512.2057814`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.2`
 - nixpkgs: `/nix/store/vsbi6gfwf2bdamw0d0d9xndb1rrxfnbk-source`

Console output from the broken rev:
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.8.9, NixOS, 24.05 (Uakari), 24.05.20240515.33d1e75`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.2`
 - nixpkgs: `/nix/store/vsbi6gfwf2bdamw0d0d9xndb1rrxfnbk-source`

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

Seems to be fixed on master

I'm having the same issue on 24.05 and switching to unstable fixed it.
Though I would rather stay on 24.05.

source: gharchive/issue

authors: EricTheMagician cschierig

repo: NixOS/nixpkgs

license: MIT

license_type: permissive

license_source: github-api


text:
Build failure: nixos-icons

Steps To Reproduce
Steps to reproduce the behavior:

use nixos-unstable
run nix flake update
run nixos-rebuild switch / nh os switch (both got same result)

Build log
┏━ 1 Errors:
┃ error: builder for '/nix/store/z91ybgfcwfb16z9qjaynw079yasj0vyy-source-patched.drv' failed with exit code 2;
┃        last 5 log lines:
┃        > Running phase: unpackPhase
┃        > unpacking source archive /nix/store/8gzig2c39hd1h1vf0rqvadw11vy3kxas-source
┃        > source root is source
┃        > Running phase: patchPhase
┃        > /nix/store/9ip31vbkgg0lp4rx042svlllv3945nxq-stdenv-linux/setup: eval: line 231: unexpected EOF while looking for matching `''
┃        For full logs, run 'nix log /nix/store/z91ybgfcwfb16z9qjaynw079yasj0vyy-source-patched.drv'.
┣━ Dependency Graph:
┃       ┌─ ⏸ unit-dbus.service waiting for 1 ⚠
┃       │  ┌─ ⏸ X-Restart-Triggers-polkit waiting for 1 ⚠
┃       ├─ ⏸ unit-polkit.service
┃    ┌─ ⏸ system-units
┃    │     ┌─ ⏸ X-Restart-Triggers-dbus waiting for 1 ⚠
┃    │  ┌─ ⏸ unit-dbus.service
┃    ├─ ⏸ user-units
┃    │        ┌─ ⚠ source-patched failed with exit code 2 after ⏱ 0s in patchPhase
┃    │     ┌─ ⏸ nixos-icons-0-unstable-2024-04-10
┃    │  ┌─ ⏸ system-path
┃    ├─ ⏸ dbus-1
┃ ┌─ ⏸ etc
┃ ⏸ nixos-system-s0mePC-nix-24.11.20241009.5633bcf
┣━━━ Builds
┗━ ∑ ⏵ 0 │ ✔ 0 │ ⏸ 12 │ ⚠ Exited after 1 build failures at 21:22:36 after 13s

Additional context
yes, flakes;
Notify maintainers
i won't ping like ~3k ppls xD

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
 ~ 𝑠𝑛𝑜𝑤𝑦 𝑝𝑙𝑎𝑐𝑒, 𝑓𝑢𝑙𝑙 𝑜𝑓 𝑓𝑙𝑎𝑘𝑒𝑠! 

╭──╴ on NixOS 24.11.0 ❄
┆ ~
╰─> nix-info -m                                                                                ❲✓ ❳ at ❗ 21:25
 - system: `"x86_64-linux"`
 - host os: `Linux 6.11.1-cachyos, NixOS, 24.11 (Vicuna), 24.11.20241004.bc947f5`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.8`
 - channels(root): `"home-manager, nixos"`
 - nixpkgs: `/nix/store/sdzpqjwx7pdx6lsq6llyfqqf7hspp83c-source`

╭──╴ on NixOS 24.11.0 ❄
┆ ~
╰─>                                                                                was 5s ❲✓ ❳ at ❗ 21:25

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

i reeeaaally don't know what to do, bc for me - this is extraordinary situation, before this all my rebuild works fine

nixos-icons build just fine for me on latest unstable.
Could you share more detailed logs?

nixos-icons build just fine for me on latest unstable.
Could you share more detailed logs?

all i have:
 ~ 𝑠𝑛𝑜𝑤𝑦 𝑝𝑙𝑎𝑐𝑒, 𝑓𝑢𝑙𝑙 𝑜𝑓 𝑓𝑙𝑎𝑘𝑒𝑠! 

╭──╴ on NixOS 24.11.0 ❄
┆ ~
╰─> nh os switch flake/                                                                                ❲✓ ❳ at ❗ 22:18
> Building NixOS configuration
these 13 derivations will be built:
  /nix/store/z91ybgfcwfb16z9qjaynw079yasj0vyy-source-patched.drv
  /nix/store/k6528l1r26mjlfr4dgsaxq1l80p5fnpw-nixos-icons-0-unstable-2024-04-10.drv
  /nix/store/v47mr6w7pfrlv7dkh93q9smck8sdmla2-system-path.drv
  /nix/store/cfg02vqif4crkb62l3995d4a5rc420z4-X-Restart-Triggers-polkit.drv
  /nix/store/3railn9wc59zxda1aakz305r9sg43qgp-unit-polkit.service.drv
  /nix/store/6j00bvmp5qn6wphn6l55qxqg7f3if17q-dbus-1.drv
  /nix/store/nvkkffmlpvhwbryslwrd2k781xa6319q-X-Restart-Triggers-dbus.drv
  /nix/store/m7jd2ifxlsg4jvlh0n01ksvmipdg2jf3-unit-dbus.service.drv
  /nix/store/cjd264d42zs7vxzlybhymiqx5r88is2j-user-units.drv
  /nix/store/xs17ir0wcgka8h14538ic83vfpvdd9ax-unit-dbus.service.drv
  /nix/store/wyyb207bwzakw54az8as8mqnjyqqq7d2-system-units.drv
  /nix/store/lzizw69ckzkvypcbd562lpsz845rspxl-etc.drv
  /nix/store/4f4b6gp5p27nkc9rwkg5hzi6rgdg7ajq-nixos-system-s0mePC-nix-24.11.20241009.5633bcf.drv
source-patched> building '/nix/store/z91ybgfcwfb16z9qjaynw079yasj0vyy-source-patched.drv'
source-patched> Running phase: unpackPhase
source-patched> unpacking source archive /nix/store/8gzig2c39hd1h1vf0rqvadw11vy3kxas-source
source-patched> source root is source
source-patched> Running phase: patchPhase
source-patched> /nix/store/9ip31vbkgg0lp4rx042svlllv3945nxq-stdenv-linux/setup: eval: line 231: unexpected EOF while looking for matching `''
error: builder for '/nix/store/z91ybgfcwfb16z9qjaynw079yasj0vyy-source-patched.drv' failed with exit code 2;
       last 5 log lines:
       > Running phase: unpackPhase
       > unpacking source archive /nix/store/8gzig2c39hd1h1vf0rqvadw11vy3kxas-source
       > source root is source
       > Running phase: patchPhase
       > /nix/store/9ip31vbkgg0lp4rx042svlllv3945nxq-stdenv-linux/setup: eval: line 231: unexpected EOF while looking for matching `''
       For full logs, run 'nix log /nix/store/z91ybgfcwfb16z9qjaynw079yasj0vyy-source-patched.drv'.
error: 1 dependencies of derivation '/nix/store/k6528l1r26mjlfr4dgsaxq1l80p5fnpw-nixos-icons-0-unstable-2024-04-10.drv' failed to build
error: 1 dependencies of derivation '/nix/store/v47mr6w7pfrlv7dkh93q9smck8sdmla2-system-path.drv' failed to build
error: 1 dependencies of derivation '/nix/store/4f4b6gp5p27nkc9rwkg5hzi6rgdg7ajq-nixos-system-s0mePC-nix-24.11.20241009.5633bcf.drv' failed to build
┏━ 1 Errors:
┃ error: builder for '/nix/store/z91ybgfcwfb16z9qjaynw079yasj0vyy-source-patched.drv' failed with exit code 2;
┃        last 5 log lines:
┃        > Running phase: unpackPhase
┃        > unpacking source archive /nix/store/8gzig2c39hd1h1vf0rqvadw11vy3kxas-source
┃        > source root is source
┃        > Running phase: patchPhase
┃        > /nix/store/9ip31vbkgg0lp4rx042svlllv3945nxq-stdenv-linux/setup: eval: line 231: unexpected EOF while looking for matching `''
┃        For full logs, run 'nix log /nix/store/z91ybgfcwfb16z9qjaynw079yasj0vyy-source-patched.drv'.
┣━ Dependency Graph:
┃       ┌─ ⏸ unit-dbus.service waiting for 1 ⚠
┃       │  ┌─ ⏸ X-Restart-Triggers-polkit waiting for 1 ⚠
┃       ├─ ⏸ unit-polkit.service
┃    ┌─ ⏸ system-units
┃    │     ┌─ ⏸ X-Restart-Triggers-dbus waiting for 1 ⚠
┃    │  ┌─ ⏸ unit-dbus.service
┃    ├─ ⏸ user-units
┃    │        ┌─ ⚠ source-patched failed with exit code 2 after ⏱ 0s in patchPhase
┃    │     ┌─ ⏸ nixos-icons-0-unstable-2024-04-10
┃    │  ┌─ ⏸ system-path
┃    ├─ ⏸ dbus-1
┃ ┌─ ⏸ etc
┃ ⏸ nixos-system-s0mePC-nix-24.11.20241009.5633bcf
┣━━━ Builds
┗━ ∑ ⏵ 0 │ ✔ 0 │ ⏸ 12 │ ⚠ Exited after 1 build failures at 22:18:09 after 3s
Error:
   0: Command exited with status Exited(1)

Location:
   src/commands.rs:151

╭──╴ on NixOS 24.11.0 ❄
┆ ~
╰─>                                                                                was 3s ❲✗ ❳ at ❗ 22:18

and
╭──╴ on NixOS 24.11.0 ❄
┆ ~
╰─> nix log "/nix/store/z91ybgfcwfb16z9qjaynw079yasj0vyy-source-patched.drv^*"                                                                                ❲✗ ❳ at ❗ 22:21
Running phase: unpackPhase
@nix { "action": "setPhase", "phase": "unpackPhase" }
unpacking source archive /nix/store/8gzig2c39hd1h1vf0rqvadw11vy3kxas-source
source root is source
Running phase: patchPhase
@nix { "action": "setPhase", "phase": "patchPhase" }
/nix/store/9ip31vbkgg0lp4rx042svlllv3945nxq-stdenv-linux/setup: eval: line 231: unexpected EOF while looking for matching `''

And does it build successfully if you try to rebuild using an older flake.lock?

And does it build successfully if you try to rebuild using an older flake.lock?

nope, i've tried 6 different (i mean, 6 gens) lock files, and nothing seems to work, idk :D

Then the problem should be in your config.
Could you share your updated configuration?

Then the problem should be in your config.
Could you share your updated configuration?

i could, but not today, 'k?

'k, found why this happened:
stylix. i'll work more with stylix, ths y'all :D


text:
Build failure: amdvlk

Steps To Reproduce
Steps to reproduce the behavior:

Attempt to build the steam package
Wait 10 minutes for amdvlk to compile

Build log
building the system configuration...
trace: evaluation warning: pagedmov profile: Setting programs.eza.icons to a Boolean is deprecated.
Please update your configuration so that

  programs.eza.icons = "auto"
[2/17/72 built, 9/34/58 copied (575.4/1708.8 MiB), 122.8/325.3 MiB DL] building amdvlk-2024.Q3.2 (buildPhase): [1447/2841] Building CXX object compiler/llpc/llvm/lib/CodeGeerror: builder for '/nix/store/jy4xs329wkwznisac8p52sd7n73fxqb9-amdvlk-2024.Q3.2.drv' failed with exit code 1;
       last 10 log lines:
       > Compiling (dxc spirv=True) InitExecuteIndirect.hlsl:InitExecuteIndirect -> InitExecuteIndirect_spv.h...Success
       > Compiling (dxc spirv=True) PairCompression.hlsl:PairCompression -> PairCompression_spv.h...Success
       > Compiling (dxc spirv=True) MergeSort.hlsl:MergeSort -> MergeSort_spv.h...Success
       > Compiling (dxc spirv=True) BuildFastAgglomerativeLbvh.hlsl:BuildFastAgglomerativeLbvh -> BuildFastAgglomerativeLbvh_spv.h...Success
       > Compiling (dxc spirv=True) BuildBVHTDTR.hlsl:BuildBVHTD -> BuildBVHTDTR_spv.h...Success
       > Compiling (dxc spirv=True) BuildQBVH.hlsl:BuildQBVH -> BuildQBVH_spv.h...Success
       > Compiling (dxc spirv=True) BuildParallel.hlsl:BuildBvh -> BuildParallel_spv.h...Success
       > [1821/2841] Building AMDGPUGenAsmWriter.inc...
       > [1822/2841] Building AMDGPUGenAsmMatcher.inc...
       > ninja: build stopped: subcommand failed.
       For full logs, run 'nix log /nix/store/jy4xs329wkwznisac8p52sd7n73fxqb9-amdvlk-2024.Q3.2.drv'.
error: 1 dependencies of derivation '/nix/store/l1bip6xf2mrjdjchpp48nwdjf02h86qv-graphics-drivers-32bit.drv' failed to build
error: 1 dependencies of derivation '/nix/store/bscsr3pmf8dn3vlsw50zim95b1n6n5j2-steam-run-usr-multi.drv' failed to build
error: 1 dependencies of derivation '/nix/store/dj5mbykaqq6yyxrivnma9p7anscxw4cg-steam-usr-multi.drv' failed to build
error: 1 dependencies of derivation '/nix/store/gqwvvg5zvjqxqji8px0l7fhcj3671dgg-graphics-driver.conf.drv' failed to build
error: 1 dependencies of derivation '/nix/store/iv62pkx4480fib4nd9qv70hvpir9rm5h-steam-fhs.drv' failed to build
error: 1 dependencies of derivation '/nix/store/rqjhi64pcp6yqq5dv157z9ypszg538s1-steam-run-fhs.drv' failed to build
error: 1 dependencies of derivation '/nix/store/s5ihzjmvl0xl1clcgfvpdaz67bb1mbyp-steam-bwrap.drv' failed to build
error: 1 dependencies of derivation '/nix/store/l4gi74lnk8y11yj3s2nnyj9qb4gx933w-steam-run-bwrap.drv' failed to build
error: 1 dependencies of derivation '/nix/store/48pggdqw9vc60pvd05jzgpjv3jwkxm72-tmpfiles.d.drv' failed to build
error: 1 dependencies of derivation '/nix/store/hrcafmxkyvbr3xrm4frrn3683v87k03i-etc.drv' failed to build
error: 1 dependencies of derivation '/nix/store/d94dryr5wrmpfmjy76k9f6szv2njawg7-steam-run.drv' failed to build
error: 1 dependencies of derivation '/nix/store/xhcfbyzda7hc3i5z6awin90j8p4znhl9-steam.drv' failed to build
error: 1 dependencies of derivation '/nix/store/rwrh1ndpcvlqh0sn50ahpp7nyjmmbxdr-nixos-system-argon-24.11.20241014.a3c0b3b.drv' failed to build

Compiler build log:
https://gist.github.com/pagedMov/2fb0b5eb84588461ef7222e0e7c4e9ef

Additional context
This was working up until today, and I'm not sure what exactly happened. I was able to build my system config with steam last night, woke up this morning and amdvlk refuses to build now. I'm enabling steam via the programs.steam module, tried it in both my system and home-manager configurations with no change in the behavior. Tried git bisect, and commits that were previously able to build the package no longer can.
Notify maintainers
@Flakebi
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
 - system: `"x86_64-linux"`
 - host os: `Linux 6.11.2, NixOS, 24.11 (Vicuna), 24.11.20241009.5633bcf`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.8`
 - channels(root): `"home-manager, nixos-24.05"`
 - nixpkgs: `/nix/store/60sn02zhawl3kwn0r515zff3h6hg6ydz-source`

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

Appears to be related to the hardware.amdgpu.amdvlk attribute set, disabling it allowed my config to rebuild. Currently testing it
with amdgpu.amdvlk.support32Bit enabled, will report results

Confirmed fails to build even with the support32Bit option enabled

Same

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

Im experiencing this too (identical error), however I'm experiencing it when building various apps like bitwarden-desktop for example - can provide logs if required

I'm also having the exact same problem

I'm getting exactly the same error as well

Same issue for me just started after updating. Any fix or workaround or just a waiting game?

I am experiencing the same issue when trying to build my system. AMDVLK fails to build.
error: builder for '/nix/store/h2adl88hvwrndpq24kw8pav8hwzia1yb-amdvlk-2024.Q3.2.drv' failed with exit code 1;
       last 10 log lines:
       > [1826/2845] Building AMDGPUGenAsmMatcher.inc...
       > [1827/2845] Building CXX object compiler/llpc/llvm/lib/CodeGen/SelectionDAG/CMakeFiles/LLVMSelectionDAG.dir/DAGCombiner.cpp.o
       > /build/amdvlk-src/drivers/llvm-project/llvm/lib/CodeGen/SelectionDAG/DAGCombiner.cpp: In function 'llvm::SDValue FoldIntToFPToInt(llvm::SDNode*, llvm::SelectionDAG&)':
       > /build/amdvlk-src/drivers/llvm-project/llvm/lib/CodeGen/SelectionDAG/DAGCombiner.cpp:17939:23: warning: possibly dangling reference to a temporary [-Wdangling-reference]
       > 17939 |   const fltSemantics &Sem = N0.getValueType().getFltSemantics();
       >       |                       ^~~
       > /build/amdvlk-src/drivers/llvm-project/llvm/lib/CodeGen/SelectionDAG/DAGCombiner.cpp:17939:62: note: the temporary was destroyed at the end of the full expression 'N0.llvm::SDValue::getValueType().llvm::EVT::getFltSemantics()'
       > 17939 |   const fltSemantics &Sem = N0.getValueType().getFltSemantics();
       >       |                             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
       > ninja: build stopped: subcommand failed.
       For full logs, run 'nix log /nix/store/h2adl88hvwrndpq24kw8pav8hwzia1yb-amdvlk-2024.Q3.2.drv'.

Same here:
building the system configuration...
error: builder for '/nix/store/jy4xs329wkwznisac8p52sd7n73fxqb9-amdvlk-2024.Q3.2.drv' failed with exit code 1;
       last 25 log lines:
       > Compiling (dxc spirv=True) InitExecuteIndirect.hlsl:InitExecuteIndirect -> InitExecuteIndirect_spv.h...Success
       > Compiling (dxc spirv=True) DeserializeAS.hlsl:DeserializeAS -> DeserializeAS_spv.h...Success
       > Compiling (dxc spirv=True) PairCompression.hlsl:PairCompression -> PairCompression_spv.h...Success
       > Compiling (dxc spirv=True) InitAccelerationStructure.hlsl:InitAccelerationStructure -> InitUpdateAccelerationStructure_spv.h...Success
       > Compiling (dxc spirv=True) InitAccelerationStructure.hlsl:InitAccelerationStructure -> InitAccelerationStructure_spv.h...Success
       > Compiling (dxc spirv=True) MergeSort.hlsl:MergeSort -> MergeSort_spv.h...Success
       > Compiling (dxc spirv=True) BuildBVHTDTR.hlsl:BuildBVHTD -> BuildBVHTDTR_spv.h...Success
       > Compiling (dxc spirv=True) CompactAS.hlsl:CompactAS -> CompactAS_spv.h...Success
       > Compiling (dxc spirv=True) BuildFastAgglomerativeLbvh.hlsl:BuildFastAgglomerativeLbvh -> BuildFastAgglomerativeLbvh_spv.h...Success
       > Compiling (dxc spirv=True) BuildQBVH.hlsl:BuildQBVH -> BuildQBVH_spv.h...Success
       > Compiling (dxc spirv=True) Rebraid.hlsl:Rebraid -> Rebraid_spv.h...Success
       > Compiling (dxc spirv=True) BuildParallel.hlsl:BuildBvh -> BuildParallel_spv.h...Success
       > [1822/2841] Building CXX object compiler/llpc/llvm/lib/CodeGen/SelectionDAG/CMakeFiles/LLVMSelectionDAG.dir/FastISel.cpp.o
       > [1823/2841] Building CXX object compiler/llpc/llvm/lib/CodeGen/SelectionDAG/CMakeFiles/LLVMSelectionDAG.dir/LegalizeDAG.cpp.o
       > [1824/2841] Building AMDGPUGenAsmWriter.inc...
       > [1825/2841] Building AMDGPUGenAsmMatcher.inc...
       > [1826/2841] Building CXX object compiler/llpc/llvm/lib/CodeGen/SelectionDAG/CMakeFiles/LLVMSelectionDAG.dir/DAGCombiner.cpp.o
       > /build/amdvlk-src/drivers/llvm-project/llvm/lib/CodeGen/SelectionDAG/DAGCombiner.cpp: In function 'llvm::SDValue FoldIntToFPToInt(llvm::SDNode*, llvm::SelectionDAG&)':
       > /build/amdvlk-src/drivers/llvm-project/llvm/lib/CodeGen/SelectionDAG/DAGCombiner.cpp:17939:23: warning: possibly dangling reference to a temporary [-Wdangling-reference]
       > 17939 |   const fltSemantics &Sem = N0.getValueType().getFltSemantics();
       >       |                       ^~~
       > /build/amdvlk-src/drivers/llvm-project/llvm/lib/CodeGen/SelectionDAG/DAGCombiner.cpp:17939:62: note: the temporary was destroyed at the end of the full expression 'N0.llvm::SDValue::getValueType().llvm::EVT::getFltSemantics()'
       > 17939 |   const fltSemantics &Sem = N0.getValueType().getFltSemantics();
       >       |                             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
       > ninja: build stopped: subcommand failed.
       For full logs, run 'nix log /nix/store/jy4xs329wkwznisac8p52sd7n73fxqb9-amdvlk-2024.Q3.2.drv'.
error: 1 dependencies of derivation '/nix/store/l1bip6xf2mrjdjchpp48nwdjf02h86qv-graphics-drivers-32bit.drv' failed to build
error: 1 dependencies of derivation '/nix/store/yn18fpg3k46nikbz6vzn85kg1wvwfa3h-graphics-driver.conf.drv' failed to build
error: 1 dependencies of derivation '/nix/store/ln880b7vk1kg0w6ljkwbfyzr7mrnkdak-tmpfiles.d.drv' failed to build
error: 1 dependencies of derivation '/nix/store/rfh8k1wapwx9f1wik9p3hixwygs04dfm-etc.drv' failed to build
error: 1 dependencies of derivation '/nix/store/vsn0sqj99hg8xqqvan1b6cr5pmhinvby-nixos-system-Yon-24.11.20241014.a3c0b3b.drv' failed to build

same here.... not just with amdvlk, but with multiple packages. Commenting them in config will lead to amdvlk
error: builder for '/nix/store/jy4xs329wkwznisac8p52sd7n73fxqb9-amdvlk-2024.Q3.2.drv' failed with exit code 1;
last 10 log lines:
> Compiling (dxc spirv=True) PairCompression.hlsl:PairCompression -> PairCompression_spv.h...Success
> Compiling (dxc spirv=True) MergeSort.hlsl:MergeSort -> MergeSort_spv.h...Success
> Compiling (dxc spirv=True) BuildFastAgglomerativeLbvh.hlsl:BuildFastAgglomerativeLbvh -> BuildFastAgglomerativeLbvh_spv.h...Success
> Compiling (dxc spirv=True) Update.hlsl:UpdateTriangles -> UpdateTriangles_spv.h...Success
> Compiling (dxc spirv=True) BuildQBVH.hlsl:BuildQBVH -> BuildQBVH_spv.h...Success
> Compiling (dxc spirv=True) BuildBVHTDTR.hlsl:BuildBVHTD -> BuildBVHTDTR_spv.h...Success
> Compiling (dxc spirv=True) BuildParallel.hlsl:BuildBvh -> BuildParallel_spv.h...Success
> [1820/2841] Building AMDGPUGenAsmWriter.inc...
> [1821/2841] Building AMDGPUGenAsmMatcher.inc...
> ninja: build stopped: subcommand failed.
For full logs, run 'nix log /nix/store/jy4xs329wkwznisac8p52sd7n73fxqb9-amdvlk-2024.Q3.2.drv'.
error: 1 dependencies of derivation '/nix/store/2wia0900dnqv62r5h0ys06417f988g4f-system-path.drv' failed to build
error: 1 dependencies of derivation '/nix/store/4s26avigpm7bdxz5fh2si5qmi28bwwij-nixos-system-Terminal-416-24.11.20241014.a3c0b3b.drv' failed to build

Seems to be caused by https://github.com/NixOS/nixpkgs/commit/c3948c21ef00fbf8ef02f3c2922e84ba72e8a62b
It also compiles with glslang-15.0.0 (with shared libs), but haven't tested it yet.

see also: https://github.com/NixOS/nixpkgs/pull/344568#issuecomment-2409029219

In addition to @unkn's overlay example above, I added this in the new attrset for my_gslang:
    cmakeFlags = [];

This effectively reverses the mentioned commit https://github.com/NixOS/nixpkgs/commit/c3948c21ef00fbf8ef02f3c2922e84ba72e8a62b.  I had to do this to get it to work again.  I didn't test if the rest of the overlay was necessary for me after adding this line.

I opened a PR to fix glslang until staging-next is merged:  #349246

authors: Ate329 Flakebi Kim-Ronin LoganBarnett RedJ1ve SeekerOfAsh Svenum bendlas oluceps pagedMov tijso unhitched9271 unkn


text:
gpg does not have fallback non-graphical pinentry on macOS

Issue description
Without configuration, any gpg command that requires pinentry fails either explicitly or silently when invoked from a non-graphical session.
E.g., if logged in both via SSH and a local graphical session, invoking gpg through SSH appears to hang while waiting for a graphical pinentry dialogue displayed in the other session. It is not apparent to the SSH user what is happening at first, since the user might not be in physical proximity to the remote machine, or the user's graphical session is in the background (i.e., fast user switching).
E.g., if logged in only via SSH, gpg explicitly fails with error sending to agent: No pinentry.
gpg should ship with a textual pinentry fallback by default.
Steps to reproduce
(over SSH)
someones-imac:~ someone$ gpg --import secret.asc
gpg: directory '/Users/someone/.gnupg' created
gpg: keybox '/Users/someone/.gnupg/pubring.kbx' created
gpg: /Users/someone/.gnupg/trustdb.gpg: trustdb created
gpg: key 7F0E3A2FA4778096: public key "Sir Example <example@example.com>" imported
^C
gpg: signal Interrupt caught ... exiting

Technical details

system: "x86_64-darwin"
host os: Darwin 17.5.0, macOS 10.13.4
multi-user?: yes
sandbox: no
version: nix-env (Nix) 2.0.2
channels(root): "nixpkgs-18.09pre139198.9d0b6b9dfc9"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixpkgs

This is a bug in pinentry-mac, but something that I would like to fix. See this comment from pinentry-mac:
https://github.com/GPGTools/pinentry-mac/blob/master/Source/main.m#L52-L82

authors: amckinlay matthewbauer


text:
dconf fails tests on armv7l-linux

Building dconf fails on armv7l-linux. The shared memory test fails.
The complete log is below:
building '/nix/store/5yqhikpp5sjl422s28vg71fcjym4q5b9-dconf-0.30.1.drv'...
unpacking sources
unpacking source archive /nix/store/canh30a3lr5pmqdr6jgnn01qh4qzyhm2-dconf-0.30.1.tar.xz
source root is dconf-0.30.1
setting SOURCE_DATE_EPOCH to timestamp 1540245184 of file dconf-0.30.1/trim-lcov.py
patching sources
applying patch /nix/store/a63acqqz1bjda6fal37gy0n8jsjjsh53-49f4d916e1151af3975df52c522c69de98ed2fbb.patch
patching file gvdb/gvdb-reader.c
patching file gvdb/gvdb-reader.h
patching script interpreter paths in meson_post_install.py
meson_post_install.py: interpreter directive changed from "/usr/bin/env python3" to "/nix/store/ihxv5wfgg5dri0q2aijzvp6wgp56m1j9-python3-3.7.2/bin/python3"
updateAutotoolsGnuConfigScriptsPhase
configuring
meson flags: --buildtype=release         --libdir=/nix/store/w26gknp61y08q7jfs4xf3gr9p0mk19a3-dconf-0.30.1-lib/lib --libexecdir=/nix/store/w26gknp61y08q7jfs4xf3gr9p0mk19a3-dconf-0.30.1-lib/libexec         --bindir=/nix/store/nr3b9r88fq4b22i1zirgj01mnhggq3ny-dconf-0.30.1/bin --sbindir=/nix/store/nr3b9r88fq4b22i1zirgj01mnhggq3ny-dconf-0.30.1/sbin         --includedir=/nix/store/47klh3xngccfbmwvwq80c9rsvjr3asa7-dconf-0.30.1-dev/include         --mandir=/nix/store/nr3b9r88fq4b22i1zirgj01mnhggq3ny-dconf-0.30.1/share/man --infodir=/nix/store/nr3b9r88fq4b22i1zirgj01mnhggq3ny-dconf-0.30.1/share/info         --localedir=/nix/store/w26gknp61y08q7jfs4xf3gr9p0mk19a3-dconf-0.30.1-lib/share/locale         -Dauto_features=disabled         --prefix=/nix/store/nr3b9r88fq4b22i1zirgj01mnhggq3ny-dconf-0.30.1 --sysconfdir=/etc -Dgtk_doc=true
The Meson build system
Version: 0.49.1
Source dir: /build/dconf-0.30.1
Build dir: /build/dconf-0.30.1/build
Build type: native build
Project name: dconf
Project version: 0.30.1
Native C compiler: /nix/store/yf357wms27m8z59zf6n6jbld34kfa560-gcc-wrapper-7.4.0/bin/cc (gcc 7.4.0 "gcc (GCC) 7.4.0")
Native Vala compiler: valac (valac 0.42.4)
Build machine cpu family: arm
Build machine cpu: armv7l
Found pkg-config: /nix/store/ksp2wzaa6yrzxcwqdcvz1s8c3afai9iy-pkg-config-0.29.2/bin/pkg-config (0.29.2)
Dependency gio-2.0 found: YES 2.58.2
Dependency gio-unix-2.0 found: YES 2.58.2
Dependency glib-2.0 found: YES 2.58.2
Dependency dbus-1 found: YES 1.12.12
Dependency vapigen found: YES 0.42.4
Dependency bash-completion found: YES 2.8
Configuring config.h using configuration
Compiler for C supports arguments -fvisibility=hidden: YES
Configuring ca.desrt.dconf.service using configuration
Program abicheck.sh found: YES (/build/dconf-0.30.1/gsettings/abicheck.sh)
Library posix found: YES
Program xsltproc found: YES (/nix/store/mi0368ff20z9ji5467klm24rp2jaqnb5-libxslt-1.1.33-bin/bin/xsltproc)
Library dl found: YES
Library m found: YES
Program meson_post_install.py found: YES (/build/dconf-0.30.1/meson_post_install.py)
Build targets in project: 29
Found ninja-1.9.0 at /nix/store/3ixxaybak98v52cc29r9z5miswdbncw4-ninja-1.9.0/bin/ninja
meson: enabled parallel building
building
build flags: -j1 -l1
[1/77] Compiling C object 'shm/feecd04@@dconf-shm@sta/dconf-shm.c.o'.
[2/77] Linking static target shm/libdconf-shm.a.
[3/77] Compiling C object 'gvdb/6f5c6fc@@gvdb@sta/gvdb-builder.c.o'.
[4/77] Compiling C object 'gvdb/6f5c6fc@@gvdb@sta/gvdb-reader.c.o'.
[5/77] Linking static target gvdb/libgvdb.a.
[6/77] Compiling C object 'common/92a5dc0@@dconf-common@sta/dconf-changeset.c.o'.
[7/77] Compiling C object 'common/92a5dc0@@dconf-common@sta/dconf-error.c.o'.
[8/77] Compiling C object 'common/92a5dc0@@dconf-common@sta/dconf-paths.c.o'.
[9/77] Linking static target common/libdconf-common.a.
[10/77] Compiling C object 'common/92a5dc0@@dconf-common-hidden@sta/dconf-changeset.c.o'.
[11/77] Compiling C object 'common/92a5dc0@@dconf-common-hidden@sta/dconf-error.c.o'.
[12/77] Compiling C object 'common/92a5dc0@@dconf-common-hidden@sta/dconf-paths.c.o'.
[13/77] Compiling C object 'engine/ed9f6f2@@dconf-engine@sta/dconf-engine.c.o'.
[14/77] Linking static target common/libdconf-common-hidden.a.
[15/77] Compiling C object 'engine/ed9f6f2@@dconf-engine@sta/dconf-engine-profile.c.o'.
[16/77] Compiling C object 'engine/ed9f6f2@@dconf-engine@sta/dconf-engine-source.c.o'.
[17/77] Compiling C object 'engine/ed9f6f2@@dconf-engine@sta/dconf-engine-source-file.c.o'.
[18/77] Compiling C object 'engine/ed9f6f2@@dconf-engine@sta/dconf-engine-source-user.c.o'.
[19/77] Compiling C object 'engine/ed9f6f2@@dconf-engine@sta/dconf-engine-source-service.c.o'.
[20/77] Compiling C object 'engine/ed9f6f2@@dconf-engine@sta/dconf-engine-source-system.c.o'.
[21/77] Generating dconf-generated.c with a custom command.
[22/77] Linking static target engine/libdconf-engine.a.
[23/77] Generating dconf-generated.h with a custom command.
[24/77] Compiling C object 'service/9df6b02@@dconf-service@sta/meson-generated_.._dconf-generated.c.o'.
[25/77] Compiling C object 'service/9df6b02@@dconf-service@sta/dconf-blame.c.o'.
[26/77] Compiling C object 'service/9df6b02@@dconf-service@sta/dconf-gvdb-utils.c.o'.
[27/77] Compiling C object 'service/9df6b02@@dconf-service@sta/dconf-shm-writer.c.o'.
[28/77] Compiling C object 'service/9df6b02@@dconf-service@sta/dconf-writer.c.o'.
../service/dconf-writer.c: In function 'dconf_writer_real_commit':
../service/dconf-writer.c:178:7: warning: ignoring return value of 'write', declared with attribute warn_unused_result [-Wunused-result]
       write (invalidate_fd, "\0\0\0\0\0\0\0\0", 8);
       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[29/77] Compiling C object 'service/9df6b02@@dconf-service@sta/dconf-keyfile-writer.c.o'.
[30/77] Compiling C object 'service/9df6b02@@dconf-service@sta/dconf-service.c.o'.
[31/77] Linking static target service/libdconf-service.a.
[32/77] Compiling C object 'service/9df6b02@@dconf-service@exe/main.c.o'.
[33/77] Linking target service/dconf-service.
[34/77] Compiling C object 'gdbus/8d60afc@@dconf-gdbus-thread@sta/dconf-gdbus-thread.c.o'.
[35/77] Linking static target gdbus/libdconf-gdbus-thread.a.
[36/77] Compiling C object 'gdbus/8d60afc@@dconf-gdbus-filter@sta/dconf-gdbus-filter.c.o'.
[37/77] Linking static target gdbus/libdconf-gdbus-filter.a.
[38/77] Compiling C object 'gsettings/df7c3da@@dconfsettings@sha/dconfsettingsbackend.c.o'.
[39/77] Compiling C object 'client/948fe60@@dconf-client@sta/dconf-client.c.o'.
[40/77] Linking target gsettings/libdconfsettings.so.
[41/77] Linking static target client/libdconf-client.a.
[42/77] Compiling C object 'client/948fe60@@dconf@sha/dconf-client.c.o'.
[43/77] Compiling C object 'bin/51a1f05@@dconf@exe/.._gvdb_gvdb-builder.c.o'.
[44/77] Linking target client/libdconf.so.1.0.0.
[45/77] Generating symbol file 'client/948fe60@@dconf@sha/libdconf.so.1.0.0.symbols'.
[46/77] Compiling Vala source ../client/dconf.vapi ../bin/gvdb.vapi ../bin/dconf-dump.vala ../bin/dconf-update.vala ../bin/dconf.vala.
[47/77] Compiling C object 'bin/51a1f05@@dconf@exe/meson-generated_dconf-dump.c.o'.
[48/77] Compiling C object 'bin/51a1f05@@dconf@exe/meson-generated_dconf-update.c.o'.
[49/77] Compiling C object 'bin/51a1f05@@dconf@exe/meson-generated_dconf.c.o'.
[50/77] Linking target bin/dconf.
[51/77] Generating dconf.1 with a custom command.
[52/77] Compiling C object 'tests/59830eb@@dconf-mock@sta/dconf-mock-dbus.c.o'.
[53/77] Generating dconf.7 with a custom command.
[54/77] Generating dconf-service.1 with a custom command.
[55/77] Compiling C object 'tests/59830eb@@dconf-mock@sta/dconf-mock-gvdb.c.o'.
[56/77] Compiling C object 'tests/59830eb@@dconf-mock@sta/dconf-mock-shm.c.o'.
[57/77] Linking static target tests/libdconf-mock.a.
[58/77] Compiling C object 'tests/59830eb@@paths@exe/paths.c.o'.
[59/77] Linking target tests/paths.
[60/77] Compiling C object 'tests/59830eb@@changeset@exe/changeset.c.o'.
[61/77] Linking target tests/changeset.
[62/77] Compiling C object 'tests/59830eb@@shm@exe/shm.c.o'.
[63/77] Compiling C object 'tests/59830eb@@shm@exe/tmpdir.c.o'.
[64/77] Compiling C object 'tests/59830eb@@gvdb@exe/gvdb.c.o'.
[65/77] Linking target tests/shm.
[66/77] Linking target tests/gvdb.
[67/77] Compiling C object 'tests/59830eb@@gdbus-thread@exe/dbus.c.o'.
[68/77] Compiling C object 'tests/59830eb@@gdbus-filter@exe/dbus.c.o'.
[69/77] Linking target tests/gdbus-thread.
[70/77] Linking target tests/gdbus-filter.
[71/77] Compiling C object 'tests/59830eb@@engine@exe/engine.c.o'.
[72/77] Linking target tests/engine.
[73/77] Compiling C object 'tests/59830eb@@client@exe/client.c.o'.
[74/77] Linking target tests/client.
[75/77] Compiling C object 'tests/59830eb@@writer@exe/meson-generated_.._.._service_dconf-generated.c.o'.
[76/77] Compiling C object 'tests/59830eb@@writer@exe/writer.c.o'.
[77/77] Linking target tests/writer.
running tests
check flags: -j1 -l1 test
[0/1] Running all tests.
 1/10 abicheck                                OK       0.05 s
 2/10 paths                                   OK       0.02 s
 3/10 changeset                               OK       0.34 s
 4/10 shm                                     FAIL     0.04 s (killed by signal 5 SIGTRAP)
 5/10 gvdb                                    OK      15.31 s
 6/10 gdbus-thread                            SKIP     0.04 s
 7/10 gdbus-filter                            SKIP     0.04 s
 8/10 engine                                  OK       6.15 s
 9/10 client                                  OK       0.04 s
10/10 writer                                  OK       0.04 s

Ok:                    7
Expected Fail:         0
Fail:                  1
Unexpected Pass:       0
Skipped:               2
Timeout:               0

The output from the failed tests:

 4/10 shm                                     FAIL     0.04 s (killed by signal 5 SIGTRAP)

--- command ---
G_TEST_BUILDDIR='/build/dconf-0.30.1/build/tests' G_DEBUG='gc-friendly,fatal-warnings' G_TEST_SRCDIR='/build/dconf-0.30.1/tests' MALLOC_CHECK_='2' LC_ALL='C.UTF-8' /build/dconf-0.30.1/build/tests/shm
--- stdout ---
/shm/mkdir-fail: OK
/shm/close-null: OK
/shm/open-and-flag:
--- stderr ---

(/build/dconf-0.30.1/build/tests/shm:2824): dconf-CRITICAL **: 09:59:39.862: failed to allocate file '/build/dconf-testcase.Q55F0Z/dconf/foo': Invalid argument.  dconf will not work properly.
-------

Full log written to /build/dconf-0.30.1/build/meson-logs/testlog.txt
FAILED: meson-test
/nix/store/5kn3lj7mimz6vl6ihd1pl7v5y1p3pj1l-meson-0.49.1/bin/meson test --no-rebuild --print-errorlogs
ninja: build stopped: subcommand failed.
builder for '/nix/store/5yqhikpp5sjl422s28vg71fcjym4q5b9-dconf-0.30.1.drv' failed with exit code ```

It seems as though this has been broken for a while, but tests have only recently been enabled.

This should be probably reported upstream https://gitlab.gnome.org/GNOME/dconf/issues


text:
Packaging for Gnome Games (libretro frontend)

Project description
Games is a GNOME application to browse your video games library and to easily pick and play a game from it. It uses libretro.
Metadata

homepage URL: https://wiki.gnome.org/Apps/Games
source URL: https://gitlab.gnome.org/GNOME/gnome-games/
license: gpl3
platforms: linux

We could probably pick this up with #68318.

I still think it could be a nice addition to nixos

Not Stale

I have started working on this:

I opened a PR for retro-gtk which is a dependency;
I started working on packaging Gnome Games in a dedicated branch.

Feel free to help by reviewing and contributing to the branch.

/cc @NixOS/gnome My branch has a buildable Gnome Games package. Because Gnome Games still depend on Tracker 2 and Gnome ships with Tracker 3, I had to include a derivation for tracker 2. When launching gnome-games, I get an error:
(org.gnome.Games:224080): GLib-GIO-ERROR **: 20:59:12.294: Settings schema 'org.freedesktop.Tracker.FTS' is not installed
Trace/breakpoint trap (core dumped)

I'm not on NixOS and I don't have tracker running so I'm not sure what the next step is.

@DamienCassou You are missing wrapGAppsHook as per https://nixos.org/manual/nixpkgs/stable/#ssec-gnome-common-issues-missing-schema.
Also, it might be more convenient to use the patch from the PR, otherwise you will also need to install Tracker 2 as systemd service, which requires more plumbing outside of NixOS/home-manager.

Thank you very much for your help @jtojnar: I've updated the branch and the application launches now. I will open a PR when https://github.com/NixOS/nixpkgs/pull/124168 is merged.

@DamienCassou Did you ever PR gnome.gnome-games?

@Krutonium: I never did. I still have the patch but now Gnome Games has been renamed to Highscore and the dependencies completely changed (e.g., no more Grilo or Tracker dependencies).
Here is the patch in case you want to work on adapting it:
{ lib
, stdenv
, fetchurl
, fetchpatch
, meson
, ninja
, pkg-config
, vala
, cmake
, libarchive
, glib
, grilo
, libxml2
, gtk3
, libhandy
, libmanette
, retro-gtk
, librsvg
, libsoup
, sqlite
, desktop-file-utils
, appstream-glib
, python3
, tracker
, wrapGAppsHook
}:

stdenv.mkDerivation rec {
  pname = "gnome-games";
  version = "40.0";

  src = fetchurl {
    url = "mirror://gnome/sources/gnome-games/${lib.versions.major version}/${pname}-${version}.tar.xz";
    sha256 = "03yzd97kpkjdzfqp8qx3mqnf9347yk830njam2q78ai9i4zl3k9j";
  };

  patches = [
    # https://gitlab.gnome.org/GNOME/gnome-games/-/merge_requests/424
    (fetchpatch {
      name   = "gnome-games-port-to-tracker3.patch";
      url    = "https://gitlab.gnome.org/GNOME/gnome-games/-/commit/d38e93160a8e16776bb1fdc46f547365d3f2c9ee.patch";
      sha256 = "0k7g7p8spdnvzfg6p9rqbvj5df5yx7wgz0m8w963ls0bv00fp0fc";
    })
  ];

  nativeBuildInputs = [
    meson pkg-config ninja vala cmake glib libxml2 grilo gtk3 libhandy libmanette retro-gtk librsvg
    libsoup sqlite libarchive tracker desktop-file-utils appstream-glib python3 wrapGAppsHook
  ];

  preInstall = ''
    patchShebangs ../build-aux/post_install.py
  '';

  meta = with lib; {
    description = "Simple game launcher for GNOME";
    longDescription = ''
      Just as your music player does, Games shows you all of your
      installed games with their cover art, even Steam and retro
      games, and sorts them by developer or platform.

      Many legacy game platforms are supported and tightly integrated
      into Games' interface. Simply select your preferred video
      filter, grab your gamepad and enjoy your game.

      When you leave an integrated game, your progress is
      automatically saved so you can restart where you left off.
    '';
    homepage = "https://wiki.gnome.org/Apps/Games";
    changelog = "https://gitlab.gnome.org/GNOME/gnome-games/-/blob/master/NEWS";
    license = licenses.gpl3Plus;
    maintainers = [ maintainers.DamienCassou ];
    platforms = platforms.all;
  };
}

authors: DamienCassou Krutonium jtojnar murdos worldofpeace


text:
R arrow package

Project description
The Apache Arrow serialization library for R.
Metadata

homepage URL: https://arrow.apache.org/docs/r/
source URL: https://github.com/apache/arrow
license: apache2
platforms: unix, linux, darwin, ...

There is already rPackages.arrow but it's missing runtime libraries. Attempting to use it gives an error:
> arrow::read_feather('my.feather')
Error in io___MemoryMappedFile__Open(path, mode) :
  Cannot call io___MemoryMappedFile__Open(). Please use arrow::install_arrow() to install required runtime libraries.

I encountered the same issue. I think the first thing to check is how the R library finds the C++ library.
I asked for help on the arrow project: https://github.com/apache/arrow/issues/7034

reading https://arrow.apache.org/docs/r/articles/install.html#how-dependencies-are-resolved, I don't think it is possible to build rPackages.arrow in such a way that it always finds the arrow-cpp installation.
I have a workaround now. https://gist.github.com/Zhen-hao/8bdc7b2afe10f270f3f7e280a89c5ef0
if the arrow library is not working in the shell, just manually install the same version one more time.

Is anyone actively looking at this? If not, I can try putting together a PR fixing this—I got an override working on my local machine on both NixOS and macOS.

Is anyone actively looking at this? If not, I can try putting together a PR fixing this—I got an override working on my local machine on both NixOS and macOS.

Is anyone actively looking at this? If not, I can try putting together a PR fixing this—I got an override working on my local machine on both NixOS and macOS.

Is anyone actively looking at this? If not, I can try putting together a PR fixing this—I got an override working on my local machine on both NixOS and macOS.

Still have this issue on NixOS unstable.

Okay. I am trying to fix this.
Last time I tried, I was held up because the R library was at version 1.0.0, but the Arrow C++ library in Nixpkgs was 2.0.0. To fix that, I opened #108268 so that the R Arrow package was brought up to 2.0.0. I had to focus on other things after that got merged; in the meantime, the Arrow C++ library in Nixpkgs got upgraded to 3.0.0.
I had a fix working locally based on @Zhen-hao's examples, but it fails to build now. I'm pretty sure it's because of the 2.0.0 vs 3.0.0 version mismatch.
What's the best way to proceed? Should I do another CRAN/etc version bump? Is there some lighter-weight way to only upgrade the R Arrow package? Is there a way to point the R package at an older version of the Arrow C++ library? Going forwards, if the C++ library has breaking releases relatively often, would we need to bump the entire R package set often to keep them in sync? Does bumping the R package set more often create an undue maintenance or testing burden?
Would love some advice from somebody more experienced with Nixpkgs and the R package system in particular. @peti or @SuperSandro2000?

I have no idea about R.

@TikhonJelvis  I'm guessing this GitHub issue has a small viewership; maybe some people who know the answer follow the Discourse forum.

rPackages.arrow should work fine in master starting after 64b5504939f37e608b3e894287abf9890a6fcc79 and c4d8bd324f2733d8706e932052bb3f2e50d64ed4.
To answer @TikhonJelvis's questions:

What's the best way to proceed? Should I do another CRAN/etc version bump? Is there some lighter-weight way to only upgrade the R Arrow package?

I have updated only the arrow package now because I didn't have much time and I just wanted to get results as quickly as possible, but updating the package set in its entirety would be the better solution here, even if it is more effort. Our package set is pretty old already. Anyhow, it is possible to cherry-pick certain updates for R if a complete update is undesirable for some reason.

Is there a way to point the R package at an older version of the Arrow C++ library?

If we would have an older version around, then it would be possible to point the R build to it by adding an appropriate override: https://github.com/NixOS/nixpkgs/blob/c4d8bd324f2733d8706e932052bb3f2e50d64ed4/pkgs/development/r-modules/default.nix#L234

Going forwards, if the C++ library has breaking releases relatively often, would we need to bump the entire R package set often to keep them in sync?

That would be the best solution, IMHO. Updating arrow comes with the risk that dependencies or arrow become outdated and we end up losing features or performance or maybe even introducing bugs. It's not a major risk, I suppose, but still updating the package set would be preferable. The maintenance effort involved in such an update is moderate, IMHO.

authors: SuperSandro2000 TikhonJelvis Zhen-hao jtrakk peti


text:
nixpkgs docs for fetchzip don't explain how the hash is calculated.

Describe the bug
After reading https://nixos.org/manual/nixpkgs/stable/#chap-pkgs-fetchers I could not tell that fetchurl and fetchzip would require different hashes for the same tarball.
In particular the docs say "The main difference between fetchurl and fetchzip is in how they store the contents." so it sounds like all other details (urls, hashes, etc…) remain identical.
After talking in irc, I realize now that the hash must be over the expanded contents for fetchzip. Also, that makes sense if all fixed output derivations always hash directly over outputs, but as a newcomer reading these docs I didn't realize that.
To Reproduce
Point a newcomer to nix at those docs and ask if the hash needs to be the same or different for fetchurl vs fetchzip. ;-)
Expected behavior
The fetchzip docs should change from saying

The main difference between fetchurl and fetchzip is in how they store the contents.

-to something like:

The main difference between fetchurl and fetchzip is in how they store the contents. Since fixed output hashes are always cover the output, the sha256 attr for these two will be different for the same archive.

Additional context
Note a tangential use case issue for my case: I need external reviewers who don't know much at all about nix to verify that the nix build is fetching the same pinned archives as our production build system. Thus, they must compare the hashes match. Therefore I cannot use fetchzip which uses a nix-specific hashing algorithm, and instead I have to use fetchurl (which uses a scheme common to many open source build/packaging systems) and then make a trivial "untar" builder.
Notify maintainers

Metadata
$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 4.15.0-112-generic, Ubuntu, 18.04.4 LTS (Bionic Beaver)`
 - multi-user?: `no`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.7`
 - channels(n): `"nixpkgs-21.03pre243353.6d4b93323e7"`
 - nixpkgs: `/home/n/.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:

and then make a trivial "untar" builder

You can actually use a hook for that, no need for a separate builder.

Note a tangential use case issue for my case [...]

I think many (transitive) use cases for fetchzip are when the hash of the archive may not really be stable but hash of the unpacked contents should be (various version control services).

Does https://nixos.wiki/wiki/Nix_Hash help? Especially https://nixos.wiki/wiki/Nix_Hash#What_exactly_is_hashed

It helped me alot.

Does https://nixos.wiki/wiki/Nix_Hash help? Especially https://nixos.wiki/wiki/Nix_Hash#What_exactly_is_hashed

Maybe just add some parentheses. IMHO it would be useful for new users like myself and it would not bloat the manual that much.

The main difference between fetchurl and fetchzip (uses nix-hash) is in how they store the contents.


text:
zoom-us: Update

Motivation for this change
Update package - This is not working yet, @danbst @tadfisher  - It segfaults with this in the log:
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
[CZPClientLogMgr::LogClientEnvironment] [MacAddr: ...][client: Linux][OS: NixOS 21.03 (Okapi)][Hardware: CPU Core:4 Frenquency:1.8 G Memory size:15833MB CPU Brand:Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz GPU Brand:][Req ID: ]
Linux Client Version is 5.4.54779.1115
QSG_RENDER_LOOP is
XDG_CURRENT_DESKTOP = GNOME;   GDMSESSION = gnome
Client: Breakpad is using Client-Server Mode! client fd = 3
Error: Send error, 22 Invalid argument
Error: Send error, 22 Invalid argument
Error: Send error, 22 Invalid argument
Graphics Card Info:: 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) (rev 02)
Zoom package arch is 64bit, runing OS arch is x86_64

IDK what to do :(.
However I made the update script act as expected - it needed a change due to how their website changed a bit the format of the version string.
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/)
[ ] 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.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/show-case-for-nix-ld-run-umodified-zoom/11004/1

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/show-case-for-nix-ld-run-umodified-zoom/11004/1

I chose a different approach in https://github.com/NixOS/nixpkgs/pull/109602
Seems to work so far.

I chose a different approach in https://github.com/NixOS/nixpkgs/pull/109602
Seems to work so far.

source: gharchive/pull-request

authors: Mic92 doronbehar nixos-discourse


text:
arduino-ci: init at 0.1.0

arduino-ci allows you to quickly add continuous integration (CI) tests
to Arduino libraries. It uses arduino-cli to install dependencies and
then it compiles every example with every board.
I am the primary author of the arduino-ci project.

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

[ ] 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/)
[ ] 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 106468 1

1 package built:

arduino-ci

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

1 package built:

arduino-ci

Result of nixpkgs-review pr 106468 1

1 package built:

arduino-ci


text:
codespell: enable tests

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)

[ ] 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.

Result of nixpkgs-review pr 112949 at d999a09b run on x86_64-linux 1

6 packages built:

codespell (python38Packages.codespell)
python37Packages.aspell-python
python37Packages.codespell
python38Packages.aspell-python
python39Packages.aspell-python
python39Packages.codespell

Result of nixpkgs-review pr 112949 at d999a09b run on aarch64-linux 1

6 packages built:

codespell (python38Packages.codespell)
python37Packages.aspell-python
python37Packages.codespell
python38Packages.aspell-python
python39Packages.aspell-python
python39Packages.codespell

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It 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 112949 run on x86_64-darwin 1

6 packages built:

codespell (python38Packages.codespell)
python37Packages.aspell-python
python37Packages.codespell
python38Packages.aspell-python
python39Packages.aspell-python
python39Packages.codespell


text:
treewide (darwin): fix or enable darwin build for many packages (6)

Motivation for this change
See #114976 for details.
Things done

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

[ ] 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)
[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/)
[ ] 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 116600 run on x86_64-darwin 1

13 packages built:

apparix
bbe
bcunit
catcli
cdi2iso
cpcfs
dejsonlz4
epstool
git-fire
idsk
ministat
mpd-mpris
zdelta

Result of nixpkgs-review pr 116600 at 2d0392f5 run on x86_64-linux 1

4 packages built successfully:

cdi2iso
dejsonlz4
epstool
zdelta

9 suggestions:

warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/tools/compression/zdelta/default.nix:19:3:
   |
19 |   meta = with lib; {
   |   ^

warning: missing-patch-comment
Please add a comment on the line above, explaining the purpose of this patch.
Near pkgs/tools/graphics/epstool/default.nix:22:15:
   |
22 |   patches = [ ./gcc43.patch ];
   |               ^

warning: missing-phase-hooks
buildPhase should probably contain runHook preBuild and runHook postBuild.
Near pkgs/tools/compression/dejsonlz4/default.nix:12:5:
   |
12 |     buildPhase = ''
   |     ^

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/tools/cd-dvd/cdi2iso/default.nix:16:3:
   |
16 |   installPhase = ''
   |   ^

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/tools/compression/dejsonlz4/default.nix:16:5:
   |
16 |     installPhase = ''
   |     ^

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/tools/compression/zdelta/default.nix:14:3:
   |
14 |   installPhase = ''
   |   ^

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/tools/graphics/epstool/default.nix:18:3:
   |
18 |   installPhase = ''
   |   ^

warning: unclear-gpl
gpl2 is a deprecated license, check if project uses gpl2Plus or gpl2Only and change meta.license accordingly.
Near pkgs/tools/cd-dvd/cdi2iso/default.nix:24:5:
   |
24 |     license = licenses.gpl2;
   |     ^

warning: unclear-gpl
gpl2 is a deprecated license, check if project uses gpl2Plus or gpl2Only and change meta.license accordingly.
Near pkgs/tools/graphics/epstool/default.nix:27:5:
   |
27 |     license = licenses.gpl2;
   |     ^

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It 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 116600 run on x86_64-darwin 1

13 packages built:

apparix
bbe
bcunit
catcli
cdi2iso
cpcfs
dejsonlz4
epstool
git-fire
idsk
ministat
mpd-mpris
zdelta

The following issues got detected with the above build packages.
Please fix at least the ones listed with your changed packages:

apparix:

warning: unclear-gpl
gpl2 is a deprecated license, check if project uses gpl2Plus or gpl2Only and change meta.license accordingly.
Near pkgs/tools/misc/apparix/default.nix:17:5:
   |
17 |     license = licenses.gpl2;
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/unclear-gpl.md

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

21 packages built:

altermime
apparix
bash_unit
bbe
bcunit
catcli
cdi2iso
cpcfs
dejsonlz4
dhcping
epstool
git-fire
httperf
idsk
imgurbash2
ministat
mpd-mpris
sfeed
spirv-cross
vimer
zdelta

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It 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 116600 run on x86_64-linux 1

5 packages built:

altermime
cdi2iso
dejsonlz4
epstool
zdelta

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It 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 116600 run on x86_64-darwin 1

21 packages built:

altermime
apparix
bash_unit
bbe
bcunit
catcli
cdi2iso
cpcfs
dejsonlz4
dhcping
epstool
git-fire
httperf
idsk
imgurbash2
ministat
mpd-mpris
sfeed
spirv-cross
vimer
zdelta

authors: SuperSandro2000 r-rmcgibbo siraben


text:
heimer: 2.2.0 -> 2.4.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/juzzlin/heimer/releases.
meta.description for heimer is: "Simple cross-platform mind map and note-taking tool written in Qt"
meta.homepage for heimer is: "https://github.com/juzzlin/Heimer"
meta.changelog for heimer 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

/nix/store/raglcc646ndi7f4hqzl9xdb5lanl8x8i-heimer-2.4.0/bin/heimer passed the binary check.

/nix/store/raglcc646ndi7f4hqzl9xdb5lanl8x8i-heimer-2.4.0/bin/.heimer-wrapped passed the binary check.

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

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

found 2.4.0 with grep in /nix/store/raglcc646ndi7f4hqzl9xdb5lanl8x8i-heimer-2.4.0

found 2.4.0 in filename of file in /nix/store/raglcc646ndi7f4hqzl9xdb5lanl8x8i-heimer-2.4.0

directory tree listing: https://gist.github.com/811399f059d655f36055e03bc22e0fe8

du listing: https://gist.github.com/6a37aa73325e577039302ff66cf95098

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
heimer

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/raglcc646ndi7f4hqzl9xdb5lanl8x8i-heimer-2.4.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 heimer https://github.com/r-ryantm/nixpkgs/archive/518f0d857d54398ef402e1a2d9c9debe13203386.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/raglcc646ndi7f4hqzl9xdb5lanl8x8i-heimer-2.4.0
ls -la /nix/store/raglcc646ndi7f4hqzl9xdb5lanl8x8i-heimer-2.4.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:

heimer

Maintainer pings
cc @dtzWill for testing.

Result of nixpkgs-review pr 118221 at 518f0d85 run on x86_64-linux 1

1 package built successfully:

heimer

1 suggestion:

warning: unclear-gpl
gpl3 is a deprecated license, please check if project uses gpl3Plus or gpl3Only and change meta.license accordingly.
Near pkgs/applications/misc/heimer/default.nix:20:5:
   |
20 |     license = licenses.gpl3;
   |     ^

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

1 package built:

heimer

authors: r-rmcgibbo r-ryantm tomberek


text:
mailman-web-unstable: 2019-09-29 -> 2021-04-10

Motivation for this change
Failing to build since #118527
setuptools-scm now required as a build input.
Upstream removed mailman_web.settings.base +
mailman_web.settings.mailman from mailman_web.settings.init.py
so now the imports in settings.py are explicit. Their
documentation on virtualenv installation specifies these too.
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"
[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)
[X] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 119135 at 1ae59812 run on aarch64-linux 1

2 packages built successfully:

mailman-web (python38Packages.mailman-web)
python39Packages.mailman-web

2 suggestions:

warning: python-include-tests
Consider adding a checkPhase for tests, or if not feasible, pythonImportsCheck.
Near pkgs/servers/mail/mailman/web.nix:40:0:
   |
40 |     description = "Django project for Mailman 3 web interface";
   | ^

warning: unclear-gpl
gpl3 is a deprecated license, please check if project uses gpl3Plus or gpl3Only and change meta.license accordingly.
Near pkgs/servers/mail/mailman/web.nix:41:5:
   |
41 |     license = licenses.gpl3;
   |     ^

Failing to build since #118527

Small correction: build failure was actually introduced by #116672

This PR changed the path mailman-web uses for its database, which broke
the mailman module.  @m1cr0man, did you test this PR with the Mailman
NixOS module?
I've reverted this PR in d0ead9021e93bbf162c7625627d426ea4206b9a4 and
marked mailman-web as broken, since it's better to have somebody be
unable to update than to update their system into something that's
broken at runtime that they might not even notice.

This PR changed the path mailman-web uses for its database, which broke the mailman module. @m1cr0man, did you test this PR with the Mailman NixOS module? I've reverted this PR in d0ead90 and marked mailman-web as broken, since it's better to have somebody be unable to update than to update their system into something that's broken at runtime that they might not even notice.

Yes! Infact it was due to a database migration I was doing myself that necessitated the update.
What is the actual issue with the path here? It is working just fine on my system, although both my core and hyperkitty are set to use postgres not sqlite.
I would rather fix the issue than mark it as broken. The package was over a year out of date on nixos.

What is the actual issue with the path here? It is working just fine
on my system, although both my core and hyperkitty are set to use
postgres not sqlite.

Recent mailman-web has set BASE_DIR to /opt/mailman/web, so it would
look there for everything where we weren't explicitly setting the PATH,
including the SQLite database.
I think the best way forward here will be to add a way to override
BASE_DIR, and probably get that upstream.

I would rather fix the issue than mark it as broken. The package was
over a year out of date on nixos.

I would too, but I don't want people's working mailman instances to be
broken in the meantime, so the thing to do here was to revert and mark
broken ASAP, then start working on fixing it properly.
By the way, was there a reason you went for an update to another
unstable version when there was a release in Jan 2021 with only 8
commits since?  Was there something you needed in one of those commits?

What is the actual issue with the path here? It is working just fine on my system, although both my core and hyperkitty are set to use postgres not sqlite.
Recent mailman-web has set BASE_DIR to /opt/mailman/web, so it would look there for everything where we weren't explicitly setting the PATH, including the SQLite database. I think the best way forward here will be to add a way to override BASE_DIR, and probably get that upstream.

Do we not just need to set BASE_DIR here? Surely that would be sufficient? Otherwise I'll go read the config schema and find something specific to the db.

By the way, was there a reason you went for an update to another unstable version when there was a release in Jan 2021 with only 8 commits since? Was there something you needed in one of those commits?

The commit/revision referenced by this PR includes a change I committed upstream to remove an error on startup. I felt it was worth using the newest commit and I reviewed the changes between 0.0.2 and master.

Recent mailman-web has set BASE_DIR to /opt/mailman/web, so it would
look there for everything where we weren't explicitly setting the
PATH, including the SQLite database. I think the best way forward
here will be to add a way to override BASE_DIR, and probably get that
upstream.

Do we not just need to set BASE_DIR
here?
Surely that would be sufficient? Otherwise I'll go read the config
schema and find something specific to the db.

It would not be sufficient, because other files in mailman-web's base.py
interpolate the value of BASE_DIR.  My new thinking though is that we
should just patch to set BASE_DIR to /var/lib/mailman-web in the
package, though, because that's the standard place for system services
from a distribution to install things.  Just like we'd set
--localstatedir=/var/lib/mailman-web if this had a configure script.
Upstream seems to mostly be targeting installation on top of existing
distributions, and uses a path by default that makes sense for that use
case.  And that's fine, but in our packaging we should set it to a
location that makes sense for us and our users, and that location is in
/var/lib.

By the way, was there a reason you went for an update to another
unstable version when there was a release in Jan 2021 with only 8
commits since? Was there something you needed in one of those
commits?

The commit/revision referenced by this PR includes a change I
committed upstream to remove an error on startup. I felt it was worth
using the newest commit and I reviewed the changes between 0.0.2 and
master.

Valid.  Let's update to that revision again in the next try, then. :)

authors: alyssais m1cr0man r-rmcgibbo


text:
python3Packages.pytest-xdist: 2.2.1 -> 2.3.0

Motivation for this change
https://github.com/pytest-dev/pytest-xdist/blob/v2.3.0/CHANGELOG.rst
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

[ ] (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 127247 at 2f4ac303 run on x86_64-linux 1

17 packages marked as broken and skipped:

cassandra_2_1
cassandra_2_2
googleearth-pro
grass
hadoop
hadoop_2_7
hadoop_2_8
hadoop_2_9
impressive
invoice2data
linuxPackages_hardkernel_4_14.virtualbox
linuxPackages_hardkernel_latest.virtualbox
natron
odpdown
opentsdb
pig
spark

11509 packages skipped due to time constraints:

DisnixWebService
EBTKS
Fabric (python38Packages.Fabric)
MACS2
R
_389-ds-base
abcl
acd-cli
acousticbrainz-client
actdiag (python38Packages.actdiag)
...

7 packages built successfully:

python38Packages.betamax
python38Packages.chardet
python38Packages.hypothesis
python38Packages.pytest-xdist (python38Packages.pytest_xdist)
python38Packages.requests
python38Packages.requests_download
python38Packages.responses

Merged into my local working tree for python-unstable. Thank you.

authors: dotlambda mweinelt r-rmcgibbo


text:
stdenv: arithmetic fixes

Motivation for this change
This is a PR in the series of stdenv proposed shell fixes
This PR can be controversial.
This removes the -i flag that makes the shell parser dynamic. (the -i flag does not work with oil shell, but is not needed as well, the drawback is that the intent that the variable is an integer is less clear).
This also uses the ((...)) form for arithmetic computation.
The original proposed commits are https://github.com/NixOS/nixpkgs/pull/127736/commits/59ec2c78d25d557a4934c8a5489c800c397a76a9
and https://github.com/NixOS/nixpkgs/pull/127736/commits/e0b7c1223b5d8bb2861c3f3810820d4f9df45b1e
I omitted some changes in the original PR because I'm not 100% sure about those.
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/)
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.

This whole set of changes needs to target staging, and not master.

@lovesegfault thank you for your feedback.
I only mentioned in it in the original PR here https://github.com/NixOS/nixpkgs/pull/13059
Basically, I'm only targeting master to get faster hydra builds.
This PR will definitely merged (if it can) on staging.

Well, for all intention-revealing, in my opinion -i is also a non-local wait-what waiting to happen (although it is true that in this case it should not happen becaue we only assign good integers, but …)
And (( )) was already used, so using it more consistently shouldn't hurt.
Have you checked any cross-compilation?
(In the ideal world we would have a full-cross test where architecture A builds a cross-compiler from B to C, the it is run in Qemu-emulated B, then the output is checked on Qemu-emulated C; but I am not aware of such a test easily available; pkgsCross could be used for some one-step tests, though)

I haven't checked cross compilation that is a good idea.
I am still trying to figure out how to run massive rebuilds myself with hydra. I'll update when I have made some progress on that.

Just talked to vladimir about running some cross tests. Hopefully I can do it in the next day or 2

Ok vladimir was nice enough to run cross compilation on a whole set of PRs
https://github.com/NixOS/nixpkgs/pull/132490
If you have time on your hands, feel free to have a look at the other PRs in the list
(the tests were run before that last -i removal, but I think we can agree that it won't change much).
Thanks again for taking a look at this!

authors: 7c6f434c happysalada lovesegfault


text:
fnm: init at 1.26.0

Motivation for this change
Add fnm
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/)
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.

Test failures on Codespaces:
failures:
    archive::zip::tests::test_zip_extraction
    commands::install::tests::test_set_default_on_new_installation
    downloader::tests::test_installing_node_12
    downloader::tests::test_installing_npm
    remote_node_index::tests::test_list
    shell::infer::unix::tests::test_get_process_info

Wait for ofborg to see if there's something different

Most tests failed due to network problem:
Installing Node v8.11.3 (x64)
error: Can't download the requested binary: HttpError: error sending request for url (https://nodejs.org/dist/v8.11.3/node-v8.11.3-linux-x64.tar.xz): error trying to connect: dns error: failed to lookup address information: Name or service not known

So I just disabled the test entirely.


text:
jetbrains-jdk: 11.0.10-b1427 -> 11_0_11-b1504.13

The homepage has been updated.

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)
[ ] 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 132379 run on x86_64-linux 1

15 packages built:

bluej
greenfoot
jetbrains.clion
jetbrains.datagrip
jetbrains.goland
jetbrains.idea-community
jetbrains.idea-ultimate
jetbrains.jdk
jetbrains.mps
jetbrains.phpstorm
jetbrains.pycharm-community
jetbrains.pycharm-professional
jetbrains.rider
jetbrains.ruby-mine
jetbrains.webstorm

authors: klDen siraben


text:
step-ca: 0.16.0 -> 0.16.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/smallstep/certificates/releases.
meta.description for step-ca is: "A private certificate authority (X.509 & SSH) & ACME server for secure automated certificate management, so you can use TLS everywhere & SSO for SSH"
meta.homepage for step-ca is: "https://smallstep.com/certificates/"
meta.changelog for step-ca is: ""
Updates performed

Golang 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

Warning: no invocation of /nix/store/vs8xv4sv9rn8lnszszvmbrrc4wysmlhq-step-ca-0.16.2/bin/step-awskms-init had a zero exit code or showed the expected version

Warning: no invocation of /nix/store/vs8xv4sv9rn8lnszszvmbrrc4wysmlhq-step-ca-0.16.2/bin/step-yubikey-init had a zero exit code or showed the expected version

Warning: no invocation of /nix/store/vs8xv4sv9rn8lnszszvmbrrc4wysmlhq-step-ca-0.16.2/bin/step-cloudkms-init had a zero exit code or showed the expected version

Warning: no invocation of /nix/store/vs8xv4sv9rn8lnszszvmbrrc4wysmlhq-step-ca-0.16.2/bin/step-pkcs11-init had a zero exit code or showed the expected version

/nix/store/vs8xv4sv9rn8lnszszvmbrrc4wysmlhq-step-ca-0.16.2/bin/step-ca passed the binary check.

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

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

found 0.16.2 in filename of file in /nix/store/vs8xv4sv9rn8lnszszvmbrrc4wysmlhq-step-ca-0.16.2

directory tree listing: https://gist.github.com/47a6d1a4dddf33ad5e53aa6f25083d85

du listing: https://gist.github.com/6e9525abf045e827548079f02866c5b1

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

8 total rebuild path(s)

3 package rebuild(s)

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

First fifty rebuilds by attrpath
nixos-install-tools
step-ca
tests.nixos-functions.nixos-test

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/vs8xv4sv9rn8lnszszvmbrrc4wysmlhq-step-ca-0.16.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 step-ca https://github.com/r-ryantm/nixpkgs/archive/6df214b21bfeda09736abe3b72658a0b9f337caf.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/vs8xv4sv9rn8lnszszvmbrrc4wysmlhq-step-ca-0.16.2
ls -la /nix/store/vs8xv4sv9rn8lnszszvmbrrc4wysmlhq-step-ca-0.16.2/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 failed to build:

nixos-install-tools

1 package built:

step-ca

Maintainer pings
cc @cmcdragonkai @mohe2015 @kalbasit for testing.

Result of nixpkgs-review pr 135361 at 6df214b2 run on aarch64-linux 1

2 packages built successfully:

nixos-install-tools
step-ca

Reasoning for backporting: https://github.com/smallstep/certificates/commit/a864f0134db9acbf64d5155f7ab3a0dbea58dd5a could be considered a security-fix. As SHA256 is probably still safe this is not super important. I talked back to upstream and they will probably add a note to the release notes.

authors: mohe2015 r-rmcgibbo r-ryantm


text:
semantik: 1.2.5 -> 1.2.7

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/semantik/versions.
meta.description for semantik is: "A mind-mapping application for KDE"
meta.homepage for semantik is: "https://waf.io/semantik.html"
meta.changelog for semantik is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

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

/nix/store/jqmadjhsmajlacshqh06pwdmxv3c17v9-semantik-1.2.7/bin/semantik passed the binary check.

/nix/store/jqmadjhsmajlacshqh06pwdmxv3c17v9-semantik-1.2.7/bin/semantik-d passed the binary check.

/nix/store/jqmadjhsmajlacshqh06pwdmxv3c17v9-semantik-1.2.7/bin/.semantik-wrapped passed the binary check.

/nix/store/jqmadjhsmajlacshqh06pwdmxv3c17v9-semantik-1.2.7/bin/.semantik-d-wrapped passed the binary check.

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

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

found 1.2.7 with grep in /nix/store/jqmadjhsmajlacshqh06pwdmxv3c17v9-semantik-1.2.7

found 1.2.7 in filename of file in /nix/store/jqmadjhsmajlacshqh06pwdmxv3c17v9-semantik-1.2.7

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

du listing: https://gist.github.com/67e700dae3ff9965d00ce27f95aaeea6

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
semantik

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/jqmadjhsmajlacshqh06pwdmxv3c17v9-semantik-1.2.7 \
  --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 semantik https://github.com/r-ryantm/nixpkgs/archive/778b89aca95ddc73c109492a32833a436a4731a3.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/jqmadjhsmajlacshqh06pwdmxv3c17v9-semantik-1.2.7
ls -la /nix/store/jqmadjhsmajlacshqh06pwdmxv3c17v9-semantik-1.2.7/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:

semantik

Maintainer pings
cc @SCOTT-HAMILTON for testing.

Result of nixpkgs-review pr 135982 at 778b89ac run on x86_64-linux 1

1 package built successfully:

semantik

1 suggestion:

warning: missing-patch-comment
Consider adding a comment explaining the purpose of this patch on the line preceeding.
Near pkgs/applications/office/semantik/default.nix:36:15:
   |
36 |   patches = [ ./qt5.patch ];
   |               ^

authors: r-rmcgibbo r-ryantm