jiebi/CodeConvo huggingface dataset:
Change:
owner = "gajim"; repo = "python-nbxmpp"; rev = "nbxmpp-${version}"; <del> sha256 = "0gzyd25sja7n49f1ihyg6gch1b0r409r0p3qpwn8w8xy7jgn6ysc"; </del> <ins> sha256 = "1c2ncx1k93gxndaw183x0vlqgjnippl3v6sknklj3z2yjcj0l1ks"; </ins> }; buildInputs = [

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: gajim <!-- 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: 1.3.2 desired version: 1.3.3 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.
Change:
owner = "systemd"; repo = "systemd-stable"; rev = "v${version}"; <del> sha256 = "sha256-Sa5diyNFyYtREo1xSCcufAW83ZZGZvueoDVuQ2r8wno="; </del> <ins> sha256 = "sha256-kao0xJwwJc4zUyaK5yxyGip4E6ADak98iVv5E8Hw0zk="; </ins> }; # On major changes, or when otherwise required, you *must* reformat the patches,

Discussion:
Hi, I'm finally able to build and compile my haskell project. But I got the following error: is there any way to know how to add to my program? is it in or else? build using webkitgtk-2.4.11 System: (MacOs) Nix version: (run ) Nixpkgs version: (17.09pre-git)
You're going to have to create an ) . The basic structure is: is tricky, but you can find some examples looking in /Applications/. Here is the source from .
hi, yeah i see it when my app build like this: After i manage to build it. However, there is no dist/build/frontend, so i recreated it once again, but still I cannot run and got the following report: So do I need to create the manually every time I finish my compilation ?
Could you provide your current setup? The issue is probably in your build files.
Can we close this due to inactivity?
Change:
cargoHash = "sha256-1WjZbmZFPB1+QYpjqq5Y+fDkMZNmWJYIxmMFWg7Tiac="; <del> nativeBuildInputs = [ pkg-config makeBinaryWrapper ]; </del> <ins> nativeBuildInputs = [ pkg-config ]; </ins> buildInputs = [ icu fontconfig harfbuzz openssl ] ++ lib.optionals stdenv.isDarwin (with darwin.apple_sdk.frameworks; [ ApplicationServices Cocoa Foundation ]);

Discussion:
Describe the bug Reproduction  Expected behavior No errors Notify maintainers Metadata Maintainer information:
The version of biber that we ship corresponds to . ships with texlive 2018 (tectonic-typesetting/tectonic-staging). And doesn't yet have a builtin solution for biber tectonic-typesetting/tectonic. You can try overriding biber to version 2.11, which should be compatible. cc as maintainer of
I would also appreciate a fix for this. I tried overriding to version 2.11, but that didn't help (similar version incompatibility), at least not on the current unstable channel or on 20.03 to match with the date of message. The version in the current derivation seems to be 3.3, which dates back to 2016, so it looks like updating would make more sense.
I marked this as stale due to inactivity. &rarr;
I've just encountered this issue too.
Which version of nixpkgs are you using? What is the output of:
Currently biber expects while nixpkgs (as well as texlive) contains . For me the override suggested in works with no issue; e.g. with home-manager: Although this works on my end, I hope this could be upstreamed to nixpkgs itself so that we can make use of the hydra cache with no need to locally rebuild tectonic; cc maintainers: Thank you very much!
Tectonic is tracking this issue in . In general, we sort of rely on Tectonic's bundles to follow texlive releases. That's why we don't embed such hardcoding of the version in Tectonic - since Tectonic could update it's bundle without an update to Tectonic itself, which could fix such an issue if it arises after a Tectonic release. Perhaps also the following Tectonic nixpkgs update will help:
Indeed... Is it then possible to create some package without the dependency, so that we can install the appropriate versions of and separately, without the need to recompile the package? :thinking: Thanks!
You have a point. I was the one who introduced the wrapping of with in ... I tend to think now that it shouldn't be that way, especially with this frequent issue of incompatibility. I pushed that as well to .

Wow nice! Thank you very much!
I have hence created a wrapper so that one can combine the two into a single package, where the -specific biber is renamed to prevent conflict with the texlive biber: I am far from proficient in nix, so the package is created following along with the previous revision of . It can be used e.g. as an override: I don't know whether it's good to upstream this or not. In any case, I think it may be useful to others like me, so it would be good to share this here haha.
Update: I am now trying to upstream a more polished solution via . would you be interested in a review? :pleading_face: The PR will close this issue.
Change:
}; mysql = { <del> configureFlags = throw "MySQL support in PHP is broken! (See https://github.com/NixOS/nixpkgs/issues/14351.)"; #["--with-mysql=${mysql.lib}"]; </del> <ins> configureFlags = ["--with-mysql=${mysql.lib}"]; </ins> buildInputs = [ mysql.lib ]; };

Discussion:
After upgrading my nixpkgs from the branch to the branch my wordpress enabled apache server crashes with the following error message: Line 68 of :
I thought the error was caused because can't be found in the RPATH of so I tried patching the RPATH using: but that still causes the error: I'm confused about this error message because seems to be in : What's the best way to debug this?
This will be fixed once is merged into .
Change:
config = { _module.args = { <del> pkgs = finalPkgs; </del> <ins> pkgs = finalPkgs.__splicedPackages; </ins> }; assertions = [

Discussion:
Derivations defined with pkgs are not compatible with cross compilation as defined in Nixpkgs manual. This is the case for all derivation defined in NixOS modules. Following derivation fails to build, since pkgs is used: Following dervation builds, since splicedPackages is used: The NixOS module system uses not splicedPackages and therefor all derivations defined with pkgs which depends on nativeBuildInputs will fail to cross compile. Select the package by hand and do not use stdenv cross compilation automatism: Derivations defined in NixOS modules can be cross compiled.
for splicing to work has to be used the following works
That's true, but not all parts in nixos uses and I did not expect this behavior. I created a PR to fix this issue.
(linking a related issue )
Change:
<del> { lib, stdenv, fetchurl }: </del> <ins> { lib, stdenv, fetchFromGitHub, pkg-config, gengetopt, m4, gnupg , git, perl, autoconf, automake, help2man, boehmgc }: </ins> stdenv.mkDerivation rec { pname = "mmv"; <del> version = "1.01b"; src = fetchurl { url = "mirror://debian/pool/main/m/mmv/mmv_${version}.orig.tar.gz"; sha256 = "0399c027ea1e51fd607266c1e33573866d4db89f64a74be8b4a1d2d1ff1fdeef"; </del> <ins> version = "2.0"; src = fetchFromGitHub { owner = "rrthomas"; repo = "mmv"; rev = "v${version}"; sha256 = "sha256-MmxDk3PBtvK/thrh6x67M+nMdCDlOQQHkREqLmzF2Mk="; fetchSubmodules = true; </ins> }; <del> hardeningDisable = [ "format" ]; patches = [ # Use Debian patched version, as upstream is no longer maintained and it # contains a _lot_ of fixes. (fetchurl { url = "mirror://debian/pool/main/m/mmv/mmv_${version}-15.diff.gz"; sha256 = "9ad3e3d47510f816b4a18bae04ea75913588eec92248182f85dd09bc5ad2df13"; }) ]; postPatch = '' sed -i  -e 's/^s*LDFLAGSs*=s*-ss*-N/LDFLAGS = -s/'  -e "s|/usr/bin|$out/bin|"  -e "s|/usr/man|$out/share/man|"  Makefile </del> <ins> preConfigure = '' ./bootstrap </ins> ''; <del> preInstall = '' mkdir -p "$out/bin" "$out/share/man/man1" ''; postInstall = '' for variant in mcp mad mln do ln -s mmv "$out/bin/$variant" ln -s mmv.1 "$out/share/man/man1/$variant.1" done ''; </del> <ins> nativeBuildInputs = [ gengetopt m4 git gnupg perl autoconf automake help2man pkg-config ]; buildInputs = [ boehmgc ]; </ins> meta = { <del> homepage = "http://linux.maruhn.com/sec/mmv.html"; </del> <ins> homepage = "https://github.com/rrthomas/mmv"; </ins> description = "Utility for wildcard renaming, copying, etc"; <del> license = lib.licenses.gpl2; platforms = lib.platforms.linux; </del> <ins> license = lib.licenses.gpl3Plus; platforms = lib.platforms.all; maintainers = with lib.maintainers; [ siraben ]; </ins> }; }

Discussion:
New upstream at Additionally, platforms should be changed to . <!-- 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: <!-- 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: 1.01b desired version: v2.0rc3 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.
Change:
inherit (darwin.apple_sdk.frameworks) Security; }; <ins> rustdesk-server = callPackage ../servers/rustdesk-server { }; </ins> rustypaste = callPackage ../servers/rustypaste { }; rustypaste-cli = callPackage ../tools/misc/rustypaste-cli { };

Discussion:
Self hosting server for Rust Desk remote desktop the rustdesk client app is available, but it would be great to be able to self-host. Metadata homepage URL: source URL: license: GNU AFFERO GENERAL PUBLIC LICENSE platforms: linux, windows, mac, android, ios
Wow, that was speedy. Thanks!
Change:
<ins> { lib , buildPythonPackage , fetchFromGitHub , pytestCheckHook , aiohttp , codecov , flake8 , pytest , pytest-asyncio , pytest-cov }: buildPythonPackage rec { pname = "throttler"; version = "1.2.2"; src = fetchFromGitHub { owner = "uburuntu"; repo = pname; rev = "refs/tags/v${version}"; hash = "sha256-fE35zPjBUn4e1VRkkIUMtYJ/+LbnUxnxyfnU+UEPwr4="; }; checkInputs = [ aiohttp codecov flake8 pytest pytest-asyncio pytest-cov pytestCheckHook ]; pytestFlagsArray = [ "tests/" ]; meta = with lib; { description = "Zero-dependency Python package for easy throttling with asyncio support."; homepage = "https://github.com/uburuntu/throttler"; license = licenses.mit; maintainers = with maintainers; [ renatoGarcia ]; }; } </ins>

Discussion:
A clear and concise description of what the bug is. Steps to reproduce the behavior: a simple Snakefile such as shown below command fails with (truncated) exception message as shown below The command does not fail with an exception This is a known issue that has been fixed in the recent versions of Snakemake Please run and paste the result.
Change:
rustPlatform.buildRustPackage rec { pname = "sudo-rs"; <del> version = "0.2.0"; </del> <ins> version = "0.2.1"; </ins> src = fetchFromGitHub { owner = "memorysafety"; repo = "sudo-rs"; rev = "v${version}"; <del> hash = "sha256-Kk5D3387hdl6eGWTSV003r+XajuDh6YgHuqYlj9NnaQ="; </del> <ins> hash = "sha256-EQEdNDUXEMMiFZKuu9LR9ywjvKWyM5bWcRHHUB9+gp4="; </ins> }; <del> cargoHash = "sha256-yeMK37tOgJcs9pW3IclpR5WMXx0gMDJ2wcmInxJYbQ8="; </del> <ins> cargoHash = "sha256-Zs9/A7u4yMLKY4cAUCnsqRHgkxI8R3w1JwkAd2lw0eo="; </ins> nativeBuildInputs = [ installShellFiles pandoc ]; buildInputs = [ pam ]; <del> patches = [ (fetchpatch { # @R-VdP's patch to work with NixOS' suid wrappers name = "Skip self_check when executed as root.patch"; url = "https://github.com/R-VdP/sudo-rs/commit/a44541dcb36b94f938daaed66b3ff06cfc1c2b40.patch"; hash = "sha256-PdmOqp/NDjFy8ve4jEOi58e0N9xUnaVKioQwdC5Jf1U="; }) ]; </del> # Don't attempt to generate the docs in a (pan)Docker container postPatch = '' substituteInPlace util/generate-docs.sh 

Discussion:
Package name: sudo-rs Latest released version: 0.2.1 <!-- Search your package here: --- Current version on the unstable channel: 0.2.0 Current version on the stable/release channel: N/A <!-- 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.
Change:
config = mkIf config.hardware.parallels.enable { services.xserver = { drivers = singleton <del> { name = "prlvideo"; modules = [ prl-tools ]; libPath = [ prl-tools ]; }; </del> <ins> { name = "prlvideo"; modules = [ prl-tools ]; }; </ins> screenSection = '' Option "NoMTRR"

Discussion:
Proposal: Make a mesa setup-hook: find opengl programs in $out, fix rpath to point to (or ). Drop .
I'm not certain about all the consequences. It isn't just &ndash; there can also be other required things on that path, e.g. and . But I guess the packages that stop finding libs should be fixable easily by adding the reference explicitly somehow. What might also be a problem: during chrooted builds we have no , so if mesa is removed_ from rpath, I think many executables wouldn't even start due to that dependency, e.g. through libcairo. That would be worked around if we only at the beginning of rpath without removing the mesa reference.
Will this affect people using Nixpkgs outside NixOS?
it should be the same, need for creating manually, or setting another proper . The behavior should be the same as of now, except we don't need which would apply to every binary.
Closely related: there might be a change how libGL implementations are switched. So far only nvidia is known to use that interface, but it's well possible the other major players will jump in soon.
(triage) any action items?
No, just brainstorming here.
(triage) I assume this hasn’t been implemented yet?
There's , which will set RUNPATH in various dispatch libraries to look in , and I suggested dropping the global there, too.
Once I remove from , when I log in via LightDM (as supposed to SDDM or a console login), I still get this in : . Note how there's no 32-bit link and there is also the absolute path to the driver directory (which in my case does nothing because libraries are under ). I'm pretty sure it's coming from . SDDM must be unsetting it while LightDM is letting it through to the user session. We should remove this so it doesn't affect the session, and fix things as necessary by adding RUNPATH to programs that need it (X server, individual display managers, wayland stuff?). I will try with NVidia but cannot try other drivers.
I see two drivers that still rely on to override default system libraries, and .

Not only do they directly provide libraries like , , and instead of using dispatch libraries (, ), they override other system libraries: has symlinks to NixOS builds of a whole bunch of Xorg libraries (e.g. , , ). There is a comment in the package saying it makes some programs work, without explaining why. has replacements of , , and some LLVM libraries (, ). Because NixOS has patched glibc to give priority over , any program that links to one of these libraries will load the one from the AMD drivers. This can result in horrible breakage (what happens to programs that link to LLVM when they get the AMD thing?). This is so ugly and prone to break things that I think we should consider dropping both drivers. If not then we should at least go forward with dropping only for drivers that don't need it (mesa, nvidia).
Change:
<ins> { lib, stdenv, buildGoModule, fetchFromGitHub, testers, kluctl }: buildGoModule rec { pname = "kluctl"; version = "2.16.0"; src = fetchFromGitHub { owner = "kluctl"; repo = "kluctl"; rev = "v${version}"; hash = "sha256-NwjPClD3P9EP7gKPPgKXI3h+kLeGPd7Gf6gZXMCCLHk="; }; vendorHash = "sha256-IC+sjctDqd0lQD5labl+UYWsRiptQKSjSHYf2SGkp14="; ldflags = [ "-s" "-w" "-X main.version=v${version}" ]; # Depends on docker doCheck = false; passthru.tests.version = testers.testVersion { package = kluctl; version = "v${version}"; }; meta = with lib; { description = "The missing glue to put together large Kubernetes deployments"; homepage = "https://kluctl.io/"; license = licenses.asl20; maintainers = with maintainers; [ sikmir ]; }; } </ins>

Discussion:
Project description Kluctl is a tool to declare and manage Kubernetes deployments (comparable to Helm, but a lot lighter). Metadata homepage URL: source URL: license: Apache-2.0 platforms: Linux, Darwin, Windows (arm64+amd64 except for Windows which is only amd64)
Change:
inherit lib pkgs stdenv; inherit (python.passthru) isPy27 isPy37 isPy38 isPy39 isPy310 isPy311 isPy3k isPyPy pythonAtLeast pythonOlder; inherit buildPythonPackage buildPythonApplication; <del> inherit (pkgs) fetchPypi; </del> inherit hasPythonModule requiredPythonModules makePythonPath disabled disabledIf; inherit toPythonModule toPythonApplication; inherit buildSetupcfg;

Discussion:
Since , was moved to top level, and and are aliases of from the top level To find the usages of these aliases, you can search for in the repository Note that there are false positives (e.g. when used in overlays) and this also might not include all usages (let inherit)
Change:
<ins> { config, lib, pkgs, ... }: let cfg = config.programs.kde-pim; in { options.programs.kde-pim = { enable = lib.mkEnableOption "KDE PIM base packages"; kmail = lib.mkEnableOption "KMail"; kontact = lib.mkEnableOption "Kontact"; merkuro = lib.mkEnableOption "Merkuro"; }; config = lib.mkIf cfg.enable { environment.systemPackages = with pkgs.kdePackages; [ # core packages akonadi kdepim-runtime ] ++ lib.optionals cfg.kmail [ akonadiconsole akonadi-search kmail kmail-account-wizard ] ++ lib.optionals cfg.kontact [ kontact ] ++ lib.optionals cfg.merkuro [ merkuro ]; }; } </ins>

Discussion:
There is currently no documentation, on how to combine the different PIM libraries, and what is needed to get a full Kontact experience. I installed all the seemingly relevant libraries, and it is still resulting in an error. I question the sense of shipping Kontact without Akonadi. Document on how to combine the different PIM libraries, and clearly stating, which one is needed in which case, and what combinations lead to what outcome. <!-- make sure this issue is not redundant or obsolete --- [x] checked [latest Nixpkgs manual] ([source][nixpkgs-source]) and [latest NixOS manual] ([source][nixos-source]) [x] checked [open documentation issues] for possible duplicates [x] checked [open documentation pull requests] for possible solutions [latest Nixpkgs manual]: [latest NixOS manual]: [nixpkgs-source]: [nixos-source]: [open documentation issues]: [open documentation pull requests]: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
We just need to figure out what's wrong and add that to the plasma6 module and maybe add a new option for it. We probably don't need and want to add explicit documentation for this.
Note to myself: We want to add an option named ` that right now only set the following but maybe more or less. To be tested. For proper testing a full log out might be necessary.
Change:
owner = "vim"; repo = "vim"; rev = "v${version}"; <del> sha256 = "04hp2gqbbj9h872bgj1g9xcaj5qlg9q45v6by2ch9n105dng9aj3"; </del> <ins> sha256 = "0ys3l3dr43vjad1f096ch1sl3x2ajsqkd03rdn6n812m7j4wipx0"; </ins> }; "vim-nox" =

Discussion:
Currently vimconfigurable is version 7.4.826 where as vim is now 8.0005. $ nix-env -f /path/to/nixpkgs -i vimconfigurable $ vim --version VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jan 1 1970 00:00:01) Included patches: 1-826 ... Updated version and sha256 in to be identical to that in System: (NixOS: 16.09beta264. (Flounder)) Nix version: (nix-env (Nix) 1.11.4) Nixpkgs version: (17.03pre-git)
Change:
}; allowedUDPPortRanges = mkOption { <del> type = types.listOf (types.attrsOf types.int); </del> <ins> type = types.listOf (types.attrsOf types.port); </ins> default = [ ]; example = [ { from = 60000; to = 61000; } ]; description =

Discussion:
networking.firewall.allowedTCPPorts = [ 443 443 ]; Seems to generate two identical iptables rules instead of just one. This kind of configuration can easily happen when multiple independent modules append the same port to the list. IMO it would be worth de-duplicating ports (and maybe sorting?) so that the generated firewall configuration is easier to read. system: host os: multi-user?: sandbox: version: channels(delroth): nixpkgs:
Great idea - want to take a stab at a PR?
Change:
doCheck = false; # fails 13 out of 13 tests (ctest) <del> # Hack to avoid TMPDIR in RPATHs. preFixup = '' rm -rf "$(pwd)" mkdir "$(pwd)" </del> <ins> # remove forbidden references to $TMPDIR preFixup = lib.optionalString stdenv.isLinux '' patchelf --shrink-rpath --allowed-rpath-prefixes "$NIX_STORE" "$out"/libexec/* </ins> ''; <ins> enableParallelBuilding = true; </ins> meta = { maintainers = with lib.maintainers; [ abbradar periklis ]; knownVulnerabilities = [

Discussion:
Steps to reproduce the behavior: on nixos-unstable I believe this is related to <!-- 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.
It'll need a similar fix like the ones in Wasn't caught in staging because it's marked insecure