text:
wg-quick doesn't work with systemd-resolved

Describe the bug
If using systemd-resolved and using DNS in a Wireguard config, wg-quick will fail to add the DNS server because it uses the resolvconf command to do so. Because systemd-resolved overrides the resolvconf command with its own implementation and wg-quick calls the openresolv version of resolvconf, applying a Wireguard config fails.
Steps To Reproduce
Steps to reproduce the behavior:

Enable systemd-resolved with services.resolved.enable = true;
Run wg-quick up {path to config} with a Wireguard config file with a DNS entry

Expected behavior
wg-quick is supposed to call systemd-resolved's resolvconf command instead of openresolv's when systemd-resolved is enabled.
Notify maintainers

@elseym @ericsagnes @mic92 @zx2c4 @globin @ma27 @d-xo
Metadata
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.10.66, NixOS, 21.11 (Porcupine)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.4pre20210908_3c56f62`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

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

Since wg-quick itself uses resolvconf and has problems with systemd-resolved, this doesn't seem like a NixOS bug to me.

I'm sorry, maybe I wasn't clear enough. systemd-resolved has its own resolvconf implementation, it's just not in the path of wg-quick. I tried locally by removing openresolv and adding systemd to the PATH of wg-tools and it works fine.

Maybe we should not hard-code resolveconf at all or only add openresolve as a fall back path after the global path?

Since wg-quick itself uses resolvconf and has problems with systemd-resolved, this doesn't seem like a NixOS bug to me.

wg-quick works with both openresolv's resolvconf and systemd's resolvconf, depending on what's in PATH. This is a Nix bug.

Since wg-quick itself uses resolvconf and has problems with systemd-resolved, this doesn't seem like a NixOS bug to me.

wg-quick works with both openresolv's resolvconf and systemd's resolvconf, depending on what's in PATH. This is a Nix bug.

That's not the point if the system is configured to use systemd-resolved than we need to use systemd's resolvconf as it will use it's dbus api to set the nameserver. If wg-quick use the openresolv version it will attempt to update /etc/resolv.conf, which is incorrect.

Right, I think we're making the same point. Not an upstream bug. This about how Nix is configured. I'll let you all handle it.

https://github.com/NixOS/nixpkgs/pull/139530 was reverted.

Opened https://github.com/NixOS/nixpkgs/pull/166308 to finally fix this


text:
Tor never finishes bootstrapping in the systemd service

Describe the bug
At launch, the Tor daemon never finishes bootstrapping, it is stuck at 0%.
However when launching manually in a terminal, tor does starts, since it's using a default configuration instead.
Steps To Reproduce
Steps to reproduce the behavior:

tor.enable = true; tor.client.enable = true;
check logs journalctl -ef -u tor

Expected behavior
Tor should start.
Additional context
Starting Tor Daemon...
Apr 06 05:05:33.657 [notice] Tor 0.4.6.10 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1n, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.5.2 and Glibc 2.33 as libc.
Apr 06 05:05:33.657 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Apr 06 05:05:33.657 [notice] Read configuration file "/nix/store/p7ssp6fp8l8p82n94jkmbcqmdvw8mgls-torrc".
Configuration was valid
Started Tor Daemon.
Apr 06 05:05:33.731 [notice] Tor 0.4.6.10 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1n, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.5.2 and Glibc 2.33 as libc.
Apr 06 05:05:33.731 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Apr 06 05:05:33.731 [notice] Read configuration file "/nix/store/p7ssp6fp8l8p82n94jkmbcqmdvw8mgls-torrc".
Apr 06 05:05:33.733 [notice] Opening Socks listener on 127.0.0.1:9050
Apr 06 05:05:33.733 [notice] Opened Socks listener connection (ready) on 127.0.0.1:9050
Apr 06 05:05:33.000 [notice] Parsing GEOIP IPv4 file /nix/store/v4jglpa7c2kmsng9000779kqc0sa16rd-tor-0.4.6.10-geoip/share/tor/geoip.
Apr 06 05:05:33.000 [notice] Parsing GEOIP IPv6 file /nix/store/v4jglpa7c2kmsng9000779kqc0sa16rd-tor-0.4.6.10-geoip/share/tor/geoip6.
Apr 06 05:05:33.000 [notice] Bootstrapped 0% (starting): Starting
Apr 06 05:05:34.000 [notice] Starting with guard context "default"

Notify maintainers
@thoughtpolice @joachifm @prusnak
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.15.27-xanmod1-tt, NixOS, 22.05 (Quokka), 22.05.20220403.bc4b9ee`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.7.0`
 - channels(root): `"nixos-22.05pre347261.6d8215281b2"`
 - nixpkgs: `/nix/store/dpj59pj2msmd25q4mdmbvpmaa2j814rm-source`

i think this has something to do with 1b34039b5f1c3bfa6a9b1f7bd78ab3adecbe2a75 and maybe 3c63da7cf87473423a8138a82fbec59b9684d1c6.
i was getting the same but only when tor.client.enable=false (default), likely because 1b34039b5f1c3bfa6a9b1f7bd78ab3adecbe2a75. So, when I tor.client.enable=true, the client tries to connect to 9050 but that won't work likely because when tor.enable=true it uses that, so the client connects to 9051 instead. BUT that is only in joutnalctl, and the service is failed Failed to start Tor Daemon.?? Looking netstat -plnt, it actually connects to 9150 and 9051 instead. http request using socks5 on 9150  works.

generated torrc
SOCKSPort 127.0.0.1:9050
SOCKSPort 9050

there seems so be some conflicting options here between settings.SOCKSPort and client.socksListenAddress.

Okay, I've made some tests.

alright this is a minimal config that works now @wyndon
  services.tor = {
    enable = true;
    settings = {
      # socksListenAddress sets 9050 by default
      # SOCKSPort = [{ port = 9050; }];
      ControlPort = [{ port = 9051; }];
    };

    client.enable = true;
  };

Your solution didn't work for me.
So I took the configuration used by the service, used it manually with sudo -u tor tor -f torrc, and removed lines from the config file to see which part was causing the problem.
It turned out that, after removing DataDirectory /var/lib/tor, Tor worked as expected. So I simply deleted /var/lib/tor and restarted the systemd service, and everything was reworking. :shrug:

nixos reproducibility at its best 😂 glad you got it working too

source: gharchive/issue

authors: wyndon yuuyins

repo: NixOS/nixpkgs

license: MIT

license_type: permissive

license_source: github-api


text:
Vulnerability roundup 114: asterisk-18.5.1: 6 advisories [9.8]

search, files

[ ] CVE-2021-37706 CVSSv3=9.8 (nixos-21.11)
[ ] CVE-2022-23608 CVSSv3=9.8 (nixos-21.11)
[ ] CVE-2022-26651 CVSSv3=9.8 (nixos-21.11)
[ ] CVE-2022-21723 CVSSv3=9.1 (nixos-21.11)
[ ] CVE-2022-26499 CVSSv3=9.1 (nixos-21.11)
[ ] CVE-2022-26498 CVSSv3=7.5 (nixos-21.11)

CVE details
CVE-2021-37706
PJSIP is a free and open source multimedia communication library written in C language implementing standard based protocols such as SIP, SDP, RTP, STUN, TURN, and ICE. In affected versions if the incoming STUN message contains an ERROR-CODE attribute, the header length is not checked before performing a subtraction operation, potentially resulting in an integer underflow scenario. This issue affects all users that use STUN. A malicious actor located within the victim’s network may forge and send a specially crafted UDP (STUN) message that could remotely execute arbitrary code on the victim’s machine. Users are advised to upgrade as soon as possible. There are no known workarounds.
CVE-2022-23608
PJSIP is a free and open source multimedia communication library written in C language implementing standard based protocols such as SIP, SDP, RTP, STUN, TURN, and ICE. In versions up to and including 2.11.1 when in a dialog set (or forking) scenario, a hash key shared by multiple UAC dialogs can potentially be prematurely freed when one of the dialogs is destroyed . The issue may cause a dialog set to be registered in the hash table multiple times (with different hash keys) leading to undefined behavior such as dialog list collision which eventually leading to endless loop. A patch is available in commit db3235953baa56d2fb0e276ca510fefca751643f which will be included in the next release. There are no known workarounds for this issue.
CVE-2022-26651
An issue was discovered in Asterisk through 19.x and Certified Asterisk through 16.8-cert13. The func_odbc module provides possibly inadequate escaping functionality for backslash characters in SQL queries, resulting in user-provided data creating a broken SQL query or possibly a SQL injection. This is fixed in 16.25.2, 18.11.2, and 19.3.2, and 16.8-cert14.
CVE-2022-21723
PJSIP is a free and open source multimedia communication library written in C language implementing standard based protocols such as SIP, SDP, RTP, STUN, TURN, and ICE. In versions 2.11.1 and prior, parsing an incoming SIP message that contains a malformed multipart can potentially cause out-of-bound read access. This issue affects all PJSIP users that accept SIP multipart. The patch is available as commit in the master branch. There are no known workarounds.
CVE-2022-26499
An SSRF issue was discovered in Asterisk through 19.x. When using STIR/SHAKEN, it's possible to send arbitrary requests (such as GET) to interfaces such as localhost by using the Identity header. This is fixed in 16.25.2, 18.11.2, and 19.3.2.
CVE-2022-26498
An issue was discovered in Asterisk through 19.x. When using STIR/SHAKEN, it is possible to download files that are not certificates. These files could be much larger than what one would expect to download, leading to Resource Exhaustion. This is fixed in 16.25.2, 18.11.2, and 19.3.2.

Scanned versions: nixos-21.11: 3c5ae9be1f1.
Cc @DerTim1
Cc @auntieNeo
Cc @yorickvp

We no longer support nixos-21.11, but this has been fixed in the currently supported NixOS versions:

nixos-22.05: asterisk-16.26.1, asterisk-19.4.1, asterisk-18.12.1
nixos-unstable: asterisk-16.26.1, asterisk-19.4.1, asterisk-18.12.1

authors: ckauhaus yorickvP


text:
QEMU package is missing support for JACK

Describe the bug
The Nixpkgs QEMU package is missing support for JACK. QEMU supports it [1][2], so I think we just need to compile qemu with the right flags (e.g., [3]).  At best, this should be a simpler matter of tweaking audio-drv-list [4], and maybe adding a libjack.so dependency, but I may be oversimplifying.
I would be more than happy to do this by myself, if someone can give me clear instructions on how to build/test Nixpkgs. ("Where's the Makefile?" I'm new to Nixpkgs dev. Reading the official docs feels like yak shaving and I don't know which docs are relevant here. Actually, I did it once last year but can't remember.)
The reason I want this:

Crackly audio. I currently have sound working with -audiodev pa,id=hda,server=unix:/run/user/1000/pulse/native,out.buffer-length=512,timer-period=1000 -device ich9-intel-hda -device hda-duplex,audiodev=hda, which means I'm using PulseAudio. And to be clear, I don't have PulseAudio installed, I have PipeWire installed, but PipeWire has a compatibility layer which handles both PulseAudio and JACK. Anyway, the sound is currently poppy/crackly. There are anecdotes that the JACK interface is a lot better about this.

Libvirt issues. I can't figure out how to get audio to work at all with libvirt, so have had to resort to a qemu-system-x86_64 script (and there are cons to doing this). Specifically, the issue I'm running into is: when I try to port my audio args (given above) to libvirt, it silently fails. I'm assuming this is due to its being run as a service (qemu-libvirt), and I'm not sure which "pulse/native" socket to point this user to. And, since the JACK audiodev doesn't require a socket file, I'm hoping to avoid this dilemma. I'm not a PulseAudio or libvirt or QEMU expert so am surely something on this bullet point.

[1] https://www.kraxel.org/blog/2020/01/qemu-sound-audiodev/
[2] https://forum.level1techs.com/t/qemu-native-jack-audio-support/156494
[3] https://bugs.archlinux.org/task/68112
[4] https://github.com/NixOS/nixpkgs/blob/nixos-21.11/pkgs/applications/virtualization/qemu/default.nix#L179
Steps To Reproduce
Run qemu with:
  -audiodev jack,id=ad0 \
  -device ich9-intel-hda \
  -device hda-duplex,audiodev=ad0

Expected behavior
A vm is created, and has sound.
Actual behavior:
audio: Unknown audio driver `jack'

Notify maintainers
@edolstra
@alyssais

Ok, I just realized this is now supported in master. (I was only looking at 21.11.) Awesome! Closing...


text:
nixos-install doesn't ask for root password anymore

Since a while doing a stock installation (which doesn't set mutableUsers = false) doesn't ask for the root password anymore.
Probably the if [ -z "$noRootPasswd" ] && [ -x $mountPoint/var/setuid-wrappers/passwd ] && [ -t 0 ]; then check doesn't work since the latest setuid wrapper changes, as the absolute symlink resolves incorrectly in the installing host.
+ ls -lah /mnt/var/setuid-wrappers
lrwxrwxrwx 1 root root 51 Sep 21 15:41 /mnt/var/setuid-wrappers -> /run/setuid-wrapper-dirs/setuid-wrappers.zHrN5I4dUK

cc @domenkozar

806e88c1

Maybe it should be:
[ "$(chroot $mountPoint '[-x /var/setuid-wrappers/passwd ] && echo true') = true ]
or something similar. cc @obadz

Not directly related to this issue, but the password setup phase is a point of possible failure (in the case the user make a mistake in the password check).
Would it make sense to separate the password setup in a dedicated command (nixos-install --setup-root-password), or to at least to add some instructions in the documentation for what to do when the password setup failed?

Well the install command can simply be re-run.
If someone wants to make it fancy, I guess it could ask the user whether to retry if the passwd command did not exit with status 0.

Argl, this definitely needs to be fixed :-(
The idea is to find out if the closure has mutableUsers turned on or off, without invoking invoking a nix evaluation (since with --closure we may only have the output and not the nix source).
Right now I can only think of parsing the json out of grep users-groups.json$ /nix/var/nix/profiles/system/activate. That's quite ugly. Maybe a better solution would be to modify the nixos/modules/config/users-groups.nix so that it creates a /etc/static/mutable-users whose existence we can test?

The flag file approach sounds sensible to me.

Is there any reason you can't do something like this?
if [ -z "$noRootPasswd" ] && [ -x "$mountPoint/$(readlink -f $mountPoint/var/setuid-wrappers/passwd)" ] && [ -t 0 ]; then
    echo "setting root password..."
    chroot $mountPoint /var/setuid-wrappers/passwd
fi

... although, a flag file would probably be less fragile.

@cstrahan, I like your solution the best.  If someone has a chance to test & push that would be great.  I'm really tied out these days so can't do it myself.

That solution feels kind of brittle, since if anybody changes the absolute symlink to relative, it will break again.

I settled for a34ec1517fc76dca1d3aa1cd3f04a04ef4109753.

@dezgeg, thanks!

authors: cstrahan dezgeg domenkozar ericsagnes obadz


text:
hydra not building - known issue, but no warning in manual for hydra

Issue description
I tried to set up hydra for a test-run on my laptop and it failed at:

g++ -DHAVE_CONFIG_H -I. -I../..    -I/nix/store/xibmb4s2xah92zx2m34gng55in38l2cq-boehm-gc-7.2g-dev/include -I/nix/store/i90xvxfz44hg85yyv9px2vkkvdarfn85-nix-1.12pre4523_3b81b26-dev/include/nix -Wall -laws-cpp-sdk-s3 -g -O2 -std=c++11 -c -o s3-binary-cache-store.o s3-binary-cache-store.cc
s3-binary-cache-store.cc:6:29: fatal error: aws/s3/S3Client.h: No such file or directory
compilation terminated.

I have tried it as described in: https://nixos.org/hydra/manual/ - i did not try the one-click install, but the channel method.
Later I found the error in https://github.com/NixOS/hydra/issues/322 with links to the workarounds, but those should be mentioned either in the manual itself, or fixed. It's an inconvenience for new hydra users, that the official manual isn't working.
Posting this in nixpkgs instead of hydra, so more people see it.
Happy Holidays,
ikervagyok

I don't think it's appropriate to use the manual as a bug tracker.

@joachifm: it is not - still, trying to install a software "by the book" and failing is bad. it's even worse, if we - the nix-guys, who are all about reproducable builds are unable to provide the best CI (hydra) in the world - can't install hydra... it's so bad, that i would love to skip the informal rule of "manuals are for the standards, not the workarounds" and state that it's WIP and we will fix it ASAP.
Explanation: i tried to show people how cool this system is for university-applications and i couldn't set up my test instance. We suck hard at the moment and can't even be honest - that's sending people the worst possible message. also this issue is in my eyes just to show people who wont follow the hydra git and bugtracker, that we care and we will fix it one way or another.
sorry for the long post, but i think this important - not for people knowing their way around NixOS, but for the ones that want to try our tooling.

@ikervagyok the issue you linked is unrelated to the current build failure, as far as I can tell (https://github.com/NixOS/nixpkgs/pull/21418 looks like an attempt at fixing it). What is the workaround you're thinking of? Builds break on unstable as a matter of routine, updating the manual whenever it happens makes no sense to me.

you are right, not to update the manual every time stuff breaks - as long as breakage isn't something so common, that it is expected to happen every now and then. in that case you should at least mark stuff experimental or broken.
@joachifm @domenkozar : if you point me into a direction, how to at least update the docs that this is unsupported/-stable/whatever and add some pointers how to try and fix breakage on affected setups, i'm glad to write that part to the docs, to be included as long as this remains an issue affecting every other release. at least as long as https://github.com/NixOS/hydra/issues/322 is open, i think we should be including a warning in the official docs for hydra.

@joachifm thanks for following my not straight-to-the-point comments, being tired doesn't help me explain myself correctly ;)
i'll try again, reporting about what works/doesn't work.

+1 I cannot enable services.hydra because the hydra package won't build. I get the same error as OP.
Hydra wasn't in 16.03 but I could still get it working by following the wiki, now it's broke :(

Yikes, hydra on 16.09 is broken due to issues with s3. Backport the patch from master upgrading hydra and then it fails because nixUnstable is 1.12pre instead of 1.11.5, I think. @domenkozar what should we do here?

Using hydra from master yields:
Jan 13 03:31:53 hydra hydra-server[2566]: [warn] Unicode::Encoding plugin is auto-applied, please remove this from your appclass and make sure to define "encoding" config
Jan 13 03:31:53 hydra hydra-server[2566]: Compress::Raw::Bzip2 version 2.07 required--this is only version 2.064 at /nix/store/v4b73k27ijng18d38d79hghxmjisif1k-hydra-perl-deps/lib/perl5/site_perl/5.22.2/IO/Compress/Adapter/Bzip2.pm line 9.
Jan 13 03:31:53 hydra hydra-server[2566]: BEGIN failed--compilation aborted at /nix/store/v4b73k27ijng18d38d79hghxmjisif1k-hydra-perl-deps/lib/perl5/site_perl/5.22.2/IO/Compress/Adapter/Bzip2.pm line 9.
Jan 13 03:31:53 hydra hydra-server[2566]: Compilation failed in require at /nix/store/v4b73k27ijng18d38d79hghxmjisif1k-hydra-perl-deps/lib/perl5/site_perl/5.22.2/IO/Compress/Bzip2.pm line 11.
Jan 13 03:31:53 hydra hydra-server[2566]: BEGIN failed--compilation aborted at /nix/store/v4b73k27ijng18d38d79hghxmjisif1k-hydra-perl-deps/lib/perl5/site_perl/5.22.2/IO/Compress/Bzip2.pm line 11.
Jan 13 03:31:53 hydra hydra-server[2566]: Compilation failed in require at /nix/store/b20crf8yisk36kwnvfdiqcqf0d8ryih4-hydra-2016-12-09/libexec/hydra/lib/Hydra/View/NixExprs.pm line 7.
Jan 13 03:31:53 hydra hydra-server[2566]: BEGIN failed--compilation aborted at /nix/store/b20crf8yisk36kwnvfdiqcqf0d8ryih4-hydra-2016-12-09/libexec/hydra/lib/Hydra/View/NixExprs.pm line 7.
Jan 13 03:31:53 hydra hydra-server[2566]: Compilation failed in require at /nix/store/v4b73k27ijng18d38d79hghxmjisif1k-hydra-perl-deps/lib/perl5/site_perl/5.22.2/Catalyst/Utils.pm line 309.
Jan 13 03:31:53 hydra hydra-server[2566]: Compilation failed in require at /nix/store/v4b73k27ijng18d38d79hghxmjisif1k-hydra-perl-deps/lib/perl5/site_perl/5.22.2/Catalyst/ScriptRunner.pm line 50.

looks like we just don't have a working hydra? What is hydra.nixos.org running?

Update: using nixpkgs master at e2be232c65432d8e543be80b1ba67756c389ab10 works fine.
let
  pkgs = import <nixpkgs> {};
  unstable = import (pkgs.fetchFromGitHub {
    owner = "NixOS";
    repo = "nixpkgs";
    rev = "e2be232c65432d8e543be80b1ba67756c389ab10";
    sha256 = "1dz3wlbz97pk0csjdzy2zlz9hsjdrd96yb5x7v33ksv7hyl9c7ld";
  }) {};
in
{
  hydra =
    { config, pkgs, ... }:
    { deployment.targetEnv = "virtualbox";
      deployment.virtualbox.memorySize = 1024;

      networking.firewall.enable = true;
      networking.firewall.allowedTCPPorts = [ 22 3000 ];

      services = {
        hydra = {
          package = unstable.hydra;
        };
      };
    };
}

Hydra package has been since fixed.

authors: Zer0- domenkozar grahamc ikervagyok joachifm


text:
Carbonyl

Carbonyl is a Chromium based browser built to run in a terminal.

Metadata

homepage URL: https://github.com/fathyb/carbonyl
source URL: https://github.com/fathyb/carbonyl
license:  BSD
platforms: linux, macos

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


text:
Package request: leptosfmt

Project description
A formatter for the leptos view! macro. Leptos is a Rust wasm framework.
Metadata

homepage URL: https://github.com/bram209/leptosfmt
source URL: https://github.com/bram209/leptosfmt
license: mit, apache
platforms: unix, linux, darwin, ...

Note to contributors: It should be possible package this similar to https://github.com/NixOS/nixpkgs/pull/244487

#248148

authors: figsoda srid


text:
Update request: unrar  6.2.12→  7.00 beta 3

Package name: unrar

Latest released version: 7.00 beta 3

Current version on the unstable channel: 6.2.12

Current version on the stable/release channel: 6.2.12

I receive more and more RAR files which are created with Unrar 7.00 beta versions / require a more recent version tan 6.2.12
I would appreciated if  the existing unrar package can be updated or a new unrar-beta package be proposed ..
Changelog : https://www.rarlab.com/rarnew.htm
Notify maintainers
@ehmry
@wegank

There was an automatic update in #266998 that I marked as draft, exactly because it's in beta. I'd much rather add a new package. @ehmry what do you think?

I don't think we should update to the beta either. Sometimes I think about adding beta and release candidate versions to package passthru, but that would be a nixpkgs policy discussion.

I receive more and more RAR files which are created with Unrar 7.00 beta versions / require a more recent version tan 6.2.12

If people are still creating new RAR files then I don't want to be maintainer of this package. Stop using RAR.

authors: carpediem29 ehmry wegank


text:
RD image overlaps OS image

Describe the bug
In a Pinebook Pro using the SD image instead of nixos-install and TowBoot, as recommended in the documentation, modifying the kernel or the kernel parameters produces a generation that fails to boot with the obscure message 'RD image overlaps OS image'.
Steps To Reproduce

Create a new configuration that modifies the boot.kernelPackages attribute.
sudo nixos-rebuild switch.
sudo reboot.
Select the last generation in the boot entry.
The last generation cannot be booted, with the message RD image overlays OS image, and the previous generation is booted instead.

Expected behavior
The last generation is booted after selecting it after the reboot.
Screenshots
N/A.
Additional context
I think the problem is modifying the kernel or kernel parameters in the SD image, but I'm not sure. The problem could also be specific of Pinebook Pro, but I think it is a problem of using a SD image instead of nixos-install. This problem should be mentioned in the documentation if not solved, and probably recommending using nixos-install with detailed instructions instead of using the SD image for a serious usage.

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

it's not "overlays" but "overlaps"

have you got any updates? i am facing the same error message.

Thanks for the correction. I couldn't fix it anyway.
The single solution for me was not modifying the kernel package with parameters, nor using another kernel package (from unstable, nixos-hardware, etc.).
Note however than updates over the default kernel package work well.

this issue started when i updated my os configuration flake, which updated the kernel version from 6.6.21 i think to 6.6.25.
i set boot.kernelPackages to a lower kernel version and the issue doesn't appear anymore for me.

This also affects the currently available sd-card images. I tried to boot the 24.05 and the unstable LTS and both failed. So it is not possible to install NixOS with a current SDcard image on a PinebookPro at the moment.

Try upgrading Tow-Boot to the most recent version https://github.com/Tow-Boot/Tow-Boot/releases/tag/release-2023.07-007 which includes https://github.com/Tow-Boot/U-Boot/pull/3. This may fix the issue.
Alternatively, I've been booting my Pinebook Pro with EFI successfully. Tow-Boot does support EFI out of the box and installing GRUB or systemd-boot on an EFI System Partition just works. I've also used https://github.com/NixOS/nixpkgs/pull/324419 and https://github.com/fpletz/nixpkgs/commit/190fcc5a73dc6295e4ac701ef1ee4b5928e80754 to get a compressed linux kernel that supports EFI.

I can confirm switching to latest tow-boot resolved the issue for me.

Yupp, switching works, this can probably be closed.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/nixos-on-rock64pro/50514/13


text:
cinny-desktop : Failed to load.

Describe the bug
cinny-desktop : Fails to load after logging in
"Failed to load. WebAssembly.Module doesn't parse at byte 0: module doesn't start with '\0asm'"
Steps To Reproduce
Steps to reproduce the behavior:

Install the cinny-desktop package
Log into a Matrix account
App fails to start with error mentioned before

Expected behavior

Screenshots

Additional context

Notify maintainers

@Qyriad
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.10.3, NixOS, 24.11 (Vicuna), 24.11.20240809.5e0ca22`
 - multi-user?: `yes`
 - sandbox: `relaxed`
 - version: `nix-env (Nix) 2.24.0pre20240723_fb450de2`
 - nixpkgs: `/nix/store/0jr2kk95c34c0b6yxi75q4fqgb43kqkm-source`

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

seems like the wasm file is missing outright for some reason

Fixed by https://github.com/NixOS/nixpkgs/pull/331078

authors: Qyriad griffi-gh


text:
Regreet program theming options need lib.mkDefault or lib.mkForce to build

Describe the bug
Error when building NixOS config, prompting me to use lib.mkForce or lib.mkDefault when setting things in programs.regreet.settings.GTK
Steps To Reproduce
Steps to reproduce the behavior:

Try to set any of the GTK Theming options for the regreet program.
Try to build the configuration
Get an error prompting you to use lib.mkForce or lib.mkDefault when setting the theming options.

Expected behavior
I believe I shouldn't be prompted to use lib.mkForce or lib.mkDefault to set option for this program option, as I'm not requested to do that for anythign else.
Notify maintainers
@Enzime
Metadata
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.41, NixOS, 24.11 (Vicuna), 24.11.20240719.1d9c2c9`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.24.0pre20240717_464e5925`
 - channels(root): `"home-manager, nixos"`
 - nixpkgs: `/nix/store/l6spwdi1xs20q24fqfi3xwxx0d2x9q2m-source`

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

I had this problem and it's not obvious from the error message, but they set up an alias to the setting, so you need to use programs.regreet.theme.name etc
Take a look at all the available preferences here https://search.nüschtos.de/?option_scope=11&option=programs.regreet.theme.name&query=programs.regreet&scope=NixOS

authors: non-bin sonjiku


text:
Tensorboard results in error about html5lib when used with python 3.6m

Issue description
Installing tensorflow-tensorboard gives this error:
error: html5lib-0.9999999 not supported for interpreter python3.6m

Steps to reproduce
Using this shell.nix:
{
  pkgs ? import (fetchTarball https://github.com/NixOS/nixpkgs-channels/archive/6c064e6b1f34a8416f990db0cc617a7195f71588.tar.gz) {}
}:
  with pkgs;
  let
    python = python36;
  in
    python.pkgs.buildPythonApplication {
      name = "testenv";
      buildInputs =  (with python.pkgs; [
        tensorflowWithCuda
        tensorflow-tensorboard
      ]);
    }

The hash is the current latest hash on nixpkgs-unstable.
@abbradar

It is as said -- Tensorboard is not supported on Python 3.6. We hack around it allowing Tensorflow to be installed without Tensorboard in this case.

authors: CMCDragonkai abbradar


text:
QGroundControl .desktop does not work

Issue description
In the file /nix/store/**qgroundcontrol**/share/applications/qgroundcontrol.desktop a non existing shell script is referenced as executable:
[Desktop Entry]
Type=Application
Name=QGroundControl
GenericName=Ground Control Station
Comment=UAS ground control station
Icon=qgroundcontrol
Exec=qgroundcontrol-start.sh
Terminal=false
Categories=Utility;

The binary in bin is called QGroundControl. Please change the Exec= line in the .desktop file accordingly.
Steps to reproduce

install software
try to run it through a launcher

Technical details

system: "x86_64-linux"
host os: Linux 4.18.0, NixOS, 18.09.1206.6d6e4e6b558 (Jellyfish)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.1.1
channels(root): "nixos-18.09.1206.6d6e4e6b558"
channels(wucke13): "nixos-unstable-small-19.03pre158251.50602de85e3, nixpkgs-unstable-19.03pre157897.c9e13806267"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Do you feel like trying to fix this in the installPhase?

Sure


text:
Should Lektor be packaged as Python application?

Issue description
Lektor is currently packaged as a Python library, i.e. using buildPythonPackage. Its primary use seems to be as an application, so I wonder whether it should be packaged as one, either additionally to the library by using toPythonApplication or instead of it, using buildPythonApplication.
Steps to reproduce
Try to get started with Lektor. You'll notice you're more likely to use its executables than importing it in your own Python code.
Technical details
n/a

Yes, it most likely should.

Do you think it should also be kept as a Python library? I guess when using the Lektor API from templates, one would still rely on the application, but maybe for developing Lektor plugins that's different?

In that case it should be kept here, and one would use toPythonApplication in all-packages.nix.

Still important to me, but I think #85476 should be fixed before making Lektor "officially" available as an application.

Any updates?

Still (somewhat) important to me, but I think #85476 should be fixed before making Lektor "officially" available as an application.

Lektor should also not offer the option to install packages using pip (when installed through Nixpkgs) and its dependency on pip should be removed: https://github.com/lektor/lektor/blob/2fb9b252c579193843f5d9e31339474f16e1075f/lektor/packages.py#L86-L91

authors: FRidh das-g dotlambda siraben


text:
Vulnerability roundup 63: file-5.35: 4 advisories

search, files

[ ] CVE-2019-8904 (nixos-19.03)
[ ] CVE-2019-8905 (nixos-19.03)
[ ] CVE-2019-8906 (nixos-19.03)
[ ] CVE-2019-8907 (nixos-19.03)

Scanned versions: nixos-19.03: 5847485e3ec. May contain false positives.

See also #56360


text:
Packaging request: pyglossary

Project description
A tool for converting dictionary files aka glossaries with various formats for different dictionary applications.
Metadata

homepage URL: https://github.com/ilius/pyglossary
source URL: https://github.com/ilius/pyglossary/releases/tag/4.0.11
license: gpl3Plus
platforms: unix

have you looked into poetry2nix ? python ecosystem is huge and while I packaged a few python libraries for nix, I've started using poetry and it seems like a nice solution.

Still wanted.

Still wanted.

Still nice to have.

authors: sikmir teto


text:
timescaledb-tune: 0.9.0 -> 0.10.0

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
[x] macOS
[ ] other Linux distributions

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

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108658 run on x86_64-linux 1

1 package built:

timescaledb-tune

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108658 run on x86_64-linux 1

1 package built:

timescaledb-tune

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108658 run on x86_64-darwin 1

1 package built:

timescaledb-tune

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108658 run on x86_64-darwin 1

1 package built:

timescaledb-tune

source: gharchive/pull-request


text:
zen-kernels: 5.10.9 -> 5.10.10

lqx2's parent is the same commit as zen1's

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

18 packages marked as broken and skipped:

linuxPackages_lqx.ixgbevf
linuxPackages_lqx.lttng-modules
linuxPackages_lqx.ndiswrapper
linuxPackages_lqx.nvidia_x11_legacy304
linuxPackages_lqx.phc-intel
linuxPackages_lqx.r8125
linuxPackages_lqx.rtl8723bs
linuxPackages_lqx.sch_cake
linuxPackages_lqx.tbs
linuxPackages_zen.ixgbevf
linuxPackages_zen.lttng-modules
linuxPackages_zen.ndiswrapper
linuxPackages_zen.nvidia_x11_legacy304
linuxPackages_zen.phc-intel
linuxPackages_zen.r8125
linuxPackages_zen.rtl8723bs
linuxPackages_zen.sch_cake
linuxPackages_zen.tbs

40 packages failed to build:

linuxPackages_lqx.akvcam
linuxPackages_lqx.amdgpu-pro
linuxPackages_lqx.anbox
linuxPackages_lqx.chipsec
linuxPackages_lqx.cryptodev
linuxPackages_lqx.dpdk
linuxPackages_lqx.ena
linuxPackages_lqx.mwprocapture
linuxPackages_lqx.mxu11x0
linuxPackages_lqx.nvidia_x11_legacy340
linuxPackages_lqx.nvidia_x11_legacy390
linuxPackages_lqx.oci-seccomp-bpf-hook
linuxPackages_lqx.rtl8192eu
linuxPackages_lqx.rtl8812au
linuxPackages_lqx.rtl8814au
linuxPackages_lqx.rtl8821au
linuxPackages_lqx.rtl8821ce
linuxPackages_lqx.rtl88x2bu
linuxPackages_lqx.rtl88xxau-aircrack
linuxPackages_lqx.rtlwifi_new
linuxPackages_zen.akvcam
linuxPackages_zen.amdgpu-pro
linuxPackages_zen.anbox
linuxPackages_zen.chipsec
linuxPackages_zen.cryptodev
linuxPackages_zen.dpdk
linuxPackages_zen.ena
linuxPackages_zen.mwprocapture
linuxPackages_zen.mxu11x0
linuxPackages_zen.nvidia_x11_legacy340
linuxPackages_zen.nvidia_x11_legacy390
linuxPackages_zen.oci-seccomp-bpf-hook
linuxPackages_zen.rtl8192eu
linuxPackages_zen.rtl8812au
linuxPackages_zen.rtl8814au
linuxPackages_zen.rtl8821au
linuxPackages_zen.rtl8821ce
linuxPackages_zen.rtl88x2bu
linuxPackages_zen.rtl88xxau-aircrack
linuxPackages_zen.rtlwifi_new

104 packages built:

linuxPackages_lqx.acpi_call
linuxPackages_lqx.asus-wmi-sensors
linuxPackages_lqx.batman_adv
linuxPackages_lqx.bbswitch
linuxPackages_lqx.bcc
linuxPackages_lqx.bpftrace
linuxPackages_lqx.broadcom_sta
linuxPackages_lqx.can-isotp
linuxPackages_lqx.cpupower
linuxPackages_lqx.ddcci-driver
linuxPackages_lqx.digimend
linuxPackages_lqx.evdi
linuxPackages_lqx.facetimehd
linuxPackages_lqx.fwts-efi-runtime
linuxPackages_lqx.gcadapter-oc-kmod
linuxPackages_lqx.hyperv-daemons
linuxPackages_lqx.intel-speed-select
linuxPackages_lqx.it87
linuxPackages_lqx.jool
linux_lqx (linuxPackages_lqx.kernel)
linuxPackages_lqx.mba6x_bl
linuxPackages_lqx.netatop
linuxPackages_lqx.nvidia_x11
linuxPackages_lqx.nvidia_x11_beta
linuxPackages_lqx.nvidia_x11_vulkan_beta
linuxPackages_lqx.nvidiabl
linuxPackages_lqx.openafs (linuxPackages_lqx.openafs_1_8)
linuxPackages_lqx.openafs_1_9
linuxPackages_lqx.openrazer
linuxPackages_lqx.perf
linuxPackages_lqx.ply
linuxPackages_lqx.r8168
linuxPackages_lqx.rtl8821cu
linuxPackages_lqx.sysdig
linuxPackages_lqx.system76
linuxPackages_lqx.system76-acpi
linuxPackages_lqx.system76-io
linuxPackages_lqx.systemtap
linuxPackages_lqx.tmon
linuxPackages_lqx.tp_smapi
linuxPackages_lqx.turbostat
linuxPackages_lqx.tuxedo-keyboard
linuxPackages_lqx.usbip
linuxPackages_lqx.v4l2loopback
linuxPackages_lqx.v86d
linuxPackages_lqx.vhba
linuxPackages_lqx.virtualbox
linuxPackages_lqx.virtualboxGuestAdditions
linuxPackages_lqx.x86_energy_perf_policy
linuxPackages_lqx.xpadneo
linuxPackages_lqx.zenpower
linuxPackages_lqx.zfs (linuxPackages_lqx.zfsStable ,linuxPackages_lqx.zfsUnstable)
linuxPackages_zen.acpi_call
linuxPackages_zen.asus-wmi-sensors
linuxPackages_zen.batman_adv
linuxPackages_zen.bbswitch
linuxPackages_zen.bcc
linuxPackages_zen.bpftrace
linuxPackages_zen.broadcom_sta
linuxPackages_zen.can-isotp
linuxPackages_zen.cpupower
linuxPackages_zen.ddcci-driver
linuxPackages_zen.digimend
linuxPackages_zen.evdi
linuxPackages_zen.facetimehd
linuxPackages_zen.fwts-efi-runtime
linuxPackages_zen.gcadapter-oc-kmod
linuxPackages_zen.hyperv-daemons
linuxPackages_zen.intel-speed-select
linuxPackages_zen.it87
linuxPackages_zen.jool
linux_zen (linuxPackages_zen.kernel)
linuxPackages_zen.mba6x_bl
linuxPackages_zen.netatop
linuxPackages_zen.nvidia_x11
linuxPackages_zen.nvidia_x11_beta
linuxPackages_zen.nvidia_x11_vulkan_beta
linuxPackages_zen.nvidiabl
linuxPackages_zen.openafs (linuxPackages_zen.openafs_1_8)
linuxPackages_zen.openafs_1_9
linuxPackages_zen.openrazer
linuxPackages_zen.perf
linuxPackages_zen.ply
linuxPackages_zen.r8168
linuxPackages_zen.rtl8821cu
linuxPackages_zen.sysdig
linuxPackages_zen.system76
linuxPackages_zen.system76-acpi
linuxPackages_zen.system76-io
linuxPackages_zen.systemtap
linuxPackages_zen.tmon
linuxPackages_zen.tp_smapi
linuxPackages_zen.turbostat
linuxPackages_zen.tuxedo-keyboard
linuxPackages_zen.usbip
linuxPackages_zen.v4l2loopback
linuxPackages_zen.v86d
linuxPackages_zen.vhba
linuxPackages_zen.virtualbox
linuxPackages_zen.virtualboxGuestAdditions
linuxPackages_zen.x86_energy_perf_policy
linuxPackages_zen.xpadneo
linuxPackages_zen.zenpower
linuxPackages_zen.zfs (linuxPackages_zen.zfsStable ,linuxPackages_zen.zfsUnstable)

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

18 packages marked as broken and skipped:

linuxPackages_lqx.ixgbevf
linuxPackages_lqx.lttng-modules
linuxPackages_lqx.ndiswrapper
linuxPackages_lqx.nvidia_x11_legacy304
linuxPackages_lqx.phc-intel
linuxPackages_lqx.r8125
linuxPackages_lqx.rtl8723bs
linuxPackages_lqx.sch_cake
linuxPackages_lqx.tbs
linuxPackages_zen.ixgbevf
linuxPackages_zen.lttng-modules
linuxPackages_zen.ndiswrapper
linuxPackages_zen.nvidia_x11_legacy304
linuxPackages_zen.phc-intel
linuxPackages_zen.r8125
linuxPackages_zen.rtl8723bs
linuxPackages_zen.sch_cake
linuxPackages_zen.tbs

40 packages failed to build:

linuxPackages_lqx.akvcam
linuxPackages_lqx.amdgpu-pro
linuxPackages_lqx.anbox
linuxPackages_lqx.chipsec
linuxPackages_lqx.cryptodev
linuxPackages_lqx.dpdk
linuxPackages_lqx.ena
linuxPackages_lqx.mwprocapture
linuxPackages_lqx.mxu11x0
linuxPackages_lqx.nvidia_x11_legacy340
linuxPackages_lqx.nvidia_x11_legacy390
linuxPackages_lqx.oci-seccomp-bpf-hook
linuxPackages_lqx.rtl8192eu
linuxPackages_lqx.rtl8812au
linuxPackages_lqx.rtl8814au
linuxPackages_lqx.rtl8821au
linuxPackages_lqx.rtl8821ce
linuxPackages_lqx.rtl88x2bu
linuxPackages_lqx.rtl88xxau-aircrack
linuxPackages_lqx.rtlwifi_new
linuxPackages_zen.akvcam
linuxPackages_zen.amdgpu-pro
linuxPackages_zen.anbox
linuxPackages_zen.chipsec
linuxPackages_zen.cryptodev
linuxPackages_zen.dpdk
linuxPackages_zen.ena
linuxPackages_zen.mwprocapture
linuxPackages_zen.mxu11x0
linuxPackages_zen.nvidia_x11_legacy340
linuxPackages_zen.nvidia_x11_legacy390
linuxPackages_zen.oci-seccomp-bpf-hook
linuxPackages_zen.rtl8192eu
linuxPackages_zen.rtl8812au
linuxPackages_zen.rtl8814au
linuxPackages_zen.rtl8821au
linuxPackages_zen.rtl8821ce
linuxPackages_zen.rtl88x2bu
linuxPackages_zen.rtl88xxau-aircrack
linuxPackages_zen.rtlwifi_new

104 packages built:

linuxPackages_lqx.acpi_call
linuxPackages_lqx.asus-wmi-sensors
linuxPackages_lqx.batman_adv
linuxPackages_lqx.bbswitch
linuxPackages_lqx.bcc
linuxPackages_lqx.bpftrace
linuxPackages_lqx.broadcom_sta
linuxPackages_lqx.can-isotp
linuxPackages_lqx.cpupower
linuxPackages_lqx.ddcci-driver
linuxPackages_lqx.digimend
linuxPackages_lqx.evdi
linuxPackages_lqx.facetimehd
linuxPackages_lqx.fwts-efi-runtime
linuxPackages_lqx.gcadapter-oc-kmod
linuxPackages_lqx.hyperv-daemons
linuxPackages_lqx.intel-speed-select
linuxPackages_lqx.it87
linuxPackages_lqx.jool
linux_lqx (linuxPackages_lqx.kernel)
linuxPackages_lqx.mba6x_bl
linuxPackages_lqx.netatop
linuxPackages_lqx.nvidia_x11
linuxPackages_lqx.nvidia_x11_beta
linuxPackages_lqx.nvidia_x11_vulkan_beta
linuxPackages_lqx.nvidiabl
linuxPackages_lqx.openafs (linuxPackages_lqx.openafs_1_8)
linuxPackages_lqx.openafs_1_9
linuxPackages_lqx.openrazer
linuxPackages_lqx.perf
linuxPackages_lqx.ply
linuxPackages_lqx.r8168
linuxPackages_lqx.rtl8821cu
linuxPackages_lqx.sysdig
linuxPackages_lqx.system76
linuxPackages_lqx.system76-acpi
linuxPackages_lqx.system76-io
linuxPackages_lqx.systemtap
linuxPackages_lqx.tmon
linuxPackages_lqx.tp_smapi
linuxPackages_lqx.turbostat
linuxPackages_lqx.tuxedo-keyboard
linuxPackages_lqx.usbip
linuxPackages_lqx.v4l2loopback
linuxPackages_lqx.v86d
linuxPackages_lqx.vhba
linuxPackages_lqx.virtualbox
linuxPackages_lqx.virtualboxGuestAdditions
linuxPackages_lqx.x86_energy_perf_policy
linuxPackages_lqx.xpadneo
linuxPackages_lqx.zenpower
linuxPackages_lqx.zfs (linuxPackages_lqx.zfsStable ,linuxPackages_lqx.zfsUnstable)
linuxPackages_zen.acpi_call
linuxPackages_zen.asus-wmi-sensors
linuxPackages_zen.batman_adv
linuxPackages_zen.bbswitch
linuxPackages_zen.bcc
linuxPackages_zen.bpftrace
linuxPackages_zen.broadcom_sta
linuxPackages_zen.can-isotp
linuxPackages_zen.cpupower
linuxPackages_zen.ddcci-driver
linuxPackages_zen.digimend
linuxPackages_zen.evdi
linuxPackages_zen.facetimehd
linuxPackages_zen.fwts-efi-runtime
linuxPackages_zen.gcadapter-oc-kmod
linuxPackages_zen.hyperv-daemons
linuxPackages_zen.intel-speed-select
linuxPackages_zen.it87
linuxPackages_zen.jool
linux_zen (linuxPackages_zen.kernel)
linuxPackages_zen.mba6x_bl
linuxPackages_zen.netatop
linuxPackages_zen.nvidia_x11
linuxPackages_zen.nvidia_x11_beta
linuxPackages_zen.nvidia_x11_vulkan_beta
linuxPackages_zen.nvidiabl
linuxPackages_zen.openafs (linuxPackages_zen.openafs_1_8)
linuxPackages_zen.openafs_1_9
linuxPackages_zen.openrazer
linuxPackages_zen.perf
linuxPackages_zen.ply
linuxPackages_zen.r8168
linuxPackages_zen.rtl8821cu
linuxPackages_zen.sysdig
linuxPackages_zen.system76
linuxPackages_zen.system76-acpi
linuxPackages_zen.system76-io
linuxPackages_zen.systemtap
linuxPackages_zen.tmon
linuxPackages_zen.tp_smapi
linuxPackages_zen.turbostat
linuxPackages_zen.tuxedo-keyboard
linuxPackages_zen.usbip
linuxPackages_zen.v4l2loopback
linuxPackages_zen.v86d
linuxPackages_zen.vhba
linuxPackages_zen.virtualbox
linuxPackages_zen.virtualboxGuestAdditions
linuxPackages_zen.x86_energy_perf_policy
linuxPackages_zen.xpadneo
linuxPackages_zen.zenpower
linuxPackages_zen.zfs (linuxPackages_zen.zfsStable ,linuxPackages_zen.zfsUnstable)

Result of nixpkgs-review pr 110797 1

18 packages marked as broken and skipped:

linuxPackages_lqx.ixgbevf
linuxPackages_lqx.lttng-modules
linuxPackages_lqx.ndiswrapper
linuxPackages_lqx.nvidia_x11_legacy304
linuxPackages_lqx.phc-intel
linuxPackages_lqx.r8125
linuxPackages_lqx.rtl8723bs
linuxPackages_lqx.sch_cake
linuxPackages_lqx.tbs
linuxPackages_zen.ixgbevf
linuxPackages_zen.lttng-modules
linuxPackages_zen.ndiswrapper
linuxPackages_zen.nvidia_x11_legacy304
linuxPackages_zen.phc-intel
linuxPackages_zen.r8125
linuxPackages_zen.rtl8723bs
linuxPackages_zen.sch_cake
linuxPackages_zen.tbs

40 packages failed to build:

linuxPackages_lqx.akvcam
linuxPackages_lqx.amdgpu-pro
linuxPackages_lqx.anbox
linuxPackages_lqx.chipsec
linuxPackages_lqx.cryptodev
linuxPackages_lqx.dpdk
linuxPackages_lqx.ena
linuxPackages_lqx.mwprocapture
linuxPackages_lqx.mxu11x0
linuxPackages_lqx.nvidia_x11_legacy340
linuxPackages_lqx.nvidia_x11_legacy390
linuxPackages_lqx.oci-seccomp-bpf-hook
linuxPackages_lqx.rtl8192eu
linuxPackages_lqx.rtl8812au
linuxPackages_lqx.rtl8814au
linuxPackages_lqx.rtl8821au
linuxPackages_lqx.rtl8821ce
linuxPackages_lqx.rtl88x2bu
linuxPackages_lqx.rtl88xxau-aircrack
linuxPackages_lqx.rtlwifi_new
linuxPackages_zen.akvcam
linuxPackages_zen.amdgpu-pro
linuxPackages_zen.anbox
linuxPackages_zen.chipsec
linuxPackages_zen.cryptodev
linuxPackages_zen.dpdk
linuxPackages_zen.ena
linuxPackages_zen.mwprocapture
linuxPackages_zen.mxu11x0
linuxPackages_zen.nvidia_x11_legacy340
linuxPackages_zen.nvidia_x11_legacy390
linuxPackages_zen.oci-seccomp-bpf-hook
linuxPackages_zen.rtl8192eu
linuxPackages_zen.rtl8812au
linuxPackages_zen.rtl8814au
linuxPackages_zen.rtl8821au
linuxPackages_zen.rtl8821ce
linuxPackages_zen.rtl88x2bu
linuxPackages_zen.rtl88xxau-aircrack
linuxPackages_zen.rtlwifi_new

104 packages built:

linuxPackages_lqx.acpi_call
linuxPackages_lqx.asus-wmi-sensors
linuxPackages_lqx.batman_adv
linuxPackages_lqx.bbswitch
linuxPackages_lqx.bcc
linuxPackages_lqx.bpftrace
linuxPackages_lqx.broadcom_sta
linuxPackages_lqx.can-isotp
linuxPackages_lqx.cpupower
linuxPackages_lqx.ddcci-driver
linuxPackages_lqx.digimend
linuxPackages_lqx.evdi
linuxPackages_lqx.facetimehd
linuxPackages_lqx.fwts-efi-runtime
linuxPackages_lqx.gcadapter-oc-kmod
linuxPackages_lqx.hyperv-daemons
linuxPackages_lqx.intel-speed-select
linuxPackages_lqx.it87
linuxPackages_lqx.jool
linux_lqx (linuxPackages_lqx.kernel)
linuxPackages_lqx.mba6x_bl
linuxPackages_lqx.netatop
linuxPackages_lqx.nvidia_x11
linuxPackages_lqx.nvidia_x11_beta
linuxPackages_lqx.nvidia_x11_vulkan_beta
linuxPackages_lqx.nvidiabl
linuxPackages_lqx.openafs (linuxPackages_lqx.openafs_1_8)
linuxPackages_lqx.openafs_1_9
linuxPackages_lqx.openrazer
linuxPackages_lqx.perf
linuxPackages_lqx.ply
linuxPackages_lqx.r8168
linuxPackages_lqx.rtl8821cu
linuxPackages_lqx.sysdig
linuxPackages_lqx.system76
linuxPackages_lqx.system76-acpi
linuxPackages_lqx.system76-io
linuxPackages_lqx.systemtap
linuxPackages_lqx.tmon
linuxPackages_lqx.tp_smapi
linuxPackages_lqx.turbostat
linuxPackages_lqx.tuxedo-keyboard
linuxPackages_lqx.usbip
linuxPackages_lqx.v4l2loopback
linuxPackages_lqx.v86d
linuxPackages_lqx.vhba
linuxPackages_lqx.virtualbox
linuxPackages_lqx.virtualboxGuestAdditions
linuxPackages_lqx.x86_energy_perf_policy
linuxPackages_lqx.xpadneo
linuxPackages_lqx.zenpower
linuxPackages_lqx.zfs (linuxPackages_lqx.zfsStable ,linuxPackages_lqx.zfsUnstable)
linuxPackages_zen.acpi_call
linuxPackages_zen.asus-wmi-sensors
linuxPackages_zen.batman_adv
linuxPackages_zen.bbswitch
linuxPackages_zen.bcc
linuxPackages_zen.bpftrace
linuxPackages_zen.broadcom_sta
linuxPackages_zen.can-isotp
linuxPackages_zen.cpupower
linuxPackages_zen.ddcci-driver
linuxPackages_zen.digimend
linuxPackages_zen.evdi
linuxPackages_zen.facetimehd
linuxPackages_zen.fwts-efi-runtime
linuxPackages_zen.gcadapter-oc-kmod
linuxPackages_zen.hyperv-daemons
linuxPackages_zen.intel-speed-select
linuxPackages_zen.it87
linuxPackages_zen.jool
linux_zen (linuxPackages_zen.kernel)
linuxPackages_zen.mba6x_bl
linuxPackages_zen.netatop
linuxPackages_zen.nvidia_x11
linuxPackages_zen.nvidia_x11_beta
linuxPackages_zen.nvidia_x11_vulkan_beta
linuxPackages_zen.nvidiabl
linuxPackages_zen.openafs (linuxPackages_zen.openafs_1_8)
linuxPackages_zen.openafs_1_9
linuxPackages_zen.openrazer
linuxPackages_zen.perf
linuxPackages_zen.ply
linuxPackages_zen.r8168
linuxPackages_zen.rtl8821cu
linuxPackages_zen.sysdig
linuxPackages_zen.system76
linuxPackages_zen.system76-acpi
linuxPackages_zen.system76-io
linuxPackages_zen.systemtap
linuxPackages_zen.tmon
linuxPackages_zen.tp_smapi
linuxPackages_zen.turbostat
linuxPackages_zen.tuxedo-keyboard
linuxPackages_zen.usbip
linuxPackages_zen.v4l2loopback
linuxPackages_zen.v86d
linuxPackages_zen.vhba
linuxPackages_zen.virtualbox
linuxPackages_zen.virtualboxGuestAdditions
linuxPackages_zen.x86_energy_perf_policy
linuxPackages_zen.xpadneo
linuxPackages_zen.zenpower
linuxPackages_zen.zfs (linuxPackages_zen.zfsStable ,linuxPackages_zen.zfsUnstable)

Result of nixpkgs-review pr 110797 1

18 packages marked as broken and skipped:

linuxPackages_lqx.ixgbevf
linuxPackages_lqx.lttng-modules
linuxPackages_lqx.ndiswrapper
linuxPackages_lqx.nvidia_x11_legacy304
linuxPackages_lqx.phc-intel
linuxPackages_lqx.r8125
linuxPackages_lqx.rtl8723bs
linuxPackages_lqx.sch_cake
linuxPackages_lqx.tbs
linuxPackages_zen.ixgbevf
linuxPackages_zen.lttng-modules
linuxPackages_zen.ndiswrapper
linuxPackages_zen.nvidia_x11_legacy304
linuxPackages_zen.phc-intel
linuxPackages_zen.r8125
linuxPackages_zen.rtl8723bs
linuxPackages_zen.sch_cake
linuxPackages_zen.tbs

40 packages failed to build:

linuxPackages_lqx.akvcam
linuxPackages_lqx.amdgpu-pro
linuxPackages_lqx.anbox
linuxPackages_lqx.chipsec
linuxPackages_lqx.cryptodev
linuxPackages_lqx.dpdk
linuxPackages_lqx.ena
linuxPackages_lqx.mwprocapture
linuxPackages_lqx.mxu11x0
linuxPackages_lqx.nvidia_x11_legacy340
linuxPackages_lqx.nvidia_x11_legacy390
linuxPackages_lqx.oci-seccomp-bpf-hook
linuxPackages_lqx.rtl8192eu
linuxPackages_lqx.rtl8812au
linuxPackages_lqx.rtl8814au
linuxPackages_lqx.rtl8821au
linuxPackages_lqx.rtl8821ce
linuxPackages_lqx.rtl88x2bu
linuxPackages_lqx.rtl88xxau-aircrack
linuxPackages_lqx.rtlwifi_new
linuxPackages_zen.akvcam
linuxPackages_zen.amdgpu-pro
linuxPackages_zen.anbox
linuxPackages_zen.chipsec
linuxPackages_zen.cryptodev
linuxPackages_zen.dpdk
linuxPackages_zen.ena
linuxPackages_zen.mwprocapture
linuxPackages_zen.mxu11x0
linuxPackages_zen.nvidia_x11_legacy340
linuxPackages_zen.nvidia_x11_legacy390
linuxPackages_zen.oci-seccomp-bpf-hook
linuxPackages_zen.rtl8192eu
linuxPackages_zen.rtl8812au
linuxPackages_zen.rtl8814au
linuxPackages_zen.rtl8821au
linuxPackages_zen.rtl8821ce
linuxPackages_zen.rtl88x2bu
linuxPackages_zen.rtl88xxau-aircrack
linuxPackages_zen.rtlwifi_new

104 packages built:

linuxPackages_lqx.acpi_call
linuxPackages_lqx.asus-wmi-sensors
linuxPackages_lqx.batman_adv
linuxPackages_lqx.bbswitch
linuxPackages_lqx.bcc
linuxPackages_lqx.bpftrace
linuxPackages_lqx.broadcom_sta
linuxPackages_lqx.can-isotp
linuxPackages_lqx.cpupower
linuxPackages_lqx.ddcci-driver
linuxPackages_lqx.digimend
linuxPackages_lqx.evdi
linuxPackages_lqx.facetimehd
linuxPackages_lqx.fwts-efi-runtime
linuxPackages_lqx.gcadapter-oc-kmod
linuxPackages_lqx.hyperv-daemons
linuxPackages_lqx.intel-speed-select
linuxPackages_lqx.it87
linuxPackages_lqx.jool
linux_lqx (linuxPackages_lqx.kernel)
linuxPackages_lqx.mba6x_bl
linuxPackages_lqx.netatop
linuxPackages_lqx.nvidia_x11
linuxPackages_lqx.nvidia_x11_beta
linuxPackages_lqx.nvidia_x11_vulkan_beta
linuxPackages_lqx.nvidiabl
linuxPackages_lqx.openafs (linuxPackages_lqx.openafs_1_8)
linuxPackages_lqx.openafs_1_9
linuxPackages_lqx.openrazer
linuxPackages_lqx.perf
linuxPackages_lqx.ply
linuxPackages_lqx.r8168
linuxPackages_lqx.rtl8821cu
linuxPackages_lqx.sysdig
linuxPackages_lqx.system76
linuxPackages_lqx.system76-acpi
linuxPackages_lqx.system76-io
linuxPackages_lqx.systemtap
linuxPackages_lqx.tmon
linuxPackages_lqx.tp_smapi
linuxPackages_lqx.turbostat
linuxPackages_lqx.tuxedo-keyboard
linuxPackages_lqx.usbip
linuxPackages_lqx.v4l2loopback
linuxPackages_lqx.v86d
linuxPackages_lqx.vhba
linuxPackages_lqx.virtualbox
linuxPackages_lqx.virtualboxGuestAdditions
linuxPackages_lqx.x86_energy_perf_policy
linuxPackages_lqx.xpadneo
linuxPackages_lqx.zenpower
linuxPackages_lqx.zfs (linuxPackages_lqx.zfsStable ,linuxPackages_lqx.zfsUnstable)
linuxPackages_zen.acpi_call
linuxPackages_zen.asus-wmi-sensors
linuxPackages_zen.batman_adv
linuxPackages_zen.bbswitch
linuxPackages_zen.bcc
linuxPackages_zen.bpftrace
linuxPackages_zen.broadcom_sta
linuxPackages_zen.can-isotp
linuxPackages_zen.cpupower
linuxPackages_zen.ddcci-driver
linuxPackages_zen.digimend
linuxPackages_zen.evdi
linuxPackages_zen.facetimehd
linuxPackages_zen.fwts-efi-runtime
linuxPackages_zen.gcadapter-oc-kmod
linuxPackages_zen.hyperv-daemons
linuxPackages_zen.intel-speed-select
linuxPackages_zen.it87
linuxPackages_zen.jool
linux_zen (linuxPackages_zen.kernel)
linuxPackages_zen.mba6x_bl
linuxPackages_zen.netatop
linuxPackages_zen.nvidia_x11
linuxPackages_zen.nvidia_x11_beta
linuxPackages_zen.nvidia_x11_vulkan_beta
linuxPackages_zen.nvidiabl
linuxPackages_zen.openafs (linuxPackages_zen.openafs_1_8)
linuxPackages_zen.openafs_1_9
linuxPackages_zen.openrazer
linuxPackages_zen.perf
linuxPackages_zen.ply
linuxPackages_zen.r8168
linuxPackages_zen.rtl8821cu
linuxPackages_zen.sysdig
linuxPackages_zen.system76
linuxPackages_zen.system76-acpi
linuxPackages_zen.system76-io
linuxPackages_zen.systemtap
linuxPackages_zen.tmon
linuxPackages_zen.tp_smapi
linuxPackages_zen.turbostat
linuxPackages_zen.tuxedo-keyboard
linuxPackages_zen.usbip
linuxPackages_zen.v4l2loopback
linuxPackages_zen.v86d
linuxPackages_zen.vhba
linuxPackages_zen.virtualbox
linuxPackages_zen.virtualboxGuestAdditions
linuxPackages_zen.x86_energy_perf_policy
linuxPackages_zen.xpadneo
linuxPackages_zen.zenpower
linuxPackages_zen.zfs (linuxPackages_zen.zfsStable ,linuxPackages_zen.zfsUnstable)

authors: Atemu Mic92 andresilva


text:
Package for certificate-transparency

This bumps evhtp's version because 1.2.11 provides pkg-config
information which makes building certificate-transparency easier.
We need an openssl-enabled version of libevent and libevhtp; the default
builds don't include openssl so I used overrides to rebuild with openssl
support.
This has been tested with doCheck = true; to verify the tests actually pass :)

Updated PR based on feedback, thanks @fpletz!
I've also bumped the version of certificate-transparency this builds; that required some updates to one of the patches.  (I have a separate PR at google/certificate-transparency#1040 to push this patch upstream.)

Updated the PR to do the following things:

use a more recent certificate-transparency version which pulls in google/certificate-transparency#1062, which means I can remove a patch
change libevent to compile TLS support by default
rebase to latest master

I think this should be good to go now?

One question I have: this derivation seems to build something which has a runtime dependency on gcc. I'm not sure why. Maybe something to do with protobuf?

travis build was killed as log length was more than 4MB :/ did I do something wrong? https://s3.amazonaws.com/archive.travis-ci.org/jobs/93503274/log.txt

No it's fine. Picked into staging with 01eb385346b09f12994c187af835ee72254640d6 since the libevent change will rebuild a lot of packages.

authors: edwtjo philandstuff


text:
xorg.libXt: 1.2.0 -> 1.2.1

Motivation for this change
https://lists.x.org/archives/xorg-announce/2021-January/003070.html
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

[x] Fits CONTRIBUTING.md.

@ofborg eval

@ofborg eval

What needs to be done to get this merged?

@ofborg eval


text:
gems: Added mime info path for mimemagic

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 117702 at 0c797246 run on aarch64-linux 1

2 packages skipped due to time constraints:

gitlab
gitlab-ee

2 packages built successfully:

iruby
redmine

Thanks @SuperSandro2000, I double checked this and you're right. Not sure why it builds anyway 🤔 Looking at the code it should check that the path is a file but it doesn't.

I added the latest master branch to my channels but now I can't install. I think this PR is the issue.

error: attribute 'mimemagic' at /nix/store/pqgaklshxjj2ji6wwya38cifw4xqn4fh-master/master/pkgs/development/ruby-modules/gem-config/default.nix:397:3 already defined at /nix/store/pqgaklshxjj2ji6wwya38cifw4xqn4fh-master/master/pkgs/development/ruby-modules/gem-config/default.nix:167:3

error: attribute 'mimemagic' at /nix/store/pqgaklshxjj2ji6wwya38cifw4xqn4fh-master/master/pkgs/development/ruby-modules/gem-config/default.nix:397:3 already defined at /nix/store/pqgaklshxjj2ji6wwya38cifw4xqn4fh-master/master/pkgs/development/ruby-modules/gem-config/default.nix:167:3

I am seeing this issue as well when trying to nix search nixpkgs/master ... after this PR.

I pushed a revert. This only added a duplicate redundant entry, which broke the eval.

The other commit that added this was 9b30cda2f6e301abc6f39e01902330d981b12a80 in #118736

Sorry! @ajs124 thank you for fixing it.

authors: ajs124 andreykaipov edude03 kylesferrazza r-rmcgibbo ryantm


text:
vivaldi: use ffmpeg instead of ffmpeg_3

Motivation for this change
https://github.com/NixOS/nixpkgs/issues/120705
Things done

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

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

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

I only made sure that it builds, not that it works.

ACK-ing. Diff looks good, I'll try it out when I get a chance later

authors: badmutex dotlambda


text:
vscode-extensions.hashicorp.terraform: 2.11.0 -> 2.12.0

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

[ ] (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 126257 run on x86_64-darwin 1

Thank you!

authors: happysalada rhoriguchi


text:
fancy-motd: unstable-2021-07-04 -> unstable-2021-07-15

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

[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 130315 at 8c504460 run on x86_64-linux 1

1 package built successfully:

fancy-motd

1 suggestion:

warning: build-tools-in-build-inputs
bc is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/tools/system/fancy-motd/default.nix:14:3:
   |
14 |   buildInputs = [ bc curl figlet fortune gawk iproute2 ];
   |   ^

authors: r-rmcgibbo rhoriguchi


text:
papertrail: deprecate phases

Motivation for this change
#28910
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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 130745 at ade7d559 run on aarch64-linux 1

1 package built successfully:

papertrail

1 suggestion:

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

authors: Stunkymonkey r-rmcgibbo


text:
aseprite.skia: cleanup, switch to pname + version, add meta

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/)
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.

@ofborg eval

Result of nixpkgs-review pr 131250 at 4449d867 run on aarch64-linux 1

1 package failed to build:

aseprite-unfree

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.


text:
nixos/nix-daemon: fix registry flake type

Before this commit, the flake option was typed with types.unspecified.
This type get's merged via mergeDefaultOption, which has a line
else if all isFunction list then x: mergeDefaultOption loc (map (f: f x) list)

lib.isFunction detects an attrs in the shape of {__functor = ...} as
a function and hence this line substitutes such attrs with a function
(f: f x).
If now, a flake input has a __functor as it's output, this will
coerce the once attrs to a function. This breaks a lot of things later
in the stack, for example a later lib.filterAttrs seive <LAMBDA> will
fail for obious reasons.
According to @infinisil, types.unspecified is due to deprecation. In
the meantime this PR provides a specific fix for the specific problem
discovered.
EDIT: this needs quite some back-porting, please someone can add the respective labels?

@roberth I'd say this warrants backporting, does it?


text:
pymol: 2.3.0 -> 2.5.0

Motivation for this change
Pymole version update.
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 packages 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 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 134720 at 5a3329d7 run on x86_64-linux 1

1 package built successfully:

pymol

2 suggestions:

warning: no-python-tests
Test runner could not discover any test cases: ‘Ran 0 tests in 0.000s’
Near pkgs/applications/science/chemistry/pymol/default.nix:52:0:
   |
52 |     description = description;
   | ^

warning: unused-argument
Unused argument: fetchurl.
Near pkgs/applications/science/chemistry/pymol/default.nix:1:8:
  |
1 | { lib, fetchurl, fetchFromGitHub, makeDesktopItem
  |        ^


text:
phoc: 0.8.0 -> 0.9.0, patch for wlroots 0.14

Motivation for this change
Not sure if this does what it should do, both the new and old version only show me a cursor on a black screen. Testing would be very much appreciated.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages 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 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.

Can I get removed as the package maintainer? I'm not using phoc or phosh.

Can I get removed as the package maintainer? I'm not using phoc or phosh.

Please send a PR.

Phoc released 0.11.0 with wlroots 0.14 support (#151519, which also drops wlroots_0_12) so this PR is no longer necessary. However, I really appreciate the efforts and initiative :heart:

Thank you for the new PR, closing this.


text:
lingua-franca: init with 0.1.0

Lingua Franca
A polyglot coordination language.
Things done

Built on platform(s)

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

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

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 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.

Squash all of these into a single init commit and also have a seperate commit for adding yourself as a maintainer

Was not really sure how the commit message for adding me as a maintainer should be formed but I hope this will due.
Thanks to you both @SuperSandro2000 @GKasparov

authors: GKasparov revol-xut


text:
nixos/podman: refactor tests

Motivation for this change
This moves all of the podman tests under nixosTests.podman so they are all checked by default while still allowing them to be run separately.
If we ever want to make just the main podman test a channel blocker we could do this:
diff --git a/nixos/release-combined.nix b/nixos/release-combined.nix
index ee3f3d19174..4782a24e9f2 100644
--- a/nixos/release-combined.nix
+++ b/nixos/release-combined.nix
@@ -64,6 +64,7 @@ in rec {
         (onFullSupported "nixos.tests.containers-imperative")
         (onFullSupported "nixos.tests.containers-ip")
         (onSystems ["x86_64-linux"] "nixos.tests.docker")
+        (onSystems ["x86_64-linux"] "nixos.tests.podman.default")
         (onFullSupported "nixos.tests.ecryptfs")
         (onFullSupported "nixos.tests.env")
         (onFullSupported "nixos.tests.firefox-esr")

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

cc @NixOS/podman @roberth

@ofborg build podman.tests

@ofborg test podman

@ofborg build podman.tests.default

Why did ofborg try podman.tests.default?
The correct attribute is podman.tests.podman.default, although I suppose podman.tests.nixos.default might be nicer. Maybe ofborg was confused by the double occurrence of podman in the attr path? idk.

@ofborg test podman
@ofborg build podman.tests

authors: roberth zowoq