jiebi/CodeConvo huggingface dataset:
Code change:
<!-- 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: coreutils <!-- 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: 9.0 desired version: 9.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.
I'm already on it :) might take some while before I do the pr because I want to build stdenv first

Related discussion:
text: stdenv.mkDerivation (rec { pname = "coreutils${optionalString (!minimal) "-full"}"; <del> version = "9.0"; </del> <ins> version = "9.1"; </ins> src = fetchurl { url = "mirror://gnu/coreutils/coreutils-${version}.tar.xz"; <del> sha256 = "sha256-zjCs30pBvFuzDdlV6eqnX6IWtOPesIiJ7TJDPHs7l84="; </del> <ins> sha256 = "sha256:08q4b0w7mwfxbqjs712l6wrwl2ijs7k50kssgbryg9wbsw8g98b1"; </ins> }; <del> patches = [ ./fix-chmod-exit-code.patch # Workaround for https://debbugs.gnu.org/cgi/bugreport.cgi?bug=51433 ./disable-seek-hole.patch # Workaround for https://debbugs.gnu.org/cgi/bugreport.cgi?bug=52330 # This patch can be dropped, once we upgrade to the next coreutils version after 9.0 ./fix-arm64-macos.patch ]; </del> postPatch = '' # The test tends to fail on btrfs,f2fs and maybe other unusual filesystems. sed '2i echo Skipping dd sparse test && exit 77' -i ./tests/dd/sparse.sh
Code change:
<!-- 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: coreutils <!-- 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: 9.0 desired version: 9.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.
I'm already on it :) might take some while before I do the pr because I want to build stdenv first

Related discussion:
text: nativeBuildInputs = [ perl xz.bin autoreconfHook ] # autoreconfHook is due to patch, normally only needed for cygwin ++ optionals stdenv.hostPlatform.isCygwin [ texinfo ];  # due to patch <del> configureFlags = [ "--with-packager=https://NixOS.org" ] </del> <ins> configureFlags = [ "--with-packager=https://nixos.org" ] </ins> ++ optional (singleBinary != false) ("--enable-single-binary" + optionalString (isString singleBinary) "=${singleBinary}") ++ optional withOpenssl "--with-openssl"
Code change:
<!-- 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: coreutils <!-- 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: 9.0 desired version: 9.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.
I'm already on it :) might take some while before I do the pr because I want to build stdenv first

Related discussion:
text: NIX_LDFLAGS = optionalString selinuxSupport "-lsepol"; FORCE_UNSAFE_CONFIGURE = optionalString stdenv.hostPlatform.isSunOS "1"; <ins> NIX_CFLAGS_COMPILE = [] # Work around a bogus warning in conjunction with musl. ++ optional stdenv.hostPlatform.isMusl "-Wno-error" ++ optional stdenv.hostPlatform.isAndroid "-D__USE_FORTIFY_LEVEL=0"; </ins> # Works around a bug with 8.26: # Makefile:3440: *** Recursive variable 'INSTALL' references itself (eventually).  Stop.
Code change:
<!-- 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: coreutils <!-- 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: 9.0 desired version: 9.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.
I'm already on it :) might take some while before I do the pr because I want to build stdenv first

Related discussion:
text: license = licenses.gpl3Plus; platforms = platforms.unix ++ platforms.windows; priority = 10; <del> maintainers = [ maintainers.eelco maintainers.das_j ]; </del> <ins> maintainers = [ maintainers.das_j ]; </ins> }; <del> } // optionalAttrs stdenv.hostPlatform.isMusl { # Work around a bogus warning in conjunction with musl. NIX_CFLAGS_COMPILE = "-Wno-error"; } // lib.optionalAttrs stdenv.hostPlatform.isAndroid { NIX_CFLAGS_COMPILE = "-D__USE_FORTIFY_LEVEL=0"; </del> })
Code change:
<!-- 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: coreutils <!-- 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: 9.0 desired version: 9.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.
I'm already on it :) might take some while before I do the pr because I want to build stdenv first

Related discussion:
text: <del> diff --git a/src/copy.c b/src/copy.c index cb9018f93..2a4ccc061 100644 --- a/src/copy.c +++ b/src/copy.c @@ -502,7 +502,7 @@ write_zeros (int fd, off_t n_bytes) return true; } -#ifdef SEEK_HOLE +#if 0 /* Perform an efficient extent copy, if possible.  This avoids the overhead of detecting holes in hole-introducing/preserving copy, and thus makes copying sparse files much more efficient. @@ -1095,7 +1095,7 @@ infer_scantype (int fd, struct stat const *sb, && ST_NBLOCKS (*sb) < sb->st_size / ST_NBLOCKSIZE)) return PLAIN_SCANTYPE; -#ifdef SEEK_HOLE +#if 0 scan_inference->ext_start = lseek (fd, 0, SEEK_DATA); if (0 <= scan_inference->ext_start) return LSEEK_SCANTYPE; @@ -1377,7 +1377,7 @@ copy_reg (char const *src_name, char const *dst_name, off_t n_read; bool wrote_hole_at_eof = false; if (! ( -#ifdef SEEK_HOLE +#if 0 scantype == LSEEK_SCANTYPE ? lseek_copy (source_desc, dest_desc, buf, buf_size, hole_size, scan_inference.ext_start, src_open_sb.st_size, diff --git a/tests/seek-data-capable b/tests/seek-data-capable index cc6372214..6e7a9ec1e 100644 --- a/tests/seek-data-capable +++ b/tests/seek-data-capable @@ -1,5 +1,7 @@ import sys, os, errno, platform +sys.exit(1) + # Pass an _empty_ file if len(sys.argv) != 2: sys.exit(1) </del>
Code change:
Can anyone run successfully? When I try it, the tool almost immediately crashes:
On 6 February 2014 19:49, Peter Simons wrote: Same here. Seems to be happening elsewhere too:
Saving to works around the issue for now.
Any way this can be wrapped to happen automatically?

Related discussion:
text: <del> {stdenv, fetchurl, gtk2, pkgconfig, perl, perlXMLParser, libxml2, gettext , python, libxml2Python, docbook5, docbook_xsl, libxslt, intltool, libart_lgpl , withGNOME ? false, libgnomeui }: </del> <ins> { stdenv, fetchgit, autoconf, automake, libtool, gtk2, pkgconfig, perl, perlXMLParser, libxml2, gettext, python, libxml2Python, docbook5, docbook_xsl, libxslt, intltool, libart_lgpl, withGNOME ? false, libgnomeui, gtk-mac-integration }: </ins> stdenv.mkDerivation rec { <del> name = "dia-${minVer}.3"; minVer = "0.97"; </del> <ins> name = "dia-${version}"; version = "0.97.3.20170622"; </ins> <del> src = fetchurl { url = "mirror://gnome/sources/dia/${minVer}/${name}.tar.xz"; sha256 = "0d3x6w0l6fwd0l8xx06y1h56xf8ss31yzia3a6xr9y28xx44x492"; }; correctPersistence = fetchurl { url = https://launchpadlibrarian.net/132677658/persistence; sha256 = "1rv6zv9i03bna4bdp1wzn72lg7kdwi900y1izdq0imibi54nxjsk"; </del> <ins> src = fetchgit { url = git://git.gnome.org/dia; rev = "b86085dfe2b048a2d37d587adf8ceba6fb8bc43c"; sha256 = "1fyxfrzdcs6blxhkw3bcgkksaf3byrsj4cbyrqgb4869k3ynap96"; </ins> }; buildInputs = [ gtk2 perlXMLParser libxml2 gettext python libxml2Python docbook5 <del> libxslt docbook_xsl libart_lgpl ] ++ stdenv.lib.optional withGNOME libgnomeui; </del> <ins> libxslt docbook_xsl libart_lgpl ] ++ stdenv.lib.optional withGNOME libgnomeui ++ stdenv.lib.optional stdenv.isDarwin gtk-mac-integration; </ins> <del> nativeBuildInputs = [ pkgconfig intltool perl ]; </del> <ins> nativeBuildInputs = [ autoconf automake libtool pkgconfig intltool perl ]; preConfigure = '' NOCONFIGURE=1 ./autogen.sh # autoreconfHook is not enough ''; </ins> configureFlags = stdenv.lib.optionalString withGNOME "--enable-gnome"; <del> patches = [ ]; </del> <ins> hardeningDisable = [ "format" ]; </ins> # This file should normally require a gtk-update-icon-cache -q /usr/share/icons/hicolor command # It have no reasons to exist in a redistribuable package postInstall = '' rm $out/share/icons/hicolor/icon-theme.cache <del> cd "$out"/bin/ mv dia .dia-wrapped echo '#! ${stdenv.shell}' >> dia echo 'test -f "$HOME/.dia/persistence" || cp ${correctPersistence} "$HOME/.dia/persistence" ' >> dia echo 'chmod u+rw "$HOME/.dia/persistence" ' >> dia echo ""$out/bin/"'.dia-wrapped" "$@"' >> dia chmod a+x dia </del> ''; meta = { description = "Gnome Diagram drawing software"; homepage = http://live.gnome.org/Dia; maintainers = with stdenv.lib.maintainers; [raskin]; <del> platforms = stdenv.lib.platforms.linux; </del> <ins> platforms = stdenv.lib.platforms.unix; </ins> }; }
Code change:
Build of failed on x86_64-linux as of . This is currently breaking maintainers cc: maintainers cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tag:
can confirm for and
I'm trying to bisect this atm, but it's a truly massive undertaking since there's hundreds of commits between current master and the last successful build... plus there's lots of other irrelevant failures :/
I was unable to find the exact commit that caused these failures, since it was interlaced a bunch of other commits that broke dependencies. Created upstream. We'll see what they say. We're not doing any patching of required dependency versions, so the test suite ought to be passing.
I also tried bisecting. Due to the massive rebuilds, I canceled after 8 hours and did a bisect with . The bad commit is from , which is a merge from staging with changes to python and others: <details</detailsLooking at the there is a requirement for werkzeug < 2.1.0. When applied, the test mostly pass. The only failing test is: There is also a requirement for pytest < 7. Since this packaged builds with the latest nixos/unstable, which includes pytest 7.0.1 I am now testing with that version.
The updates usually breaks the package. I guess from 1.5.7 to 1.5.8. Edit: Was part of
Further investigation: When I apply the following two changes: downgrade to downgrade to sentry-sdk builds without issues. How should we go about this? Just disabling the tests could lead to malfunction of the sentry-sdk package (because they did correctly detected a regression in the SDK). Downgrading both packages Adding an override in for those two packages could lead to potential breakages due to dual imports of two different or imports in packages, which import sentry-sdk and one of the two packages. Obviously it would be awesome if upstream update their end of the SDK of werkzeug. This could take some time and sentry-sdk is needed by other packages.
I notified the authors of the breaking commits and
Another breakage is pgadmin (tracked in )
Module can't have overrides. Thus, till the issues are fixed by upstream the failing tests should be disabled.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:

Related discussion:
text: "test_auto_session_tracking_with_aggregates" # Network requests to public web "test_crumb_capture" <ins> # TypeError: cannot unpack non-iterable TestResponse object "test_rpc_error_page" </ins> ]; disabledTestPaths = [
Code change:
Build of failed on x86_64-linux as of . This is currently breaking maintainers cc: maintainers cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tag:
can confirm for and
I'm trying to bisect this atm, but it's a truly massive undertaking since there's hundreds of commits between current master and the last successful build... plus there's lots of other irrelevant failures :/
I was unable to find the exact commit that caused these failures, since it was interlaced a bunch of other commits that broke dependencies. Created upstream. We'll see what they say. We're not doing any patching of required dependency versions, so the test suite ought to be passing.
I also tried bisecting. Due to the massive rebuilds, I canceled after 8 hours and did a bisect with . The bad commit is from , which is a merge from staging with changes to python and others: <details</detailsLooking at the there is a requirement for werkzeug < 2.1.0. When applied, the test mostly pass. The only failing test is: There is also a requirement for pytest < 7. Since this packaged builds with the latest nixos/unstable, which includes pytest 7.0.1 I am now testing with that version.
The updates usually breaks the package. I guess from 1.5.7 to 1.5.8. Edit: Was part of
Further investigation: When I apply the following two changes: downgrade to downgrade to sentry-sdk builds without issues. How should we go about this? Just disabling the tests could lead to malfunction of the sentry-sdk package (because they did correctly detected a regression in the SDK). Downgrading both packages Adding an override in for those two packages could lead to potential breakages due to dual imports of two different or imports in packages, which import sentry-sdk and one of the two packages. Obviously it would be awesome if upstream update their end of the SDK of werkzeug. This could take some time and sentry-sdk is needed by other packages.
I notified the authors of the breaking commits and
Another breakage is pgadmin (tracked in )
Module can't have overrides. Thus, till the issues are fixed by upstream the failing tests should be disabled.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:

Related discussion:
text: "tests/integrations/rq/" # broken since pytest 7.0.1; AssertionError: previous item was not torn down properly "tests/utils/test_contextvars.py" <ins> # broken since Flask and Werkzeug update to 2.1.0 (different error messages) "tests/integrations/flask/test_flask.py" "tests/integrations/bottle/test_bottle.py" "tests/integrations/django/test_basic.py" "tests/integrations/pyramid/test_pyramid.py" ] # test crashes on aarch64 ++ lib.optionals (stdenv.buildPlatform != "x86_64-linux") [ "tests/test_transport.py" "tests/integrations/threading/test_threading.py" </ins> ]; pythonImportsCheck = [
Code change:
On current nixpkgs unstable, GraalVM 11 won't build (also breaking clojure-lsp, clj-kondo, babashka, etc). Steps to reproduce the behavior: macOS: It should build successfully graalvm17-ce fails for the same reason. GraalVM package maintainers: Please run and paste the result.
My bad, this was probably one change that I made on the previous refactor. This PR should fix it:

Related discussion:
text: outputs = [ "out" "lib" ]; installPhase = '' <ins> # ensure that $lib/lib exists to avoid breaking builds mkdir -p "$lib/lib" </ins> # jni.h expects jni_md.h to be in the header search path. ln -s $out/include/linux/*_md.h $out/include/
Code change:
On current nixpkgs unstable, GraalVM 11 won't build (also breaking clojure-lsp, clj-kondo, babashka, etc). Steps to reproduce the behavior: macOS: It should build successfully graalvm17-ce fails for the same reason. GraalVM package maintainers: Please run and paste the result.
My bad, this was probably one change that I made on the previous refactor. This PR should fix it:

Related discussion:
text: # `native-image -H:CLibraryPath=''${lib.getLib graalvmXX-ce}/lib ...` and reduce # closure size by not depending on GraalVM $out (that is much bigger) # we always use glibc here, since musl is only supported for static compilation <del> mkdir -p "$lib/lib" </del> for f in "${glibc}/lib/"*; do ln -s "$f" "$lib/lib/$(basename $f)" done
Code change:
Project description Add Khmeros TrueType font for Khmer language. Also, see All issues have attached PRs. Metadata homepage URL: source URL: mirror://debian/pool/main/f/fonts-khmeros/fonts- license: gpl2+ platforms: all

Related discussion:
text: <ins> { fetchzip, lib }: let version = "5.0"; in fetchzip { name = "khmeros-${version}"; url = "mirror://debian/pool/main/f/fonts-khmeros/fonts-khmeros_${version}.orig.tar.xz"; sha256 = "sha256-pS+7RQbGwlBxdCfSVxHmARCAkZrZttwYNlV/CrxqI+w="; postFetch = '' unpackDir="$TMPDIR/unpack" mkdir "$unpackDir" cd "$unpackDir" tar xf "$downloadedFile" --strip-components=1 mkdir -p $out/share/fonts cp *.ttf $out/share/fonts ''; meta = with lib; { description = "KhmerOS Unicode fonts for the Khmer language"; homepage = "http://www.khmeros.info/"; license = licenses.gpl2Plus; maintainers = with lib.maintainers; [ serge ]; platforms = platforms.all; }; } </ins>
Code change:
Project description Add Khmeros TrueType font for Khmer language. Also, see All issues have attached PRs. Metadata homepage URL: source URL: mirror://debian/pool/main/f/fonts-khmeros/fonts- license: gpl2+ platforms: all

Related discussion:
text: kde-rounded-corners = libsForQt5.callPackage ../data/themes/kwin-decorations/kde-rounded-corners { }; <ins> khmeros = callPackage ../data/fonts/khmeros {}; </ins> kochi-substitute = callPackage ../data/fonts/kochi-substitute {}; kochi-substitute-naga10 = callPackage ../data/fonts/kochi-substitute-naga10 {};
Code change:
Project description Add Korean Nanum fonts: Nanum Gothic Nanum Barun Gothic Nanum Barunpen Nanum Brush Nanum Myengjo Nanum Pen Nanum Square Nanum Square Round Metadata homepage URL: source URL: license: ofl platforms: all

Related discussion:
text: <ins> { fetchzip, lib }: let version = "20170925"; in fetchzip { name = "nanum-${version}"; url = "mirror://ubuntu/pool/universe/f/fonts-nanum/fonts-nanum_${version}.orig.tar.xz"; sha256 = "sha256-lSTeQEuMmlQxiQqrx9tNScifE8nMOUDJF3lCfoAFIJk="; postFetch = '' unpackDir="$TMPDIR/unpack" mkdir "$unpackDir" cd "$unpackDir" tar xf "$downloadedFile" --strip-components=1 mkdir -p $out/share/fonts cp *.ttf $out/share/fonts ''; meta = with lib; { description = "Nanum Korean font set"; homepage = "https://hangeul.naver.com/font"; license = licenses.ofl; maintainers = with lib.maintainers; [ serge ]; platforms = platforms.all; }; } </ins>
Code change:
Project description Add Korean Nanum fonts: Nanum Gothic Nanum Barun Gothic Nanum Barunpen Nanum Brush Nanum Myengjo Nanum Pen Nanum Square Nanum Square Round Metadata homepage URL: source URL: license: ofl platforms: all

Related discussion:
text: nafees = callPackage ../data/fonts/nafees { }; <ins> nanum = callPackage ../data/fonts/nanum {  }; </ins> nanum-gothic-coding = callPackage ../data/fonts/nanum-gothic-coding {  }; national-park-typeface = callPackage ../data/fonts/national-park { };
Code change:
Commit from broke haskell.compiler.ghc6102Binary haskell.compiler.ghc704Binary and therefore the packages haskell.compiler.ghc6104 haskell.compiler.ghc704 haskell.compiler.ghc722 haskell.compiler.ghc742 haskell.compiler.ghc763 which depend on them.
Please try . I test-built the binary GHCs but no further.
Aha. I relied on the update being API-compatible, but the first bootstraping steps don't recompile...
I'm test-building the whole list above.
All succeeded on x86_64-linux.

Related discussion:
text: <del> {stdenv, lib, fetchurl, perl, libedit, ncurses, gmp}: </del> <ins> {stdenv, lib, fetchurl, perl, libedit, ncurses5, gmp}: </ins> stdenv.mkDerivation rec { version = "6.10.2";
Code change:
Commit from broke haskell.compiler.ghc6102Binary haskell.compiler.ghc704Binary and therefore the packages haskell.compiler.ghc6104 haskell.compiler.ghc704 haskell.compiler.ghc722 haskell.compiler.ghc742 haskell.compiler.ghc763 which depend on them.
Please try . I test-built the binary GHCs but no further.
Aha. I relied on the update being API-compatible, but the first bootstraping steps don't recompile...
I'm test-building the whole list above.
All succeeded on x86_64-linux.

Related discussion:
text: (if stdenv.isLinux then '' find . -type f -perm -0100  -exec patchelf --interpreter "$(cat $NIX_CC/nix-support/dynamic-linker)"  <del> --set-rpath "${libedit}/lib:${ncurses.out}/lib:${gmp.out}/lib" {} ; </del> <ins> --set-rpath "${libedit}/lib:${ncurses5.out}/lib:${gmp.out}/lib" {} ; </ins> for prog in ld ar gcc strip ranlib; do find . -name "setup-config" -exec sed -i "s@/usr/bin/$prog@$(type -p $prog)@g" {} ; done
Code change:
Commit from broke haskell.compiler.ghc6102Binary haskell.compiler.ghc704Binary and therefore the packages haskell.compiler.ghc6104 haskell.compiler.ghc704 haskell.compiler.ghc722 haskell.compiler.ghc742 haskell.compiler.ghc763 which depend on them.
Please try . I test-built the binary GHCs but no further.
Aha. I relied on the update being API-compatible, but the first bootstraping steps don't recompile...
I'm test-building the whole list above.
All succeeded on x86_64-linux.

Related discussion:
text: <del> {stdenv, fetchurl, perl, ncurses, gmp, libiconv}: </del> <ins> {stdenv, fetchurl, perl, ncurses5, gmp, libiconv}: </ins> stdenv.mkDerivation rec { version = "7.0.4";