jiebi/CodeConvo huggingface dataset:
Change:
gettext gmp iconv <ins> imap </ins> intl ldap mbstring

Discussion:
this package () is not available for any platforms. When I try to install the package from the shell To be available for popular platform like x86/amd64. arm64 If applicable, add screenshots to help explain your problem. Add any other context about the problem here. : Answered me by email. Merci :) <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
For the context: I use the wrapper layer of Nix Package Manager and docker with
The extension is a core PHP extension and therefore, it is already available. On my side, I succeeded to test with my own project (loophp/nix-shell) by doing: a random file containing: in or . : in the same directory The thing is that is not in NixOS, if you want to enable it, you have to add it explicitly. The syntax to use is: Hope this helps.
Dear , I guess we can now close this issue ?
any idea why ?
No, but this is a good question, I guess or might help here.
So I did some digging into this, because it's a very good question. The reason for it not being enabled by default on darwin is because it wasn't enabled by default before we migrated to our modular build of PHP. The latest release branch before the modular build was 19.09 and here's the PHP definition from that time, where I have highlighted the line that we emulated by leaving it disabled after that big refactoring: -- so in 19.09 it was disabled on darwin. Inspecting that line further, the last time it was changed before that I linked it as of 19.09 was as part of a refactoring in July 2018: -- however, this commit actually didn't change the fact if it was enabled or not. So looking back ever further I found this, the commit authored in June 2016: That made a bunch of changes to the PHP definition, in which, one of the changes was to disable the imap extension on darwin. So I would assume that at that time, in June 2016, either as a dependency or the PHP extension itself actually didn't build on darwin, hence it was disabled to make PHP build at all on darwin.

Digging deeper: Here's the PR for that latest commit to fix the build back in 2016: And the corresponding issue: In the issue we can conclude that didn't build on darwin at that time. So it was a reasonable desicsion back then to disable that extension. Of course... now... 6 years later... this may not be a problem anymore and maybe we should revisit this :wink:
So now we have the PR merged to build on darwin, which sholud be a good first step to enable the imap extension:
Change:
<del> { lib, buildPythonApplication, fetchFromGitHub, python, pyyaml, fonttools, fontforge }: </del> <ins> { lib, buildPythonApplication, fetchFromGitHub, python, pyyaml, fonttools, fontforge, setuptools, }: </ins> buildPythonApplication { pname = "scfbuild";

Discussion:
Steps to reproduce the behavior: on current master, system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Error in logs from : Upstream maintenance status for this is quite questionable, current repo for is archived since 2018: It is a 20 min build on hydra for resulting fonts that are unlikely to ever change. Fix for is pretty easy - just patching distutils part and add to dependencies (or even remove that check altogether because fonttools version in nixpkgs has been over 2.5 for years): But considering it is archived it may be better to either drop both (as nothing else seem to depend on ) or switch to release tarball similar to :
I wouldn't remind emojione being removed if there's a useful alternative. I don't know of a good way to get complete coverage over emojis, and so far I've installed emojione, nerdfonts, noto-fonts, stix-two, and twemoji-color-font, none of which seem to cover any of the other emoji code points completely.
Potentially related: and Potential fix: or
Change:
<del> { stdenv, autoreconfHook, pkgconfig, SDL2, SDL2_mixer, SDL2_net, fetchFromGitHub }: </del> <ins> { stdenv, autoreconfHook, pkgconfig, SDL2, SDL2_mixer, SDL2_net, fetchFromGitHub, fetchpatch }: </ins> stdenv.mkDerivation rec { pname = "crispy-doom";

Discussion:
, CVSSv3=9.8 (nixos-unstable) Scanned versions: nixos-unstable: . May contain false positives. Cc
Fixed:
Change:
<ins> { godot, lib }: # https://docs.godotengine.org/en/stable/development/compiling/compiling_for_x11.html#building-export-templates godot.overrideAttrs (oldAttrs: rec { pname = "godot-export-templates"; sconsFlags = "target=release platform=x11 tools=no"; installPhase = '' # The godot export command expects the export templates at # .../share/godot/templates/3.2.3.stable with 3.2.3 being the godot version. mkdir -p "$out/share/godot/templates/${oldAttrs.version}.stable" cp bin/godot.x11.opt.64 $out/share/godot/templates/${oldAttrs.version}.stable/linux_x11_64_release ''; outputs = [ "out" ]; meta.description = "Free and Open Source 2D and 3D game engine (export templates)"; meta.maintainers = with lib.maintainers; [ twey jojosch ]; }) </ins>

Discussion:
Project description made with godot engine it does not run with steam-run (), so a proper package would be great Metadata homepage URL: source URL: license: Blue Oak Model License platforms: linux, darwin, windows
Change:
''; postInstall = lib.optionalString libOnly '' <del> rm -rf $out/{bin,share,etc,lib/{pulse-*,systemd}} </del> <ins> find $out/share -maxdepth 1 -mindepth 1 ! -name "vala" -prune -exec rm -r {} ; find $out/share/vala -maxdepth 1 -mindepth 1 ! -name "vapi" -prune -exec rm -r {} ; rm -r $out/{bin,etc,lib/pulse-*} </ins> '' + '' moveToOutput lib/cmake "$dev"

Discussion:
As I am trying to port the budgie desktop form the abandoned PR A of my port results in the error: mentioned this may be due to missing introspection files in the libpulseaudio package. The relevant part of the derivation is:
It ought to be sufficient to add to PulseAudioʼs and to .
Apparently, libpulse is not based on GObject so it does not provide introspection. It should install VAPIs though, not sure why it is not happening.
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've recently been trying to build budgie as well, and have run into the same issue. Was any solution found? Here's my derivation:
Looking at it again, the issue is that the vapi files (in ) are removed here: So you would either need to fix that in nixpkgs, or use the gigantic package instead.
Would a fix in nixpkgs just be removing all of $out/share except for any .vapi (and possibly .deps) files?
Correct. Or rather, the whole directory should be preserved.
Change:
rmatio = [ pkgs.zlib.dev ]; Rmpfr = [ pkgs.gmp pkgs.mpfr.dev ]; Rmpi = [ pkgs.openmpi ]; <del> RMySQL = [ pkgs.zlib pkgs.mysql.connector-c pkgs.openssl.dev ]; </del> <ins> RMariaDB = [ pkgs.mariadb.connector-c.dev ]; RMySQL = [ pkgs.zlib pkgs.mysql.connector-c.dev pkgs.openssl.dev ]; </ins> RNetCDF = [ pkgs.netcdf pkgs.udunits ]; RODBCext = [ pkgs.libiodbc ]; RODBC = [ pkgs.libiodbc ];

Discussion:
I had this issue as well on "19.09.976.". I wasn't able to build either or . In the latter case, it looks like needs to have in its stage. It also seemed to me that it wasn't getting the correct libraries passed to it. You can fix it with an overlay like this:
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . 3. Ask on the on .
In the meantime (20.09 at least), you have to use instead of .
I marked this as stale due to inactivity. &rarr;
RMariaDB probably still fails to build, as there's no fix in . I just need to port my fix from 19.09 to master.
For the record on recent Nixpkgs versions, package correctly builds. I think we can close this issue now.
Change:
nix-store --init <del> cp -r ${pkgs-path + "/lib"} lib cp -r ${pkgs-path + "/pkgs"} pkgs cp -r ${pkgs-path + "/default.nix"} default.nix cp -r ${pkgs-path + "/nixos"} nixos cp -r ${pkgs-path + "/maintainers"} maintainers cp -r ${pkgs-path + "/.version"} .version cp -r ${pkgs-path + "/doc"} doc </del> <ins> cp -r ${pkgs-path}/lib lib cp -r ${pkgs-path}/pkgs pkgs cp -r ${pkgs-path}/default.nix default.nix cp -r ${pkgs-path}/nixos nixos cp -r ${pkgs-path}/maintainers maintainers cp -r ${pkgs-path}/.version .version cp -r ${pkgs-path}/doc doc </ins> echo "Running pkgs/top-level/release-attrpaths-superset.nix" nix-instantiate --eval --strict --json pkgs/top-level/release-attrpaths-superset.nix -A names > /dev/null

Discussion:
This blocks all three unstable channels. For log see e.g. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
platforms = platforms.linux; }; }; <ins> # FIXME: check if this downgrade is still required when bumping gerbolyze # https://github.com/jaseg/gerbolyze/issues/47 resvg' = resvg.overrideAttrs (old: rec { version = "0.41.0"; src = old.src.override { rev = "v${version}"; hash = "sha256-plZiyEiBWeV2mwTsNK5Je8Axs/hcHH8aV2VpOix6QCY="; }; cargoDeps = old.cargoDeps.overrideAttrs (lib.const { name = "${old.pname}-${version}-vendor.tar.gz"; inherit src; outputHash = "sha256-U7xzb9e9wh9XbLvlYQ0ofIjH8FuSzVcrXnrehQmZgww="; }); }); </ins> in python3Packages.buildPythonApplication rec { inherit version src; pname = "gerbolyze";

Discussion:
Steps to reproduce the behavior: gerbolyze Test failures: and Upstream issue . While upstream is working on a fix, the issue can be worked around using the shell (run ) from the following : Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
systemd.sockets.mpd = mkIf cfg.startWhenNeeded { wantedBy = [ "sockets.target" ]; listenStreams = [ <ins> ""  # Note: this is needed to override the upstream unit </ins> (if pkgs.lib.hasPrefix "/" cfg.network.listenAddress then cfg.network.listenAddress else "${optionalString (cfg.network.listenAddress != "any") "${cfg.network.listenAddress}:"}${toString cfg.network.port}")

Discussion:
startWhenNeeded doesn't seem to work anymore. Try to enable it via: should load. It says that port 6600 is used, but it's not on my system (maybe socket is started together with service?): Please run and paste the result.
I can confirm I have the exact same problem. I just performed the upgrade. From the output of it seems no other services are listening on that port, so I don't know what's up with the message.
This is a breaking change in systemd 250. What's already listening on that port is systemd itself. Look at the resulting unit: I'm not sure if the previous behavior was correct, but in v249 our override was actually overriding the value from the upstream unit. Now, in v250, it's simply being to a list of socket addresses. It obviously fails as both are trying to listen on the same port.
Until the PR is merged you can use .
Change:
sha256 = "18bp7fcpv7879q3ppdxlqj7ayqmlh5zwrkz8gch6rq9lkmmrklrf"; }; <del> buildInputs = [ libxslt systemd libaio docbook_xsl ]; </del> <ins> nativeBuildInputs = [ libxslt docbook_xsl makeWrapper ]; buildInputs = [ systemd libaio ]; </ins> makeFlags = [ "PREFIX=${placeholder "out"}"

Discussion:
By looking at the there is a service file that can be embedded with the package . It would be nice to port that to the tgt nixpkg I might do it myself if I find the time to learn the build system properly
If the service is installed into , it can be in a nixos module like that:
Change:
}; user = mkOption { <ins> type = types.string; </ins> default = "openldap"; description = "User account under which slapd runs."; }; group = mkOption { <ins> type = types.string; </ins> default = "openldap"; description = "Group account under which slapd runs."; }; <ins> dataDir = mkOption { type = types.string; default = "/var/db/openldap"; description = "The database directory."; }; </ins> extraConfig = mkOption { <ins> type = types.lines; </ins> default = ""; description = " sldapd.conf configuration

Discussion:
There seems to be even more wrong with openldap as mentioned in When I declare openldap as follows: The service won't start due to: Shouldn't the be linked to /etc? It is not.
Set to something else:
Still not working:
I guess you have to create this directory with proper permissions. And yeah, I wouldn't use /var/run for databases. ;-)
Hmm, looking at the module I would suggest using . This directory is automatically created by systemd service and gets the right permissions.
Change:
in assert lib.all (p: p.enabled -> ! (builtins.elem null p.buildInputs)) plugins; stdenv.mkDerivation rec { <del> version = "2.6"; </del> <ins> version = "2.7.1"; </ins> pname = "weechat"; src = fetchurl { url = "https://weechat.org/files/src/weechat-${version}.tar.bz2"; <del> sha256 = "1narazk28m7lmn1vqi7bhyvnr8apjrmaa4w1hbadn64hwr8ya1hb"; </del> <ins> sha256 = "0acz41jg7lmipni9z2agfqw4dhmx5hf6k9w4pvr4zih1fhkldva2"; </ins> }; outputs = [ "out" "man" ] ++ map (p: p.name) enabledPlugins;

Discussion:
Currently we have two expressions that both build the kernel, whose only interface differences are in whether or not the .config is generated or provided. These builds should be merged with the two different interfaces simply being two ways to call the same underlying function, reducing code duplication and allowing the generic kernel builds to benefit from the IMO better structure of the newer manual kernel builds.
+1 on getting rid of duplication What is the "better structure"?
Structure may have been the wrong word, but the manual kernel build uses multiple outputs (suboptimally currently, which was part of the problem with the old PR) and uses the official kernel build system for building and installing, while the generic one (last I checked) had a manually maintained shell script to handle the install and parts of the build.
Fixed by

For example: If this is called with instead of , it will fail to produce a output. This causes an assertion of the form: Unfortunately, doesn't keep the build directory around, making the source of the problem difficult to debug.
This is more of an issue for Thanks for reporting though!
Whoops! Is there an easy way to move it?
Not that I know of, sorry.
Fixed, thanks!

migrated from python branch issue tracker
I'm closing this as it seems no longer relevant. From what I could find, python-virtinst is "CLI tools for building virtual machines using libvirt". But it is now merged with virtmanager: <-- contains one single file named MERGEDWITHVIRTMANAGER
Change:
prePatch = '' substituteInPlace variety_lib/varietyconfig.py  <del> --replace "__variety_data_directory__ = "../data"" "__variety_data_directory__ = "$out/share/variety"" </del> <ins> --replace "__variety_data_directory__ = "../data""  "__variety_data_directory__ = "$out/share/variety"" </ins> substituteInPlace data/scripts/set_wallpaper  <del> --replace /bin/bash ${stdenv.shell} </del> <ins> --replace /bin/bash ${runtimeShell} </ins> substituteInPlace data/scripts/get_wallpaper  <del> --replace /bin/bash ${stdenv.shell} </del> <ins> --replace /bin/bash ${runtimeShell} </ins> ''; <del> propagatedBuildInputs = [ beautifulsoup4 configobj dbus-python gexiv2 gobject-introspection gtk3 hicolor-icon-theme httplib2 libnotify librsvg lxml pillow pycairo pygobject3 requests setuptools ] ++ lib.optional fehSupport feh ++ lib.optional imagemagickSupport imagemagick; </del> meta = with lib; { homepage = "https://github.com/varietywalls/variety"; description = "A wallpaper manager for Linux systems";

Discussion:
Recently variety stops working on NixOS. Pictures are downloaded well but the wallpaper can't be changed and can only be set in system setting. That's because of the hardcoded shebang which is taken from on the first installation. So when the bash is updated the script can't find it. It should be set as something like . Not sure if this is a nixos bug. Steps to reproduce the behavior: variety bash It works after the bash update. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
IIRC now we use . I am patching it now.
Change:
# Related scripts are update-hackage.sh, for updating the snapshot of the # Hackage database used by hackage2nix, and update-cabal2nix-unstable.sh, # for updating the version of hackage2nix used to perform this task. <ins> # # Note that this script doesn't gcroot anything, so it may be broken by an # unfortunately timed nix-store --gc. </ins> set -euo pipefail

Discussion:
The values of these options can easily be determined using and , so it should be very easy to just remove this part of the configuration from and generate it on demand in .
Change:
# !!! fix this children = mapAttrs (childName: childConfig: (import ../../../lib/eval-config.nix { <del> inherit baseModules; </del> <ins> inherit baseModules specialArgs; </ins> system = config.nixpkgs.initialSystem; modules = (optionals childConfig.inheritParentConfig modules)

Discussion:
Describe the bug Example config gives me this . To Reproduce Steps to reproduce the behavior: your nixos-config while using nix flakes recursion Additional context Code in nixos
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
I think it's because of . This patch works, though I'm not sure how robust it is:
any chance this patch will be upstreamed?
Just for information to everyone who comes here because they try to create specialised configs in flakes, if you use (I did to inject home-manager) then it should be possible to replace it with an inline module like explained here: Using will result in an "attributes missing" error
Change:
, buildPythonPackage , cachetools , cryptography <del> , fetchpatch </del> , fetchPypi , flask , freezegun

Discussion:
Package name: Latest released version: 2.27.0 <!-- Search your package here: --- Current version on the unstable channel: 2.21.0 Current version on the stable/release channel: 2.21.0 <!-- 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]:
Change:
<del> { stdenv, fetchurl, qt4, pkgconfig, libsamplerate, fftwSinglePrec, which, cmake </del> <ins> { stdenv, fetchurl, pkgconfig, which, cmake , fftwSinglePrec, libsamplerate, qtbase </ins> , darwin }: let version = "1.1.0"; in

Discussion:
Describe the bug Since some day, clementine refuse to work. I bisected the error to the commit . The error message in the terminal is: realloc(): invalid pointer fish : Tâche , './result/bin/clementine' terminée par le signal SIGABRT (Abandon) To Reproduce go to a nixpkgs git tree Expected behavior clementine start as expected 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(root): channels(marius): nixpkgs: Maintainer information:
Looks like we are hitting here. cc
I could have sworn I tested this… let me see if I can reproduce this issue.
Yup, and reverting the projectm fix makes it run again. Hm… I was really sure I tested clementine. I don't think I'll have time to look into this properly until the weekend, so as a quick fix, you can revert the projectm update, if you want to.
Change:
}) ]; <ins> propagatedUserEnvPkgs = [ gtk-engine-murrine ]; </ins> sourceRoot = "."; installPhase = ''

Discussion:
Describe the bug Sweet theme doesn't provide murrine gtk engine compared to other themes: Apps thus don't detect the murrine engine because it is not installed. There might also be other problems with the package as I think pixbuf and librsvg are mendatory for themes, I am not sure about that but it could be. Expected behavior The sweet package should install all necessary dependencies. Screenshots ! Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Maintainer information:
Nice! Thank you
Change:
# relax version constraint, https://storyboard.openstack.org/#!/story/2009723 substituteInPlace requirements.txt --replace 'PyYAML>=3.10.0,<6' 'PyYAML>=3.10.0' <ins> # Allow building with setuptools from nixpkgs. # Related: https://github.com/NixOS/nixpkgs/issues/238226. substituteInPlace requirements.txt --replace 'setuptools<=65.7.0' 'setuptools' </ins> export HOME=$TMPDIR '';

Discussion:
Steps to reproduce the behavior: [...] tests.testplugins.PluginsTestScenarios.testpluginversionobjectcomparison(baseurl2,s13)
Captured traceback: ~ Traceback (most recent call last): File "/build/python-jenkins-", line 311, in testpluginversionobjectcomparison plugininfo = j.getplugins()[pluginname] File "/build/python-jenkins-", line 939, in getplugins pluginsdata[keys] = plugins.Plugin(**plugindata) File "/build/python-jenkins-", line 59, in init self['version'] = version File "/build/python-jenkins-", line 66, in setitem value = PluginVersion(value) File "/build/python-jenkins-", line 79, in init self.parsedversion = pkgresources.parseversion( File "/nix/store/basb8wsyinlwbcawx0v9lklvv06qpph6-python3.10-setuptools-67.4.0/lib/python3.10/site-", line 197, in init raise InvalidVersion(f"Invalid version: '{version}'") Invalid version: '1.0a.preview' [...] Totals Ran: 600 tests in 4.0974 sec. Passed: 592 Skipped: 0 Expected Fail: 0 Unexpected Success: 0 Failed: 8 [...] error: builder for '/nix/store/6p6xqf08cd3fj5lnz2yhlhhp74q10j6f-python3.10-python-jenkins-' failed with exit code 1; last 10 log lines: For full logs, run 'nix log /nix/store/6p6xqf08cd3fj5lnz2yhlhhp74q10j6f-python3.10-python-jenkins-'. error: 1 dependencies of derivation '/nix/store/17m131aya6dd610k58fa056nakfidnzm-python3.10-jenkins-job-builder-' failed to build It's 8 tests blocking it from completing the build. It's a regression since release-22.11 -- now it's broken in both master and release-23.05 branches. I think it's caused by ("python310Packages.setuptools: 65.0.3 -67.4.0") and upstream did to fix it (downgrading setuptools).

There are no maintainers listed for jenkins-job-builder, but since it's technically python-jenkins that fails to build: CC
Upstream issue: ("InvalidVersion exception when invalid version used on Setuptools 66").
Yes. Confirmed by git bisect. CC
Fix (by disabling failing tests and relaxing setuptools version requirement):