jiebi/CodeConvo huggingface dataset:
Code change:
# Generate build symbols once after the final build # https://firefox-source-docs.mozilla.org/crash-reporting/uploading_symbol.html <del> preInstall = '' </del> <ins> preInstall = lib.optionalString crashreporterSupport '' </ins> ./mach buildsymbols mkdir -p $symbols/ cp mozobj/dist/*.crashreporter-symbols.zip $symbols/ <ins> '' + '' </ins> cd mozobj '';

Related discussion:
text: Steps to reproduce the behavior: librewolf from nixpkgs master Add any other context about the problem here. Please run and paste the result.
I have the exact same issue but my machine is a little slower :|. Also this means (not just Git ) is now broken.
I also reproduced this on master.
I think it's related to . I'm guessing the crash reporter symbols aren't generated because we disable the crash reporter. Running some tests to confirm.
is the first broken commit on master.
I'm going to close this. The PR by fixes the problem.
Code change:
<ins> { lib , stdenv , fetchFromGitHub , boca , smooth , systemd }: stdenv.mkDerivation rec { pname = "freac"; version = "1.1.3"; src = fetchFromGitHub { owner = "enzo1982"; repo = "freac"; rev = "v${version}"; sha256 = "1sdrsc5pn5901bbds7dj02n71zn5rs4wnv2xxs8ffql4b7jjva0m"; }; buildInputs = [ boca smooth systemd ]; makeFlags = [ "prefix=$(out)" ]; meta = with lib; { description = "The fre:ac audio converter project"; license = licenses.gpl2Plus; homepage = "https://www.freac.org/"; maintainers = with maintainers; [ shamilton ]; platforms = platforms.linux; }; } </ins>

Related discussion:
text: Project description fre:ac is a free audio converter and CD extractor for Microsoft Windows, Linux, macOS and FreeBSD, distributed under the GNU General Public License.[1] Besides extracting audio from compact discs (with various features including hidden track detection), fre:ac can also convert audio files from one format to another or to the same format but a lower bitrate. fre:ac is compatible with many audio formats such as Ogg Vorbis, FLAC, MP3, MP4/M4A, AAC, WAV, WMA and more.[2][3] fre:ac uses the CDex library to convert from CDs and uses freedb to retrieve artist/song information from the internet which is written to the files as various types of ID3 tags; this library supports cdparanoia which aims to improve audio quality.[4] The user interface is multilingual with 43 languages and is able to be a portable install on a USB drive. Metadata homepage URL: source URL: license: GNU General Public License v2.0 platforms: Windows, macOS, Linux, FreeBSD, HaikuOS
freac is already available on my nur repo If you want to avoid building it, it should be on my cachix https://scott- (for nixos-20.9, nixpkgs-unstable and nixos-unstable)
Code change:
, libiconv ? null, ncurses <del> , enableDwarf ? !stdenv.targetPlatform.isDarwin && !stdenv.targetPlatform.isWindows, elfutils # for DWARF support </del> , # GHC can be built with system libffi or a bundled one. libffi ? null

Related discussion:
text: Our can no longer link executables. For example: This issue is present in current versions of . Compiling and linking works fine with an older revision, say . It looks like this might be related to some change in binutils, maybe?
This is probably from
Yes, it is. came to the same conclusion.
This probably is GHC bug though. Things like gmp and libiconv get their paths hardcoded so this isn't a problem. I would expect the same treatment for elfutils. should provide a arg.
/cc
I guess now I know why there's a patch in branch.
I'll reopen the PR fixing the linking issues.
I opened while we wait on upstream fix.
Which one, from
Yes, although it doesn't help. See
Yes, it would have surprised me a bit if it helped against that symptom -- my patch fixes that DWARF-enabling is skipped completely.
I'm surprised this worked for you back then and now there are linking errors.
Code change:
, tables , xlwt , runtimeShell <ins> , isPy38 </ins> , libcxx ? null }:

Related discussion:
text: Describe the bug I cannot make a shell with pandas installed. To Reproduce Expected behavior A shell opens and works. Additional context <details<summaryI get this error message:</summary</detailsNotify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(noah): nixpkgs: Maintainer information:
Code change:
preFixup = '' patchelf --replace-needed liblttng-ust.so.0 liblttng-ust.so $out/lib/libcoreclrtraceptprovider.so patchelf --replace-needed libGraphicsMagick++-Q16.so.12 libGraphicsMagick++.so.12 $out/usr/lib/x86_64-linux-gnu/pcoip-client/vchan_plugins/libvchan-plugin-clipboard.so <ins> patchelf --replace-needed libhiredis.so.0.14 libhiredis.so $out/lib/libpcoip_core.so </ins> ''; installPhase = ''

Related discussion:
text: Package name: aws-workspaces Latest released version: 4.5.0 <!-- Search your package here: --- Current version on the unstable channel: 4.1.0.1523 Current version on the stable/release channel: 4.1.0.1523 <!-- 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.
Code change:
}; }; <ins> systemd.user.generators = mkOption { type = types.attrsOf types.path; default = {}; example = { systemd-gpt-auto-generator = "/dev/null"; }; description = '' Definition of systemd generators; see {manpage}`systemd.generator(5)`. For each `NAME = VALUE` pair of the attrSet, a link is generated from `/etc/systemd/user-generators/NAME` to `VALUE`. ''; }; </ins> systemd.additionalUpstreamUserUnits = mkOption { default = []; type = types.listOf types.str;

Related discussion:
text: Unable to use Podman's quadlets feature for a user, since the service unit files are not generated by systemd. Steps to reproduce the behavior: a quadlet file in (say, ) . Systemd says that no unit files were found. Caddy service should have been generated and its status displayed. This issue is caused by not symlinking the provided by the package to . Does not occur at the system level, since is already symlinked to Fix: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Confirmed the quadlet systemd user generator is not found in /etc/systemd. I'm gonna take this one and try to come up with a fix in NixOS module.
Code change:
runHook preBuild mvnDeps=$(cp -dpR ${fetchedMavenDeps}/.m2 ./ && chmod +w -R .m2 && pwd) <del> mvn package --offline "-Dmaven.repo.local=$mvnDeps/.m2" -P desktop,all-platforms </del> <ins> mvn package --offline "-Dmaven.repo.local=$mvnDeps/.m2" ${mvnParameters} </ins> runHook postBuild '';

Related discussion:
text: The dbeaver package does not build on . Steps to reproduce the behavior: Dbeaver should build <details<summaryTruncated build log</summary<br</details
Code change:
, babel , buildPythonPackage , fetchFromGitLab <ins> , fetchpatch </ins> , pythonRelaxDepsHook , html2text , lxml

Related discussion:
text: When used through the command line, complains about imports and fails. <!-- 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]:
I've opened but haven't had the time to test it quite yet. If you get around to it before me feel free to merge it
I suggest another fix in
Code change:
systemd.services.garage = { description = "Garage Object Storage (S3 compatible)"; <del> after = [ "network.target" "network-online.target" ]; wants = [ "network.target" "network-online.target" ]; </del> <ins> after = [ "network.target" "network-online.target" ]; wants = [ "network.target" "network-online.target" ]; </ins> wantedBy = [ "multi-user.target" ]; <del> restartTriggers = [ configFile ] ++ (lib.optional (cfg.environmentFile != null) cfg.environmentFile); </del> <ins> restartTriggers = [ configFile ] ++ (lib.optional (cfg.environmentFile != null) cfg.environmentFile); </ins> serviceConfig = { ExecStart = "${cfg.package}/bin/garage server"; <del> StateDirectory = mkIf (hasPrefix "/var/lib/garage" cfg.settings.data_dir || hasPrefix "/var/lib/garage" cfg.settings.metadata_dir) "garage"; </del> <ins> StateDirectory = mkIf ( anyHasPrefix "/var/lib/garage" cfg.settings.data_dir || hasPrefix "/var/lib/garage" cfg.settings.metadata_dir ) "garage"; </ins> DynamicUser = lib.mkDefault true; ProtectHome = true; NoNewPrivileges = true;

Related discussion:
text: Steps to reproduce the behavior: -rebuild test on settings.datadir = "/mnt/garage0"; resolves fine Tested on nixos24.05 but code of the module is unchanged in nixos_unstable. I'm using flakes as well Please run and paste the result.
Looks like doesn't apply, maybe should tinker a bit on my own
It looks like the option type was adjusted, but not the other code in the module that checks that value. Shouldn't be too hard to fix.
Code change:
<del> { stdenv, fetchurl, libpng }: </del> <ins> { stdenv, fetchurl, libpng, perl, perlPackages, makeWrapper }: </ins> stdenv.mkDerivation rec { name = "icoutils-0.31.0";

Related discussion:
text: icoutils' extresso missing perl dependencies. install pkgs.icoutils and execute "extresso" in shell. This works(): NixOS 16.03
Code change:
patchExecutable genymotion patchExecutable player <del> patchExecutable qemu/x86_64/bin/qemu-img patchExecutable qemu/x86_64/bin/qemu-system-x86_64 </del> <ins> patchInterpreter qemu/x86_64/bin/qemu-img patchInterpreter qemu/x86_64/bin/qemu-system-x86_64 </ins> patchTool adb patchTool aapt

Related discussion:
text: I used Genymotion for a long time on macOS but with Virtualbox. I switch to Linux/nixOS about 5 months ago and was pleasantly surprised to read Genymotion now supported the QEMU engine. Alas, myself and a few other of my friends were never able to get Genymotion to work using QEMU, which is the preferred Hypervisor. I've tried to source some help at but to no avail. Steps to reproduce the behavior: a running working QEMU installation. Presumably with at least 1 functional VM too Genymotion Genymotion, ensure QEMU is selected as the Hypervisor a random Android device, add it and run it. 'll first get a 'can't start virtual device' error trying to start the Android device again gives a 'Another QEMU process appears to be using the same resources' error I'd expect Genymotion to start the Android device using QEMU, naturally If applicable, add screenshots to help explain your problem. 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]: ! !
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
! !
Duplicate of . Does the workaround in work for you?
I'm not really sure this is a duplicate but that's up to you. I'm not a coder so had no idea what to do with that old 'work-around' either. I had a colleague who kindly looked at it, spent some time, and turned it in to a flake which can be found at And now the broken Genymotion functions great with QEMU. Perhaps the flake code can help in fixing the package. Thanks for the pointer to the old work-around
Code change:
patchExecutable genymotion patchExecutable player <del> patchExecutable qemu/x86_64/bin/qemu-img patchExecutable qemu/x86_64/bin/qemu-system-x86_64 </del> <ins> patchInterpreter qemu/x86_64/bin/qemu-img patchInterpreter qemu/x86_64/bin/qemu-system-x86_64 </ins> patchTool adb patchTool aapt

Related discussion:
text: Steps to reproduce the behavior: ... ... ... A clear and concise description of what you expected to happen. If applicable, add screenshots to help explain your problem. 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.
Hey have you ever made Genymotion work under Wayland ? For instance, on any other distribution ? I'm not sure the support for Wayland has dropped quite officially for Genymotion or I might be wrong, maybe there is no need since it's a QT based graphic interface and platform plugins do exist for Wayland nowadays. EDIT: To add more information, on ArchLinux, here is what I'm getting as an error you might want to share your exact genymotion logs I'm running Sway and I have the following env variables set : QTQPAPLATFORMTHEME="qt5ct" QTQPAPLATFORM=wayland #QTWAYLANDFORCEDPI=physical #QTWAYLANDDISABLEWINDOWDECORATION=1 XDGSESSIONTYPE=wayland XDGSESSIONDESKTOP=sway XDGCURRENTDESKTOP=sway
Okay so I made it work on my end but I'm not under NixOS/not using Genymotion installed from Nix, try
I have run with , but still get error. and this is the QT relate envs and this is XDG relate envs
Could you give a try and use every single platform listed here :
Also please share your genymotion logs, there might be more to the error in there And finally, please let us know your exact Desktop Environnement, Wayland is being used, I suppose.
One more thing, could you retry using xcb as a platform after having installed in the environnement ? EDIT : Also set So to sum up run :
I am using wayland + plasma, so I think the dependencies is ok and this is
This may not fix your issue, but try it with this : ! EDIT: Also are you running with an Nvidia GPU or not Wayland ? If yes, you should try everything related as well.
Code change:
patchExecutable genymotion patchExecutable player <del> patchExecutable qemu/x86_64/bin/qemu-img patchExecutable qemu/x86_64/bin/qemu-system-x86_64 </del> <ins> patchInterpreter qemu/x86_64/bin/qemu-img patchInterpreter qemu/x86_64/bin/qemu-system-x86_64 </ins> patchTool adb patchTool aapt

Related discussion:
text: EDIT2: I've found this so I believe it should work, but something may be wrong, I may need to look at the Nix definition of the package and compare with the way it is packaged for ArchLinux and see if there is anything that could explain what's going on. ! There could be also issues regarding Wayland + Plasma : If you could try another desktop environment, maybe Sway if possible, if you cannot, I will give this a try in a VM under the latest NixOS when I have some time.
See this commit too this maybe a fix, that you don't have yet, maybe you have it already because it's been backported.
Could you please the run of the command ? And uploads the logs to a GitHub Gist. If you can't or are busy, let me know, I'll try to reproduce inside a VM and investigate.
This is the log
I know what causes this problem, because I have different qt version, so I have to add to , and it works for me, thanks for your patience and help
Should I make a PR?
Hm I'm not familiar with the process but I believe you should make a PR if you can or maybe let's tag the maintainer of Genymotion here ? I believe it is
Let's wait a week or 2, if he answers back and can make the PR then you can wait to close this issue once the PR gets merged.
Still relevant. Genymotion tries to load some Qt plugins from nixpkgs and fails for whatever reason. I was able to workaround it by doing . used to work before too but is failing now (and it's unclear why, since its effects are similar to , I guess genymotion still picks something from env vars besides plugins)
Hi! I'm there is seems no this issue on unstable, but I've found another one - Can't start virtual device: qemu libpixmin not found. Here is log: Should I create another issue?
That's weird, I believe you should open a new issue yes however I'm not sure if including as a dependency in the derivation of might fix your issue : Running outputs :
as the maintainer of genymotion's package in Nixpkgs any advice/idea, what's going wrong ?
Seems like you were trying to launch genymotion with qemu instead of virtualbox.
Code change:
patchExecutable genymotion patchExecutable player <del> patchExecutable qemu/x86_64/bin/qemu-img patchExecutable qemu/x86_64/bin/qemu-system-x86_64 </del> <ins> patchInterpreter qemu/x86_64/bin/qemu-img patchInterpreter qemu/x86_64/bin/qemu-system-x86_64 </ins> patchTool adb patchTool aapt

Related discussion:
text: A while ago I managed to make qemu version working (at least on my machine) by adding some bloaty dependencies: I didn't test it on latest unstable, but you could give it a shot. It also workarounds that Qt issue via in wrapper.
Code change:
, gtk3 , libextractor , libgcrypt <ins> , libsodium </ins> , libxml2 , pkg-config , wrapGAppsHook

Related discussion:
text: Describe the bug To Reproduce Steps to reproduce the behavior: ... ... ... Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screenshots to help explain your problem. Additional context Add any other context about the problem here. Notify maintainers and edited it last Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
I really have no idea, contains it, even bumping gnunet-gtk to be the same release version still doesn't fix it.
Have you tried applying
Code change:
attr bash btrfs-progs <ins> cdrkit </ins> criu dnsmasq <ins> e2fsprogs getent </ins> gnutar gptfdisk gzip iproute2 iptables <ins> kmod lvm2 minio nftables </ins> qemu_kvm qemu-utils rsync squashfsTools <ins> thin-provisioning-tools </ins> util-linux virtiofsd xz

Related discussion:
text: When tries to create a volume of type=block, it cannot be created due to the occurrence of . This is because is not registered in . Steps to reproduce the behavior: Create block type volume. If you check nixpkgs for lxd 5.20, you can see other package dependencies that are not present in incus. For example with lvm, this is expected to severely impact the lvm backend. (Currently, it cannot be confirmed because there is no lvm drive.) Can we change it in the same way as lxd? <!-- 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]:
Opened a PR to fix. Sorry about that. Not sure why I dropped these...
Code change:
mkdir -p $out/share/powershell cp -r * $out/share/powershell makeWrapper $out/share/powershell/pwsh $out/bin/pwsh --prefix ${platformLdLibraryPath} : "${stdenv.lib.makeLibraryPath libraries}"  <del> --set TERM xterm --set POWERSHELL_TELEMETRY_OPTOUT 1 </del> <ins> --set TERM xterm --set POWERSHELL_TELEMETRY_OPTOUT 1 --set DOTNET_CLI_TELEMETRY_OPTOUT 1 </ins> ''; dontStrip = true;

Related discussion:
text: Cc (PowerShell maintainer) Describe the bug Powershell uses telemetry unless explicitly told not to do it. In addition to its own environment variable (already set in the wrapper), it should require another one to disable telemetry from the underlying .NET platform, i.e. should be set to To Reproduce Steps to reproduce the behavior: powershell with (assumes you have the unstable channel installed) it with and verify that it's not set (i.e. no output) Expected behavior should be set to : Additional context Example of PowerShell's own CI config that disables telemetry on Linux: This should be fairly easy to change here: Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(user): nixpkgs: Maintainer information:
Code change:
export TZ="$new_TZ" fi fi <ins> # udev event notifications don't work reliably inside containers. # SDL2 already tries to automatically detect flatpak and pressure-vessel # and falls back to inotify-based discovery [1]. We make SDL2 do the # same by telling it explicitly. # # [1] <https://github.com/libsdl-org/SDL/commit/8e2746cfb6e1f1a1da5088241a1440fd2535e321> export SDL_JOYSTICK_DISABLE_UDEV=1 </ins> '' + extraProfile; runScript = writeScript "steam-wrapper.sh" ''

Related discussion:
text: Describe the bug I'm trying to get Steam big picture to work with , xbox wireless adapter and a couple of xbox controllers. But if Steam is already running and I turn on my controllers, they successfully connect to the dongle, but steam doesn't detect them. If i first turn on the controllers, and then i start Steam, it recognizes them and they work fine. xow: I couldn't use the service file provided by the package because it would never start. I read somewhere that systemd is picky with symlinks, so i defined it myself, now it's starting fine. I also had to blacklist else xow would crash. Steam: To Reproduce Steps to reproduce the behavior: sure xow is running fine Steam on steam controllers to see if they work (they dont) Additional context I think xow is working fine. I tried the latest version (0.5) and the last commit, importing udev rules from the package and adding them to I also tried adding my user to the group. It doesn't matter if steam is running in big picture or not, i also tried steam native, still not working. Metadata Edit: Steam won't detect controllers even when using the wire. And also i tested the controllers with and and they work as expected. So i'm pretty sure the issue must be with steam.
This might be an upstream problem with , have you tried using it on a non NixOS system? I also maintain (a kernel driver for Xbox controllers) and I don't have this problem with Steam. Maybe try to test if there's still a problem on your system with xpadneo?
You might also want to try enabling xow using the NixOS module instead of writing a custom service:
Yes, i have another system with Arch and it's working fine there. Steam detects controller connections even when it's already running. That's what i tried at first, but xow wouldn't start, the service was hanging in an state. And I think it might be because when importing the service from the package, nix is creating a symlink to the service and it might cause some issues.