jiebi/CodeConvo huggingface dataset:
Change:
stdenv.mkDerivation { pname = "rtl8812au"; <del> version = "${kernel.version}-unstable-2023-07-20"; </del> <ins> version = "${kernel.version}-unstable-2023-07-22"; </ins> src = fetchFromGitHub { owner = "morrownr"; repo = "8812au-20210629"; <del> rev = "51338202d21a63202b324afd22bd361141c8c5e5"; hash = "sha256-NIdKUP5t/dzQ9xIG5Kc6eRudr6vTpCafunXZHZLcoL8="; </del> <ins> rev = "b5f4e6e894eca8fea38661e2fc22a2570e0274ad"; hash = "sha256-3uPowesJVh/cnagMz/Uadb+U5rDUAWfU39tZaDNCoqg="; </ins> }; nativeBuildInputs = [ bc nukeReferences ] ++ kernel.moduleBuildDependencies;

Discussion:
Steps to reproduce the behavior: nixos-unstable (tested with ) for full log Add any other context about the problem here. Please run and paste the result.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
rec { <del> version="1.0.56"; name="sbcl-1.0.56"; hash="0cq5hyzv3nnva0y1y6zjyd7rfdwwpxswnvmbfmqvhihz72ivyl1w"; url="http://downloads.sourceforge.net/project/sbcl/sbcl/1.0.56/sbcl-1.0.56-source.tar.bz2"; advertisedUrl="http://downloads.sourceforge.net/project/sbcl/sbcl/1.0.56/sbcl-1.0.56-source.tar.bz2"; </del> <ins> version="1.0.57"; name="sbcl-1.0.57"; hash="1vvifyq0lapx6p6wz6jknsgch3lbyr7m785844wdgkdx2hh8ch51"; url="http://downloads.sourceforge.net/project/sbcl/sbcl/1.0.57/sbcl-1.0.57-source.tar.bz2"; advertisedUrl="http://downloads.sourceforge.net/project/sbcl/sbcl/1.0.57/sbcl-1.0.57-source.tar.bz2"; </ins> }

Discussion:
Describe the bug Thunderbird 78.2.1 is working. master (Thunderbird 78.2.2) has rendering issues (see screenshot). Most buttons do not react to clicks and the menu is also not reacting. To Reproduce Switch to the mentioned commit and rebuild. Expected behavior Normally working thunderbird. Screenshots ! Notify maintainers Metadata
This was also a bug in Ubuntu, it was fixed there with:
Upstream bug appears to be
Btw temporary workaround would be to switch to thunderbird-bin-78 if you are not opposed to binaries
Change:
example = { system = "x86_64-linux"; }; # Make sure that the final value has all fields for sake of other modules # referring to this. <del> apply = lib.systems.elaborate; </del> <ins> apply = inputBuildPlatform: let elaborated = lib.systems.elaborate inputBuildPlatform; in if lib.systems.equals elaborated cfg.hostPlatform then cfg.hostPlatform  # make identical, so that `==` equality works; see https://github.com/NixOS/nixpkgs/issues/278001 else elaborated; </ins> defaultText = literalExpression ''config.nixpkgs.hostPlatform''; description = lib.mdDoc ''

Discussion:
A clear and concise description of what the bug is. When a nixos configuration has and both set to the same string, the module defined always determines that the system is cross-compiled, even when it should not be. Steps to reproduce the behavior: a nixos config with the example configuration: building and notice that the entire world gets rebuilt since it tries to build cross-compilation toolchains A clear and concise description of what you expected to happen. I would expect that the module would determine I am not cross-compiling the nixos system and build accordingly. If applicable, add screenshots to help explain your problem. 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]:
Change:
ln -sT "${vscode}/share/applications/${executableName}.desktop" "$out/share/applications/${executableName}.desktop" ln -sT "${vscode}/share/applications/${executableName}-url-handler.desktop" "$out/share/applications/${executableName}-url-handler.desktop" makeWrapper "${vscode}/bin/${executableName}" "$out/bin/${executableName}" ${lib.optionalString (vscodeExtensions != []) '' <del> --add-flags "--extensions-dir ${combinedExtensionsDrv}" </del> <ins> --add-flags "--extensions-dir ${combinedExtensionsDrv}/share/vscode/extensions" </ins> ''} ''

Discussion:
Describe the bug A clear and concise description of what the bug is. the vscode-extensions directory has the structure so should be called with the argument instead of To Reproduce Steps to reproduce the behavior: ... ... ... Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screenshots to help explain your problem. Additional context Add any other context about the problem here. 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 Please run and paste the result. Maintainer information:
Change:
# Refer to comments in the overrides for cuda_nvcc for explanation # CUDA_TOOLKIT_ROOT_DIR is legacy, # Cf. https://cmake.org/cmake/help/latest/module/FindCUDA.html#input-variables <ins> # NOTE: We unconditionally set -Xfatbin=-compress-all, which reduces the size of the compiled #   binaries. If binaries grow over 2GB, they will fail to link. This is a problem for us, as #   the default set of CUDA capabilities we build can regularly cause this to occur (for #   example, with Magma). </ins> '' mkdir -p $out/nix-support cat <<EOF >> $out/nix-support/setup-hook

Discussion:
Steps to reproduce the behavior: magma From : Also may be interested.
Is this related to the race condition error you saw before?
can you tell me more about what hardware you're using, and what your looks like? For reference, runs without issue for me with using a 4090 and an i9 13900k: EDIT: Would you also try building with I made some changes there that moved the CUDA runtime stub and NVCC into . I'm curious if that helps at all.
I don't think so -- closest I can remember to this was the linking error AMD HIP had with 2.7.x (which is why its stuck on magma 2.6.x), but that was a different inscrutable error from .
CPU is a Xeon Gold 5218 with Quadro RTX 8000 GPUs. I haven't set any configuration other than and .
I don't know why this issue isn't affecting your builds but most likely the fix is to set :
Haven't tried yet either, sorry.
Any idea when this failure started occurring?
magma 2.6.2 I believe works but 2.7.1 fails. I can try to bisect at some point if needed.
What channel were you building from by the way? I'm gonna try to find a way to match your setup but I need to know exactly which version of nixpkgs you're using to build.
Okay, I was able to reproduce it. It happened while a Nixpkgs-review for that magma PR I linked earlier. I suspect it has something to do with either my disabling or restricting . Time to investigate ‍
Something for me to look at later tonight; if it is the case that the increased number of cuda capabilities being targeted is causing the binary to bloat, check that we're using , like PyTorch : IIRC Magma doesn't set that flag. Also, I remember being unable to find specifically in the NVCC docs. Since PyTorch also ships binaries targeting a bunch of different CUDA capabilities, their configs are a goldmine of flags we might need to look into. EDIT: Haven't built with it yet, but it seems like it should fix it.

Apache MXNet had the same issue: EDIT2: Reminder to self: if that is the fix, add here: and here:
I know it's still a draft but can you try building again with I think it should fix your issue. Unrelated, but if you're building anything from source and you want faster builds I highly recommend specifying the single compute capability you need to build for (like I do here ) because it results in massively faster builds. HEAD right now builds for 14 different capabilities and that PR gets it down to 8, but it's much faster to build for just one.
is building for me from that branch (without any configuring compute capabilities yet), thanks.
Change:
platforms = platforms.unix; maintainers = with maintainers; [ sikmir ]; knownVulnerabilities = [ <del> "CVE-2018-7453: loop in PDF objects" "CVE-2018-16369: loop in PDF objects" </del> "CVE-2019-9587: loop in PDF objects" "CVE-2019-9588: loop in PDF objects" "CVE-2019-16088: loop in PDF objects"

Discussion:
XPDF updated their version from 4.04 → 4.05 and seem to have broken the download URL to the older version. returns a 404, but works
Change:
<ins> diff --git a/CMakeLists.txt b/CMakeLists.txt index 98752ec..aa029b3 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -55,7 +55,15 @@ endif() qt_standard_project_setup() find_package(OpenSSL REQUIRED) -find_package(lcms REQUIRED) +SET(LCMS2_NAMES ${LCMS2_NAMES} lcms2 liblcms2 liblcms2_static) +FIND_LIBRARY(LCMS2_LIBRARY NAMES ${LCMS2_NAMES} ) +FIND_PATH(LCMS2_INCLUDE_DIR lcms2.h) +add_library(lcms2::lcms2 UNKNOWN IMPORTED) +set_target_properties(lcms2::lcms2 PROPERTIES +    IMPORTED_LOCATION ${LCMS2_LIBRARY} +    INTERFACE_INCLUDE_DIRECTORIES ${LCMS2_INCLUDE_DIR} +    INTERFACE_COMPILE_DEFINITIONS "HAVE_LCMS2=1;CMS_NO_REGISTER_KEYWORD=1") +set_property(GLOBAL APPEND PROPERTY INTERNAL_DEPS_PROP lcms2::lcms2) find_package(ZLIB REQUIRED) find_package(Freetype REQUIRED) find_package(OpenJPEG CONFIG REQUIRED) </ins>

Discussion:
Package request: A simple and powerful PDF viewer and editor powered by the Qt framework. With a robust C++ library, intuitive PDF viewing/editing applications, and a handy command-line tool, PDF4QT streamlines your PDF interactions.
Change:
sha256 = "12nypzb1m14yip4zrbzin5jc5awyp1d5md5y40g5anj4phb4hx1i"; }; <ins> patches = [ ./python312-fix.patch ]; </ins> buildInputs = [ alsa-lib ]; meta = with lib; {

Discussion:
simpleaudio in python312Packages crashes after playing a sound. It works in python311Packages : Run <!-- 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]:
I think it's coming from upstream: Possibly fixed here:
Change:
Terminal=false NoDisplay=true Icon=org.gnome.Shell.Extensions.GSConnect <ins> diff --git a/src/__nix-prepend-search-paths.js b/src/__nix-prepend-search-paths.js new file mode 100644 index 00000000..d009dfd9 --- /dev/null +++ b/src/__nix-prepend-search-paths.js @@ -0,0 +1,2 @@ +import GIRepository from 'gi://GIRepository'; +'@typelibPath@'.split(':').forEach(path => GIRepository.Repository.prepend_search_path(path)); </ins> diff --git a/src/extension.js b/src/extension.js <del> index 3fae443a..7aa19842 100644 </del> <ins> index 53ecd5fc..78782357 100644 </ins> --- a/src/extension.js +++ b/src/extension.js <del> @@ -4,6 +4,8 @@ </del> <ins> @@ -2,6 +2,8 @@ // // SPDX-License-Identifier: GPL-2.0-or-later </ins> <del> 'use strict'; +'@typelibPath@'.split(':').forEach(path => imports.gi.GIRepository.Repository.prepend_search_path(path)); </del> <ins> +import './__nix-prepend-search-paths.js'; </ins> + <del> const Gio = imports.gi.Gio; const GObject = imports.gi.GObject; const Gtk = imports.gi.Gtk; </del> <ins> import Gio from 'gi://Gio'; import GObject from 'gi://GObject'; </ins> diff --git a/src/prefs.js b/src/prefs.js <del> index b8860c82..d6292606 100644 </del> <ins> index dd20fd20..5f82c53a 100644 </ins> --- a/src/prefs.js +++ b/src/prefs.js <del> @@ -4,6 +4,8 @@ </del> <ins> @@ -2,6 +2,8 @@ // // SPDX-License-Identifier: GPL-2.0-or-later </ins> <del> 'use strict'; +'@typelibPath@'.split(':').forEach(path => imports.gi.GIRepository.Repository.prepend_search_path(path)); </del> <ins> +import './__nix-prepend-search-paths.js'; </ins> + <del> const {Gio, GLib, Adw} = imports.gi; // Bootstrap </del> <ins> import Gio from 'gi://Gio'; import GLib from 'gi://GLib'; import Adw from 'gi://Adw'; </ins>

Discussion:
Package name: gnomeExtensions.gsconnect Latest released version: 56 <!-- Search your package here: --- Current version on the unstable channel: 55 Current version on the stable/release channel: 55 <!-- 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. Priorities Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
This is important, as gsconnect doesn't work on 23.11 with Gnome 45.
Change:
patchPhase = '' substituteInPlace qmltermwidget.pro  <del> --replace '$$[QT_INSTALL_QML]' "/lib/qml/" </del> <ins> --replace '$$[QT_INSTALL_QML]' "/lib/qt5/qml/" </ins> ''; configurePhase = "qmake PREFIX=$out";

Discussion:
After running , cool-retro-term doesn't seem to work. When attempting to run, it outputs errors and hangs: This is on the current nixos-unstable channel:
Confirmed, already on 15.09 and persist on current master. /cc for latest changes and maintainer
That error message indicates it has missing dependencies; it is at least missing and . Unfortunately, Qt defers detection of dependencies until runtime whenever it can, instead of complaining during the build that these dependencies are missing.
Yeah, I've been looking into this a bit and and to buildInputs. The error message is now:
Although it's in the build inputs, it doesn't look like is being to the environment: returns no results.
isn't installing its QML files into the correct prefix. QML stuff should go into and QML2 stuff should go into , but puts everything into . Since the files are in the wrong location, they aren't picked up by .
Can we just tell that there's some QML stuff elsewhere? It's probably not the cleanest solution, but it would allow the package to work.
It would be better to fix . The Nix expression specifically patches the package to set the wrong QML path; I think if you simply remove that, it would work.
I tried removing the whole block: cool-retro-term gives the same error (), however.
Yeah, that's because there are more serious problems with how is packaged. You are the maintainer of , can you help us out here? I've taken a look at the package and I can't get it to respect Qt's QML import paths during installation.
Yeah, I will look into it.
Just got the same error:
I can confirm this issue on Ubuntu. Same problem here. installed using (v 1.1.1, rev126, stable) on Ubuntu 18.04.2 LTS
forgive me if I'm being dumb, but how does using on Ubuntu relate to NixPkgs?
Cool-retro-term simply "fails to run" due to this unresolved dependencies on many linux distributions. I just confirmed another one.

I don't understand, why this issue is closed now, that problem is not fixed - especially snaps shlould be able to handle QML dependencies somehow ,
In any case, I confirm this failure on nixpkgs master:
I don't see any changes in nixpkgs since this ticket was closed, but works on my nixos box.
QML packages rely on so they cannot be used without being installed to a profile.
Right, I apparently didn't know that at the time (or didn't recall it).
Try this....
I have the same problem. how to fix? user cool-retro-term QQmlApplicationEngine failed to load component Type TerminalContainer unavailable Type PreprocessedTerminal unavailable module "QMLTermWidget" is not installed Cannot load QML interface jre
Change:
chardet beautifulsoup4 html5lib PyRSS2Gen pynzb rpyc jinja2 jsonschema requests dateutil <del> pathpy guessit_2_0 APScheduler </del> <ins> pathpy guessit APScheduler </ins> terminaltables colorclass cherrypy flask flask-restful flask-restplus flask-compress

Discussion:
Flexget refused to work after upgrade. I noticed the problem was guessit. Having a look at the .nix files I noticed that was actually updated to use guessit 3.0. However guessit 3.0 uses different stuff and flexget breaks when using guessit 3.0. For me, I can't really understand why a file named uses guessit 3.0. Try to install and run flexget from nixos unstable or nixos unstable small. Please run and paste the results. system: host os: multi-user?: sandbox: version: channels(hyper): channels(root): nixpkgs:
Can you please check whether fixes your problem?
That's because of an accidental version update. I'm merging because it's a step in the right direction and closing this.
yep, that works fine now. Thx
Change:
<del> { lib, stdenv, fetchFromGitHub, fetchurl, makeWrapper, pcre2, coreutils, which, openssl, libxml2, cmake, z3, substituteAll, python3, </del> <ins> { lib, stdenv, fetchFromGitHub, fetchpatch, makeWrapper, pcre2, coreutils, which, openssl, libxml2, cmake, z3, substituteAll, python3, </ins> cc ? stdenv.cc, lto ? !stdenv.isDarwin }: stdenv.mkDerivation (rec {

Discussion:
Steps to reproduce the behavior: ponyc (or, actually - don't) Can be seen here: - but in summary: The new kernel headers removed DECNet and libponyrt had a dependency on it. The excellent opened a PR against ponyc to remove that dependency which was merged an in the current release. OHHAI (Note: I will be raising a PR to fix this in the next few hours)
Change:
stdenv.mkDerivation rec { name = "${product}-${version}"; product = "vivaldi"; <del> version = "1.15.1147.42-1"; </del> <ins> version = "2.1.1337.51-1"; </ins> src = fetchurl { url = "https://downloads.vivaldi.com/stable/${product}-stable_${version}_amd64.deb"; <del> sha256 = "15cajvn2sv05qdp3y538n2xvyy3il49q8zi5928z1mfirjz3dlwh"; </del> <ins> sha256 = "00rxp6rardxjg17g2b28y2rj8szqlainp4ga6c58z981zkxvdlls"; </ins> }; unpackPhase = ''

Discussion:
This probably isn't a strictly NixOS issue, but nevertheless should be mentioned. The hash for vivaldi-stable2.1.1337.51-1 has changed. The old one in nixpkgs is 08x6abyz65vx4ycj8ys8sib9z1adb8ybmnrqjck69b30kbz78rj2, while nix-env reports 00rxp6rardxjg17g2b28y2rj8szqlainp4ga6c58z981zkxvdlls. to unstable channels. -env -i vivaldi system: host os: multi-user?: sandbox: version: channels(void): channels(root): nixpkgs:
unfortunately, sometimes software projects update different package sources with different sha256sums on their website, which will then error during build, until it gets fixed again Can you add a Pull Request, updating the hash in
Change:
''; meta = with stdenv.lib; { <del> description = "A simple web browser based on WebKit/GTK"; </del> <ins> description = "A simple web browser based on WebKitGTK"; </ins> longDescription = '' <del> Surf is a simple web browser based on WebKit/GTK. It is able to display </del> <ins> surf is a simple web browser based on WebKitGTK. It is able to display </ins> websites and follow links. It supports the XEmbed protocol which makes it possible to embed it in another application. Furthermore, one can point surf to another URI by setting its XProperties.

Discussion:
Prefer Git revision rather release. Version 2.0 is from 2017-03-28.
Hello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use or on the relevant files to find them. Lastly, you can always ask for help at or at .
I created which addresses this issue.
Thanks! Since the time, I had my own version: Terminal [] []: [] []:
Feel free to change/add you to the maintainers if you want to.
Change:
gtk-engine-murrine ]; <del> dontBuild = true; </del> installPhase = '' runHook preInstall mkdir -p $out/share/themes/${themeName}

Discussion:
Describe the bug While building ant-theme 3.0 with latest master the following error occurs: To Reproduce Steps to reproduce the behavior: ant-theme Expected behavior builds Screenshots If applicable, add screenshots to help explain your problem. Additional context Add any other context about the problem here. Metadata system: host os: multi-user?: sandbox: version: channels(maciej): channels(root): nixpkgs: Maintainer information:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
fetch = { type = "git"; url = "https://go.googlesource.com/net"; <del> rev = "7f726cade0ab"; sha256 = "0zv5var5agbhd2mcn7lciwip0j49gxka73f0csvh3hvb1di068gn"; </del> <ins> rev = "ba9fcec4b297"; sha256 = "1hbqvy6r0s5h0dpdqw8fynl3cq0acin3iyqki9xvl5r8h33yb9bx"; </ins> }; } {

Discussion:
I can't compile on macOS: Metadata system: host os: multi-user?: sandbox: version: channels(eridius): nixpkgs: Maintainer information:
Change:
# Sadly, systemd-vconsole-setup doesn't support binary keymaps. vconsoleConf = pkgs.writeText "vconsole.conf" '' KEYMAP=${cfg.keyMap} <del> FONT=${cfg.font} </del> <ins> ${optionalString (cfg.font != null) "FONT=${cfg.font}"} </ins> ''; consoleEnv = kbd: pkgs.buildEnv {

Discussion:
NixOS's default kernel configuration only enables the 8x8 and 8x16 fonts. This is not ideal, because they are too small for high-resolution displays. The current workaround used by is to set . There are problems with this however: during early boot, before the GPU drivers are loaded, the firmware or bootloader may initialize the display at a lower resolution, resulting in an oversized font in fact, the hidpi module sets , which in my opinion is a bad idea, because it will force switching to a low resolution when the firmware could have set us up with a high-res framebuffer; this also breaks seamless boot for those who care (sd-boot's default is to keep the mode unchanged) resolution switches reset the font to the kernel default, and under certain circumstances it seems a race condition can prevent userspace from setting the font correctly again The kernel is actually able to select an appropriate font for the current resolution using a simple heuristic since mid-2019 (). This bypasses the problems listed above and ensures a good font is always selected after resolution switches. The only requirement appears to be that the fonts must be built into the kernel. Font-related kconfig options as configured by NixOS: Arch Linux: So Arch enables the default 8x16 and Terminus 16x32 (the same font that the hidpi module sets). The observed behavior on Arch is that it seamlessly switches fonts after mode switches, and I've never seen this break since it has been enabled.
Same issue here with a NVIDIA card and a 3840x1600 monitor. tty0 console text covers the entire screen. I couldn't resolve this issue manually with and (DP-3 is my monitor). Setting the font manually to the default value () gives the right font size but this particular font doesn't have antialiasing which looks quite bad on a HIDPI monitor.
There's no antialiasing in console fonts, they're all bitmap fonts.
Gotcha, thanks. On side note, I looked for a different consolefont and came up with this. Looks a lot better now :smile:
Change:
# Return ‘x’ if it evaluates, or ‘def’ if it throws an exception. try = x: def: let res = tryEval x; in if res.success then res.value else def; <del> defaultConfig = { # These attributes are used in pkgs/stdenv/generic/check-meta.nix allowBroken = builtins.getEnv "NIXPKGS_ALLOW_BROKEN" == "1"; allowInsecure = builtins.getEnv "NIXPKGS_ALLOW_INSECURE" == "1"; allowUnfree = builtins.getEnv "NIXPKGS_ALLOW_UNFREE" == "1"; allowUnsupportedSystem = builtins.getEnv "NIXPKGS_ALLOW_UNSUPPORTED_SYSTEM" == "1"; }; </del> in { # We combine legacy `system` and `platform` into `localSystem`, if

Discussion:
Describe the bug Unable to evaluate due to bug To Reproduce Expected behavior does a nix-review Additional context Add any other context about the problem here. Metadata