jiebi/CodeConvo huggingface dataset:
Change:
builder = ./builder.sh; <del> meta = { description = "An open-source 8086 emulator"; </del> <ins> meta = with stdenv.lib; { description = "An open-source small 8086 emulator"; </ins> longDescription = '' <del> 8086tiny is a tiny, open-source (MIT), portable (little-endian hosts) Intel PC emulator, powerful enough to run DOS, Windows 3.0, Excel, MS Flight Simulator, AutoCAD, Lotus 1-2-3, and similar applications. 8086tiny emulates a "late 80's era" PC XT-type machine. </del> <ins> 8086tiny is a tiny, open-source (MIT), portable (little-endian hosts) Intel PC emulator, powerful enough to run DOS, Windows 3.0, Excel, MS Flight Simulator, AutoCAD, Lotus 1-2-3, and similar applications. 8086tiny emulates a "late 80's era" PC XT-type machine. </ins> <del> 8086tiny is based on an IOCCC 2013 winning entry. In fact that is the "unobfuscated" version :) </del> <ins> 8086tiny is based on an IOCCC 2013 winning entry. In fact that is the "unobfuscated" version :) </ins> ''; <del> homepage = "http://www.megalith.co.uk/8086tiny/index.html"; license = stdenv.lib.licenses.mit; maintainers = [ stdenv.lib.maintainers.AndersonTorres ]; platforms = stdenv.lib.platforms.linux; </del> <ins> homepage = "https://github.com/adriancable/8086tiny"; license = licenses.mit; maintainers = [ maintainers.AndersonTorres ]; platforms = platforms.linux; </ins> }; } <del> # TODO: add support for a locally made BIOS </del>

Discussion:
Describe the bug Homepage is down, current src link is dead. Project moved to the author's GitHub. I have no clue how to even use this package. It's one of the first you see on the "Search NixOS Packages" webpage though, and the dead links & abandoned expression has been a thorn in my eye for awhile now. I'll prolly step up and fix it myself in afew months if noone else wants to do it. To Reproduce Steps to reproduce the behavior: package expression / search on NixOS packages page. any of the links. Installation itself still works. Expected behavior A maintained package. :slightlyfrowningface: Screenshots Not really applicable. Additional context See above. Notify maintainers Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(bt1cn): nixpkgs: Maintainer information:
Change:
cfg = config.services.mediawiki; fpm = config.services.phpfpm.pools.mediawiki; user = "mediawiki"; <del> group = if cfg.webserver == "apache" then "apache" else "mediawiki"; </del> <ins> group = if cfg.webserver == "apache" then config.services.httpd.group else "mediawiki"; </ins> cacheDir = "/var/cache/mediawiki"; stateDir = "/var/lib/mediawiki";

Discussion:
Since 23.05 (likely since ), sets to be owned by /, but apache’s group is by default. Steps to reproduce the behavior: mediawiki that has the wrong group, also in I’d expect to be owned by a group that the httpd process is in. I assume that using instead of here might help: Please run and paste the result.
Change:
<ins> { stdenv, wayland, xorgserver, xkbcomp, xkeyboard_config, epoxy, libxslt, libunwind, makeWrapper } : with stdenv.lib; overrideDerivation xorgserver (oldAttrs: { name = "xwayland-${xorgserver.version}"; propagatedNativeBuildInputs = oldAttrs.propagatedNativeBuildInputs ++ [wayland epoxy libxslt makeWrapper libunwind]; configureFlags = [ "--disable-docs" "--disable-devel-docs" "--enable-xwayland" "--disable-xorg" "--disable-xvfb" "--disable-xnest" "--disable-xquartz" "--disable-xwin" "--with-default-font-path=" "--with-xkb-bin-directory=${xkbcomp}/bin" "--with-xkb-path=${xkeyboard_config}/etc/X11/xkb" "--with-xkb-output=$out/share/X11/xkb/compiled" ]; postInstall = '' rm -fr $out/share/X11/xkb/compiled ln -s /var/tmp $out/share/X11/xkb/compiled ''; }) // { meta = { description = "An X server for interfacing X11 apps with the Wayland protocol"; homepage = http://wayland.freedesktop.org/xserver.html; license = licenses.mit; platforms = platforms.linux; }; } </ins>

Discussion:
A in the xwayland package output causes nixos-rebuild to fail due to permission issues, since /var/tmp contains private directories (mode 700) System: NixOS 16.09 Nix version: 1.11.4 Nixpkgs version: 16.09.901.
Essentially the same problem as in vanilla X server:
found some more info on the problem the issue, is that both wayland and xorg have the same "fix" for packages wanting to write to the store, at the same place /nix/store/dd65ni8yzibvq2aj5jdylnv557i3hcd1-xwayland-1.18.4/share/X11/xkb/compiled and /nix/store/v82zrx8dnm5j8lq4a2fc5g0rcx2jx04k-xorg-server-1.18.4/share/X11/xkb/compiled are "conflicting" so buildEnv tries to cd into both, find every file within, and then create a compiled directory with symlinks to merge the 2 except, both versions of compiled are symlinks to /var/tmp in this case, there is no need to merge the contents of "compiled" since its 2 identical symlinks that are conflicting, so id say buildEnv should be patched and i have a simple testcase:
I'm guessing that this works OK when built in a sandbox?
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 . on the on .
As both the referenced packages build now, I guess it's safe to close this.
Change:
pythonPackages.buildPythonApplication rec { pname = "simp_le-client"; <del> version = "0.2.0"; </del> <ins> version = "0.6.1"; </ins> name = "${pname}-${version}"; src = pythonPackages.fetchPypi { inherit pname version; <del> sha256 = "1zg18jfry9mvkri3yd2f5mwfsl27ac9zmnll3bm93jb91jhd6ssh"; </del> <ins> sha256 = "0x4fky9jizs3xi55cdy217cvm3ikpghiabysan71b07ackkdfj6k"; </ins> }; checkPhase = ''

Discussion:
ACME certificates cannot be provisioned automatically, even though run in manual mode succeeds. This seems to occur whenever allocating a new certificate, and possibly when renewing one. System: (Flounder) Nix version: nix-env (Nix) 1.11.2 Nixpkgs version: "16.03.1168."
Hi guys; if any of you know what's going on here, it'd be greatly appreciated. From what I can tell, the Terms of Service are out of date for nixpkgs's version of letsencrypt - and this makes the service pretty much unusable. If you have any ideas about how we can fix this, I'll be happy to investigate further and make a fix.
Luckily only happens when creating a new account, so renews are not affected. Thanks for reporting. Fixed. :beers:
Awesome; thanks for the very fast fix! I'm wondering if there's a more permanent way to solve this - being unable to deploy new servers whenever letsencrypt releases a new TOS seems a bit fragile. Maybe we could add a configuration option to set the TOS hash on the command line when invoking simp_le?
That's a good idea. Also as we're right before releasing 16.09 we should add that option before the release so NixOS users can easily update the hash themselves if needed.
Hi! Even if the new configuration option to set the TOSH hash would only appear in (makes sense, it's a new feature), is the hash fix () going to reach ? It doesn't seem to be there for now:
Thanks for the reminder. I'll look at it. The only potential problem is that is at another version in 16.03. The patch should apply cleanly, though.
any news? If someone need a fix, just add the following snippet to your configuration to override the package with a patched one: Then you can use the options as usual! But I hope the patch will soon be available in :)
Ah, thanks for testing that! In that case I'll simply backport that patch.
Ok, backported. Will be in the 16.03 channel soon. I'll keep this issue open because I want an to add an option for 16.09 to specify the TOS hash in the module.
Confirmed to work on ! Thanks a lot!

are you still planning on doing this in time for 16.09?
what are actionables here for 16.09?
We won't implement this for now because we need to replace simp_le anyway.
This is happening again?
That fix worked for me. I've no idea if it breaks anything else for others.
Change:
sha256 = "1nqhk3n1s1p77g2bjnj55acicsrlyb2yasqxqwpx0w0djfx64ygm"; }; <del> unpackCmd = "tar --lzip -xf"; </del> nativeBuildInputs = [ lzip ]; <del> /* FIXME: Tests currently fail on Darwin: building test scripts for ed-1.5... testing ed-1.5... *** Output e1.o of script e1.ed is incorrect *** *** Output r3.o of script r3.ed is incorrect *** make: *** [check] Error 127 */ doCheck = !(hostPlatform.isDarwin || hostPlatform != buildPlatform); installFlags = [ "DESTDIR=$(out)" ]; configureFlags = [ "--exec-prefix=${stdenv.cc.targetPrefix}" "CC=${stdenv.cc.targetPrefix}cc" ]; </del> <ins> doCheck = hostPlatform == buildPlatform; </ins> meta = { description = "An implementation of the standard Unix editor";

Discussion:
There seems to be no man page for ed, the standard text editor.
It looks like an issue in how ed installs things:
The target directory is set with: There's another configure flag, , that defaults to . I think nix automatically replaces that by . Resulting in . would default to '$(prefix), but since it was set, the bin files ended up in the right place. Not setting any installFlags results in a correct tree. It basically lets nix figure it out. I noticed very recently replaced by'. Todo: [x] Confirm it's ok to not set the
Yes, removing is usually the correct option.
Fixed by .
Change:
cmakeFlags = "-DWITH_VTE=OFF -DWITH_TELEPATHY=OFF -DWITH_AVAHI=OFF -DWINPR_INCLUDE_DIR=${freerdp_git}/include/winpr2"; <ins> preFixup = '' gappsWrapperArgs+=( --prefix LD_LIBRARY_PATH : "${libX11.out}/lib" ) ''; </ins> postInstall = '' mkdir -pv $out/share/applications cp ${desktopItem}/share/applications/* $out/share/applications <del> wrapProgram $out/bin/remmina --prefix LD_LIBRARY_PATH : "${libX11.out}/lib" </del> ''; meta = with stdenv.lib; {

Discussion:
when adding new entry , changing protocol will cause SIGTRAP with seems to be something like installing remmina version: remmina-1.2.0-rcgit.15 System: (NixOS: , Ubuntu/Fedora: , ...) 09.773. (Flounder) Nix version: (run ) nix-env (Nix) 1.11.4 Nixpkgs version: (run ) "16.09.773."
Change:
"cve_bin_tool" ]; <del> # required until https://github.com/intel/cve-bin-tool/pull/1665 is merged postPatch = '' sed '/^pytest/d' -i requirements.txt ''; </del> <ins> passthru.tests.version = testers.testVersion { package = cve-bin-tool; }; </ins> meta = with lib; { description = "CVE Binary Checker Tool";

Discussion:
Trying to install (either with nix-env or nix-shell) fails. I'm not sure if this is a macOS only issue or not. Steps to reproduce the behavior: for install to fail with error: Relevant error logs: Please run and paste the result.
Change:
<ins> { lib , stdenv , fetchFromBitbucket , cmake }: stdenv.mkDerivation (finalAttrs: { pname = "wolfstoneextract"; version = "1.2"; src = fetchFromBitbucket { owner = "ecwolf"; repo = "wolfstoneextract"; rev = finalAttrs.version; hash = "sha256-yrYLP2ewOtiry+EgH1IEaxz2Q55mqQ6mRGSxzVUnJ8Q="; }; nativeBuildInputs = [ cmake ]; meta = with lib; { description = "Utility to extract Wolfstone data from Wolfenstein II"; homepage = "https://bitbucket.org/ecwolf/wolfstoneextract/src/master/"; platforms = [ "x86_64-linux" ]; license = with licenses; [ gpl3Only bsd3 ]; maintainers = with maintainers; [ keenanweaver ]; }; }) </ins>

Discussion:
Project description Buried inside the game files for and is game data for two new -engine games, . WolfstoneExtract allows you to convert the embedded Wolfstone 3D and Elite Hans: Die Neue Ordnung game data into a format that’s usable by . Metadata homepage URL: URL: GPLv3 and various permissive free licenses platforms: Linux
Change:
} { <del> assertion = cfg.open -> (cfg.package ? open); </del> <ins> assertion = useOpenModules -> (cfg.package ? open); </ins> message = "This version of NVIDIA driver does not provide a corresponding opensource kernel driver."; } { <del> assertion = cfg.open -> cfg.gsp.enable; </del> <ins> assertion = useOpenModules -> cfg.gsp.enable; </ins> message = "The GSP cannot be disabled when using the opensource kernel driver."; }

Discussion:
Steps to reproduce the behavior: after update 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. But I am using flakes and following unstable. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
It was an intentional breaking change
TY.
To sum up, is non-optional and must be set now: When , use open source NVIDIA kernel module, this is now recommended by NVIDIA, but it doesn't work with older drivers. When , use proprietary kernel module. This is needed for people with older NVIDIA cards. More information:
Change:
]; prePatch = lib.optionalString stdenv.isDarwin '' <del> substituteInPlace configure --replace "-install_name libR.dylib" "-install_name $out/lib/R/lib/libR.dylib" </del> <ins> substituteInPlace configure  --replace "-install_name libRblas.dylib" "-install_name $out/lib/R/lib/libRblas.dylib"  --replace "-install_name libRlapack.dylib" "-install_name $out/lib/R/lib/libRlapack.dylib"  --replace "-install_name libR.dylib" "-install_name $out/lib/R/lib/libR.dylib" </ins> ''; dontDisableStatic = static;

Discussion:
Describe the bug To Reproduce Expected behavior It should give me a shell Additional context I can fix it with which is based off 20.09-beta but I don't seem to be able to use HEAD (it breaks for another reason). Notify maintainers Metadata Maintainer information:
Change:
(v: { inherit (v) name; value = fetchFromGitHub { <del> name = "${v.name}-${v.version}"; </del> <ins> name = "${v.name}-theme-${v.version}"; </ins> owner = "DFgraphics"; repo = v.name; rev = v.version;

Discussion:
nixpkgs.obsidian () and () have conflicting names, 1) causing confusion, and 2) causing issues when trying to update packages using . (current version is ) (should install obsidian-0.13.31, the knowledge base app) (removes obsidian-0.13.31, the knowledge base app, and installs obsidian-74.05, the dwarf fortress theme) obsidian-0.13.31 (the knowledge base app) should remain installed. (Or, later when a new version is available, that new version should be installed.) It should not be removed and replaced by the dwarf fortress theme. obsidian-0.13.31 (the knowledge base app) has 1.9k github stars () obsidian-74.05 (the dwarf fortress theme) has 3 github stars () imo, most people trying are probably looking for the knowledge base app. I'd suggest either the dwarf fortress theme should be given a new name, or both packages should be given new names. obsidian-0.13.31 maintainers: obsidian-74.05 maintainers:
As a user of both, +1 to renaming the dwarf fortress theme. :)
I think renaming the dwarf fortress theme would be sensible
+1 to rename the Dwarf Fortress theme.
Change:
<ins> { lib , fetchPypi , buildPythonPackage , types-requests , requests }: buildPythonPackage rec { pname = "pyarr"; version = "4.1.0"; src = fetchPypi { inherit pname version; sha256 = "sha256-3DX02V3Srpx6hqimWbesxfkDqslVH4+8uXY7XYDmjX0="; }; propagatedBuildInputs = [ requests types-requests ]; pythonImportsCheck = [ "pyarr" ]; meta = with lib; { description = "Python client for Servarr API's (Sonarr, Radarr, Readarr, Lidarr)"; homepage = "https://github.com/totaldebug/pyarr"; license = licenses.mit; maintainers = with maintainers; [ onny ]; }; } </ins>

Discussion:
Project description Python client for Servarr APIs (Sonarr, Radarr, Readarr, Lidarr) Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin
Change:
./hardware/nitrokey.nix ./hardware/opengl.nix ./hardware/pcmcia.nix <ins> ./hardware/printers.nix </ins> ./hardware/raid/hpsa.nix ./hardware/steam-hardware.nix ./hardware/usb-wwan.nix

Discussion:
Allow configuration of a cups printer by pointing at a ppd file and specifying a single URL in Currently, such configuration requires clicking through a web-interface. 09
I actually ran into problems with the imperative configuration. I configured my printer (samsung scx3200) and after a system upgrade i was unable to print anymore. An error was shown in the cups web interface for the printer: "unable to load PPD, /nix/store/.... no such file or directory". It looks like the driver i used was garbage-collected. That would not happen with a declarative configuration. However i am certain that this module is no easy piece of work because it requires deep insight into how cups works.
Interestingly for my driver it just copy them to . Does the files within this directory has references to the nix store?
I created a half-stateful solution similar to , which uses etc. to create the configured printers and force them in the right configuration, without having to touch the deep parts of cups. Works quite well, still have to see how it works on printer driver updates, though. Will pose a PR when that succeeds.
PR: please go and test it. :)
Upvote this! Will test on weekend. (looks better, than my own unconditional injection of ppd into /var/.../cups)
Hi, I just stumbled over this issue by accident and realized I'm using something similar in my machines own printing config. So I'm thinking it might help you if I'd share this code with you. Sorry for just dumping this file here. I've been planning to clean it up and suggest my module via a pull-request on its own, but I haven't found the time to do so yet. Still, I hope my module contains some usable ideas towards declarative printer config (e.g. set options, and check that each declared printer has its backend and ppd file installed).
Change:
, "meat" , "mocha" , "multi-file-swagger" <del> , "musescore-downloader" </del> , "near-cli" , "neovim" , "nijs"

Discussion:
I'm trying to package which directly depends on I get the following error: If I set , then I get the following error from npm: The error messages are good enough at explaining why it's a problem, but I don't know how to fix it. I'd appreciate some help! I cannot feasibly remove the pdfkit dependency because generating PDFs is essential functionality of this package. Steps to reproduce the behavior: to build the package from , e.g. by issuing: The package builds. cc
Setting should fix that problem specifically but there are more issues which the git deps error is warning will probably be the case So the problem specifically is: dl-librescore depends on pdfkit as a git dep rather than registry dep pdfkit doesn't have a npm lockfile (only a ) npm requires dev dependencies for git deps that have install scripts (which pdfkit has) npm does not lock transitive dev dependencies at all, so without an upstream npm lockfile then there just is no (npm) lock information for these required dev dependencies There's only so much we can do downstream about this, but we have had some ideas for how to deal with mixed lockfiles (like having a in a git dev dep with install scripts), but it'll be a good while before we get around to implementing such a thing (since it's more in the "nice to have" rather than "required for many packages" sort of thing) As for what you can do about it now, here are some options: to depend on only as a registry dep rather than git dep out install scripts from really needs an unreleased version, pester to make a new release and then have depend on as a registry dep similar to option 1 I wish I had better news for you, but npm is kinda hell in regards to git deps :(
Change:
githubId = 1550265; name = "Dominic Steinitz"; }; <ins> ifurther = { email = "55025025+ifurther@users.noreply.github.com"; github = "ifurther"; githubId = 55025025; name = "Feather Lin"; }; </ins> igsha = { email = "igor.sharonov@gmail.com"; github = "igsha";

Discussion:
Traceback (most recent call last): File "/nix/store/z4sd700l05shq1z72g21w0fav2xs955d-pipenv-2022.1.8/lib/python3.9/site-", line 83, in androidfolder from jnius import autoclass # noqa: SC200 ModuleNotFoundError: No module named 'jnius' The error is belong in pipenv using jnius on Android. <!-- 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(nix-on-droid): nixpkgs:
Change:
hash = "sha256-+ejYHQQFumbRgVKa9CozVPg4yTkJX/mZMNpqqc32/kY="; }; <del> "nss-3.87.tar.gz" = fetchurl { url = "https://ftp.mozilla.org/pub/security/nss/releases/NSS_3_87_RTM/src/nss-3.87-with-nspr-4.35.tar.gz"; hash = "sha256-63DqC1jc5pqkkOnp/s0TKn1kTh2j1jHhYzdqDcwRoCI="; </del> <ins> "nss-3.92.tar.gz" = fetchurl { url = "https://ftp.mozilla.org/pub/security/nss/releases/NSS_3_92_RTM/src/nss-3.92-with-nspr-4.35.tar.gz"; hash = "sha256-IcF2v/+27IQLX5hcf48BRoL0ovtVsGkkc0Fy1cBIbcU="; </ins> }; "boringssl.zip" = fetchurl { <del> url = "https://github.com/google/boringssl/archive/3a667d10e94186fd503966f5638e134fe9fb4080.zip"; hash = "sha256-HsDIkd1x5IH49fUF07dJaabMIMsQygW+NI7GneULpA8="; </del> <ins> url = "https://github.com/google/boringssl/archive/1b7fdbd9101dedc3e0aa3fcf4ff74eacddb34ecc.zip"; hash = "sha256-daVVQvpxkuEL/8/+QtLOJkdO+ECYZE3P4qJmDjV1GM0="; </ins> }; <del> "nghttp2-1.46.0.tar.bz2" = fetchurl { url = "https://github.com/nghttp2/nghttp2/releases/download/v1.46.0/nghttp2-1.46.0.tar.bz2"; hash = "sha256-moKXjIcAcbdp8n0riBkct3/clFpRwdaFx/YafhP8Ryk="; </del> <ins> "nghttp2-1.56.0.tar.bz2" = fetchurl { url = "https://github.com/nghttp2/nghttp2/releases/download/v1.56.0/nghttp2-1.56.0.tar.bz2"; hash = "sha256-L13Nv1d6LfUTokZGRUhMw10uTQczZT1jGTrlHbQd70E="; </ins> }; }

Discussion:
Package name: curl-impersonate Latest released version: 0.6.0 <!-- Search your package here: --- Current version on the unstable channel: 0.5.4 Current version on the stable/release channel: 0.5.4 <!-- 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 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:
mkdir -p $out/${gimp.targetScriptDir}/${name}; for p in "$@"; do cp "$p" -r $out/${gimp.targetScriptDir}/${name}; done } <del> installPlugins(){ mkdir -p $out/${gimp.targetPluginDir}/${name}; for p in "$@"; do cp "$p" -r $out/${gimp.targetPluginDir}/${name}; done </del> <ins> installPlugin() { # The base name of the first argument is the plug-in name and the main executable. # GIMP only allows a single plug-in per directory: # https://gitlab.gnome.org/GNOME/gimp/-/commit/efae55a73e98389e38fa0e59ebebcda0abe3ee96 pluginDir=$out/${gimp.targetPluginDir}/$(basename "$1") install -Dt "$pluginDir" "$@" </ins> } '';

Discussion:
Describe the bug I'm adding gimp like this in 20.09: However the fourier plugin is not being recognized. It should add: Filters/Generic/Forward FFT Filters/Generic/Inverse FFT But these filters are missing. Expected behavior FFT plugin should be recognized by gimp. 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:
I'm not sure about these specific plugins, but gimp-with-plugins comes with G'MIC, which includes a FFT filter under Filters -G'MIC Qt... -Available Filters -Frequency -Fourier transform