jiebi/CodeConvo huggingface dataset:
Change:
sha256 = "sha256-Yv1XjD8sZcmGr2SVD6TEElUH7vspJ61WwQwfXLOrao0="; }; <ins> postPatch = '' substituteInPlace mysqltuner.pl  --replace '$basic_password_files = "/usr/share/mysqltuner/basic_passwords.txt"' "$basic_password_files = "$out/share/basic_passwords.txt""  --replace '$opt{cvefile} = "/usr/share/mysqltuner/vulnerabilities.csv"' "$opt{cvefile} = "$out/share/vulnerabilities.csv"" ''; </ins> buildInputs = [ perl ]; installPhase = '' <del> mkdir -p $out/bin install -m0755 mysqltuner.pl $out/bin/mysqltuner </del> <ins> runHook preInstall mkdir -p "$out/bin" install -Dm 0755 mysqltuner.pl "$out/bin/mysqltuner" install -Dm 0644 basic_passwords.txt "$out/share/basic_passwords.txt" install -Dm 0644 vulnerabilities.csv "$out/share/vulnerabilities.csv" runHook postInstall </ins> ''; meta = with lib; { description = "Make recommendations for increased performance and stability of MariaDB/MySQL"; homepage = "http://mysqltuner.com"; <del> license = licenses.gpl3; maintainers = with maintainers; [ peterhoeg ]; </del> <ins> license = licenses.gpl3Plus; maintainers = with maintainers; [ peterhoeg shamilton ]; </ins> }; }

Discussion:
Describe the bug When running mysqltuner, it says: So i suggest to add to the package that in included in the projects repo. To Reproduce Steps to reproduce the behavior: ... ... ... Expected behavior A clear and concise description of what you expected to happen. Additional context Add any other context about the problem here. Notify maintainers Metadata used with Maintainer information:
Good catch - feel like doing a PR?
Not now, maybe later. But it's fine if someone else does it. Should be pretty easy, so good first issue.
Change:
''; }; <ins> bazelRC = writeTextFile { name = "bazel-rc"; text = '' build --override_repository=${remote_java_tools.name}=${remote_java_tools} build --distdir=${distDir} startup --server_javabase=${runJdk} # load default location for the system wide configuration try-import /etc/bazel.bazelrc ''; }; </ins> in stdenv.mkDerivation rec { pname = "bazel";

Discussion:
Describe the bug By default and according to bazel documentation (), bazel is looking for a system-wide configuration is . In I decided to override this path and make it point in . It was the easiest solution to pass arguments to bazel in order to fix a few runtime issues. However it breaks the assumption that user can configure bazel using . To Reproduce Use bazel from nixpkgs with . Set some bazel settings in your file Observe that bazel ignores this file Expected behavior I'm opening this bug report to discuss what should be the expected behavior here? Should we respect the ? If yes, I'll open a pull request to restore the previous behavior.
I'll be in favour of keeping support for all paths specified in the documentation - having a system-wide is something people might want to make use of, so we shouldn't take away that possibility. We currently set the following options in bazelrc: We should either patch these as defaults into nixos, or introduce reading from a distro-provided location (should be coordinated with bazel upstream). I think adding a wrapper is a bit too much for all these options.
I do agree with your point of view. I'll try to propose a PR which restore the old behavior. In the meantime, I'm open to other comments on this issue. Regarding the options you quote, they are used in a local during build only. The global bazelrc that I provide is way simpler: Both were ad hoc solution for different problems, respectively issue and commit .
Change:
<del> { stdenv, fetchgit, fontforge, pythonFull }: </del> <ins> { stdenv, fetchgit, fontforge, python3 }: </ins> stdenv.mkDerivation rec { pname = "rictydiminished-with-firacode";

Discussion:
Describe the bug Trying to rebuild from git master and it complains about fonttools and python version mismatch. To Reproduce Metadata Please run and paste the result. root nix run -c nix-info -m system: host os: multi-user?: sandbox: version: nixpkgs: channels(root): Maintainer information:
Looks like an issue with trying to build it with Python 2.7.x. The code isn't entirely compatible with Python 3.x nevertheless.
The issue seems to be with nototools which we currently have disabled for python3. The last nototools release is apparently fully compatible with python3. I'm working on a fix for this, however, the build now has a strange relationship with noto-fonts that I haven't quite figured out yet.
In the latest release nototools seems to still fail, or at least does on mine. The only relationship I found is that nototools is a dependency on noto-fonts.
you mean when running , or something similar? That's expected since nototools has been disabled for python3 (python3 support has only recently been upstream). I believe the relationship is actually that nototools is a dep of noto-fonts-emoji. The current nototools seems to require noto-fonts as a dep. I've gotten most of the way to a fix I think (changed nototools version and enabled py3 and what we fetch with the fetchZip in noto-fonts). However, the way that nototools expects noto-fonts is pretty strange (as an example look at the top level makefile where it looks for the noto-fonts repo in nototools' parent directory). I'm having a bit of trouble getting noto-fonts in the form nototools expects. I'm trying not to just copy the entire noto-fonts source into nototools source which seems like it should be unnecessary. Once nototools is fixed for python3 the rest should be easy bc we can just change noto-fonts etc to use python3. If you have any thoughts on how to fix nototools I'd love to hear them, or if you think I'm missing something here pls do let me know.
should be a dependency of the derivation. I'm not sure where you're seeing the fact that needs as a dependency.

The farthest I've gotten is removing all the errors from the configuration but the build still fails with .
You mean that it should be a dependency of or it is currently? In regard to "is currently" I don't see it as currently being a dependency. The only place appears in noto- is in the following lines as part of derivation. If you mean it should be, then how you get to build on its own? If you change the nototools version to 0.2.0 which adds python3 support I get errors about missing font directories (these directories come from noto-fonts). What am I missing here?
Proposed fix Still building though...
, and have the same error.
Change:
diff --git a/src/hotplug_libudev.c b/src/hotplug_libudev.c <del> index a8ba1b8..a53700b 100644 </del> <ins> index 51bd95f..84f959b 100644 </ins> --- a/src/hotplug_libudev.c +++ b/src/hotplug_libudev.c <del> @@ -119,7 +119,8 @@ static LONG HPReadBundleValues(void) </del> <ins> @@ -120,7 +120,8 @@ static LONG HPReadBundleValues(void) </ins> if (NULL == hpDir) {

Discussion:
The package installs that contains an unconfigured variable: This results in the following message in system journal: Obviously, not critical, but still this doesn’t sound right. The contains , so it looks like gets replaced by literal , but I am not sure where this happens or why. Steps to reproduce the behavior: There should be no unsubstituted variables in the installed unit. Maintainer information:
Looks like this line was upstream in 1.9.2 and the version in nixpkgs was upgraded from 1.9.1 to 1.9.4 in October ().
Ok, I am not particularly good with Autotools, but it seems to me that it is an upstream bug. The generate does this replacement, but I think it is supposed to happen only in a context in which this will be further expanded, not in plaintext files intended to be simply copied to their final install location.
Yes, it’s definitely an upstream issue. This usage of is explicitly called out as incorrect in Autconf docs:
Reported upstream:
Fixed in 1.9.5 (just released):
Keep in mind that this needs to point at if it is to be used for anything instead of into the nix store.
Can we make an option to allow specific ? I can help to make a PR if you agree : )
Send a PR I guess? Although, I am not sure how useful this option will be, given that, I assume, all other packages have to be linked to the same pcsc that provides the daemon. On the other hand, many other packages have this option, and I don’t know if there is some pattern or policy in NixOS.
The fixes PR is merged, but if a stable user (, etc.) wants to solve these issues, he could be: nix overlays, let = the package from newer channel, this will cause rebuild of all package that depends on it. to override attribute of , which is tedious and error-prone. So I suggest either we add an option to allow specific the package,or backport the changes to stable branch...?
Change:
zinnia = callPackage ../tools/inputmethods/zinnia { }; tegaki-zinnia-japanese = callPackage ../tools/inputmethods/tegaki-zinnia-japanese { }; <del> zimreader = callPackage ../tools/text/zimreader { }; </del> zimwriterfs = callPackage ../tools/text/zimwriterfs { }; par = callPackage ../tools/text/par { };

Discussion:
Describe the bug Kiwix fails to build with a C++ code error. To Reproduce Steps to reproduce the behavior: , because the package is marked as insecure, Expected behavior Kiwix builds. Additional context The error: Probably this needs to be solved for . 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 system: host os: multi-user?: sandbox: version: channels(mario): channels(root): nixpkgs: Maintainer information:
I marked this as stale due to inactivity. &rarr;
See
Change:
<ins> { libraw, fetchFromGitHub }: libraw.overrideAttrs (_: rec { version = "unstable-2021-12-03"; src = fetchFromGitHub { owner = "LibRaw"; repo = "LibRaw"; rev = "52b2fc52e93a566e7e05eaa44cada58e3360b6ad"; sha256 = "kW0R4iPuqnFuWYDrl46ok3kaPcGgY2MqZT7mqVX+BDQ="; }; }) </ins>

Discussion:
Krita fails to build with the following error Steps to reproduce the behavior: Build Krita should build. nixpkgs @
In libraw was updated. Switch to the old stable libraw020 to fix this build.
Installing kirta is showing like it's not in the cache, any idea why?
You're attempting to build the older derivation. And building it would fail. Newer binaries are available:
If you rely on channels, you might want to watch
I'm using the "" and just updated it, and I get this: So, that means the PR is not in that channel yet? If it's that, good to know, didn't know that tool.
Yes, channels that are not -small usually lag by roughly one day.
Change:
# qt.conf is not working, so override everything using environment variables wrapProgram $out/opt/viber/Viber  <ins> --set QT_QPA_PLATFORM "xcb"  </ins> --set QT_PLUGIN_PATH "$out/opt/viber/plugins"  --set QT_XKB_CONFIG_ROOT "${xorg.xkeyboardconfig}/share/X11/xkb"  --set QTCOMPOSE "${xorg.libX11.out}/share/X11/locale" 

Discussion:
Describe the bug Viber doesn't work on sway. I get this error: viber Failed to load client buffer integration: "wayland-egl" Available client buffer integrations: () failed to acquire GL context to resolve capabilities, using defaults.. No shell integration named "xdg-shell" found No shell integration named "xdg-shell-v6" found No shell integration named "wl-shell" found No shell integration named "ivi-shell" found Loading shell integration failed. Attempted to load the following shells ("xdg-shell", "xdg-shell-v6", "wl-shell", "ivi-shell") To Reproduce Steps to reproduce the behavior: sway. viber inside of terminal emulator. Expected behavior Should work:) Screenshots ! Notify maintainers
a workaround
yep. It works! Can it this variable be into package until viber will be fixed?
I marked this as stale due to inactivity. &rarr;
Change:
libxfce4util libxklavier pam <ins> pythonEnv </ins> systemd xfconf ];

Discussion:
Apparently there's a problem with wrapped command. When try to configure my screensaver (e.g. slideshow), it won't open. Opening it via terminal returns nothing. The command itself points to /nix/store/hash-xfce4-screensaver-version/bin/.xfce4-screensaver-configure-wrapped. Its a python script, but interpreter is set as #!/usr/bin/python3, which is obviously not available on nixos. Steps to reproduce the behavior: Configuration program should open ! strace output:
Does help?
Thanks, now it works. Shall i close the issue or wait for PR?
Change:
<del> { lib, stdenv, fetchFromGitHub, btrfs-progs }: </del> <ins> { lib, stdenv, fetchFromGitHub, fetchurl, btrfs-progs }: let # https://github.com/kilobyte/compsize/issues/52 btrfs-progs' = btrfs-progs.overrideAttrs (old: rec { pname = "btrfs-progs"; version = "6.10"; src = fetchurl { url = "mirror://kernel/linux/kernel/people/kdave/btrfs-progs/btrfs-progs-v${version}.tar.xz"; hash = "sha256-M4KoTj/P4f/eoHphqz9OhmZdOPo18fNFSNXfhnQj4N8="; }; }); in </ins> stdenv.mkDerivation rec { pname = "compsize"; version = "1.5";

Discussion:
Steps to reproduce the behavior: compsize Add any other context about the problem here. <!-- 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
The reason is update makes it build again on current master Something there breaks it: Seems like quite a few things that used got removed:
Here's a quick workaround:
Seems due to this commit: and this:
Here's the corresponding compsize upstream bug:
Change:
stdenv.mkDerivation (finalAttrs: { pname = "ldtk"; <del> version = "1.4.1"; </del> <ins> version = "1.5.2"; </ins> src = fetchurl { url = "https://github.com/deepnight/ldtk/releases/download/v${finalAttrs.version}/ubuntu-distribution.zip"; <del> hash = "sha256-Qt6ADyIbhuxFGh7IP1WwcsvMtjOUZoTd99GeWt5s4UM="; </del> <ins> hash = "sha256-/2exLVMdSnn/Rc2lL1ytDZ6NvYRJA6W+NT7gGzxm6Vc="; </ins> }; nativeBuildInputs = [ unzip makeWrapper copyDesktopItems appimage-run ];

Discussion:
Package name: ldtk Latest released version: 1.5.2 <!-- Search your package here: --- Current version on the unstable channel: 1.4.1 Current version on the stable/release channel: 1.4.1 <!-- 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. Changelog: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
''; checkFlags = [ <del> "--skip=conf::test_config_parse"        # panicking due to sandbox "--skip=smtp::test::test_smtp"          # requiring network "--skip=utils::xdg::query_default_app"  # doesn't build "--skip=utils::xdg::query_mime_info"    # doesn't build </del> <ins> "--skip=conf::tests::test_config_parse"            # panicking due to sandbox "--skip=utils::tests::test_shellexpandtrait_impls" # panicking due to sandbox "--skip=utils::tests::test_shellexpandtrait"       # panicking due to sandbox </ins> ]; meta = with lib; {

Discussion:
Package name: meli Latest released version: 0.8.7 <!-- Search your package here: --- Current version on the unstable channel: 0.8.6 Current version on the stable/release channel: 0.8.5 <!-- 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]:
Release notes: This will not fix , since is still at in meli 0.8.7. It was only updated in , which is not part of any release yet.
Sure, do you want to PR an update?
I created It builds, but tests failed locally with " executable not found in PATH". In addition to fixing that I also need to work through
is done from my point of view, apart from some error in the ofborg-eval-darwin job that I can't explain and don't know how to solve:
Change:
{ "bookmarks": { <del> "sha256": "0xx331bgly91y8ncxk36ha3ncrr2xlivblfi7rix6ffkrdx73yb9", "url": "https://github.com/nextcloud/bookmarks/releases/download/v13.0.1/bookmarks-13.0.1.tar.gz", "version": "13.0.1", "description": "- 📂 Sort bookmarks into foldersn- 🏷 Add tags and personal notesn- 🔍 Full-text searchn- 📲 Synchronize with all your browsers and devicesn- 👪 Share bookmarks with other users and publiclyn- ☠ Find broken linksn- ⚛ Generate RSS feeds of your collectionsn- 📔 Read archived versions of your links in case they are depublishedn- 💬 Create new bookmarks directly from within Nextcloud Talkn- 💼 Built-in Dashboard widgets for frequent and recent linksnnRequirements:n - PHP v7.4+n - PHP extensions:n   - intl: *n   - mbstring: *n - when using MySQL, use at least v8.0", </del> <ins> "sha256": "16j10gj5nghgji36jhng60291wl4h9c3vndjx9j8jij9qn6hz23f", "url": "https://github.com/nextcloud/bookmarks/releases/download/v13.1.0/bookmarks-13.1.0.tar.gz", "version": "13.1.0", "description": "- 📂 Sort bookmarks into foldersn- 🏷 Add tags and personal notesn- 🔍 Full-text searchn- 📲 Synchronize with all your browsers and devicesn- 👪 Share bookmarks with other users and publiclyn- ☠ Find broken linksn- ⚛ Generate RSS feeds of your collectionsn- 📔 Read archived versions of your links in case they are depublishedn- 💬 Create new bookmarks directly from within Nextcloud Talkn- 💼 Built-in Dashboard widgets for frequent and recent linksnnRequirements:n - PHP extensions:n   - intl: *n   - mbstring: *n - when using MySQL, use at least v8.0", </ins> "homepage": "https://github.com/nextcloud/bookmarks", "licenses": [ "agpl"

Discussion:
The nextcloud package set offers apps, that have licensing information attached, but not exposed as part of their meta attribute. Also, there are some apps, like news, where the licensing information says , which requires clarification. This needs to be fixed.
Thank you for opening the draft PR in order to fix my mistakes and broken packages. I'm sorry for the bad communication and the inability to resolve this serious issue. 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.
Change:
qtInputs = [ qtbase qtdeclarative qtsvg ]; propagatedBuildInputs = [ hunspell ]; nativeBuildInputs = [ pkg-config ]; <del> outputs = [ "out" ]; </del> }

Discussion:
This means nearly all qt6 packages depend on gdb which is 641M on its own. Why is that the case? I can't imagine needing Valgrind for "production" qt6 builds but I have no knowledge in this domain. cc
valgrind was not in my qt6 draft in valgrind was in but valgrind or gdb dont show up in the closure of <details </summaryto compare, </detailsso ... no problem? edit: <details </summary</details
The inputs are only propagated in the output and that's what other packages use. I only came across this because I found gdb in my system closure. showed <the package-quazip -qtbase -valgrind -gdb why did you add valgrind to qt6's propagatedBuildInputs?
It should have been a build time dependency for qtbase. And as it is only referenced in dev output, it should normally not be referenced in system closures, except for issues like Edit, quazip wasn't fixed by that, let me look into it tomorrow.
... so should not be there &rarr; /nix/store/y1m61ayisqmp29ckzi0qq4fp640qfl3l-qtbase-6.4.1-dev/include/QtTest/qtestmouse.h &rarr; /nix/store/y1m61ayisqmp29ckzi0qq4fp640qfl3l-qtbase-6.4.1-dev/include/QtTest/qtestmouse.h &rarr; propagatedBuildInputs &rarr; propagatedBuildInputs also may be relevant: in , are copied to
For the , they should have been in dev output, but and do not have dev output, adding it back should be enough. For , it should be of the same problem as in , maybe we should add that in the hooks of qtbase, or we can fix this ad-hoc.
Change:
pwsafe = callPackage ../applications/misc/pwsafe { }; <ins> pw-viz = callPackage ../applications/misc/pw-viz { }; </ins> napi-rs-cli = callPackage ../development/tools/napi-rs-cli { }; neil = callPackage ../development/tools/neil { };

Discussion:
... in Rust! Project description Pipewire graph editor written in Rust. ( WIP warning ) Maybe it's too early? I'm not sure, it looks usable at least from the screenshot... Metadata homepage URL: source URL: license: gpl3 platforms: linux,
Change:
pomegranate = callPackage ../development/python-modules/pomegranate { }; <del> poppler-qt4 = buildPythonPackage rec { name = "poppler-qt4-${version}"; version = "0.18.1"; disabled = isPy3k || isPyPy; src = pkgs.fetchurl { url = "mirror://pypi/p/python-poppler-qt4/" + "python-poppler-qt4-${version}.tar.gz"; sha256 = "00e3f89f4e23a844844d082918a89c2cbb1e8231ecb011b81d592e7e3c33a74c"; }; propagatedBuildInputs = [ self.pyqt4 pkgs.pkgconfig pkgs.poppler_qt4 ]; preBuild = "${python}/bin/${python.executable} setup.py build_ext" + " --include-dirs=${pkgs.poppler_qt4.dev}/include/poppler/"; NIX_CFLAGS_COMPILE = "-I${pkgs.poppler_qt4.dev}/include/poppler/"; meta = { description = "A Python binding to Poppler-Qt4"; longDescription = '' A Python binding to Poppler-Qt4 that aims for completeness and for being actively maintained. ''; license = licenses.lgpl21Plus; maintainers = with maintainers; [ sepi ]; platforms = platforms.all; }; }; </del> poppler-qt5 = callPackage ../development/python-modules/poppler-qt5 { inherit (pkgs.qt5) qtbase; inherit (pkgs.libsForQt5) poppler;

Discussion:
Recently released removes the QT4 support. For now, we will split the package and keep on 0.61.
It is still used so it should remain at an older version.
~It's used just in two packages, apparently ( and ).~ Hopefully those can be soon migrated to Qt5. Otherwise we can keep old version for only and keep updating the rest...
Those are only python dependents. It is also referenced from calligra, texstudio, texmaker, qpdfview, diffpdf,
Thanks, I grepped for a wrong string.
Yeah. (I meant that should remain at an older version, while can be decoupled and upgraded.)
moves diffpdf away from poppler_qt4, FWIW.
currently working on a fix for package as its latest version uses qt5 now, so poppler_qt4 isn't needed anymore
I opened a updating qpdfview, which makes open-pdf-presenter the last thing depending on (via the python library). Since it is abandoned, it is not likely to be updated. Do we remove it?
almost done, need some rest for now, PR for will come tomorrow :)
Finally getting rid of this in .
Change:
{ lib , buildPythonPackage <del> , fetchFromGitHub , python </del> <ins> , fetchPypi </ins> , notebook <ins> , notebook-shim </ins> , pythonOlder , jupyter_server , pytestCheckHook

Discussion:
Steps to reproduce the behavior: I have this in my home-manager config packages, and the build only fails if jupyterlab is uncommented. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
Looks like it's broken because of : Looking at the commit range in the evaluation, it seems that it was broken by in
Already reported:
Right, thanks for the info. So I close the issue.

Steps to reproduce the behavior: This is a dependency of jupyterlab which prevents me from using the latest jupyterlab in jupyterWith I think this just needs somewhere but I'm not experienced enough with nixpkgs to inject it in the correct place.
Note: I tried to fix this using but it didn't work... idk why.