jiebi/CodeConvo huggingface dataset:
Change:
glib gtk-layer-shell gtk3 <ins> gvfs </ins> json-glib libgee libhandy <ins> libnotify </ins> libpulseaudio librsvg pantheon.granite

Discussion:
(still as of at the time of writing, but ever since ) is missing the runtime dependency which, , is required to fix (which is the issue I am experiencing). Please take a look at the original issue on the upstream repository linked prior, as everything mentioned there is identical (to the behaviour on my machine). I have read on the and which I saw was left unresponded. This issue was opened to hopefully clear up the need for this missing dependency. This is my first time contributing to , so I want to apologise in advance in case I am doing anything wrong here. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
feel free to patch the package, I can't look into it :(
Change:
, qtwayland , wayland , wrapQtAppsHook <ins> , kdePackages </ins> }: stdenv.mkDerivation rec { pname = "CopyQ"; <del> version = "7.1.0"; </del> <ins> version = "8.0.0"; </ins> src = fetchFromGitHub { owner = "hluk"; repo = "CopyQ"; rev = "v${version}"; <del> hash = "sha256-aAmpFKIIFZLPWUaOcf4V1d/wVQ7xRcnXFsqFjROsabg="; </del> <ins> hash = "sha256-Ewunl4k9f0aDjilhKAsVxwR3S6uSZ1xwtu6ccNsNOgk="; </ins> }; <del> patches = [ # itemfakevim: fix build with qt 6.6.0 # https://github.com/hluk/CopyQ/pull/2508 (fetchpatch2 { url = "https://github.com/hluk/CopyQ/commit/a20bfff0d78296b334ff8cabb047ab5d842b7311.patch"; hash = "sha256-F/6cQ8+O1Ttd4EFFxQas5ES6U+qxWdmYqUWRQLsVMa4="; }) ]; </del> nativeBuildInputs = [ cmake ninja <del> extra-cmake-modules </del> <ins> kdePackages.extra-cmake-modules </ins> wrapQtAppsHook ];

Discussion:
Package name: copyq Latest released version: Current version on the unstable channel: 7.1.0 Current version on the stable/release channel: 7.1.0 Notify maintainers
Change:
[ kernelPatches.bridge_stp_helper kernelPatches.cpu-cgroup-v2."4.9" kernelPatches.modinst_arg_list_too_long <ins> # https://github.com/NixOS/nixpkgs/issues/42755 # Remove these xen-netfront patches once they're included in # upstream! Fixes https://github.com/NixOS/nixpkgs/issues/42755 kernelPatches.xen-netfront_fix_mismatched_rtnl_unlock kernelPatches.xen-netfront_update_features_after_registering_netdev </ins> ]; };

Discussion:
Network access works well on a new instance booted from the stable AMIs listed on the website, but after running and rebooting the instance, it is broken. More specifically, the host can no longer send packets with an MSS larger than 3836. two EC2 instances from one of the 18.03 AMIs in the same VPC one of them latest stable with and reboot the security group to allow internal VPC communication on the host without the updates and on the updated one As I was writing this, I dug a bit deeper and found out that this is a bug introduced in the 4.14.37 release of the kernel. It is fixed in master (commit and possibly .) Applying those patches to the 4.14.51 kernel in stable fixes this issue for me.
Fix is now backported to 18.03.
Change:
<ins> { lib, bundlerApp, bundlerUpdateScript, makeWrapper, gnugrep, libinput }: bundlerApp { pname = "fusuma"; gemdir = ./.; exes = [ "fusuma" ]; nativeBuildInputs = [ makeWrapper ]; postBuild = '' wrapProgram "$out/bin/fusuma"  --prefix PATH : ${lib.makeBinPath [ gnugrep libinput ]} ''; passthru.updateScript = bundlerUpdateScript "fusuma"; meta = with lib; { description = "Multitouch gestures with libinput driver on X11, Linux"; homepage = "https://github.com/iberianpig/fusuma"; license = licenses.mit; maintainers = with maintainers; [ nicknovitski Br1ght0ne ]; platforms = platforms.linux; }; } </ins>

Discussion:
Package name: fusuma Latest released version: 3.5.0 <!-- Search your package here: --- Current version on the unstable channel: 3.3.1 Current version on the stable/release channel: 3.3.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. Add a :+1: [reaction] to [issues you find important]. By the way, fusuma now use yml file instead of yaml file as config file. now when I use HM , it will generate a yaml file in .config, please update it to change it to a yml file. and when I use = true; it wont be installed. [reaction]: [issues you find important]:
I guess that this should be addressed at home-manager repository as nixpkgs does not offer a fusuma service, as far as I rembember
you are right
Already fixed in home-manager:
sorry, I don't understand. if it has been fixed, why I still have the same issue? I just installed yesterday.
Are you perhaps not on ?
ah, right. I use stable nixos and HM, install some new software with pkgs-unstable. But this is a service, how do I change the package to unstable version? I tried = pkgs- But the result is still same.
It's fixed on master branch of Home Manager and not have been backported to release-23.11. Home manager master always follows the NixOS unstable branch, so I won't suggest switching to master branch of HM unless you upgrade your system to nixos-unstable.
Change:
stdenv.mkDerivation (finalAttrs: { pname = "plymouth"; <del> version = "23.356.9"; </del> <ins> version = "23.360.11"; </ins> outputs = [ "out" "dev" ];

Discussion:
On my work laptop, the boot is often stuck at “Starting Show Plymouth Boot Screen” (After a timeout, rescue prompt will appear but it will be possible to enter any commands because “cannot open access to console the root account is locked”. If I set , I am able to proceed.) The logs reveal that Plymouth crashed: Happens even if I remove console font = "Lat2-Terminus16";systemd-vconsole-setup.service. Steps to reproduce the behavior: on a computer. that full-disk-encryption password prompt never appears. User should be asked for LUKS password, either by Plymouth, or if it crashes, by systemd. I managed to pinpoint it to plymouth crash with 23.356.9 but the same symptoms appeared in earlier generations as well (although less frequently). coredumpctl cannot find any coredumps in the emergency shell. Relevant configuration: cc NixOS Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Same issue on
Change:
broken = !(cudaSupport || rocmSupport) # At least one back-end enabled || (cudaSupport && rocmSupport) # Mutually exclusive <del> || (cudaSupport && strings.versionOlder cudaVersion "9"); </del> <ins> || (cudaSupport && cudaOlder "9.0"); </ins> }; }

Discussion:
Build of failed on x86_64-linux as of . This is currently breaking . python3Packages.torchvision maintainers cc: magma maintainers cc: Other cc: n/a nixpkgs at commit Contents of : This issue was automatically generated by . that created this issue. Internal tags:
This is also breaking atm
This shows that fortran name mangling is using the underscore ``. (See ) Magma should have the flag "-DADD" set during compilation to fix this
And, in fact, clmagma already sets :
Both of the following overlays fixed the problem: Specify the fortran name mangling convention To explain this, in , we see that if USEFORTRAN=off then the FORTRANCONVENTIONS flag is set and also copied to CFLAGS and CXXFLAGS. FORTRANCONVENTIONS is copied outside of this block into the NVCCFLAGS, and DEVCCFLAGS (which can't otherwise be set), so all three flags are necessary if we use the default of USE_FORTRAN=on. Disable fortran in magma
Nice! Would you be interested in turning that into a PR? It'd be great to fix on master!
Change:
, apulse # Media support (implies audio support) <del> , mediaSupport ? false </del> <ins> , mediaSupport ? true </ins> , ffmpeg , gmp

Discussion:
Describe the bug Tor Browser does not correctly display audio/video streams, and instead tries to download it. To Reproduce Steps to reproduce the behavior: Tor Browser. an audio or video stream such as or Expected behavior The stream should play correctly as it does on Tails. Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
I just noticed that there is a parameter which is set to false by default. I guess this bug is actually intentional then.
By using I figured that you can manually override the package like this: The Tor Browser appears to work fine with this adjustment, and it's still relatively safe because NoScript blocks multimedia by default as well. So I suggest that be changed to by default.

Describe the bug Tor Browser doesn't show the thumbnail icons for search engines. To Reproduce Steps to reproduce the behavior: the search bar in Tor Browser. something. Expected behavior The icons should appear as they do in Firefox on NixOS, and on Tor Browser on other platforms. Screenshots ! Additional context Add any other context about the problem here. Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
This worked in 9.0.5 but has stopped working since. In 9.0.9 there are no search engine thumbnails. Please reopen.
if this was originally fixed by , a new bug should be opened - the issue is likely a different one this time.
Change:
sha256 = "043g0gnjc7wn1szvrs0rc1vvrq1qmhqh45b0y2kwrlxsgprpv8ll"; }; <del> nativeBuildInputs = [ fontforge ] ++ (with python2Packages; [ python fonttools ]); </del> <ins> nativeBuildInputs = (with python3Packages; [ python fonttools fontforge ]); </ins> postPatch = '' rm *.otf

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:
dosbox-staging = callPackage ../applications/emulators/dosbox-staging { }; <ins> eiciel = callPackage ../tools/filesystems/eiciel { }; </ins> emu2 = callPackage ../applications/emulators/emu2 { }; apt = callPackage ../tools/package-management/apt { };

Discussion:
Project description Eiciel is a viewer/editor for ACLs and xattrs. It integrates with Nautilus, but also works standalone. Metadata homepage URL: source URL: license: gpl2+ platforms: linux
Change:
sed -i -e '/qmltermwidget/d' cool-retro-term.pro ''; <del> buildInputs = [ qtbase qtquick1 qmltermwidget ]; </del> <ins> buildInputs = [ qtbase qtquick1 qmltermwidget qtquickcontrols qtgraphicaleffects ]; </ins> nativeBuildInputs = [ makeQtWrapper ]; 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:
{ lib, stdenv, <del> clangStdenv, </del> fetchFromGitHub, opencl-headers, cmake,

Discussion:
Describe the bug I'm not sure what's exactly going on here, but it looks like the build is attempting to use gcc10 includes from somewhere, while the default nvcc from cudatoolkit only supports gcc9 at best. Maybe someone better versed with how cmake works on NixOS could take a look? To Reproduce Steps to reproduce the behavior: to build from nixpkgs (). Expected behavior The package builds successfully with CUDA support. Additional context Persists after version bump Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --cc Maintainer information:
Change:
runHook postInstall ''; <del> postInstall = (makeDesktopItem { name = "zoom-us"; exec = "$out/bin/zoom-us %U"; icon = "$out/share/zoom-us/application-x-zoom.png"; desktopName = "Zoom"; genericName = "Video Conference"; categories = "Network;Application;"; mimeType = "x-scheme-handler/zoommtg;"; }).buildCommand + '' </del> <ins> postInstall = '' mkdir -p $out/share/{applications,appdata,icons} # Desktop File cp ${desktopIntegration}/us.zoom.Zoom.desktop $out/share/applications substituteInPlace $out/share/applications/us.zoom.Zoom.desktop  --replace "Exec=zoom" "Exec=$out/bin/zoom-us" # Appdata cp ${desktopIntegration}/us.zoom.Zoom.appdata.xml $out/share/appdata # Icons for icon_size in 64 96 128 256; do path=$icon_size'x'$icon_size icon=${desktopIntegration}/us.zoom.Zoom.$icon_size.png mkdir -p $out/share/icons/hicolor/$path/apps cp $icon $out/share/icons/hicolor/$path/apps/us.zoom.Zoom.png done </ins> ln -s $out/share/zoom-us/zoom $out/bin/zoom-us '';

Discussion:
Describe the bug is missing its icon, because it does not appear in the source tarball. I see a couple of options to fix: the icon separately, perhaps from the source to one of the packaged releases for another distro that includes the icon cc Maintainer information:
I would install the desktop file and appdata from there as well :+1:
Change:
{input="viostor"; output="viostor";} {input="viorng"; output="viorng";} ]; <del> in lib.concatStringsSep "n" ((map (copy "amd64" "w8.1") virtio) ++ (map (copy "x86" "w8.1") virtio)); </del> <ins> in '' runHook preInstall ${lib.concatStringsSep "n" ((map (copy "amd64" "w10") virtio) ++ (map (copy "x86" "w10") virtio))} runHook postInstall ''; </ins> meta = with lib; { description = "Windows VirtIO Drivers"; homepage = "https://fedoraproject.org/wiki/Windows_Virtio_Drivers"; <ins> license = [ licenses.bsd3 ]; </ins> maintainers = [ maintainers.tstrobel ]; platforms = platforms.linux; };

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: win-virtio <!-- 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: 0.1.141-1 desired version: 0.1.204-1 maintainers: Hi Linus, the original maintainer---Thomas Strobel---appears to be unavailable on GH, so I just tagged you since you made the last version update a few years ago. I'll submit a PR for this myself though.
Good catch, and thanks for the ping :) I think 0.1.141-1 was the stable version at the time, not sure if we want stable or latest? I don't really mind either way though.
Why not package both?
Good point. Using stable seems sensible in this case, it looks like very little time has elapsed between them anyway so I doubt there's much value in bumping to latest. I'll stick with that if there's no objection.

name: win-spice <!-- 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: 0.11 desired version: 0.21 Note that this is a collection of components with separate version numbers, the package version is taken only from one of them. The following updates also should be made: qxlwddm: 0.11 -0.21 usbdk: 1.0.4 -1.0.22 vdagent: 0.7.3 -0.10.0 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Hi Fortune, the original maintainer---Thomas Strobel---appears to be unavailable on GH, so I just tagged you since you fixed the 7z issue recently. I'll submit a PR for this myself though.
Change:
freetype systemd libpulseaudio <ins> cairo gdk-pixbuf gtk3 pixman </ins> ]; libPath = lib.makeLibraryPath packages; in

Discussion:
Can't start virtual device: qemu libpixmin not found. Steps to reproduce the behavior: Genymotion any Android device it An android VM is started Here is log: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
ln -s "$out/share/PrusaSlicer/icons/PrusaSlicer-gcodeviewer_192px.png" "$out/share/pixmaps/PrusaSlicer-gcodeviewer.png" ''; <del> desktopItems = [ (makeDesktopItem { name = "prusa-slicer"; exec = "prusa-slicer"; icon = "PrusaSlicer"; comment = "G-code generator for 3D printers"; desktopName = "PrusaSlicer"; genericName = "3D printer tool"; categories = [ "Development" ]; }) (makeDesktopItem { name = "prusa-gcodeviewer"; exec = "prusa-gcodeviewer"; icon = "PrusaSlicer-gcodeviewer"; comment = "G-code viewer for 3D printers"; desktopName = "PrusaSlicer G-code Viewer"; genericName = "G-code Viewer"; categories = [ "Development" ]; }) ]; </del> meta = with lib; { description = "G-code generator for 3D printer"; homepage = "https://github.com/prusa3d/PrusaSlicer";

Discussion:
A clear and concise description of what the bug is. The prusa-slicer package has duplicate desktop files Steps to reproduce the behavior: package there are duplicate icons in menus There should only be one of each desktop file: Gcode viewer and slicer. Instead there are two of each. If applicable, add screenshots to help explain your problem. ! Please run and paste the result.
Looks like we can drop our generated desktop items in favor of the defaults They dont need patching either since it's not using absolute paths
Change:
{ lib, stdenv, fetchFromGitHub, cmake, boost, glog, leveldb, marisa, opencc, <del> yaml-cpp, gtest, capnproto, pkg-config, plugins ? [ ] }: </del> <ins> yaml-cpp, gtest, capnproto, pkg-config, librime-lua, plugins ? [ librime-lua ] }: </ins> let copySinglePlugin = plug: "cp -r ${plug} plugins/${plug.name}";

Discussion:
Project description as a substitute of librime, librime-lua add lua engine to librime, so we can extend rime by lua. Many schemas of rime use librime-lua but not rime. So please add librime-lua. Metadata homepage URL: source URL: license: bsd3 platforms: linux
I do not think we have in Nixpkgs. Let's reopen this.
Change:
# Tests a additional requirements doCheck = false; <del> # Circular import # pythonImportsCheck = [ "dash_bootstrap_components" ]; </del> <ins> pythonImportsCheck = [ "dash_bootstrap_components" ]; </ins> meta = with lib; { description = "Bootstrap components for Plotly Dash";

Discussion:
Importing as recommended in the docs should work. The circular import was notificed by the expression author: ,L32 Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
(optionalAttrs has-owner { owner = head splitted; })); }; } { case = isAttrs; <del> out = let { version = arg.version or "dev"; src = (arg.fetcher or fetcher) (location // (arg.location or {})); }; } </del> <ins> out = { version = arg.version or "dev"; src = (arg.fetcher or fetcher) (location // (arg.location or {})); }; } </ins> { case = isPath; out = { version = "dev" ;

Discussion:
According to our investigation seems to be invalid syntax. Steps to reproduce the behavior: No error. I'm writing a parser for Nix and this breaks it. It is also the only occurrence of the syntax.
CC
The should probably be removed.