jiebi/CodeConvo huggingface dataset:
Code change:
, qtbase , qttools , qtwayland <del> , rtaudio </del> <ins> , rtaudio_6 </ins> , rtmidi , wrapQtAppsHook }:

Related discussion:
text: Package name: Latest released version: 5.2.0 Current version on the unstable channel: 5.2.0 Current version on the stable/release channel: 5.2.0 Notify maintainers Note for maintainers: Please tag this issue in your PR.
Pending on
Code change:
python3Packages.buildPythonApplication rec { pname = "heisenbridge"; <del> version = "1.6.0"; </del> <ins> version = "1.7.0"; </ins> src = fetchFromGitHub { owner = "hifi"; repo = pname; rev = "v${version}"; <del> sha256 = "sha256-Q7xqKjAUBHh87VAgsgDOCPDINDh0yUdr3UoUlLqJr5k="; </del> <ins> sha256 = "sha256-rN+qoBS9zIy5EHlFQxgAlcz9haoYJNMKJ2wlS46UOi0="; </ins> }; postPatch = '' echo "${version}" > heisenbridge/version.txt <del> substituteInPlace setup.cfg  --replace "mautrix >=0.10.5, <0.11" "mautrix >=0.10.5, <0.12" </del> ''; propagatedBuildInputs = with python3Packages; [

Related discussion:
text: The latest heisenbridge version doesn't build on nixpkgs-unstable (). Steps to reproduce the behavior: error: This repro's on darwin and on linux, using this nixpkgs revision. I believe this may be due to , where mautrix was bumped to version 0.11.3, but heisenbridge requires 0.10.x. build success. Please run and paste the result. Maintainer information:
The requirement is adjusted in heisenbridge 1.7.0:
Code change:
serviceConfig.PrivateNetwork = "yes"; serviceConfig.NoNewPrivileges = "yes"; serviceConfig.ReadOnlyDirectories = "/"; <del> serviceConfig.ReadWriteDirectories = cfg.output; </del> <ins> serviceConfig.ReadWriteDirectories = dirOf cfg.output; </ins> }; systemd.timers.update-locatedb = mkIf cfg.enable

Related discussion:
text: I noticed my locatedb hasn't been updated in ~34 days. The is failing. Here's the full output: And for some reason, some of the log lines are missing from that, so here's the systemctl status output for that service: Relevant lines:
I can't find any trace of (with a ), at least on master and the latest unstable channel. What service do you mean?
Argh, sorry, I read it (notice ). Sorry, sleepy.
has problems on my unstable NixOS system too:
I confirm the problem
I have the same problem and see this in systemd's journal: The systemd service seems to have been defined like this: So it seems that is not being correctly specified.
This is what I wanted to write: However, this is still not fixed: returns (after a call to (which has exit status 0)) So, this is not fixed in 16.03. Please reopen. If is not meant to be callable as root, then should be a wrapper of some kind which would say However, I think pretty much anyone with some Linux experience wants to be able to easily build a new index when they want and has historically been the UI/API to do that. Changing that, if that was the intention, is a rather ill-conceived idea.
So, is this supposed to be working? I am still getting the same error.
This issue was about the systemd service failing with a / , it wasn't about not being able to find the file, even after running manually (I would file a separate issue for that). is the error you are still getting the failure in the systemd service? If so, which release / branch / channel are you running?
I still get the same error "read-only filesystem." I suspect this is because the only service I have running that wants to create /var/cache is the one for updatedb, which still doesn't have write permissions to /var to do so. Manually creating /var/cache as root fixes the problem.
Just installed nixos. I to get this errror. Is there any fix for this.?
Code change:
serviceConfig.PrivateNetwork = "yes"; serviceConfig.NoNewPrivileges = "yes"; serviceConfig.ReadOnlyDirectories = "/"; <del> serviceConfig.ReadWriteDirectories = cfg.output; </del> <ins> serviceConfig.ReadWriteDirectories = dirOf cfg.output; </ins> }; systemd.timers.update-locatedb = mkIf cfg.enable

Related discussion:
text: Same here on a fresh install as root: nixos /nix/store/w1gzi0342kiha08pym7qj09w09ffzhj4-findutils-4.6.0/bin/updatedb: line 323: /nix/store/w1gzi0342kiha08pym7qj09w09ffzhj4-findutils-4.6.0/var/locatedb.n: Read-only file system
just installed 16.09 and I'm getting the same, Read-only file system on updatedb
VERSION="16.09.1836. (Flounder)" nix-env (Nix) 1.11.7 works fine if updatedb is used with --output and later locate is used with --database when invoked by root in a login shell, updatedb tries to write to: /nix/store/95vfigaqdg8jg5bk961k1x06j86p5fh0-findutils-4.6.0/var/locatedb.n: Read-only file system when invoked by user in a login shell, updatedb tries to write to: /nix/store/95vfigaqdg8jg5bk961k1x06j86p5fh0-findutils-4.6.0/var/locatedb.n: Read-only file system this path comes from updatedb shell script which was modified in nix (this line is different in the gnu sources): 186: ${LOCATE_DB=/nix/store/95vfigaqdg8jg5bk961k1x06j86p5fh0-findutils-4.6.0/var/locatedb} systemd service seems to be updating the db: but doesn't have access to some dirs: I'm not surprised it doesn't have access to home, but shouldn't the service be able to list /nix/store files? There are no error messages for /nix/store: the ticket is about service failing to write to /var/cache/locatedb, but it works fine on 16.09, so I think it can be closed.
Code change:
serviceConfig.PrivateNetwork = "yes"; serviceConfig.NoNewPrivileges = "yes"; serviceConfig.ReadOnlyDirectories = "/"; <del> serviceConfig.ReadWriteDirectories = cfg.output; </del> <ins> serviceConfig.ReadWriteDirectories = dirOf cfg.output; </ins> }; systemd.timers.update-locatedb = mkIf cfg.enable

Related discussion:
text: I see two other problems though: update-locatedb service not being able to process /nix/store running updatedb on the cli tries to write to /nix/store which is a read-only file system
is caused by an option, now named , which contains "/nix/store" by default, the issue is closed already. is resolved by merged , the issue can be closed. is about using updatedb from cli and missing /var/cache directory and needs a decision.
Code change:
buildPythonPackage rec { pname = "scs"; <del> version = "3.0.0"; </del> <ins> version = "3.2.3"; </ins> src = fetchFromGitHub { owner = "bodono"; repo = "scs-python"; rev = version; <del> hash = "sha256-7OgqCo21S0FDev8xv6/8iGFXg8naVi93zd8v1f9iaWw="; </del> <ins> hash = "sha256-/5yGvZy3luGQkbYcsb/6TZLYou91lpA3UKONviMVpuM="; </ins> fetchSubmodules = true; };

Related discussion:
text: Project description qpsolvers is python library for solving quadratic programming problems. It contains wrappers for multiple solvers like osqp, cvxopt, quadprog and much more. Metadata homepage URL: source URL: license: LGPLv3 platforms: platform independent (python3.10)
This package wants new version of and new package - . I will try add PR today, but now you can use my NUR repo if you want:
Code change:
}; testScript = '' <ins> import json </ins> def mosquitto_cmd(binary, user, topic, port): return ( "mosquitto_{} "

Related discussion:
text: lists a listener option called that can be used to listen for incoming network connections only on the specified interface. Unfortunately does not accept this option. Steps to reproduce the behavior: This should evaluate cleanly. Incidentally, that assertion message drops the component in the attribute path, it might be nice to fix that.
Code change:
#     https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=956ea65cd707707c0f725930214cbc781367a831 ./bfd-elf-Dont-read-non-existing-secondary-relocs.patch <ins> # Fix building plv8’s v8. # https://github.com/NixOS/nixpkgs/issues/134190 # Obtained from: https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=586e30940e640f67bd55bd72e1d1355a4faf8079 ./gold-Update-GNU_PROPERTY_X86_XXX-macros.patch </ins> ./CVE-2020-35448.patch ] ++ lib.optional stdenv.targetPlatform.isiOS ./support-ios.patch ++ # This patch was suggested by Nick Clifton to fix

Related discussion:
text: The v8 derivation used by plv8 fails to link: cc Using . Hydra job: Maintainer information:
According to it should be fixed by ;a=commit;h=.
Code change:
subversion = common { version = "1.12.2"; sha256 = "0wgpw3kzsiawzqk4y0xgh1z93kllxydgv4lsviim45y5wk4bbl1v"; <ins> extraPatches = [ ./CVE-2020-17525.patch ]; </ins> }; }

Related discussion:
text: , CVSSv3=7.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc Cc
Code change:
description = "A daemon that implements the UPnP Internet Gateway Device (IGD) specification"; platforms = platforms.linux; license = licenses.bsd3; <ins> mainProgram = "miniupnpd"; </ins> }; }

Related discussion:
text: We already have in , but only with iptables support. It would be nice to have the nftables version available as well.
Being worked on in , I'm trying to test myself but couldn't make it to work yet.
I think the PR is ready now, testing welcome!
Maybe add an option for will be better?
Code change:
machine.wait_until_succeeds( "curl --fail -L http://localhost:8080/" ) <ins> _, out = machine.execute("grep SABCTools /var/lib/sabnzbd/logs/sabnzbd.log") machine.log(out) machine.fail("grep 'SABCTools disabled: no correct version found!' /var/lib/sabnzbd/logs/sabnzbd.log") </ins> ''; })

Related discussion:
text: When booting up SABnzbd having done an update recently (5min ago at time of writing), I'm getting the following errors: ! Steps to reproduce the behavior: your on NixOS using current unstable, include the following: . I expected it to pick up SABCtools 7.1.2, but it got 7.0.2 instead. See above N/a
Opened a PR to fix this and provide better testing.
:+1: thanks
Code change:
./thisroot.patch # https://sft.its.cern.ch/jira/browse/ROOT-8728 <del> (fetchpatch { url = "https://sft.its.cern.ch/jira/secure/attachment/20025/0001-std-string_view-has-no-more-to_string.patch"; sha256 = "0ngyk960xfrcsj4vhr1ax8h85fx0g1cfycxi3k35a6ych2zmyg8q"; }) </del> ./ROOT-8728-extra.patch ];

Related discussion:
text: I have a system without Command Line Tools or XCode and nix'es cmake can't find headers and tries to pick up system frameworks. Try to build this: On my system I get: System: Darwin Nix version: nix-env (Nix) 1.11.9 Nixpkgs version: 17.09pre-git () Sandboxing enabled: no
Related to
Code change:
}; nativeBuildInputs = [ <del> pkg-config intltool </del> <ins> pkg-config intltool makeWrapper </ins> ]; buildInputs = [

Related discussion:
text: Since commit the command is missing. It is used by xscreensaver to display text inside the screensavers like system information and kernel versions. It used to be in the package, as can be seen from this diff: The same applies to which was also removed by that commit Steps to reproduce the behavior: Text is printed when running instead of If applicable, add screenshots to help explain your problem. Add any other context about the problem here. system: host os: multi-user?: sandbox: version: channels(root): channels(pinpox): nixpkgs: Maintainer information:
«removed» here means «same lack of special measures as before» (the lines you cite are just fixes for the installed stuff), but upstream underwent a major rewrite. (Not saying that fix is not most welcome, just that this was not a removal as much as lack of finding out what to do now) Apparently the scripts are there in the tarball, maybe they need manual copying now, not sure
I just noticed it seems to work fine in the previewer application that comes with xscreensaver . E.g.: ! The same screensaver does not work though, when it starts "on it's own" after some idle time. The text then only reads Not sure what the difference is.
xscreensaver-text and others are in $out/libexec/xscreensaver btw speeds up the build of xscreensaver by a lot
Hm, is not in my path, but hacks launched via XScreenSaver proper find text just fine. And the daemon source code implies that is indeed to PATH in a normal situation.
Not sure if it's related, but it is also missing commands like and (output is shown in some of the screensavers). I have enabled xsceensaver with the home-manager option
Code change:
description = "The node agent for Tailscale, a mesh VPN built on WireGuard"; license = licenses.bsd3; mainProgram = "tailscale"; <del> maintainers = with maintainers; [ danderson mbaillie twitchyliquid64 jk ]; </del> <ins> maintainers = with maintainers; [ danderson mbaillie twitchyliquid64 jk mfrw ]; </ins> }; }

Related discussion:
text: Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: Current version on the stable/release channel: <!-- 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! --- 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.
You don't need to open an issue if you're going to make a PR right after.
Apologies, my bad. I was not aware :(. I am only 1 day & 1 PR old here.
Code change:
${optionalString (cfg.smtp.passwordFile != null) ''password: "@smtpPassword@",''} domain: "${cfg.smtp.domain}", ${optionalString (cfg.smtp.authentication != null) "authentication: :${cfg.smtp.authentication},"} <del> enable_starttls_auto: ${toString cfg.smtp.enableStartTLSAuto}, </del> <ins> enable_starttls_auto: ${boolToString cfg.smtp.enableStartTLSAuto}, </ins> ca_file: "/etc/ssl/certs/ca-certificates.crt", openssl_verify_mode: '${cfg.smtp.opensslVerifyMode}' }

Related discussion:
text: GitLab service do not start with configuration . TLDR should be used instead of when creating config file. There is an error message in the log: To Reproduce Steps to reproduce the behavior: to Expected behavior GitLab service should be running after switching to new configuration. Additional context The file mentioned in the error: Note the missing value for . The problem seems to be at , generates empty string: Notify maintainers Metadata Maintainer information:
Thank you for reporting this! I've fixed this on master and will backport the fix to 20.03 and 19.09.
Code change:
url = "https://chromium.googlesource.com/chromium/tools/build/+/e77882e0dde52c2ccf33c5570929b75b4a2a2522/recipes/recipe_modules/chromium/resources/clang-format?format=TEXT"; sha256 = "0ic3hn65dimgfhakli1cyf9j3cxcqsf1qib706ihfhmlzxf7256l"; }; <ins> # https://webrtc-review.googlesource.com/c/src/+/255601 webrtcWaylandScreenshareCoredumpFix = fetchurl { # PipeWire capturer: check existence of cursor metadata name = "webrtc-wayland-screenshare-coredump-fix.patch"; url = "https://webrtc-review.googlesource.com/changes/src~255601/revisions/2/patch?download"; hash = "sha256-PHGwEoYhMa+ZL2ner10FwdGUWUxsVr+HWuZOAEugYDY="; }; </ins> # The additional attributes for creating derivations based on the chromium # source tree.

Related discussion:
text: Chromium coredumps on wayland/sway when trying to share a screen. Steps to reproduce the behavior: sway/wayland "" on "share screen" anywhere -Dump A selector for the screen to share should appear According chromium setting: According nixos configuration: Console output when the error occurs: Also this works fine with firefox-wayland and used to work with chromium. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Please run and paste the result.
Could be related to as it also states
Did screen sharing work before / is that crash (segmentation fault) new? And do you know since which version it stopped working? So far screen sharing did never work reliably and there have been frequent regressions: (I've fixed it twice on my test setup but I've given up since then). We might want to close this issue in favor of to keep the discussion in one place.
For me, screenshare works on Chromium v99, and stopped working after update to v100
For me it also worked in the past without issues. This is new and this is chrome core-dumping. This is a different issue. If screen sharing did not work in the past, it just did not work. It did not cause an out of bounds read or crash of the browser. Please don't close this issue.
Sure, we can leave it open. We should mention it in the other issue though (I just did that) for better visibility. Now we need someone with time and motivation to handle this issue (analyzing the issue, searching for upstream issues, etc. and eventually someone needs to submit a fix).
Since this is NixOS and we have the boon of input-reproducibility and a binary cache, could you post: the nixpkgs commit you are on the nix store path of your chromium binary This will make it even easier for others to reproduce. You may also be able to get the stack trace with GDB using , use , make the segfault happen, and use in GDB.
Code change:
url = "https://chromium.googlesource.com/chromium/tools/build/+/e77882e0dde52c2ccf33c5570929b75b4a2a2522/recipes/recipe_modules/chromium/resources/clang-format?format=TEXT"; sha256 = "0ic3hn65dimgfhakli1cyf9j3cxcqsf1qib706ihfhmlzxf7256l"; }; <ins> # https://webrtc-review.googlesource.com/c/src/+/255601 webrtcWaylandScreenshareCoredumpFix = fetchurl { # PipeWire capturer: check existence of cursor metadata name = "webrtc-wayland-screenshare-coredump-fix.patch"; url = "https://webrtc-review.googlesource.com/changes/src~255601/revisions/2/patch?download"; hash = "sha256-PHGwEoYhMa+ZL2ner10FwdGUWUxsVr+HWuZOAEugYDY="; }; </ins> # The additional attributes for creating derivations based on the chromium # source tree.

Related discussion:
text: nixpkgs: /nix/store/07346c7jv5wnwg30r5dvmlgqbk52hinz-chromium-100.0.4896.60/bin/chromium
Regarding gdb: ` How do I get gdb on the actual executable but keep the env vars of the shell script wrapper?
Now edit , replacing like this: Then terminate all chromium instances (to avoid joining existing instances), and run .
Thank you for the detailed instructions!
Looks like it should be fixed in m101
I tried to build chromiumDev(102) or chrimiumBeta (101) - but both failed with errors related to:
This patch may be useful: https://webrtc-
I'm a week old to nix, but trying to figure out a way to patch it. It seems it needs a special flag due to it's location:
building chrome is an undertaking not to be embarked on lightly. you can install the chrome dev or beta channel package. On my up-to-date, flakes-enabled nixos-unstable: The issue seems fixed there. There are builds of chromium upstream here: (under other), but I'm not sure if there is a nix derivation for them.
I've opened for a quick and dirty fix - the code isn't pretty but should do the job (I wish would support Base64 patches or even better: Gerrit and gitiles would support fetching patches using a sane format like basically any other web VCS frontend does...). Anyway, I'll check if the VM test passes (although that patch is so trivial that it should be unnecessary) and can merge the fix tomorrow.
I love the name and thanks a lot for your time & effort!
Code change:
<del> { lib, fetchurl, buildPythonApplication, libjack2, pydbus, pyliblo, pyqt5, which, bash, qt5 }: </del> <ins> { lib, fetchurl, buildPythonApplication, libjack2, pyliblo, pyqt5, which, bash, qt5 }: </ins> buildPythonApplication rec { pname = "raysession"; <del> version = "0.13.1"; </del> <ins> version = "0.14.2"; </ins> src = fetchurl { url = "https://github.com/Houston4444/RaySession/releases/download/v${version}/RaySession-${version}-source.tar.gz"; <del> sha256 = "sha256-iiFRtX43u9BHe7a4ojza7kav+dMW9e05dPi7Gf9d1GM="; </del> <ins> sha256 = "sha256-qEN3zBK/goRLIZaU06XXm8H5yj4Qjj/NH+bkHkjhLaw="; </ins> }; postPatch = ''

Related discussion:
text: Package name: raysession Latest released version: 0.14.2 Current version on the unstable channel: 0.13.1 Current version on the stable/release channel: 0.13.1 Notify maintainers Note for maintainers: Please tag this issue in your PR.
Update PR:
Code change:
gst-plugins = with gst_all; [ gst-plugins-base gst-plugins-good gst-plugins-bad gst-plugins-ugly gst-ffmpeg ]; gtk_modules = [ libcanberra_gtk2 ]; <del> in stdenv.mkDerivation { </del> <ins> in stdenv.mkDerivation { </ins> inherit name; desktopItem = makeDesktopItem { name = browserName; <del> exec = browserName + " %U"; </del> <ins> exec = "${browserName}${nameSuffix} %U"; </ins> inherit icon; comment = ""; <del> desktopName = desktopName; </del> <ins> desktopName = "${desktopName}${nameSuffix}"; </ins> genericName = "Web Browser"; categories = "Application;Network;WebBrowser;"; mimeType = stdenv.lib.concatStringsSep ";" [

Related discussion:
text: When "set as default browser" is clicked from within Firefox, it places a custom .desktop file in , and points to this from in the same directory. This file launches Firefox without the wrapper when it's opened using xdg-open. The result is that if xdg-open is used when no Firefox window exists, it will be opened without environment variables set correctly, and without plugins.
This is a great example why wrappers are error prone.
Is there a easy way to fix this? I don't see one
The easy way is to use a non-absolute path in the .desktop file, i.e. . This also ensures that after an upgrade, the new Firefox will be invoked.
This .desktop file is generated by Firefox when "set as default browser" is clicked - it's not one of nixpkgs's .desktop files. That'd involve a patch (which would have to be kept up to date with each Firefox release).
Right, shouldn't be hard to do.
Testing a patch now...
I can't see the patch anywhere -- did it work?
Chromium .desktop file includes and suffers from the same problem.
This is handled and detected with mimetypes.
Would be really nice to fix this one, any takers?
I think I have solved it for Firefox; as for Chromium — apparently it is non-trivial to test for me (StumpWM, not a DE)
There's still no obvious way to set the default browser that I can find - anyone know what the status is here?
A possibly reasonable option in the case of Firefox would be to disable the default browser check using the preferences file, and write a custom dialog for selecting the default browser in the wrapper itself, a very rough basis being: According to a google, similar should work for Chrome/Chromium, except passing instead of messing with config files. Opinions?
Is there no way to trick firefox into thinking its executable name is the wrapper ?
Yes: but this needs some testing, and it affects many browsers.
I fixed the wrapper to work with (), but we get another issue. When we update firefox, we end up with a different /nix path, which firefox considers as a different browser. If you restart firefox (for example when installing addons) then you get the not-your-default-browser" warning. Investaigating MOZAPPLAUNCHER as solution, but I start to think that may be the most general solution.
Code change:
primeEnabled = syncCfg.enable || reverseSyncCfg.enable || offloadCfg.enable; busIDType = lib.types.strMatching "([[:print:]]+[:@][0-9]{1,3}:[0-9]{1,2}:[0-9])?"; ibtSupport = cfg.open || (nvidia_x11.ibtSupport or false); <del> settingsFormat = pkgs.formats.keyValue {}; in { </del> <ins> settingsFormat = pkgs.formats.keyValue { }; in { </ins> options = { hardware.nvidia = { datacenter.enable = lib.mkEnableOption ''

Related discussion:
text: Package name: Latest released version: 555.42.02 <!-- Search your package here: --- Current version on the unstable channel: 550.78 Current version on the stable/release channel: 545.29.02 <!-- 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! --- 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]: