jiebi/CodeConvo huggingface dataset:
Change:
buildInputs = [ karchive kconfig kwidgetsaddons kcompletion kcoreaddons kguiaddons <del> ki18n kitemmodels kitemviews kwindowsystem kio kcrash </del> <ins> ki18n kitemmodels kitemviews kwindowsystem kio kcrash breeze-icons </ins> boost libraw fftw eigen exiv2 lcms2 gsl openexr libheif giflib openjpeg opencolorio poppler curl ilmbase qtmultimedia qtx11extras quazip

Discussion:
Krita requires breeze-icons for it's buttons which is currently either miss configured or missing. To Reproduce Steps to reproduce the behavior: nixos unstable krita without breeze-icons, missing icons on buttons. breeze-icons, icons show. Expected behavior Icons to show on buttons. Screenshots ! ! Additional context This is my first issue, I am kind of shaky on Nix packaging. Sorry if I got something wrong. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(wyatt): channels(root): nixpkgs:
Change:
llvmPackages.openmp SDL Cocoa CoreGraphics ForceFeedback OpenAL OpenGL ]) ++ optional jackaudioSupport libjack2 <del> ++ optional cudaSupport cudatoolkit </del> <ins> ++ optional cudaSupport cudatoolkit_11 </ins> ++ optional colladaSupport opencollada ++ optional spaceNavSupport libspnav; <del> pythonPath = with python39Packages; [ numpy requests ]; </del> <ins> pythonPath = with python310Packages; [ numpy requests ]; </ins> postPatch = '' # allow usage of dynamically linked embree

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 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: blender <!-- The current version can be found easily with the same process as 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: 2.93.5 desired version: 3.1 <!-- 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:
sed -i mkspecs/common/linux.conf  -e "/^QMAKE_INCDIR_OPENGL/ s|$|${libGL.dev or libGL}/include|"  -e "/^QMAKE_LIBDIR_OPENGL/ s|$|${libGL.out}/lib|" <ins> '' + lib.optionalString (stdenv.hostPlatform.isx86_32 && stdenv.cc.isGNU) '' sed -i mkspecs/common/gcc-base-unix.conf  -e "/^QMAKE_LFLAGS_SHLIB/ s/-shared/-shared -static-libgcc/" </ins> '' );

Discussion:
Seems to be related to /. Makes it so I can't use , which depends on it for some reason Update to latest git master nixpkgs Please run and paste the results. system: host os: multi-user?: sandbox: version: nixpkgs:
Got the same error when rebuilding my system on nixos-unstable channel relevant log:
I think previously this was fixed by using gcc6 instead of gcc7. Something like this for qtbase:
I am also having this problem. I have bisected it to
I attempted to apply 's suggestion to only qt packages. The failure is the same. Perhaps a dependency also needs to compile with gcc6? Is there a way to default the i686 packages to gcc6?
Maybe that would be a usable workaround. EDIT: at least it does make build again (for me). In any case, more in-depth discussion of this was in
that worked for almost everything. Except packages using . That causes a failure. EG: dhcp: I've overrideAttr the dhcp to confirm. There are ~10 other derivations using that warning. Is it necessary to override each individually?
FWIW, works around this, assuming you don't need gstreamer support of course...
gstreamerSupport in wine cause more problems than solve (concretely -- wrapper with gstreamer specific variables for wine64), but it completely unrelated for this case
it is unrelated to the ultimate cause, yes. It is still a useful workaround for the symptom that tadeokondrak was dealing with (being unable to build wine). I mis-judged whether or not that would be clear from context...
qtbase still fails to build on latest unstable and latest unstable-small.
Perhaps we can use that fix for now? Otherwise I'm not sure how to handle it without breaking something else.
That might solve on symptom of the problem but not the root cause. If I try to build wine on my x64 machine it wants to build some version of and that fails. Even with vcunat's patch it doesn't build.
I was able to compile (almost) the full plasma 5 desktop with: However, while that passes the plasma5 test on my branch I can't actually get plasma to run on my desktop. Nor can I get many QT apps to run.

Those issues may be regressions from until that's verified I'm reluctant to open a PR with those workarounds. Tho compiling and failing is better than not compiling for dev I suppose...
Change:
stdenv.mkDerivation rec { pname = "whitesur-gtk-theme"; <del> version = "2021-07-27"; </del> <ins> version = "2021-09-24"; </ins> src = fetchFromGitHub { owner = "vinceliuice"; repo = pname; rev = version; <del> sha256 = "17x4lqlv6whx8vg0c1nm89j7671l033apn4alqyhjb9qx5w2fa43"; </del> <ins> sha256 = "12dwmgq0kadjfky5bjm62vwgdlw3nmrrhqqs5iw15w0pn3mbmd5c"; </ins> }; nativeBuildInputs = [

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: whitesur-gtk-theme <!-- 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: "2021-07-27" desired version: 2021-09-24 <!-- 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:
stdenv.mkDerivation rec { pname = "openmm"; <del> version = "8.0.0"; </del> <ins> version = "8.1.0"; </ins> src = fetchFromGitHub { owner = "openmm"; repo = pname; rev = version; <del> hash = "sha256-89ngeZHdjyL/OoGuQ+F5eaXE1/od0EEfIgw9eKdLtL8="; </del> <ins> hash = "sha256-uNAqjklgBWM2v2z6qu17ZMFO4gn3fsnYPxyGO++UtTw="; </ins> }; # "This test is stochastic and may occassionally fail". It does.

Discussion:
Importing before other packages with C extensions results in with when the latter package is imported. In nixpkgs tree, on master: results in Note: this does not occur if the import order is switched: does not result in an error. Scipy is used as an example, but this also occurs when importing other packages with C extensions after openmm (e.g. rdkit): The above commands should not result in s. Seems likely to be a result of overriding and to use GCC 11 in (Removing these overrides results in a build failure with , so maybe not easy to fix..) <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --- system: host os: multi-user?: sandbox: version: channels(matt): channels(root): nixpkgs:
I am afraid it is the override of stdenv and gfortran. The override became necessary due to and and I am afraid for the moment I cannot fix both this issue and until the upstream problems are gone. However, only hits you if you compile the OpenCL kernels, so if disabling OpenCL in OpenMM is an option for you, you should be able to use plain and and work around the python import issue.
Ah, thanks! I don't need the OpenCL kernels, so this is an option for me. Confirmed that disabling OpenCL and overriding to use the default stdenv and gfortran is a solution: (no errors) :tada:
Change:
{ stdenv, fetchurl, glib, flex, bison, pkgconfig, libffi, python <del> , libintlOrEmpty, cctools </del> <ins> , libintlOrEmpty, cctools, cairo </ins> , substituteAll, nixStoreDir ? builtins.storeDir }: # now that gobjectIntrospection creates large .gir files (eg gtk3 case)

Discussion:
The typelib for cairo contains a non-absolute path: This means that the resulting call to will need a correctly set up to succeed. This in turn causes . Other typelibs contain absolute paths into the nix store (tested with the other typelib files from gobject-introspection and with pango 1.40.11). The above fails with . Awesome still tries to continue, but lots of stuff errors out. Sorry, but (a) I don't think this is necessary and (b) I cannot copy&paste from the VM and so this is quite non-trivial for me to provide. But it's x86_64-linux, NixOS 17.09.2799....
This can be actually fixed quite easily: Though there might be a problem with increased closure size?
Is it okay for me to read this as "this stops being broken and now actually depends on its dependencies"? ;-)
The issue is that the is not really needed by , only by the single GIR/typelib file. It would make more sense if the typelib were part of the package but apparently we cannot have nice things.
Libraries should always be hardcoded. What are the sizes with and without the change? I'm not familiar with this code, but maybe we can put it in a separate output.
How do I measure it? ? In that case it is 41M → 56M. That would work but we would need to check all packages depending on if they use the cairo typelib. And could only be found out during runtime.
I suggest merging your fix along with a comment/reference to this issue. Whoever wants to reduce the closure size can then look into multiple-outputs.
I do not really like it but at the moment I do not have time for the effort.
Fix () is in staging.
FYI
Can't we drop the file totally from the package and then patch the package to extract that file from ?
We could but it would make the packages needlessly complex and the different behaviour from upstream might be confusing.
Change:
# This file is autogenerated from update.sh in the same directory. <del> # VHASH: 5e5af2017fa2e05f11aa741c6f87fff0549b93e3bc2aa40e6cc0a0aff84ba010 </del> <ins> # VHASH: 545cfbcd1fc31d037d1e6b5382995075d2a875a51d181cc26851e49dbd2227d8 </ins> { dev = { <del> version = "21.0.1180.15"; url = "http://commondatastorage.googleapis.com/chromium-browser-official/chromium-21.0.1180.15.tar.bz2"; sha256 = "0ahsrsyw4928vg1kl3dv44q77ksp85crw6m7fy20nq46qihb0mxa"; </del> <ins> version = "22.0.1207.1"; url = "http://commondatastorage.googleapis.com/chromium-browser-official/chromium-22.0.1207.1.tar.bz2"; sha256 = "1kzzaaczz1mwsfw7fn8la6h4yls2wy537ypabqgwyim01jhfmilp"; </ins> }; beta = { <del> version = "20.0.1132.47"; url = "http://commondatastorage.googleapis.com/chromium-browser-official/chromium-20.0.1132.47.tar.bz2"; sha256 = "1rd1lfn9xchf4nrgi46van5aigqxj2n303890sslc4bcj6p8fkm3"; </del> <ins> version = "21.0.1180.41"; url = "http://commondatastorage.googleapis.com/chromium-browser-official/chromium-21.0.1180.41.tar.bz2"; sha256 = "1225ny7y5msyk44lb5dspd4aq0yiaawsb5xi9g8iimiv80j4h34a"; </ins> }; stable = { <del> version = "20.0.1132.47"; url = "http://commondatastorage.googleapis.com/chromium-browser-official/chromium-20.0.1132.47.tar.bz2"; sha256 = "1rd1lfn9xchf4nrgi46van5aigqxj2n303890sslc4bcj6p8fkm3"; </del> <ins> version = "20.0.1132.57"; url = "http://commondatastorage.googleapis.com/chromium-browser-official/chromium-20.0.1132.57.tar.bz2"; sha256 = "06v4ybvaj3gx1v4visfyfzbq2q3xasa8xlf05f4wi2bf62vcc98j"; </ins> }; }

Discussion:
I nixpkgs recently and got some strange zsh behavior. I have , so I'm not sure how to reproduce it properly yet. But there are some observations: it doesn't work properly with starship which is RPROMPT: ! Note where is the cursor - it's behind the arrow and once it type anything it overwrites the arrow. Also RPROMPT is not aligned properly - it has too much space at the right border which wasn't the case before. tab completion also suffers: ! Here I just typed and then pressed TAB for completion, and it printed echo at wrong position, making it printed twice (if I press backspaces it just deletes second printed echo and stops). And finally remote building doesn't work for me anymore - it just hangs at ssh attempt (I see the established connection on the builder but it does nothing). It might be related to shell, but might be a completely different problem. Steps to reproduce the behavior: not sure yet I'm filling this issue in a hope that someone might know what has recently changed. Will try to investigate it further and add an additional info here.
Hm, my locales are also broken - I can type only English letters in my terminals. Also it seems zsh has problems only when starship is enabled.
Yet another observation - midnight commander can render only ascii symbols now in it's UI.
Looks like something is wrong with locale generation:
ok, found the problem. I was overriding and didn't have there. It somehow worked before the update, but broke after. Adding it to supportedLocales fixed the problem.
Change:
users.users.gnunet = { group = "gnunet"; description = "GNUnet User"; <del> home = homeDir; createHome = true; </del> uid = config.ids.uids.gnunet; };

Discussion:
After enabling the GNUnet service with , it prints a lot of errors at startup: Additionally, attempting to stop the deamon with reveals that it is apparently not even running: Please run and paste the result.
Change:
''; in mkDerivation rec { pname = "deadd-notification-center"; <del> version = "2.0.4"; </del> <ins> version = "2.1.1"; </ins> src = fetchFromGitHub { owner = "phuhl"; repo = "linux_notification_center"; rev = version; <del> hash = "sha256-ascg31HsHeXKhvMNntiRLuZ4+T2+fokfDhZ3c8N/Gzg="; </del> <ins> hash = "sha256-VU9NaQVS0n8hFRjWMvCMkaF5mZ4hpnluV31+/SAK7tU="; </ins> }; isLibrary = false;

Discussion:
Package name: -notification-center Latest released version: 2.1.1 <!-- Search your package here: --- Current version on the unstable channel: 2.0.4 Current version on the stable/release channel: <!-- 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:
pythonImportsCheck = [ "tensorflow" <del> "tensorflow.keras" </del> "tensorflow.python" "tensorflow.python.framework" ];

Discussion:
Build of failed on x86_64-linux as of . This is currently breaking python3Packages.tensorflow-bin. python3Packages.tensorflow-bin maintainers cc: python39Packages.tensorflow maintainers cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tag:
I'm not quite sure why this doesn't have the same internal tag as they seem to be the same AFAICT.
oh I see... the hashes in /nix/store/[hash]-pname-version for each of the dependencies changed. hmmmm
Change:
, configTemplate , configTemplatePath ? null , libnvidia-container <ins> , cudaPackages </ins> }: assert configTemplate != null -> (lib.isAttrs configTemplate && configTemplatePath == null);

Discussion:
Project description The NVIDIA Container Toolkit CLI provides a number of utilities that are useful for working with the NVIDIA Container Toolkit. Metadata homepage URL: source URL: license: Apache License platforms: linux More Info Looks some of the related tools for the container runtime. Have already been included. But not . Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: Current version on the stable/release channel: <!-- 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. -- Latest nvidia driver , which is linked against. for inclusion of into a container. Without it, OpenGL inside container is broken. Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
As a workaround, I mount into the container explicitly.
Change:
firestr = throw "firestr has been removed."; # added 2019-12-08 fish-foreign-env = throw "fish-foreign-env has been replaced with fishPlugins.foreign-env"; # added 2020-12-29, modified 2021-01-10 flameGraph = flamegraph; # added 2018-04-25 <ins> flink_1_5 = throw "flink_1_5 was removed, use flink instead"; # added 2021-01-25 </ins> flvtool2 = throw "flvtool2 has been removed."; # added 2020-11-03 foldingathome = fahclient; # added 2020-09-03 font-awesome-ttf = font-awesome; # 2018-02-25

Discussion:
, CVSSv3=7.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc

, CVSSv3=7.5 (nixos-20.09, nixos-unstable) CVSSv3=7.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc
Change:
<ins> { lib, fetchzip }: # Source Sans Pro got renamed to Source Sans 3 (see # https://github.com/adobe-fonts/source-sans/issues/192). This is the # last version named "Pro". It is useful for backward compatibility # with older documents/templates/etc. let version = "3.006"; in fetchzip { name = "source-sans-pro-${version}"; url = "https://github.com/adobe-fonts/source-sans/archive/${version}R.zip"; postFetch = '' mkdir -p $out/share/fonts/{opentype,truetype,variable} unzip -j $downloadedFile "*/OTF/*.otf" -d $out/share/fonts/opentype unzip -j $downloadedFile "*/TTF/*.ttf" -d $out/share/fonts/truetype unzip -j $downloadedFile "*/VAR/*.otf" -d $out/share/fonts/variable ''; sha256 = "sha256-uWr/dFyLF65v0o6+oN/3RQoe4ziPspzGB1rgiBkoTYY="; meta = with lib; { homepage = "https://adobe-fonts.github.io/source-sans/"; description = "Sans serif font family for user interface environments"; license = licenses.ofl; platforms = platforms.all; maintainers = with maintainers; [ ttuegel ]; }; } </ins>

Discussion:
The font as installed by the package, is now called . This breaks all references to the font in documents, but also in web pages, etc. The font Open this webpage: The logo uses the Source Sans Pro font and it should look correct when the package is installed. Instead, it shows an alternative font with serif. The font should be called and not , keeping all references. If this was not desirable (because the font is just too different) then a package should be provided to install the old version with the old name. Please run and paste the result.
The upstream name change was intentional (adobe-fonts/source-serif).
Thank you andersk that explains a lot! I guess then it makes sense to also install the older version? Edit: or provide it as a separate package.
We should be able to deal with this through fontconfig.
If I understand correctly, it's not only the name that has been changed, but the renamed font has also different metrics. This means that if we just configure fontconfig to replace "Source Sans Pro" with "Source Sans 3", the layout of existing documents might change. So I think, it would make sense to either reintroduce Pro fonts as a separate package, or include the older (Pro) version together with the new one (which is what ). If is interested, I can turn , which does the former, to a PR.
I agree. Either of these two solutions would be satisfying to me.
I wasn't aware of the metrics changes. I think adding the older version back as a new package makes perfect sense, thank you!
Change:
postFixup = '' addToSearchPath program_PYTHONPATH $out/${python.sitePackages} patchPythonScript $out/share/matrix.py <ins> substituteInPlace $out/${python.sitePackages}/matrix/server.py --replace "matrix_sso_helper" "$out/bin/matrix_sso_helper" </ins> ''; meta = with lib; {

Discussion:
Describe the bug weechat-matrix script cannot find the helper binary that's used when logging in to matrix homeservers that require sso To Reproduce an override to weechat to add weechat script logging in to a homeserver that requires SSO Actual results Weechat prints a message: Expected behavior weechat-matrix should print a link that user's supposed to click in browser Notify maintainers Metadata system: host os: multi-user?: sandbox: version: nixpkgs: Maintainer information:
I locally hacked an overlay that works by making the path to static:
This solution looks reasonable (replace the wildcard by the actual file name and use instead of ). Would you mind opening a PR fixing this?
Change:
KERNEL=="nvidia_uvm", RUN+="${pkgs.runtimeShell} -c 'mknod -m 666 /dev/nvidia-uvm-tools c $$(grep nvidia-uvm /proc/devices | cut -d   -f 1) 1'" ''; hardware.opengl = { <del> extraPackages = [ nvidia_x11.out ] ++ (lib.optional (builtins.hasAttr "libXNVCtrl" nvidia_x11.settings) nvidia_x11.settings.libXNVCtrl); </del> <ins> extraPackages = [ nvidia_x11.out ]; </ins> extraPackages32 = [ nvidia_x11.lib32 ]; }; environment.systemPackages = [ nvidia_x11.bin ];

Discussion:
Going by , I would not trust to work reliably with a different version of the Nvidia driver. It may happen to work with some version combinations if the protocol versions happen to match, but could break at any time if an update makes the protocols not match.
I should have looked at the history before posting my previous comment. The comment has not changed since at least , so it is quite stable. The also appears to be between client and , rather than between the library and the driver.
If we confirm this to work, I'd suggest we move into a separate package in , except that we write it in a generic manner so that each variant of can override it with different sources
Change:
sierra-gtk-theme = callPackage ../data/themes/sierra { }; <ins> sil-padauk = callPackage ../data/fonts/sil-padauk { }; </ins> snap7 = callPackage ../development/libraries/snap7 {}; snowblind = callPackage ../data/themes/snowblind { };

Discussion:
Project description Add SIL Padauk - Burmese Unicode 6 TrueType font. Metadata homepage URL: source URL: license: ofl platforms: all
Change:
<del> { stdenv, fetchurl, p7zip }: stdenv.mkDerivation rec { version = "1.13.2"; name = "inziu-iosevka-${version}"; package = fetchurl { url = "http://7xpdnl.dl1.z0.glb.clouddn.com/inziu-iosevka-ttfs-${version}.7z"; sha256 = "1i7qqcv1x6s1xkp687wq79zqg9ly6a7l5mnmg1iqgfgcbglgjbaw"; }; nativeBuildInputs = [ p7zip ]; unpackPhase = '' 7z x $package ''; installPhase = '' mkdir -p $out/share/fonts/truetype cp *.ttf $out/share/fonts/truetype ''; meta = with stdenv.lib; { description = "Inziu Iosevka font"; homepage = https://be5invis.github.io/Iosevka/inziu; # license is clarified here: https://github.com/be5invis/Iosevka/issues/265 license = licenses.ofl; maintainers = [ maintainers.ChengCat ]; platforms = platforms.all; # large package, mainly i/o bound hydraPlatforms = []; }; } </del>

Discussion:
Hi Could you please note that Inziu is already deprecated and it is replaced by Sarasa Gothic/Sarasa Mono? Yours Sincerely, Belleve
This has been discussed here: Due to stability reasons, I need Inziu Iosevka for myself at least for now, and it may also be helpful to others. Just out of curiosity, why do you want a font to be deprecated? I suppose different fonts have different styles, and could be useful in different cases.
Because I lost its building system (after an PC replace). If you want to keep that please mirror its files to GitHub.
I am sorry to hear that. I'll do the mirroring work tomorrow.
I changed my mind to remove this font due to license issues. ()
closing after font was removed