jiebi/CodeConvo huggingface dataset:
Change:
coreutilsMinimal = coreutils.override (args: { <del> # We want coreutils without ACL support. </del> <ins> # We want coreutils without ACL/attr support. </ins> aclSupport = false; <ins> attrSupport = false; </ins> # Our tooling currently can't handle scripts in bin/, only ELFs and symlinks. singleBinary = "symlinks"; });

Discussion:
When trying to copy a file with extended attributes, the attributes don't get copied. When forcing to copy the attributes, it reports: The issue was probably introduced with multiple outputs support. Previously, would find libs&headers while building, propagated through . But now, only the libs propagate and not , so can't find the header and disables support. Not sure if coreutils should just list as a (when is) or if should somehow signal that its output should propagate too. System: Nix version: Nixpkgs version:
By default, the output should be propagated and it should propagate libs and some others in turn. I'll re-check all this later (if noone else is faster).
Hmm, as far as I can tell from the git logs, at least explicitly didn't propagate .
When I tested 16.03 it doesn't have xattr support there either. But anyway, enables it.
I'm pretty sure it used to work at some point, but it might have been a few years ago :) Thanks!
Change:
diff --git a/src/extension.ts b/src/extension.ts <del> index c3833e9..611e84c 100644 </del> <ins> index f34e865..f12d4db 100644 </ins> --- a/src/extension.ts +++ b/src/extension.ts <del> @@ -544,7 +544,7 @@ export class Ext extends Ecs.System<ExtEvent> { return true } </del> <ins> @@ -556,7 +556,7 @@ export class Ext extends Ecs.System<ExtEvent> { return true; }; </ins> <del> -        const ipc = utils.async_process_ipc(["gjs", path]) +        const ipc = utils.async_process_ipc([path]) </del> <ins> -        const ipc = utils.async_process_ipc(['gjs', '--module', path]); +        const ipc = utils.async_process_ipc([path]); </ins> if (ipc) { const generator = (stdout: any, res: any) => { diff --git a/src/panel_settings.ts b/src/panel_settings.ts <del> index 5d02d33..1cd70d0 100644 </del> <ins> index fbcafbf..ef409ee 100644 </ins> --- a/src/panel_settings.ts +++ b/src/panel_settings.ts <del> @@ -348,7 +348,7 @@ function color_selector(ext: Ext, menu: any) { </del> <ins> @@ -352,7 +352,7 @@ function color_selector(ext: Ext, menu: any) { </ins> color_selector_item.add_child(color_button); color_button.connect('button-press-event', () => { <del> let path = Me.dir.get_path() + "/color_dialog/main.js"; -        let resp = GLib.spawn_command_line_async(`gjs ${path}`); </del> <ins> let path = get_current_path() + '/color_dialog/main.js'; -        let resp = GLib.spawn_command_line_async(`gjs --module ${path}`); </ins> +        let resp = GLib.spawn_command_line_async(`${path}`); if (!resp) { return null; <del> -- 2.37.3 </del> <ins> } </ins>

Discussion:
Package name: gnome-shell-extension-pop-shell Latest released version: unstable-2023-11-10 <!-- Search your package here: --- Current version on the unstable channel: unstable-2023-04-27 Current version on the stable/release channel: unstable-2023-04-27 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --This brings about Gnome 45 support, as far as I know. Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Priorities Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
thanks for alle the involved to fix it so fast
Change:
trees or files; and vifn, to invoke vi given a function name rather than a file name. ''; <del> platforms = platforms.linux; </del> maintainers = with maintainers; [ peterhoeg ]; <ins> platforms = platforms.unix; </ins> }; }

Discussion:
Hello, Huge thanks for contributing to nix! I am trying to use this great package manager with a Mac, and I am having some issues trying to install my favourite email client. When I try to install mu with nix-env -I mu, I get the following error: I checked the pmccabe derivation, and it has indeed a constraint on the platform: platforms = ;. Any way this derivation can work on Mac OS X x64? Thanks, Andrea System: Mac OS X Sierra 10.12.4 Nix version: 1.11.8 Nixpkgs version: 17.09pre104948.
It seems the dependency is not used or at least optional, this builds fine without it.
cc it, I think. iirc, that dep is for the test suite.
This isn't the first time I'm breaking the build on Darwin. How do other people test properly without access to a mac?
Thanks, this works!
You can use to check evaluation for darwin or other platforms. That should catch simple cases like this if you don't have enabled in your config.
Thanks for the pointer I think the trick is to get darwin running in a VM instead...
Change:
, pamixer          # pamixer , pulseaudio       # pactl , libdbusmenu-gtk3 # tray <ins> , playerctl </ins> }: python3Packages.buildPythonApplication rec { pname = "nwg-panel"; <del> version = "0.7.17"; </del> <ins> version = "0.9.11"; </ins> src = fetchFromGitHub { owner = "nwg-piotr"; repo = "nwg-panel"; <del> rev = "refs/tags/v${version}"; sha256 = "sha256-HGbPBHf5PIjbuMSd/2fFSCLQ/7s1Xbys+KoGXctQOvM="; </del> <ins> rev = "v${version}"; hash = "sha256-4/R/x3iQ6nsG5OLy/FMA24uxS3xKD/2901gBNe6lkk4="; </ins> }; # No tests

Discussion:
package-name: nwg-panel nwg-panel latest verison: 0.9.11 nixpkg unstable: 0.7.17 nixpkg stable: 0.7.17 Notify mainters; no maintainers
Change:
src = fetchurl { url = "https://download.virtualbox.org/virtualbox/${version}/VirtualBox-${version}.tar.bz2"; <del> sha256 = main; </del> <ins> sha256 = "b031c30d770f28c5f884071ad933e8c1f83e65b93aaba03a4012077c1d90a54f"; </ins> }; outputs = [ "out" "modsrc" ];

Discussion:
Describe the bug Virtualbox kernel drivers don't build with latest kernel. To Reproduce Steps to reproduce the behavior: on latest master, channel hasn't updated yet d=(import /home/maciej/Projekte/nix { configuration = {pkgs, ...}: { boot.kernelPackages = pkgs.linuxPackageslatest; = true; }; }).vm Expected behavior Builds Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(maciej): nixpkgs: Maintainer information:
Hi sorry for the duplicate bug report. You may find some useful information in this other issue trackers: Upstream tracker: Related to this issue: [Patch available]
Virtualbox 6.1.6 was released last week, which fixes the Linux 5.6 issues. I opened a PR with a fix for , which needs to be merged into to
Change:
export NIX_STATE_DIR=$TEST_ROOT/var/nix export NIX_STORE_DIR=$TEST_ROOT/store <del> # cargo tests run in parallel by default, which would then run into # https://github.com/NixOS/nix/issues/2706 unless the store is initialised first </del> <ins> # Ensure that even if tests run in parallel, we don't get an error # We'd run into https://github.com/NixOS/nix/issues/2706 unless the store is initialised first </ins> nix-store --init ''; <ins> # The tests use the shared environment variables, # so we cannot run them in parallel dontUseCargoParallelTests = true; </ins> postCheck = '' cargo fmt --check cargo clippy -- -D warnings

Discussion:
Since , the tool started failing its tests on aarch64-linux. Reproduce (probably, I can't test this myself) with: Failing Hydra build: Logs:
Ohh it's not deterministic! I can reproduce this even on if I try it a couple times.. Investigating
Fix:
Change:
''; nativeBuildInputs = [ autoPatchelfHook makeWrapper wrapQtAppsHook ]; <del> buildInputs = [ dbus qtbase qtwebkit qtx11extras libX11 ]; </del> <ins> buildInputs = [ dbus getconf qtbase qtwebkit qtwebengine qtx11extras libX11 ]; </ins> propagatedBuildInputs = [ qtquickcontrols ]; installPhase = ''

Discussion:
Describe the bug When busybox is installed - teamviewer cannot starts correctly To Reproduce Steps to reproduce the behavior: " = true;" to busybox to "environment.systemPackages = with pkgs;" to launch the teamviewer Expected behavior Teamviewer gui starts Screenshots If applicable, add screenshots to help explain your problem. ! Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata these paths will be fetched (0.05 MiB download, 0.28 MiB unpacked): /nix/store/d43v6bx7r6fcaq3fbbfd5mwh1f5s7rmg-bash-interactive-4.4-p23-dev copying path '/nix/store/d43v6bx7r6fcaq3fbbfd5mwh1f5s7rmg-bash-interactive-4.4-p23-dev' from ''... system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
I marked this as stale due to inactivity. &rarr;
This should be fixed by . Please confirm by closing if it indeed does.
Change:
wantedBy = [ "sysinit.target" ]; aliases = [ "dbus-org.freedesktop.timesync1.service" ]; restartTriggers = [ config.environment.etc."systemd/timesyncd.conf".source ]; <ins> # systemd-timesyncd disables DNSSEC validation in the nss-resolve module by setting SYSTEMD_NSS_RESOLVE_VALIDATE to 0 in the unit file. # This is required in order to solve the chicken-and-egg problem when DNSSEC validation needs the correct time to work, but to set the # correct time, we need to connect to an NTP server, which usually requires resolving its hostname. # In order for nss-resolve to be able to read this environment variable we patch systemd-timesyncd to disable NSCD and use NSS modules directly. # This means that systemd-timesyncd needs to have NSS modules path in LD_LIBRARY_PATH. When systemd-resolved is disabled we still need to set # NSS module path so that systemd-timesyncd keeps using other NSS modules that are configured in the system. environment.LD_LIBRARY_PATH = config.system.nssModules.path; </ins> preStart = ( # Ensure that we have some stored time to prevent

Discussion:
I'm bringing up new RPis and their clocks are often wrong. Even though upstream systemd has given exceptions to be able to skip dnssec check for ntp sync, it doesn't... appear to be working. If I set the date manually, often by time I check timesyncd will have already taken care of kicking in and it reports that it's synced. Steps to reproduce the behavior: the clock badly. . and see if your DNS works
If I read it right, only works for systemd-resolved. One general workaround is to use hard-coded IP addresses for NTP (our routers actually do that IIRC).
That commit seems to indicate that it should bypass DNSSEC for timesyncd. This would get my clock back in sync, thus resolving DNSSEC errors for the rest of the system. But timesyncd isn't doing its job. I assume that's because: date wrong -dnssec failure. But maybe also fails if the clock is just too askew? I'll try to look more later, maybe I have to opt-in large corrections? Seems a bit weird to me. Or do we maybe use timesyncd in a non-standard way?
I ran into this on a Raspberry Pi 3B. I'm using systemd-networkd including systemd-resolved. At some point DNS started failing, and I noticed the system clock was out of sync by about 4 hours and not synchronizing anymore. The log of systemd-resolved was full of DNSSEC s: I'm not sure what changed, because I was able to install NixOS just fine. It also was offline before for some time without this problem happening (as far as I noticed at least), and it started happening after it was online for some time without break. Also, the systemd-native workaround should be working on NixOS as well, I can't find anything that indicates a non-standard setup that might overwrite tha workaround. Checking is the standard original systemd unit file that includes the relevant line and as far as I can see it isn't overridden. I also checked and it includes . For now, I worked around the issue by specifying my NTP servers by IP (I used the ones by the ).
Closing as this should be fixed by Please reopen if this is still an issue.
Change:
<ins> { config, lib, pkgs, ... }: let cfg = config.programs.envision; in { options = { programs.envision = { enable = lib.mkEnableOption "envision"; package = lib.mkPackageOption pkgs "envision" {}; openFirewall = lib.mkEnableOption "the default ports in the firewall for the WiVRn server" // { default = true; }; }; }; config = lib.mkIf cfg.enable { services.avahi = { enable = true; publish = { enable = true; userServices = true; }; }; environment.systemPackages = [ cfg.package ]; networking.firewall = lib.mkIf cfg.openFirewall { allowedTCPPorts = [ 9757 ]; allowedUDPPorts = [ 9757 ]; }; }; meta.maintainers = pkgs.envision.meta.maintainers; } </ins>

Discussion:
Project description UI for building, configuring and running Monado, the open source OpenXR runtime. Metadata homepage URL: source URL: license: agpl3 platforms: unix, linux, darwin Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
To my information, software without a stable release isnt accepted yet.
Not even in unstable? Fair enough, I guess.
unstable automatically becomes stable, so yes :) I think once a release is done (even 0.x), it can be packaged, but don't take my word as the ultimate truth, please :sweat_smile:
This appears to be incorrect. was merged targeting a specific commit (despite actually having stable releases).
This is indeed incorrect; there are even specific rules for the attribute of unreleased versions.
Change:
{ <del> "version": "1.115.0", "hash": "sha256-H2FCR55redomrDjnnCQys47AaYbWEmlxO5NJEcVMBwY=", </del> <ins> "version": "1.116.2", "hash": "sha256-vbLUHNgUHnKAO424j/MwKDv0GZhBZ2T6vwjLsIHhMxM=", </ins> "components": { "cli": { <del> "npmDepsHash": "sha256-+zKtPHXjBd1KAKvI5xaY2/9qzVUg+8Ho/wrV9+TlU64=", "version": "2.2.19" </del> <ins> "npmDepsHash": "sha256-M0A+B9qHmRRb6XW0P57Huo85cL8PUpLGe32IJzJgZhY=", "version": "2.2.22" </ins> }, "server": { <del> "npmDepsHash": "sha256-6CehRhPepspDpQW1h0Bx7EpH7hn42Ygqma/6wim14jA=", "version": "1.115.0" </del> <ins> "npmDepsHash": "sha256-1gOJxg+OXG4t6jZdia5+1Ie5gOjtZhqpqOgPi3I/U+k=", "version": "1.116.2" </ins> }, "web": { <del> "npmDepsHash": "sha256-ZmXfYktgOmMkDjfqSGyyflr2CmnC9yVnJ1gAcmd6A00=", "version": "1.115.0" </del> <ins> "npmDepsHash": "sha256-mI/hMDf7mBV1oMkJIh6IYVzqGv+h+sc9wiGJsL0Rmog=", "version": "1.116.2" </ins> }, "open-api/typescript-sdk": { <del> "npmDepsHash": "sha256-l1mLYFpFQjYxytY0ZWLq+ldUhZA6so0HqPgCABt0s9k=", "version": "1.115.0" </del> <ins> "npmDepsHash": "sha256-lfqk/2YBbB6qiFXjeTYqnkslVmI8fXTvHe/wGCSD8Ok=", "version": "1.116.2" </ins> } } }

Discussion:
Package name: immich Latest released version: 1.116.2 Current version on the unstable channel: 1.115.0 Current version on the stable/release channel: N/A Notify maintainers Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
tar xf nxplayer.tar.gz rm $(find . -maxdepth 1 -type f) ''; nativeBuildInputs = [ file makeWrapper autoPatchelfHook ]; buildInputs = [ jsoncpp libpulseaudio ];

Discussion:
Describe the bug Installing nomachine-client fails To Reproduce Steps to reproduce the behavior: to environment.systemPackages Expected behavior It should build the derivation Screenshots If applicable, add screenshots to help explain your problem. Additional context Add any other context about the problem here. Metadata Please run and paste the result. Maintainer information:
I tried overriding the hash (any tip on how to more properly do this would be appreciated), but still got build errors in my under environment.systemPackages result:
There's a PR to upgrade : I this to my and it seems to be working for me:
Yep, this is because NoMachine removes each old release as soon as they make a new one. To combat this, I'll add to the sources list when the update is done.
I was finding at the time that even overriding with the latest URL and hash from the nomachine website, that it was failing to download the whole blob. I could do it from my browser, but it seemed to abort/not download the full size via nixos
Oh, that's strange.. Thankfully, it seems to work just fine now :)
Change:
pdfstudio2022 = callPackage ./common.nix rec { inherit desktopName longDescription pname program year; <del> version = "${year}.2.2"; </del> <ins> version = "${year}.2.4"; </ins> src = fetchurl { url = "https://download.qoppa.com/pdfstudio/v${year}/PDFStudio_v${dot2dash version}_linux64.deb"; <del> sha256 = "sha256-CP2cCmvedQJ/xjZWQ4wj6UZRqCsU5qK3Ta83TUVJyts="; </del> <ins> sha256 = "sha256-bti+WI8JdOmUsHq8ijfxGC4ZsWXwbwwM26kuBgPDUMQ="; </ins> }; extraBuildInputs = [ (lib.getLib stdenv.cc.cc)  # for libstdc++.so.6 and libgomp.so.1 ]; jdk = jdk17; <del> broken = true; # URL 404s, probably unstable </del> }; }.${pname}

Discussion:
The package had been silently marked as broken. From what I can see, the developers now only provide a deb file for the latest version, see The deb link is I guess we should update the link instead of marking the package broken.
Change:
<del> { callPackage, ... } @ args: callPackage ./generic.nix (args // { version = "1.5.2"; branch = "1.5"; revision = "version.1.5.2"; sha256 = "1dvvpvb597i5z8srz2v4c5dsbxb966h125jx3m2z0r2gd2wvpfkp"; testsSupport = false; }) </del>

Discussion:
, CVSSv3=7.8 (nixos-20.09, nixos-unstable) CVSSv3=5.5 (nixos-20.09, nixos-unstable) CVSSv3=5.5 (nixos-20.09, nixos-unstable) CVSSv3=5.5 (nixos-20.09, nixos-unstable) CVSSv3=5.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc
See also: ,
Change:
<ins> { stdenv, lib, fetchurl, autoPatchelfHook }: stdenv.mkDerivation rec { pname = "stt"; version = "0.9.3"; src = fetchurl { url = "https://github.com/coqui-ai/STT/releases/download/v${version}/native_client.tf.Linux.tar.xz"; sha256 = "0axwys8vis4f0m7d1i2r3dfqlc8p3yj2nisvc7pdi5qs741xgy8w"; }; setSourceRoot = "sourceRoot=`pwd`"; nativeBuildInputs = [ autoPatchelfHook ]; buildInputs = [ stdenv.cc.cc.lib ]; installPhase = '' install -D stt $out/bin/stt install -D coqui-stt.h $out/include/coqui-stt.h install -D libstt.so $out/lib/libstt.so ''; meta = with lib; { homepage = https://github.com/coqui-ai/STT; description = "Deep learning toolkit for Speech-to-Text, battle-tested in research and production"; license = licenses.mpl20; platforms = [ "x86_64-linux" ]; maintainers = with maintainers; [ rvolosatovs ]; }; } </ins>

Discussion:
<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on github to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the the current version of the package --- <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- name: tts <!-- The current version can be found easily with the same process than above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 0.0.9 desired version: 0.0.11 maintainers: mozilla fired the team and they founded a new company to continue their work new releases can be found here
We are aware of the forks, we'll probably get to it before the branch-off. STT (DeepSpeech) was recently packaged, but does not build from source, so my interest in that package is limited.
Same also not a STT user.
can you update deepspeech to the new repo, call it stt and deprecate deepspeech? how to deprecate a package is documented here: please add a review. when anything is unclear, i would like to improve it
How about we call it instead?
i don't think that is very helpful for the end-user. the package name should match the upstream project name
do you want to update tts again?
Hello, just wanted to say that there has been a new release , in case someone wants to give it a shot.
Change:
in buildBazelPackage rec { pname = "bazel-watcher"; <del> version = "0.23.1"; </del> <ins> version = "0.24.0"; </ins> src = fetchFromGitHub { owner = "bazelbuild"; repo = "bazel-watcher"; rev = "v${version}"; <del> sha256 = "sha256-fnhbxrgwffFQDIRLGisi1Wk3EjfkN8Mi8wtWT/Gy+78="; </del> <ins> hash = "sha256-ebNHAYKyE3226KiCc2/VSz1OSITuPwuYlAIS3JrWzj0="; </ins> }; nativeBuildInputs = [ go git python3 ];

Discussion:
Steps to reproduce the behavior: The builds are also failing on Hydra Please run and paste the result.
Several errors like this locally and in
is not set on the system outside the nix-shell and also does not seem to be set when the bazel command is executed within the nix-build. On the same system, with bazelisk, version 0.23.1 builds from source:
merge introduced a build failure (found via git bisect) which merged this change: Reverting it on master makes it work but also reverts bazel-watcher to an older version. AND only works if the is set. I assume it will not actually call the updated fetch logic at all since it just uses the fetched dependencies from the cache. Maybe can help out fixing it...
:)
The makes it hard to bisect since it will "hide" all fetch affecting changes behind that cached results. Long live fixed output derivations!
I was wrong. The fetchAttrs.sha256 hid that it was, in fact, broken before
I bisected this to the following commit: with this bisect script: Unfortunately, it is a huge merge.
Okay fetching broke when go was unpinned:
Maybe related to
: Could you maybe merge ? It would be appreciated.
Change:
"systemd-timedated.service" "systemd-localed.service" "systemd-hostnamed.service" <del> "systemd-binfmt.service" </del> "systemd-exit.service" "systemd-update-done.service" ] ++ optionals config.services.journald.enableHttpGateway [

Discussion:
Describe the bug The indicates a dependency on . However, this unit is not automatically included with the help of . It is therefore listed as : highlights this: Expected behavior Units that are relied upon should be found. Additional context Commit seems to something to do with it. Notify maintainers Metadata Please run and paste the result. Maintainer information:
This has last been touched in I see we set in if , so we could move there as well. After reading a bit on and , is this currently halfway broken? Maybe more of the logic should be moved into …
Can you see if fixes this for you? You might want to reboot, to make sure the mount isn't active. Also, do you use any binfmt stuff?
Yes, it fixes the problem: I do not think so. I am not familiar with binfmt.
Change:
<del> { python3 , fetchPypi }: with python3; pkgs.buildPythonApplication rec { pname = "pypi2nix"; version = "2.0.4"; src = fetchPypi { inherit pname version; sha256 = "0y4zkkcijz5hchd8j6a106ysrg1dnad7dzdgnmz38rgm6zbrky0d"; }; propagatedBuildInputs = with pkgs; [ attrs click jinja2 nix-prefetch-github packaging parsley setuptools toml jsonschema ]; # https://github.com/nix-community/pypi2nix/issues/460 meta.broken = true; } </del>

Discussion:
Steps to reproduce the behavior: Command should execute without an error None? Please run and paste the result.
Change:
networks are set, it will default to using a configuration file at <literal>/etc/wpa_supplicant.conf</literal>. You should edit this file yourself to define wireless networks, WPA keys and so on (see <del> wpa_supplicant.conf(5)). </del> <ins> <citerefentry> <refentrytitle>wpa_supplicant.conf</refentrytitle> <manvolnum>5</manvolnum> </citerefentry>). </ins> </para> <para>

Discussion:
References to (5) should have hyperlinks to the article/section.
These are references to man pages so there can't easily be a hyperlink. I made a PR that makes sure these are referenced to using , though. So that they at least carry some semantic meaning.
My bad I didn't think about the man pages. There are man pages online, too. I found this site: but it'd be nice to have them generated into the NixOS documentation. Having the man page sources piped into HTML would be useful I not a huge space waster.