jiebi/CodeConvo huggingface dataset:
Code change:
<del> --- old/build/pkgs/singular/spkg-install	2015-07-26 15:34:43.000000000 +0200 +++ new/build/pkgs/singular/spkg-install	2015-09-15 20:42:51.716505855 +0200 @@ -115,6 +115,11 @@ done } </del> <ins> --- old/build/pkgs/singular/spkg-install	2017-10-15 10:35:41.826540964 -0500 +++ new/build/pkgs/singular/spkg-install	2017-10-15 10:36:40.613743443 -0500 @@ -4,6 +4,9 @@ ## Singular ########################################### </ins> <del> +nix_nuke_bin_rm() +{ +    find . -exec sed -e 's@/bin/rm@rm@g' -i '{}' ';' +} </del> <ins> +find . -type f -exec sed -e 's@/bin/rm@rm@g' -i '{}' ';' +#echo '#!/usr/bin/env bashnIgnoring missing $1' > src/build-aux/missing </ins> + <del> remove_old_version() { rm -f "$SAGE_LOCAL"/bin/Singular* @@ -306,11 +311,11 @@ # Actually run all the functions defined above -for i in choose_patches apply_patches remove_old_version config  +for i in choose_patches apply_patches nix_nuke_bin_rm remove_old_version config  build_singular build_libsingular build_factory build_libfac  create_singular_script install_docs ; do echo "### Singular spkg-install: $i ###" -    cd "$SRC" && $i +    cd "$SRC" && pwd && $i if [ $? -ne 0 ]; then echo >&2 "Error building Singular (error in $i)." exit 1 </del> <ins> if [ -z "$SAGE_LOCAL" ]; then echo >&2 "Error: SAGE_LOCAL undefined -- exiting..." echo >&2 "Maybe run 'sage -sh'?" </ins>

Related discussion:
text: Since Sage is huge and complicated, I figured I would make this issue to collaboratively track progress and share branches. One big issue is that Sage 7 , instead they use some with scant documentation . has the correct SHA256 for Sage 7.6 and updates a patch file. It currently fails when Sage tries to build . Some nice things to do for the future: ) cc:
thanks for picking this up
Me myself being a miserable loser who has failed to update Sage in the past, I hope you succeed… My attempt hit the following wall. It is unbearably slow to let Sage build everything, but when I had convinced it to use the system versions of majority of dependencies it began to complain cryptically about their interaction in some case.
Can you elaborate? Do you have a branch that has that work? Also, to be clear: I probably don't have the skills or time to upgrade Sage by myself, I was hoping that if we shared our knowledge and de-duplicated efforts we might be able to get closer together
I think it was 6-dot-something; it required a metric ton of adding options to the packages in NixPkgs (I have pushed that all to master long ago), and the Sage tricks are most likely too version-specific. It was long enough ago that I have since abandoned and lost the changes.
In case anybody in here is still waiting for this: I got sage to compile and run. I'm currently trying to minimize the dependencies and check that everything is working correctly (there is one doctest failure, but it was mentioned multiple times in the mailing list and apperas to be harmles -- just a timeout). I'll probably make a PR in the next couple of days.
Code change:
<del> --- old/build/pkgs/singular/spkg-install	2015-07-26 15:34:43.000000000 +0200 +++ new/build/pkgs/singular/spkg-install	2015-09-15 20:42:51.716505855 +0200 @@ -115,6 +115,11 @@ done } </del> <ins> --- old/build/pkgs/singular/spkg-install	2017-10-15 10:35:41.826540964 -0500 +++ new/build/pkgs/singular/spkg-install	2017-10-15 10:36:40.613743443 -0500 @@ -4,6 +4,9 @@ ## Singular ########################################### </ins> <del> +nix_nuke_bin_rm() +{ +    find . -exec sed -e 's@/bin/rm@rm@g' -i '{}' ';' +} </del> <ins> +find . -type f -exec sed -e 's@/bin/rm@rm@g' -i '{}' ';' +#echo '#!/usr/bin/env bashnIgnoring missing $1' > src/build-aux/missing </ins> + <del> remove_old_version() { rm -f "$SAGE_LOCAL"/bin/Singular* @@ -306,11 +311,11 @@ # Actually run all the functions defined above -for i in choose_patches apply_patches remove_old_version config  +for i in choose_patches apply_patches nix_nuke_bin_rm remove_old_version config  build_singular build_libsingular build_factory build_libfac  create_singular_script install_docs ; do echo "### Singular spkg-install: $i ###" -    cd "$SRC" && $i +    cd "$SRC" && pwd && $i if [ $? -ne 0 ]; then echo >&2 "Error building Singular (error in $i)." exit 1 </del> <ins> if [ -z "$SAGE_LOCAL" ]; then echo >&2 "Error: SAGE_LOCAL undefined -- exiting..." echo >&2 "Maybe run 'sage -sh'?" </ins>

Related discussion:
text: Sage needs texlive-core-2014, which is deprecated. Run with modern nixpkgs (i.e. from git) System: NixOS: (Flounder) Nix version: nix-env (Nix) 1.11.2 Nixpkgs version:
Code change:
./patches/widevine-79.patch ]; <del> postPatch = '' </del> <ins> postPatch = optionalString (versionRange "100" "101") '' base64 --decode ${webrtcWaylandScreenshareCoredumpFix} | patch -p1 -d third_party/webrtc '' + '' </ins> # remove unused third-party for lib in ${toString gnSystemLibraries}; do if [ -d "third_party/$lib" ]; then

Related discussion:
text: Chromium coredumps on wayland/sway when trying to share a screen. Steps to reproduce the behavior: sway/wayland "" on "share screen" anywhere -Dump A selector for the screen to share should appear According chromium setting: According nixos configuration: Console output when the error occurs: Also this works fine with firefox-wayland and used to work with chromium. <!-- 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.
Could be related to as it also states
Did screen sharing work before / is that crash (segmentation fault) new? And do you know since which version it stopped working? So far screen sharing did never work reliably and there have been frequent regressions: (I've fixed it twice on my test setup but I've given up since then). We might want to close this issue in favor of to keep the discussion in one place.
For me, screenshare works on Chromium v99, and stopped working after update to v100
For me it also worked in the past without issues. This is new and this is chrome core-dumping. This is a different issue. If screen sharing did not work in the past, it just did not work. It did not cause an out of bounds read or crash of the browser. Please don't close this issue.
Sure, we can leave it open. We should mention it in the other issue though (I just did that) for better visibility. Now we need someone with time and motivation to handle this issue (analyzing the issue, searching for upstream issues, etc. and eventually someone needs to submit a fix).
Since this is NixOS and we have the boon of input-reproducibility and a binary cache, could you post: the nixpkgs commit you are on the nix store path of your chromium binary This will make it even easier for others to reproduce. You may also be able to get the stack trace with GDB using , use , make the segfault happen, and use in GDB.
Code change:
./patches/widevine-79.patch ]; <del> postPatch = '' </del> <ins> postPatch = optionalString (versionRange "100" "101") '' base64 --decode ${webrtcWaylandScreenshareCoredumpFix} | patch -p1 -d third_party/webrtc '' + '' </ins> # remove unused third-party for lib in ${toString gnSystemLibraries}; do if [ -d "third_party/$lib" ]; then

Related discussion:
text: nixpkgs: /nix/store/07346c7jv5wnwg30r5dvmlgqbk52hinz-chromium-100.0.4896.60/bin/chromium
Regarding gdb: ` How do I get gdb on the actual executable but keep the env vars of the shell script wrapper?
Now edit , replacing like this: Then terminate all chromium instances (to avoid joining existing instances), and run .
Thank you for the detailed instructions!
Looks like it should be fixed in m101
I tried to build chromiumDev(102) or chrimiumBeta (101) - but both failed with errors related to:
This patch may be useful: https://webrtc-
I'm a week old to nix, but trying to figure out a way to patch it. It seems it needs a special flag due to it's location:
building chrome is an undertaking not to be embarked on lightly. you can install the chrome dev or beta channel package. On my up-to-date, flakes-enabled nixos-unstable: The issue seems fixed there. There are builds of chromium upstream here: (under other), but I'm not sure if there is a nix derivation for them.
I've opened for a quick and dirty fix - the code isn't pretty but should do the job (I wish would support Base64 patches or even better: Gerrit and gitiles would support fetching patches using a sane format like basically any other web VCS frontend does...). Anyway, I'll check if the VM test passes (although that patch is so trivial that it should be unnecessary) and can merge the fix tomorrow.
I love the name and thanks a lot for your time & effort!
Code change:
# TODO: aarch64-darwin has mcpu incompatible with gcc + optionalString ((targetPlatform ? gcc.arch) && !isClang && !(stdenv.isDarwin && stdenv.isAarch64) && <del> isGccArchSupported targetPlatform.gcc.arch && !disableMarch) '' </del> <ins> isGccArchSupported targetPlatform.gcc.arch) '' </ins> echo "-march=${targetPlatform.gcc.arch}" >> $out/nix-support/cc-cflags-before ''

Related discussion:
text: Since was merged into the master, swift cannot be built on aarch64. Steps to reproduce the behavior: reported in I'm not familiar with swift or clang, but I'm using the following overlay as a workaround until it's fixed. <!-- 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
states that this only fixed the swift build but all downstream packages are still broken. re-opening.
Actually, it seems only dark-mode-notify is broken, others seem fine. Probably because it uses Cocoa or disables sandbox. I don't know for sure.
I noticed that my personal package does not build either. Maybe it's because of swift itself or swiftpm?
The above open PR seems to run into the same issue…
Code change:
, gobject-introspection , itstool , libsecret <ins> , libportal-gtk3 </ins> , gsettings-desktop-schemas , python3 }:

Related discussion:
text: Steps to reproduce the behavior: shotwell from latest nixos-unstable I simply install shotwell with . Noticed that often updates this derivation, last time it was changed by but I don't think his change would cause this. Otherwise - meta.maintainers is empty. Please run and paste the result.
Code change:
cp tool/target/gp.jar "$out/share/java" makeWrapper "${jre8_headless}/bin/java" "$out/bin/gp"  --add-flags "-jar '$out/share/java/gp.jar'"  <del> --prefix LD_LIBRARY_PATH : "${pcsclite.out}/lib" </del> <ins> --prefix LD_LIBRARY_PATH : "${lib.getLib pcsclite}/lib" </ins> ''; meta = with lib; {

Related discussion:
text: uses two actions and do get necessary authorization via . but these actions are not properly registed, leading to error: (It can be verified that these actions don't exist by using ) This breaks and . I tried both pcsclite 1.9.5 and 2.0.1 ending up with the same error. Steps to reproduce the behavior: and in , configure your smartcard (yubikey) to use yubikey error There actions are registered correctly and usable. Please run and paste the result. I'm using flakes (no channels). Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
correct description of your effect, i am not able to use my yubikey with gpg.
This can be solved by
this works, thanks! but this is really unintuitive, given that is already adding the package to : I am leaving this open as I believe a proper fix should be provided in the module itself.
Same issue here. It was working approx. last Dec. I don't have a specific commit hash. Adding to works for me.
Looks like a regression in () - is implying to me that polkit actions get included in the output, however: isn't included, which explains why adding to fixes the issue. Solution ideas: Add to . Not sure about this one? seems to also contain some libraries that probably don't need to be installed. Install polkit actions to instead of . IMO this one makes the most sense, especially as it seems to have been the previous behaviour before this change.
I was bitten by this when attempting to update over the weekend as well. In my case it prevented login because I use smartcards for user login which made debugging difficult due to the number of reboots required. I tend to agree with that going back to having the polkit actions file in the output instead of makes the most sense. That will mean that of the pcsc module will again result in the polkit action file being to the system configuration.
Cc: ()
I also think the location should be fine, the files are also there.
I ran into this issue when I couldn't access my yubikey anymore via pcsc for commits. The above solution worked for me.
Code change:
cp tool/target/gp.jar "$out/share/java" makeWrapper "${jre8_headless}/bin/java" "$out/bin/gp"  --add-flags "-jar '$out/share/java/gp.jar'"  <del> --prefix LD_LIBRARY_PATH : "${pcsclite.out}/lib" </del> <ins> --prefix LD_LIBRARY_PATH : "${lib.getLib pcsclite}/lib" </ins> ''; meta = with lib; {

Related discussion:
text: I'm going to add some comments for SEO so this is easier to find
I think you have found the right culprit that caused the issue, but I suppose the issue has more to do with the itself, where it only includes if . This has been rectified in from what it seems. For now the proper solution seems to enabling polkit with .
I think that makes more sense based on the existing file structure but maybe we just switch bin to out, so it is the default and move the libs to lib instead of being in out.
I've created to make the outputs a lot more expected by moving the udev file and the systemd service to the out output and the libraries to the lib output: I didn't test it yet, so it is still in draft. If someone could verify that it doesn't break security keys again, that would be great and then please undraft it, otherwise I do it in the evening.
I do not think I can fully test this due to the amount of rebuilds, so please chime in for reviews and find the one mistake I might have done (which I hope I didn't)
Tried to build but it fails on my machine:
I've xdist to dulwich here . Let me see if we can just disable some tests as a speed up from 66s to 9s is quite good.
This should be a lot better with . I did a lot of rebuilds locally on a low and high core machine and didn't encounter any failures anymore.
This was fixed in , works fine for me.
Code change:
my $action = shift @ARGV; <ins> if ("@localeArchive@" ne "") { $ENV{LOCALE_ARCHIVE} = "@localeArchive@"; } </ins> if (!defined $action || ($action ne "switch" && $action ne "boot" && $action ne "test" && $action ne "dry-activate")) { print STDERR <<EOF; Usage: $0 [switch|boot|test]

Related discussion:
text: When executing switch-to-configuration in a pure environment it fails: I am calling switch-to-configuration via systemd-run to active a new profile using the Hail update tool. The actual executed script is as follows: Actual output: <preactivating the configuration... perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LCALL = (unset), LANG = "enUS.UTF-8" are supported and installed on your system. perl: warning: Falling back to the standard locale ("C"). setting up /etc... perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LCALL = (unset), LANG = "enUS.UTF-8" are supported and installed on your system. perl: warning: Falling back to the standard locale ("C"). setting up tmpfiles Too few arguments. sh: systemctl: command not found </preThe script works if I pass on the PATH and LOCALE_ARCHIVE environment variables: System: (NixOS: 17.09pre-git (Hummingbird)) Nix version: nix-env (Nix) 1.11.13 Nixpkgs version: nixos-unstable (Commit ) Sandboxing enabled: no (Related Hail issue: )
Code change:
buildPythonPackage rec { pname = "dvc"; <del> version = "3.53.1"; </del> <ins> version = "3.53.2"; </ins> pyproject = true; disabled = pythonOlder "3.8";

Related discussion:
text: Steps to reproduce the behavior: dvc actually it is hash problem. error from my nixos: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
This happens not for the first time and probably not for the last time :cry:
Code change:
<ins> { lib , buildNpmPackage , fetchFromGitHub , fetchpatch }: buildNpmPackage rec { pname = "emmet-ls"; version = "0.4.1"; src = fetchFromGitHub { owner = "aca"; repo = "emmet-ls"; rev = version; hash = "sha256-TmsJpVLF9FZf/6uOM9LZBKC6S3bMPjA3QMiRMPaY9Dg="; }; npmDepsHash = "sha256-Boaxkad7S6H+eTW5AHwBa/zj/f1oAGGSsmW1QrzuFWc="; patches = [ # update package-lock.json as it is outdated (fetchpatch { name = "fix-lock-file-to-match-package-json.patch"; url = "https://github.com/aca/emmet-ls/commit/111111a2c2113f751fa12a716ccfbeae61c32079.patch"; hash = "sha256-/3ZbOBxScnfhL1F66cnIoD2flVeYTJ2sLxNHQ9Yrgjw="; }) ]; meta = with lib; { description = "Emmet support based on LSP"; homepage = "https://github.com/aca/emmet-ls"; changelog = "https://github.com/aca/emmet-ls/releases/tag/${version}"; license = licenses.mit; maintainers = with maintainers; [ figsoda ]; mainProgram = "emmet-ls"; }; } </ins>

Related discussion:
text: Project description Emmet support based on LSP. Metadata source URL: license: mit platforms: all
Code change:
version = "0.43"; src = fetchFromGitHub { <del> owner = "evgeni"; </del> <ins> owner = "linux-thinkpad"; </ins> repo = "tp_smapi"; rev = "tp-smapi/${version}"; sha256 = "1rjb0njckczc2mj05cagvj0lkyvmyk6bw7wkiinv81lw8m90g77g"; <del> name = "tp-smapi-${version}"; </del> }; <ins> patches = [ # update DEFINE_SEMAPHORE usage for linux 6.4+ # https://github.com/linux-thinkpad/tp_smapi/pull/45 (fetchpatch { url = "https://github.com/linux-thinkpad/tp_smapi/commit/0c3398b1acf2a2cabd9cee91dc3fe3d35805fa8b.patch"; hash = "sha256-J/WvijrpHGwFOZMMxnHdNin5eh8vViTcNb4nwsCqsLs="; }) ]; </ins> nativeBuildInputs = kernel.moduleBuildDependencies; hardeningDisable = [ "pic" ];

Related discussion:
text: Steps to reproduce the behavior: on old thinkpad Device: Thinkpad X220 <!-- 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.
greetings ! are you able to test ? an other workaround is to stick to < 6.4 kernel
for now I can't test your commit since I'm newbie and asking you to teach me would take a lot of your time Gonna stick to < 6.4 kernel and try to test commit in free time
appreciate your concerns! from looking at your setup you seem to know fair bit already, and I dont mind spending some time for as long we all learn something useful you should be able to test that PR by changing in your flake to edit: also no rush to test this
Well that was actually easy to test! PR works! I thought I need to use overlays to test it and I have zero experience with them for now.
Code change:
{ lib , stdenv <del> , buildPythonApplication , colorama </del> , fetchFromGitHub , fetchpatch <del> , flask , flask-compress , flask-socketio , gevent-websocket </del> , obfs4 <del> , psutil , packaging , pycrypto , pynacl , pyside6 , pysocks , pytestCheckHook , qrcode </del> <ins> , python3 </ins> , qt5 <del> , requests </del> , snowflake <del> , stem </del> , substituteAll , tor <del> , unidecode , waitress , werkzeug </del> }: let version = "2.6.2"; src = fetchFromGitHub { owner = "onionshare"; repo = "onionshare"; rev = "v${version}"; hash = "sha256-J8Hdriy8eWpHuMCI87a9a/zCR6xafM3A/Tkyom0Ktko="; }; meta = with lib; { description = "Securely and anonymously send and receive files"; longDescription = ''

Related discussion:
text: Steps to reproduce the behavior: onionshare <!-- 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
The package distutils was remove in Python 3.12. Depends on upsteam. I raised a PR for the fix:
Code change:
<ins> diff --git a/configure.pri b/configure.pri index 897bea54..6f834c20 100644 --- a/configure.pri +++ b/configure.pri @@ -269,7 +269,7 @@ defineReplace(webEngineGetMacOSVersion) { } defineReplace(webEngineGetMacOSSDKVersion) { -    value = $$system("/usr/bin/xcodebuild -sdk $$QMAKE_MAC_SDK -version ProductVersion 2>/dev/null") +    value = $$system("xcrun --show-sdk-version") return($$value) } </ins> diff --git a/mkspecs/features/platform.prf b/mkspecs/features/platform.prf <ins> index 35eb6b89..7eed640a 100644 </ins> --- a/mkspecs/features/platform.prf +++ b/mkspecs/features/platform.prf @@ -40,8 +40,6 @@ defineTest(isPlatformSupported) {

Related discussion:
text: The component of the derivation fails to compile on MacOS. But in two ways, and I can't tell what causes one or the other to trigger. On command: On command: the channel compilation failure Compiles.
It has been broken for a while now for different reasons. Maintaining it for darwin is a lot of work and nobody has stepped up to do that. Also, this is a duplicate of
By the way, what is your use case for ?
We're building a desktop version of mobile application and we need for our in-app browser with Ethereum support.
Code change:
<ins> diff --git a/configure.pri b/configure.pri index 897bea54..6f834c20 100644 --- a/configure.pri +++ b/configure.pri @@ -269,7 +269,7 @@ defineReplace(webEngineGetMacOSVersion) { } defineReplace(webEngineGetMacOSSDKVersion) { -    value = $$system("/usr/bin/xcodebuild -sdk $$QMAKE_MAC_SDK -version ProductVersion 2>/dev/null") +    value = $$system("xcrun --show-sdk-version") return($$value) } </ins> diff --git a/mkspecs/features/platform.prf b/mkspecs/features/platform.prf <ins> index 35eb6b89..7eed640a 100644 </ins> --- a/mkspecs/features/platform.prf +++ b/mkspecs/features/platform.prf @@ -40,8 +40,6 @@ defineTest(isPlatformSupported) {

Related discussion:
text: Full log: Error message: That's the result I get from my macOS remote builder. When I run the build on my desktop Mac, it builds fine and uses the impure SDK from my Catalina install (10.15.1): However, the local build displays this warning repeatedly: I assume this is related to the macOS patches and hopefully gives some clue as to why it's broken.
qtbase builds fine on hydra: qtwebengine fails:
Those links point to the same thing. Anyway, strictly speaking I'm trying to build , but it's failing in .
Can you explain what do you mean? How are you using ?
It's a dependency of . edit: sorry, I see what you mean now. is a dependency of . I was confused by the message from the build saying that QT would be installed in .
Sure, depends on . Realistically, your best bet for now is to just use anki from an old version of nixpkgs. You see, doesn't have a darwin maintainer. I think, I was the last person to fix it around last January. The problem is that it's hard to keep up with all the updates. Every "minor" Qt version bump brings serious breaking changes for on darwin (like they might not even support our version of SDK anymore...). To make things worse we port all those bumps to the stable branch, so it quickly breaks there too.
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 .
Still important to me, many qt apps are broken on darwin due to this one.