jiebi/CodeConvo huggingface dataset:
Code change:
in stdenv.mkDerivation rec { pname = "mwprocapture"; <del> subVersion = "4373"; </del> <ins> subVersion = "4390"; </ins> version = "1.3.0.${subVersion}-${kernel.version}"; src = fetchurl { url = "https://www.magewell.com/files/drivers/ProCaptureForLinux_${subVersion}.tar.gz"; <del> sha256 = "sha256-/6q+6CTlgkHOgq1PF8dSPfl/xm/UFczr/AGkac2mXZ8="; </del> <ins> sha256 = "sha256-HOVAR9auc8ulENPLoI0scdCMZoSbDYkTaCLgZoFG7eU="; </ins> }; nativeBuildInputs = kernel.moduleBuildDependencies;

Related discussion:
text: Version V1.3.0.4373 of mwprocapture (the Linux driver for the Magewell Pro Capture family) FTBFS when building against Linux 6.8 or newer. Steps to reproduce the behavior: Add to your Nix configuration. Add to your Nix configuration. Magewell has provided a revised driver update to address this issue. I am working on a pull request for nixpkgs. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Code change:
clang, libbpf, bpftools, <ins> fetchurl, </ins> }: let <del> # Compare with https://github.com/draios/sysdig/blob/0.38.0/cmake/modules/falcosecurity-libs.cmake </del> <ins> # Compare with https://github.com/draios/sysdig/blob/0.38.1/cmake/modules/falcosecurity-libs.cmake </ins> libsRev = "0.17.2"; libsHash = "sha256-BTLXtdU7GjOJReaycHvXkSd2vtybnCn0rTR7OEsvaMQ=";

Related discussion:
text: Steps to reproduce the behavior: sysdig Add any other context about the problem here. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Can't repro on master () and the error isn't in the log output, can you provide additional info?
Hey, thanks for the response - checking again - it only happens if for me if I enable the sysdig-option in my config not building the sysdig-package - maybe this helps to reproduce and depends on the used kernel-version? I've uploaded the full build log:
Thanks, seems this is the error:
I guess this is already fixed upstream in the drivers () but needs to be to nixpkgs to fix 6.10-kernel builds.
fixes it for me
~Ah 0.38.1 - got released somehow oversaw it should check first if that includes the fix~ 38.1 does not include a driver-bump
Code change:
, pymongo , pytestCheckHook , python <del> , pythonAtLeast </del> , python-dateutil <ins> , pythonAtLeast , pythonRelaxDepsHook </ins> , pytz , pyyaml , requests , requests-mock <ins> , scikit-learn </ins> , setuptools , sqlalchemy , tenacity <del> , typing-extensions </del> , testcontainers <del> , scikit-learn }: </del> <ins> , typing-extensions }: </ins> buildPythonPackage rec { pname = "apache-beam";

Related discussion:
text: Build of failed on x86_64-linux as of . This is currently breaking . python39Packages.tensorflow-datasets maintainers cc: maintainers cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tags:
Code change:
"--set LOCALE_ARCHIVE ${glibcLocales}/lib/locale/locale-archive" ]; <ins> # mixxx installs udev rules to DATADIR instead of SYSCONFDIR # let's disable this and install udev rules manually via postInstall # see https://github.com/mixxxdj/mixxx/blob/2.3.0/CMakeLists.txt#L1381-L1392 cmakeFlags = [ "-DINSTALL_USER_UDEV_RULES=OFF" ]; postInstall = lib.optionalString stdenv.isLinux '' rules="$src/res/linux/mixxx-usb-uaccess.rules" if [ ! -f "$rules" ]; then echo "$rules is missing, must update the Nix file." exit 1 fi mkdir -p "$out/lib/udev/rules.d" cp "$rules" "$out/lib/udev/rules.d/69-mixxx-usb-uaccess.rules" ''; </ins> meta = with lib; { homepage = "https://mixxx.org"; description = "Digital DJ mixing software";

Related discussion:
text: Describe the bug When adding to the NixOS configuration the udev rules do not get installed. To Reproduce Steps to reproduce the behavior: mixxx with a DJ controller plugged in. controller is not recognized by mixxx Expected behavior The udev rules are in the correct folder i.e. or and therefore the udev service does not recognizes them. Additional context The fix in worked for me after a little modification (the rules file got renamed). Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
Originally, mixxx did the right thing = install udev files to - see Later they changed the behaviour and they install to - see Sigh.
Code change:
<del> [ "de_DE" , "fr_FR" , "ro_RO" ] </del> <ins> { "de_DE": "gpl2Plus" , "fr_FR": "gpl2Plus" , "ro_RO": "gpl2Plus" } </ins>

Related discussion:
text: The package with that are automatically fetched carry no license. ` cc
Poking upstream does not seem to yield anything. They did indicate they wouldn't support this use case, so what are you expecting from them?
I talked to the authors of wp4nix and they are happy for new contributions. It would be nice if the wp4nix script would somehow handle license informations, for example by manually defining them. Not quite sure yet how to implement it
If we don't know the licenses to these packages we honestly cannot keep them around. For example, it is absolutely unclear, whether we have a license to even redistribute them. Of course upstream will take patches, but they're not exactly in the same boat we are. I think your attitude towards the whole licensing situation around wp4nix/nc4nix and its resulting packages is alarming.
As written : Fixing this for Wordpress packages and themes (wp4nix) and Nextcloud apps (nc4nix) in a foreseeable time exceeds my skills and competence. Therefore I would like to offer to add a flag to these package sets and remove them for the next release 23.11 if it's not resolved by then.
Couldn't we mark them as unfree so they don't get cached on hydra but people can still use them if they want? Unfortunately it seems like the wordpress plugins repository doesn't seem to provide the license information in an easy manner. And I don't know whether it is stored somewhere else or can even be extracted from the derivation without import-from-derivation.
Actuallly we seem to be safe in theory. claims
In an ideal world, that would hold true, but it is up to the user and distributor to validate the final outcome. I therefore think this situation remains unresolved.
Code change:
sed -i '/TestDisasmExtld/areturn' src/cmd/objdump/objdump_test.go <ins> sed -i 's/unrecognized/unknown/' src/cmd/link/internal/ld/lib.go sed -i 's/unrecognized/unknown/' src/cmd/go/build.go </ins> touch $TMPDIR/group $TMPDIR/hosts $TMPDIR/passwd sed -i '1 aexit 0' misc/cgo/errors/test.bash

Related discussion:
text: System: (macOS 10.11.6) Nix version: nix-env (Nix) 1.11.2 Nixpkgs version: 16.09pre-git
may fix this problem for you, though you may also wind up needing something like to get a functional set of go commands on darwin.
Code change:
mkdir build pushd build <del> cmake -G "Unix Makefiles" . ../third_party/ycmd/cpp -DPYTHON_LIBRARIES:PATH=${python}/lib/libpython2.7.so -DPYTHON_INCLUDE_DIR:PATH=${python}/include/python2.7 -DUSE_CLANG_COMPLETER=ON -DUSE_SYSTEM_LIBCLANG=ON </del> <ins> cmake -G "Unix Makefiles" . ../third_party/ycmd/cpp -DPYTHON_LIBRARIES:PATH=${python}/lib/libpython2.7.so -DPYTHON_INCLUDE_DIR:PATH=${python}/include/python2.7 -DUSE_CLANG_COMPLETER=ON  $EXTRA_CMAKE_ARGS </ins> make ycm_core -j''${NIX_BUILD_CORES} -l''${NIX_BUILD_CORES}} <del> ${python}/bin/python ../third_party/ycmd/build.py --gocode-completer --clang-completer --system-libclang </del> <ins> ${python}/bin/python ../third_party/ycmd/build.py --gocode-completer --clang-completer </ins> popd '';

Related discussion:
text: Building on Darwin fails. The problem seems very similar to which was solved by —however I do not know how to apply that solution here.
Wasn't this fixed by merging
This issue is fixed, but it broke again recently. Same issue as but we use
Proposed
Fixed by
Code change:
c64-debugger = callPackage ../applications/emulators/c64-debugger { }; <ins> cameractrls-gtk4 = cameractrls.override { withGtk = 4; }; cameractrls-gtk3 = cameractrls.override { withGtk = 3; }; </ins> camunda-modeler = callPackage ../applications/misc/camunda-modeler { }; checkpointBuildTools = callPackage ../build-support/checkpoint-build.nix {};

Related discussion:
text: Project description cameractrls is a UI for v4l camera settings, like pan/tilt/... on fancy Logitech cameras. Metadata homepage URL: source URL: license: MIT platforms: Linux
Here's a prototype:
I'm using this successfully with the latest version,
Is there any progress with this request?
Please test my PR I don't have the device.
Tbh, I would like to, but I don't know how to test a custom package...
For new CLI: Or
I executed and then nothing happened... I can also not find cameractrls
Check your current directory, there's a symlink to store, and the executable is in
I only tested the gui app and it seems to work fine!
Thanks! What about the others executables? Have you tested all the functionality of the app?
I can only test the the GUI, because I don't know how to use the CLI program. But the GUI is working fine, afaict.
Code change:
type = types.str; default = poolName; description = '' <del> Name of the phpfpm pool to use and setup. If not specified, a pool will be created </del> <ins> Name of the php-fpm pool to use and setup. If not specified, a pool will be created </ins> with default values. ''; };

Related discussion:
text: When enabling freshrss and rebuilding, no freshrss systemd service is started. Steps to reproduce the behavior: (as well other requirements for minimal config) (with , for me) The only freshrss units are and . to in browser. Unable to connect. A service with (or something?) is created and runs automatically. The http server is accessible from a browser. I initially tried running in a container, but running on the host OS had the same result Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Freshrss doesn't run as a systemd service. It runs under php-fpm. The associated systemd service is . This is then exposed via nginx. I believe the default nginx configuration will expose freshrss on port 80, so http://localhost may work for your current configuration. The used by nginx for freshrss is . My guess is you'll need to configure it. If you want to access freshrss via "http://localhost:8080" you could use a config like:
Sorry I never responded to this! This worked, thank you.
i guess we can close this then? please report back if i am wrong.
I do agree with qyriad that this could be explicitly documented better, but I don't have any further issue to specifically track
any specific location where you want this documented? where would you look something like this up?
I would probably put in the description of the option.
Code change:
''; }; }; specialisation.dns-01.configuration = {pkgs, config, nodes, lib, ...}: { security.acme.certs."example.test" = { domain = "*.example.test";

Related discussion:
text: I use enabled. I also have a web server service that specifies: Because my web server is a bit long to start, the timeout and its systemd unit fails. To Reproduce Use the following example module: Expected behavior The acme systemd units created by  should wait that nginx is started before starting. Metadata Maintainer information:
Should adding to what is already to  fix the issue?
Making a note that has the same code and presumably the same issue so any fix on should likely be ported to .
Thank you for the issue and reproducer. I'll have a closer look at this today
what exactly do you mean by "timeout" here by the way. could you provide some journal logs of this failure? I can try reproduce when I'm home, but maybe the logs are enough to understand what is going wrong
I mean "Timeout during connect (likely firewall problem)" in the logs below. Note that the hostname, email and domain have been redacted. Also notice the long time between and . nginx was not started when the Let's Encrypt tried to retrieve the challenge:
I'm scared that won't work. The lack of here is very deliberate pulls in (Through and ) to create fake certs, as nginx crashes hard when certificate paths aren't present. We want to start up before the acme challenge is initiated, as nginx is responsible for serving the director to complete it. If starts before nginx, it will always fail. It's all a bit mind-boggling and the dependencies are a bit complicated. I wish it was a bit more simpler too. However; isn't what we want here instead? We want to guarentee that is running before the certificate request is fired off. So adding a to might work? I'll see if that fixes it..
Absolutely, that is what I meant but I wrote it wrongly.
Should we go for the solution proposed?
Yep. I have a PR in the works on my machine. I'll try to get it out this week
Code change:
maintainers = with maintainers; [ goibhniu gilligan cko marsam ]; platforms = platforms.linux ++ platforms.darwin; mainProgram = "node"; <del> knownVulnerabilities = optional (versionOlder version "12") "This NodeJS release has reached its end of life. See https://nodejs.org/en/about/releases/."; </del> <ins> knownVulnerabilities = optional (versionOlder version "14") "This NodeJS release has reached its end of life. See https://nodejs.org/en/about/releases/."; </ins> }; passthru.python = python; # to ensure nodeEnv uses the same version

Related discussion:
text: The NodeJS 12 release goes end-of-life on 2022-04-30, which needs handling before the next release. Worst case we update like in .
Code change:
destination = mkOption { type = types.str; example = "10.0.0.1:80"; <del> description = "Forward tcp connection to destination ip:port"; </del> <ins> description = "Forward connection to destination ip:port"; }; proto = mkOption { type = types.str; default = "tcp"; example = "udp"; description = "Protocol of forwarded connection"; </ins> }; }; }); default = []; <del> example = [ { sourcePort = 8080; destination = "10.0.0.1:80"; } ]; </del> <ins> example = [ { sourcePort = 8080; destination = "10.0.0.1:80"; proto = "tcp"; } ]; </ins> description = '' List of forwarded ports from the external interface to

Related discussion:
text: Should there be an ability to specify UDP port forwarding in the nat module? It would necessitate an extra property in the forwarding list specification, like .
Has done this!
Code change:
seexpr = callPackage ../development/compilers/seexpr { }; <ins> selectdefaultapplication = libsForQt5.callPackage ../applications/misc/selectdefaultapplication { }; </ins> semgrep = python3.pkgs.callPackage ../tools/security/semgrep { }; semgrep-core = callPackage ../tools/security/semgrep/semgrep-core.nix { };

Related discussion:
text: Project description  Selectdefaultapplication is a very simple GUI application that lets you define default applications on Linux in a sane way. Basically it just loads all installed applications by reading their .desktop files, reads the MimeType fields to see what it supports, and updates with what the user wants. Not all desktop environments provide such a tool, prompting for an agnostic tool. Metadata homepage URL: source URL: license: gpl2 platforms: linux Additional info: AUR package:
You can try using this in an overlay, use .
Seems to work!
Code change:
libwnck sassc udisks2 <ins> libX11 libXext libXNVCtrl </ins> ]; <ins> # Force link against Xext, otherwise build fails with: # ld: /nix/store/...-libXNVCtrl-495.46/lib/libXNVCtrl.a(NVCtrl.o): undefined reference to symbol 'XextAddDisplay' # ld: /nix/store/...-libXext-1.3.4/lib/libXext.so.6: error adding symbols: DSO missing from command line # https://github.com/stsdc/monitor/issues/292 NIX_LDFLAGS = "-lXext"; mesonFlags = [ "-Dindicator-wingpanel=enabled" ]; </ins> postPatch = '' chmod +x meson/post_install.py patchShebangs meson/post_install.py

Related discussion:
text: <!-- 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: <!-- 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: desired version: <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: are you already working on it? if not i can do it
I have some exams to take tomorrow, so maybe I cannot open a PR in 17 hours. Feel free to open one if you have done the update.
I just wanted to make sure you haven't started to work on it, so we don't do duplicate work. I wish you great success with the exams!
Just also have a try on this, fails with . Actually I have no idea what happened so I just opened , downstream workaround should be something like , actually this seems to work, builds and launches. <img src="https://user-" width=50%Also I noticed that we maybe need in , haven't tested yet.
downstream workaround should be something like , actually this seems to work, builds and launches. i don't understand what it does, but it works Also I noticed that we maybe need in , haven't tested yet. I noticed before that the indicators do not work. I'll try it.
Code change:
options = { services.flatpak = { enable = mkEnableOption "flatpak"; <del> extraPortals = mkOption { type = types.listOf types.package; default = []; description = '' List of additional portals to add to path. Portals allow interaction with system, like choosing files or taking screenshots. At minimum, a desktop portal implementation should be listed. GNOME already adds <package>xdg-desktop-portal-gtk</package>; for KDE, there is <package>xdg-desktop-portal-kde</package>. Other desktop environments will probably want to do the same. ''; }; </del> }; }; ###### implementation config = mkIf cfg.enable { environment.systemPackages = [ pkgs.flatpak ]; <del> services.dbus.packages = [ pkgs.flatpak pkgs.xdg-desktop-portal ] ++ cfg.extraPortals; </del> <ins> services.dbus.packages = [ pkgs.flatpak ]; </ins> <del> systemd.packages = [ pkgs.flatpak pkgs.xdg-desktop-portal ] ++ cfg.extraPortals; </del> <ins> systemd.packages = [ pkgs.flatpak ]; </ins> environment.profiles = [ "$HOME/.local/share/flatpak/exports" "/var/lib/flatpak/exports" ]; <del> environment.variables = { XDG_DESKTOP_PORTAL_PATH = map (p: "${p}/share/xdg-desktop-portal/portals") cfg.extraPortals; }; </del> }; }

Related discussion:
text: It is possible to use Plasma’s native file dialogues in Firefox 64 to open or save a file. Currently this feature is not working in NixOS, and it seems to me some small changes would need to be made to derivation in order to enable it. I propose we include this option together with as a Firefox option in NixOS (see also: ). I followed the explanation on how to enable this feature as it was published on : Firefox (64 is current stable) from a terminal emulator But it produces the following error: system: host os: multi-user?: sandbox: version: channels(root): channels(hook): nixpkgs:
You'll probably have to do something like this to expose the dbus service:
Where? In:
It needs to go into a nixos module or your .
Code change:
# Misc. stuff. "pcips2" "atkbd" <ins> # Temporary fix for https://github.com/NixOS/nixpkgs/issues/18451 # Remove as soon as upstream gets fixed - marking it: # TODO # FIXME "i8042" </ins> # To wait for SCSI devices to appear. "scsi_wait_scan"

Related discussion:
text: Linux Kernel 4.7.3 seems broken, as my laptops keyboard doesn't work. experienced by the arch community too: update, reboot - 4.6 and 4.7.2 work, 4.7.3 doesn't nixos-version: (Gorilla) nix-env --version: nix-env (Nix) 1.11.4 nix-instantiate --eval github/nixpkgs -A lib.nixpkgsVersion: ""
Same issue with kernel 4.4.20 (lts). I can no longer enter my cryptsetup password. The reason is that i8042 is no longer integrated in initramfs, I suppose because of: Update: To fix this issue I had to add it to
Thanks, created a quick fix with your solution, which should fix it for everyone
Code change:
which wrapGAppsHook ] <ins> ++ lib.optionals crashreporterSupport [ dump_syms ] </ins> ++ lib.optionals pgoSupport [ xvfb-run ] ++ extraNativeBuildInputs;

Related discussion:
text: Steps to reproduce the behavior: librewolf from nixpkgs master Add any other context about the problem here. Please run and paste the result.
I have the exact same issue but my machine is a little slower :|. Also this means (not just Git ) is now broken.
I also reproduced this on master.
I think it's related to . I'm guessing the crash reporter symbols aren't generated because we disable the crash reporter. Running some tests to confirm.
is the first broken commit on master.
I'm going to close this. The PR by fixes the problem.
Code change:
sha256 = "1cidki3av9wnkgwi7fklxbg3bh6kysf8w3fk2qadjr05a92mx3zp"; }; <del> patchPhase = '' patchShebangs ./src/shaders/gpp.py ''; preConfigure = '' sed -i -e "s,LIBVA_DRIVERS_PATH=.*,LIBVA_DRIVERS_PATH=$out/lib/dri," configure ''; </del> <ins> # Set the correct install path: LIBVA_DRIVERS_PATH = "${placeholder "out"}/lib/dri"; </ins> postInstall = stdenv.lib.optionalString enableHybridCodec '' ln -s ${vaapi-intel-hybrid}/lib/dri/* $out/lib/dri/ ''; configureFlags = [ <del> "--enable-drm" </del> "--enable-x11" "--enable-wayland" ] ++ stdenv.lib.optional enableHybridCodec "--enable-hybrid-codec"; <del> nativeBuildInputs = [ autoreconfHook gnum4 pkgconfig python2 ]; </del> <ins> nativeBuildInputs = [ autoreconfHook gnum4 pkg-config python3 ]; </ins> buildInputs = [ intel-gpu-tools libdrm libva libX11 libXext libGL wayland ] ++ stdenv.lib.optional enableHybridCodec vaapi-intel-hybrid;

Related discussion:
text: Describe the bug Upstream intel-vaapi-driver removed the --enable-drm ./configure option. It is now turned on by default. Happened in commit To Reproduce Steps to reproduce the behavior: the package and read through compile log Additional context This is a warning, package builds just fine despite this. Metadata Please run and paste the result. Maintainer information: (I don't know if I am dealing with attribute or module. I think attribute, but just to cover all bases.)
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . 3. Ask on the on .
Code change:
(mkRenamedOptionModule [ "networking" "dnsExtensionMechanism" ] [ "networking" "resolvconf" "dnsExtensionMechanism" ]) (mkRenamedOptionModule [ "networking" "extraResolvconfConf" ] [ "networking" "resolvconf" "extraConfig" ]) (mkRenamedOptionModule [ "networking" "resolvconfOptions" ] [ "networking" "resolvconf" "extraOptions" ]) <ins> (mkRemovedOptionModule [ "networking" "resolvconf" "useHostResolvConf" ] "This option was never used for anything anyways") </ins> ]; options = {

Related discussion:
text: Describe the bug seems to be unused in NixOS. Instead it seems to be a duplicate of . When greping for the option, only references of the later are found. Metadata Maintainer information:
This issue has been mentioned on NixOS Discourse. There might be relevant details there: