jiebi/CodeConvo huggingface dataset:
Code change:
python3Packages.buildPythonPackage rec { pname = "yubikey-manager"; version = "4.0.7"; <ins> format = "pyproject"; </ins> src = fetchFromGitHub { repo = "yubikey-manager";

Related discussion:
text: Not valid cryptography in python3 ... Steps to reproduce the behavior: switch "Screenshot" Install yubikey-manager ;) 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. -- as cryptography maintainer Please run and paste the result.
Code change:
<del> { qtModule, qtCompatVersion, qtdeclarative, qtquickcontrols, qtlocation, qtwebchannel </del> <ins> { qtModule , qtdeclarative, qtquickcontrols, qtlocation, qtwebchannel </ins> , bison, coreutils, flex, git, gperf, ninja, pkgconfig, python2, which

Related discussion:
text: Describe the bug qtwebengine fails just after successfully configuring with error message To Reproduce ` Expected behavior should compile Notify maintainers Metadata
Pull request works on my machine. Thx.
Code change:
./0001-toolchain.patch ]; <ins> nativeBuildInputs = [ makeWrapper ]; </ins> buildInputs = [ gnu-efi ]; hardeningDisable = [ "stackprotector" ];

Related discussion:
text: efibootmgr is not a dependency, despite being needed Steps to reproduce the behavior: refind refind-install the error message: ! efibootmgr is a dependency of refind I already had refind installed (from another distro) Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Code change:
description = "Mailman package to use"; }; <ins> enablePostfix = mkOption { type = types.bool; default = true; example = false; description = '' Enable Postfix integration. Requires an active Postfix installation. If you want to use another MTA, set this option to false and configure settings in services.mailman.settings.mta. Refer to the Mailman manual for more info. ''; }; </ins> siteOwner = mkOption { type = types.str; example = "postmaster@example.org";

Related discussion:
text: Describe the bug Mailman module in NixOS requires postfix enabled and has no way to configure Mailman to work with other MTAs supported by both NixOS and mailman upstream. To Reproduce Steps to reproduce the behavior: postfix mailman the evaluation with an assertion Expected behavior The Mailman module allows to select an MTA of choice (or even adapts to the currently enabled MTA) Screenshots n/a Additional context Notify maintainers cc Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(vika): nixpkgs: Maintainer information:
It looks like exim's configuration should be RFC42-ised first if we want to inject Mailman-related settings into Exim config, which is a requirement (Mailman requires a custom Exim router and transport).
Yes, the module is currently quite opinionated. If you're willing to contribute exim support that's great.
I see how I could make it work, but the first version of it will require manual editing of Exim's config files (because RFC42-ising Exim will be a pain, even though I have some drafts on how to translate Nix into the syntax that's required), and I'm not sure if it will be merge-worthy enough :3
Exim config is complicated enough as is, I'm not sure adding an intermediate layer from nix will help that much. I also don't really see this integrating well with existing or other exim config. I'm honestly kind of surprised this works for postfix.
Code change:
arrow werkzeug click <ins> html5lib vcrpy </ins> ]; <ins> postPatch = '' # Jailbreak problematic dependencies sed -i  -e "s,'PyYAML.*','PyYAML',g"  setup.py ''; </ins> preCheck = '' # Fixes two tests for wrong encoding export PYTHONIOENCODING=utf-8

Related discussion:
text: tests pass, while tests fail with: Official Hydra sees the same thing: with their Travis setup. (That is a build of a recent commit, but I still see the same failures after pointing at a checkout of ) Does anyone have any ideas? With nixpkgs master,
See scrapinghub/dateparser, scrapinghub/dateparser and scrapinghub/dateparser.
As long as this problem remains, the best thing to do is using for affected application. Switching to should be done in commits that don't change anything else and that reference this issue in their commit message so that they can easily be reverted. Simply skipping the tests does not make much sense since these are real incompatibilities.
Code change:
echo -n "$startScript" > $out/bin/${pname} chmod +x $out/bin/${pname} <del> ln -s ${androidStudio}/bin/studio.png $out/share/pixmaps/${drvName}.png </del> <ins> ln -s ${androidStudio}/bin/studio.png $out/share/pixmaps/${pname}.png </ins> ln -s ${desktopItem}/share/applications $out/share/applications ''

Related discussion:
text: I'm using NixOS "/ on tmpfs" mode, so I persist my dconf by using a module of home-manager. When I persist the state of GNOME app drawer, I need to write down desktop file name to .nix config. But currently, Android Studio's desktop contains a string of version, this because contains . Details: I also notice used in icon too, which will cause icon file contains version string, I think we can remove them too. If maintainer agrees, I will make a PR to deal with this. Also, I noticed another maintainer deleted the account: Maybe I can send him / her an E-mail for asking what happened, and drop the maintainer info.
Code change:
value.fsType = "9p"; value.neededForBoot = true; value.options = <del> [ "trans=virtio" "version=9p2000.L"  "msize=${toString cfg.msize}" ] </del> <ins> [ "trans=virtio" "version=9p2000.L"  "msize=${toString cfg.msize}" "x-systemd.requires=modprobe@9pnet_virtio.service" ] </ins> ++ lib.optional (tag == "nix-store") "cache=loose"; }; in lib.mkMerge [

Related discussion:
text: The systemd initrd (or stage1) does not work with a volatile root when there are 9p mounts present. A result of this is that VMs built with nixos/qemu-vm do not work when disabling the (and thus running on a tmpfs) and using the systemd initrd. Create a test that sets these options: The test should work just like the test works in who has identified the root cause (an ordering issue where the tmpfs is mounted before the 9p infrastructure is up) and found a hack around this behaviour.
I this to the board because it will require a test when it is fixed.
As a side note, we should consider using to implement volatile root with systemd stage 1.
As far as I can tell we could only do this if we mounted under .
So this works probabilistically. Sometimes it succeeds, and sometimes it fails with for one of the 9p file systems.
Ok this patch seems to fix it Which begs the question... why does it ever work, with or without volatile root? EDIT: Oh I bet it's a race condition caused by not depending on . In order for to appear, virtio modules need to have already been loaded. So, because gets mounted first, and needs to wait for to appear, that means virtio modules are definitely already loaded before any children of are mounted. And indeed, switching from to just does the trick as well.
Code change:
CoreWLAN Quartz Cocoa <ins> LocalAuthentication </ins> openbsm libunwind

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:
CoreWLAN Quartz Cocoa <ins> LocalAuthentication </ins> openbsm libunwind

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.
Code change:
quazip ghc_filesystem tomlplusplus <del> ] ++ lib.optional (lib.versionAtLeast qtbase.version "6") qtwayland; </del> <ins> ] ++ lib.optional (lib.versionAtLeast qtbase.version "6") qtwayland ++ lib.optional gamemodeSupport gamemode.dev; </ins> cmakeFlags = lib.optionals (msaClientID != "") [ "-DLauncher_MSA_CLIENT_ID=${msaClientID}" ] ++ lib.optionals (lib.versionAtLeast qtbase.version "6") [ "-DLauncher_QT_VERSION_MAJOR=6" ];

Related discussion:
text: A clear and concise description of what the bug is. Prism Launcher doesn't allow enabling Feral GameMode or MangoHud under the "Performance" tab because it can't find it. Steps to reproduce the behavior: GameMode ( ) MangoHud ( ) Prism Launcher ( ) new instance in Prism Launcher instance and go to "Performance" tab A clear and concise description of what you expected to happen. GameMode and MangoHud should be able to be enabled when installed. 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.
Addressed here -
Code change:
https://github.com/liuchengxu/space-vim/,, https://github.com/ctjhoa/spacevim/,, https://github.com/chrisgeo/sparkup/,, <del> https://github.com/edluffy/specs.nvim/,, </del> <ins> https://github.com/cxwx/specs.nvim/,HEAD, </ins> https://github.com/lewis6991/spellsitter.nvim/,HEAD, https://github.com/stsewd/sphinx.nvim/,, https://github.com/sjl/splice.vim/,,

Related discussion:
text: Specs-nvim does not work in Neovim 0.10 and the author has not updated the upstream version. The derivation should point to the updated fork instead: Steps to reproduce the behavior: specs-nvim with Neovim 0.10 specs-nvim errors Should I have used the out-of-date packaging report issue template instead? Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
no pb for me. Feel free to submit a PR. Pinging as he might know better.
What does no pb mean? I'll make a PR
I guess that it means "go for it, let's switch to the fork".
Code change:
, mpv , qtmultimedia , qtquickcontrols2 <ins> , yt-dlp </ins> }: mkDerivation {

Related discussion:
text: plasmatube can't play the video (black screen). probably need to add a dependency or similar. Steps to reproduce the behavior: plasmatube can play videos from youtube. ! system: host os: multi-user?: sandbox: version: channels(hervyqa): channels(root): nixpkgs:
solved, need install . !
Code change:
''; license = licenses.lgpl3; platforms = platforms.unix; <del> maintainers = with maintainers; [ sjmackenzie ]; </del> <ins> maintainers = with maintainers; [ sjmackenzie bertof ]; </ins> }; }

Related discussion:
text: The default boost version has been bumped from 1.69 (or 1.75) to 1.77. This is a notice for maintainers that the following packages are now failing to build: - - - - - - - - - - [x] cryfs A typical fix would involve pinning the package to a specific version (e.g. see )
My fix in is not the same as . Is there a very good reason to prefer one over the other ?
Well, I like trying to keep it away from the huge top-level file. (which is e.g. harder to use in git)
Re. pivx, I think we should mark it broken. Our current version is very old (and therefore useless), and the new version includes a rust build. I don't have the capacity to fix this ATM.
In my case, what broke it was the update from boost175 to boost177. Fix is in .
It's in the branch now, so please target any further fixes there as well (unless they're a mass rebuild, etc.)
colobot fixed with
FYI, ledger has some broken behavior with the new boost version, although it curiously doesn't cause a test failure: ledger/ledger.
Our expression does not attempt to run tests.
Ah, that would be why, thanks. Nevertheless, the binary exhibits the same problem described in that issue in interactive use.
Code change:
datagrip = buildDataGrip rec { name = "datagrip-${version}"; <del> version = "2019.3.4"; /* updated by script */ </del> <ins> version = "2020.1"; /* updated by script */ </ins> description = "Your Swiss Army Knife for Databases and SQL"; license = stdenv.lib.licenses.unfree; src = fetchurl { url = "https://download.jetbrains.com/datagrip/${name}.tar.gz"; <del> sha256 = "1ygbi212sga6mdkassi51idh7ppchr77ifq3vi5bbm4ibgnsf2b4"; /* updated by script */ </del> <ins> sha256 = "1z3asz9fp3xnmbhngar60g8rba83kx987ar67j5m8ws7cijqlzix"; /* updated by script */ </ins> }; wmClass = "jetbrains-datagrip"; update-channel = "DataGrip RELEASE";

Related discussion:
text: Please update Goland to a current version. The Current Version is now 2020.1 Thx and Greetz
Code change:
{stdenv, fetchgit, fetchsvn, autoconf, automake, libtool, gfortran, clang, cmake, gnumake, hwloc, jre, liblapack, blas, hdf5, expat, ncurses, readline, qt4, webkitgtk, which, lp_solve, omniorb, sqlite, libatomic_ops, pkgconfig, file, gettext, flex, bison, <del> doxygen, boost, openscenegraph, gnome2, pangox_compat, xorg, git, bash, gtk2, makeWrapper }: </del> <ins> doxygen, boost, openscenegraph, gnome2, xorg, git, bash, gtk2, makeWrapper }: </ins> let

Related discussion:
text: Describe the bug Seems like some updates to pango broke a few packages Among the broken ones: ettercap (see ) pangox-compat (which anydesk needs) probably a few more To Reproduce Steps to reproduce the behavior: to build ettercap or anydesk from master will fail to build with some pango-related errors Expected behavior It should work Screenshots If applicable, add screenshots to help explain your problem. Additional context Add any other context about the problem here. Metadata system: host os: multi-user?: sandbox: version: channels(maciej): nixpkgs: Maintainer information:
Also remmina is broken But doesn't seem to depend on pango directly, so unsure which dependency actually is broken
Here's an issue for pangox-compat
Lutris is broken too - not an urgent requirement but just making you fine folks aware!
Not sure why Lutris is broken, but Lutris-unwrap is fine.
It's a failure in the dependency chain, in this case .
no longer depends on on its master branch: We should probably switch to that. should not be needed in according to the README in , I suspect it was only there because we did not propagate it until ebassi also suggests switching to HEAD and says we need not worry about ABI changes:
Not having pangox_compat fixed is definitively still an issue. Can this be re-opened?
After , the only program depending on this is anydesk and openmodelica which is broken.
So it breaks anydesk thus either we mark anydesk as broken or we fix that?
Anydesk shouldn't use this deprecated library. Yes, we can mark it as broken.
Code change:
owner = "named-data"; repo = pname; rev = "ndn-tools-${version}"; <del> sha256 = "1q2d0v8srqjbvigr570qw6ia0d9f88aj26ccyxkzjjwwqdx3y4fy"; </del> <ins> sha256 = "sha256-3hE/esOcS/ln94wZIRVCLjWgouEYnJJf3EvirNEGTeA="; </ins> }; nativeBuildInputs = [ pkg-config sphinx wafHook ]; buildInputs = [ libpcap ndn-cxx openssl ]; wafConfigureFlags = [ <del> "--boost-includes=${boost.dev}/include" "--boost-libs=${boost.out}/lib" "--with-tests" </del> <ins> "--boost-includes=${boost175.dev}/include" "--boost-libs=${boost175.out}/lib" # "--with-tests" </ins> ]; <del> doCheck = true; </del> <ins> doCheck = false; </ins> checkPhase = '' <ins> runHook preCheck </ins> build/unit-tests <ins> runHook postCheck </ins> ''; meta = with lib; {

Related discussion:
text: The default boost version has been bumped from 1.69 (or 1.75) to 1.77. This is a notice for maintainers that the following packages are now failing to build: - - - - - - - - - - [x] cryfs A typical fix would involve pinning the package to a specific version (e.g. see )
My fix in is not the same as . Is there a very good reason to prefer one over the other ?
Well, I like trying to keep it away from the huge top-level file. (which is e.g. harder to use in git)
Re. pivx, I think we should mark it broken. Our current version is very old (and therefore useless), and the new version includes a rust build. I don't have the capacity to fix this ATM.
In my case, what broke it was the update from boost175 to boost177. Fix is in .
It's in the branch now, so please target any further fixes there as well (unless they're a mass rebuild, etc.)
colobot fixed with
FYI, ledger has some broken behavior with the new boost version, although it curiously doesn't cause a test failure: ledger/ledger.
Our expression does not attempt to run tests.
Ah, that would be why, thanks. Nevertheless, the binary exhibits the same problem described in that issue in interactive use.
Code change:
mesaPackage = mkOption { type = types.package; <del> default = pkgs.mesa_23; defaultText = literalExpression "pkgs.mesa_23"; </del> <ins> default = pkgs.mesa; defaultText = literalExpression "pkgs.mesa"; </ins> example = literalExpression "pkgs.mesa_22"; description = lib.mdDoc '' The Mesa driver package used for rendering support on the system.

Related discussion:
text: The laptop screen freezes with the current contents (systemd startup messages) at the point starts. Nothing else visible happens. I can switch VT's back to text consoles, switching back to VT7 again just freezes the display. All the normal processes seem to be running, but they don't draw anything. I'm using gnome and wayland. Updated to today's () Booted previous system generation, was working again. With some excellent help on Matrix from I have confirmed that: building from previous branch revision () and switching (no reboot) makes gdm work again. building from current revision () with also works. building from the previous revision with that line fails to evaluate, because the multi-version package change isn't there yet. So / are clearly implicated. K900 suggested raising this as an upstream Mesa bug. I had some issues registering there, but may try again later and will add a link here in case system: host os: multi-user?: sandbox: version: channels(root): channels(dan): nixpkgs: bits of relevant config: note that the displaylink driver is not in use (no device connected) at this point, it's all on the internal display only. Hardware is a Dell XPS 13 9360
Code change:
mesaPackage = mkOption { type = types.package; <del> default = pkgs.mesa_23; defaultText = literalExpression "pkgs.mesa_23"; </del> <ins> default = pkgs.mesa; defaultText = literalExpression "pkgs.mesa"; </ins> example = literalExpression "pkgs.mesa_22"; description = lib.mdDoc '' The Mesa driver package used for rendering support on the system.

Related discussion:
text: If gdm is enabled with Gnome enabled, gdm will crash and not load into the login screen after logout or reboot. This is due to gdm using wayland as the default. Once wayland is disabled in gdm, the login works. Steps to reproduce the behavior: channel nixos-unstable, "sudo nixos-rebuild switch upgrade-all" with Gnome enabled and gdm enabled in will hang at the gdm check point. gdm wayland in and the reboot works but with Wayland not working. Reboot into gdm with Wayland <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
I just hit the same issue. After updating to latest nixos-unstable, the boot hangs just before login screen I think this is related to , at least the workaround posted there worked for me also
Would be relevant with a machine without AMD graphics and without KDE? As, I am running Intel's build in graphics and using Gnome. Also, I did find a "workaround" by disabling wayland in gdm then nixos-unstable will boot.
I managed to work around this issue with on GNOME Wayland. Graphic card: Intel Xe Graphics (TGL GT2)
Totally worked! Thanks and ! Should I leave this open as this is a bug or a new config that needs to be applied to 23.05?
Code change:
CapabilityBoundingSet = ""; # ProtectClock= adds DeviceAllow=char-rtc r DeviceAllow = ""; <del> LockPersonality = true; </del> NoNewPrivileges = true; PrivateDevices = true; PrivateMounts = true;

Related discussion:
text: introduced systemd syscall filtering which seems overly restrictive for common use cases. We use for coverage reports of our Rust projects which makes use of the ptrace(2) system call (denied by ). Android projects commonly rely on which uses chown(2) (denied by ). In my opinion, those use cases are too common and should work out of the box. Also, workflow failures are difficult to debug if syscall filtering (or any hardening) steps in. I'd suggest to revise the syscall filtering: Also, it might help with debugging or employing a custom hardening configuration if we add a module option which defaults to . Please run and paste the result.
I agree that if the hardening make github-runner not to work as expected or as "standard" installation, we should remove them or make them optional with new option Do you want it to default to ? Maybe better with so it work as expected out of box?
also noted problems with makefile workflows in that I have been able to reproduce. I am sorry I did not catch this when making the changes originally. My usecase was running binaries on uncommon targets (e.g. ) connected over USB; and I only had light testing for other usecases. I have since a makefile test to the runner I use for testing package/module updates and will add a coverage workflow now too. I am ok with removing the harderning entirely, or making it more permissive. I only this because at the time I thought it would be a sane default for majority of applications. I would prefer we keep some hardening. Most people probably do not want a CI process to change the clock, hostname, or reboot the system entirely. I have been working on this in the background since reported issues; this is what I have come up with so far, I have not tested it with yet (will do that later this weekend); but it does allow and debug related tools such as to function. In addition to changes should also be changed to so that nix does not emit warnings when running.
:+1: :+1: Yes, all this hardening is already available and entirely optional! Every user is free to add anything to that they want.