jiebi/CodeConvo huggingface dataset:
Change:
After installing a fresh system with the following configuration: the file is not created, hence wpasupplicant fails to start with the following error: nixpkgs
I don't know the logic of , but I think you're supposed to provide the file yourself. I guess it could be ed if wpa_supplicant fails without one.
You can do
That probably wouldn't work due to permissions. EDIT: wpa_supplicant is still running as root, so it should work.
Fixed in

Discussion:
fi ''} <ins> # ensure wpa_supplicant.conf exists, or the daemon will fail to start ${optionalString cfg.allowAuxiliaryImperativeNetworks '' touch /etc/wpa_supplicant.conf ''} </ins> # substitute environment variables if [ -f "${configFile}" ]; then ${pkgs.gawk}/bin/awk '{

}; }; <ins> imperative = { ... }: { imports = [ ../modules/profiles/minimal.nix ]; # add a virtual wlan interface boot.kernelModules = [ "mac80211_hwsim" ]; # wireless client networking.wireless = { enable = lib.mkOverride 0 true; userControlled.enable = true; allowAuxiliaryImperativeNetworks = true; interfaces = [ "wlan1" ]; }; }; </ins> # Test connecting to the SAE-only hotspot using SAE machineSae = machineWithHostapd { networking.wireless = {

assert "Failed to connect" not in status,  "Failed to connect to the daemon" <ins> with subtest("Daemon can be configured imperatively"): imperative.wait_for_unit("wpa_supplicant-wlan1.service") imperative.wait_until_succeeds("wpa_cli -i wlan1 status") imperative.succeed("wpa_cli -i wlan1 add_network") imperative.succeed("wpa_cli -i wlan1 set_network 0 ssid '"nixos-test"'") imperative.succeed("wpa_cli -i wlan1 set_network 0 psk '"reproducibility"'") imperative.succeed("wpa_cli -i wlan1 save_config") imperative.succeed("grep -q nixos-test /etc/wpa_supplicant.conf") </ins> machineSae.wait_for_unit("hostapd.service") machineSae.copy_from_vm("/run/hostapd/wlan0.hostapd.conf") with subtest("Daemon can connect to the SAE access point using SAE"):
Change:
I have no idea if this is a problem, but i seems suspicious, especially since I've been looking into some odd keyboard issues lately. Run . I would expect this to have the value of in the final bit ( in my case). System: 18.03pre116572. (Impala) Nix version: 1.11.5 Nixpkgs version: 18.03pre116572. Sandboxing enabled: yes

Discussion:
target = "X11/xkb"; } ]) <ins> # localectl looks into 00-keyboard.conf ++ [ { text = '' Section "InputClass" Identifier "Keyboard catchall" MatchIsKeyboard "on" Option "XkbModel" "${cfg.xkbModel}" Option "XkbLayout" "${cfg.layout}" Option "XkbOptions" "${cfg.xkbOptions}" Option "XkbVariant" "${cfg.xkbVariant}" EndSection ''; target = "X11/xorg.conf.d/00-keyboard.conf"; } ] </ins> # Needed since 1.18; see https://bugs.freedesktop.org/show_bug.cgi?id=89023#c5 ++ (let cfgPath = "/X11/xorg.conf.d/10-evdev.conf"; in [{

${cfg.monitorSection} EndSection <del> Section "InputClass" Identifier "Keyboard catchall" MatchIsKeyboard "on" Option "XkbModel" "${cfg.xkbModel}" Option "XkbLayout" "${cfg.layout}" Option "XkbOptions" "${cfg.xkbOptions}" Option "XkbVariant" "${cfg.xkbVariant}" EndSection </del> # Additional "InputClass" sections ${flip concatMapStrings cfg.inputClassSections (inputClassSection: '' Section "InputClass"
Change:
Hyprshade works as expected, but the systemd service provided by fails to run due to an inability to find . hyprland and hyprshade shader (eg. blue light filtering) to run at certain times. to generate a user service to automatically run in the background with hyprshade.service and to enable the generated user service. for failure at the time designated in your hyprshade configuration. Hyprshade should have access to and call appropriately. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Discussion:
, hatchling , more-itertools , click <ins> , hyprland , makeWrapper </ins> }: buildPythonPackage rec {

nativeBuildInputs = [ hatchling <ins> makeWrapper </ins> ]; propagatedBuildInputs = [ more-itertools click ]; postFixup = '' <del> wrapProgram $out/bin/hyprshade --set HYPRSHADE_SHADERS_DIR $out/share/hyprshade/shaders </del> <ins> wrapProgram $out/bin/hyprshade  --set HYPRSHADE_SHADERS_DIR $out/share/hyprshade/shaders  --prefix PATH : ${lib.makeBinPath [ hyprland ]} </ins> ''; meta = with lib; {
Change:
I tried to install skype with: But I still get the same error as without , which is telling me that I should add to the command line.
The following works for me: Alternatively, putting into should also work.
Not for me:
That should read . It doesn't work with the channel because the config argument is not propagated.
Ehm, so the issue is "fixed" now?
Yeah it works now.
So is there a way to set allowUnfree with argument?
I don't think there is (on a channel). Just the docs were updated not to suggest doing it. In any case, it seems much more practical to set that option persistently if you want to use unfree stuff (instead of appending the argument every time you e.g. update that package). You can do that (as suggested) in or, on NixOS, in your .

Discussion:
import ./generic.nix ( rec { <del> version = "3.4.2"; </del> <ins> version = "3.4.4"; </ins> testing = false; preConfigure = ''

src = fetchurl { url = "mirror://kernel/linux/kernel/v3.x/${if testing then "testing/" else ""}linux-${version}.tar.xz"; <del> sha256 = "0pd96g1qcp2wgdnvk79hljjrpr6xjk0159lks47n181a3yirzf4x"; </del> <ins> sha256 = "0l4h7amhsmgpnii8rgwi32nd7ajsifk2xckjd39pfzwdifacw5yw"; </ins> }; config = configWithPlatform stdenv.platform;
Change:
forgejo fails to start up because the static file root path that is meant to point at the output of the package was not correctly patched at build time Steps to reproduce the behavior: forgejo (I used nixpkgs-unstable) (I was moving an existing install to the nix package to be up to date) the following output: Forgejo should find the required frontend files provided by the output and start properly. I am aware that using nix and especially nixpkgs-unstable on a non-NixOS system comes with essentially no warranty whatsoever. However, given that the nix derivation is clearly intended to remove this placeholder () and that it failing to do so seems to be the only thing wrong with my installation, I do not believe there is an error on my part. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
Hi, thanks a lot for the report! Turns out, there is a typo in It should be not , just like the patch: This went unnoticed when using forgejo with the nixos module, because we explicitly set in the to by default[^1]. Will open a PR with a fix shortly :) [^1]:
Thank you very much! I didn't notice the typo, glad I was able to provide enough information anyhow ^^
I heard substituteInPlace has a new --replace-fail option(?). Using that should prevent silent failures like this.
There is now. From what I can tell, does not apply to . But feel free to check and write a review in :)

Discussion:
buildInputs = lib.optional pamSupport pam; patches = [ <del> ./../gitea/static-root-path.patch </del> <ins> ./static-root-path.patch </ins> ]; postPatch = '' <del> substituteInPlace modules/setting/setting.go --subst-var data </del> <ins> substituteInPlace modules/setting/server.go --subst-var data </ins> ''; tags = lib.optional pamSupport "pam"

<ins> diff --git a/modules/setting/server.go b/modules/setting/server.go index 183906268..fa02e8915 100644 --- a/modules/setting/server.go +++ b/modules/setting/server.go @@ -319,7 +319,7 @@ func loadServerFrom(rootCfg ConfigProvider) { OfflineMode = sec.Key("OFFLINE_MODE").MustBool() Log.DisableRouterLog = sec.Key("DISABLE_ROUTER_LOG").MustBool() if len(StaticRootPath) == 0 { -		StaticRootPath = AppWorkPath +		StaticRootPath = "@data@" } StaticRootPath = sec.Key("STATIC_ROOT_PATH").MustString(StaticRootPath) StaticCacheTime = sec.Key("STATIC_CACHE_TIME").MustDuration(6 * time.Hour) </ins>
Change:
It would be nice if the package included shell completions for bash, zsh, fish. Steps to reproduce the behavior: (In fish): pipx-specific shell completions should show. One problem specific to is that the instructions you get with do not work unless you know to install the binary first (e.g. ). I hope that mimicking would work (though I'd also like completions to be included). I might be able to try that myself at some point, but I'm not very familiar with testing that a patch to works. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Discussion:
, fetchFromGitHub , hatchling , hatch-vcs <ins> , installShellFiles </ins> , packaging , platformdirs , pytestCheckHook

tomli ]; <ins> nativeBuildInputs = [ installShellFiles ]; </ins> nativeCheckInputs = [ pytestCheckHook git

"test_skip_maintenance" ]; <ins> postInstall =  '' installShellCompletion --cmd pipx  --bash <(${argcomplete}/bin/register-python-argcomplete pipx --shell bash)  --zsh <(${argcomplete}/bin/register-python-argcomplete pipx --shell zsh)  --fish <(${argcomplete}/bin/register-python-argcomplete pipx --shell fish) ''; </ins> meta = with lib; { description = "Install and run Python applications in isolated environments"; mainProgram = "pipx";
Change:
I don't think exists in Bash?
See and
Okay, then why am I seeing this?
Because this is not how you should use . Look for examples in nixpkgs. Try this:
Ah, I see. Thanks for your help!

Discussion:
{ stdenv, fetchurl, qt48 }: let <del> baseVersion = "2.7"; revision = "1"; </del> <ins> baseVersion = "2.8"; revision = "0"; </ins> version = "${baseVersion}.${revision}"; qt4_for_qtcreator = qt48.override { developerBuild = true;

src = fetchurl { url = "http://download.qt-project.org/official_releases/qtcreator/${baseVersion}/${version}/qt-creator-${version}-src.tar.gz"; <del> sha256 = "04vn7y3dkk9vi1rsmsxby57mvc2h9n5q842hayq2mdlsax4qnhjv"; </del> <ins> sha256 = "7ac5d9a36c2f561f74d77378d4eae95a78c7752b323e1df924d6e895e99f45d2"; </ins> }; buildInputs = [ qt4_for_qtcreator ];
Change:
Steps to reproduce the behavior: hydra build: build logs: 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]:
Not sure why this suddenly started failing after it worked fine for the last 11 days. Reproduced this and submitted a patch in that fixed it for me locally.
Thanks, I can confirm that the patch does work.
In my observation, it only breaks on , the works just fine. That's extremely weird.
I logged the test phase on the latest commit and the one before that, here’s what’s changed: Looks like it is to do with the
Nice work, It looks like is the commit that upgraded to pytest 8, but that was two weeks ago. So I'm not sure how this passed for 4 days ago.
The build that passed 4 days ago used as and the also wasn’t pointing to , here’s a snippet from the logs: The log file: But the latest build which failed, had set to and set to .

Discussion:
typing-extensions ]; <del> pytestFlagsArray = [ # Pass -c /dev/null so that pytest does not use the bundled pytest.ini, which adds # options to run additional integration tests that are overkill for our purposes. "-c" "/dev/null" ]; </del> <ins> # Remove the bundled pytest.ini, which adds options to run additional integration # tests that are overkill for our purposes. preCheck = '' rm pytest.ini ''; </ins> pythonImportsCheck = [ "bidict" ];
Change:
When setting in , the user gets a warning when using any command that use under the hood: The setting is ineffective. Users still need to press the Enter key at each prompt. Add the above mentioned setting to . Notice the warning e.g. with in any Git repository with a dirty working tree. System: 18.03pre116347. (Impala) Nix version: nix-env (Nix) 1.11.15 Nixpkgs version: 18.03pre116572.
Fixed by

Discussion:
# Also put git-http-backend into $PATH, so that we can use smart # HTTP(s) transports for pushing ln -s $out/libexec/git-core/git-http-backend $out/bin/git-http-backend <ins> # wrap perl commands gitperllib=$out/lib/perl5/site_perl for i in ${builtins.toString perlLibs}; do gitperllib=$gitperllib:$i/lib/perl5/site_perl done wrapProgram $out/libexec/git-core/git-cvsimport  --set GITPERLLIB "$gitperllib" wrapProgram $out/libexec/git-core/git-add--interactive  --set GITPERLLIB "$gitperllib" wrapProgram $out/libexec/git-core/git-archimport  --set GITPERLLIB "$gitperllib" wrapProgram $out/libexec/git-core/git-instaweb  --set GITPERLLIB "$gitperllib" wrapProgram $out/libexec/git-core/git-cvsexportcommit  --set GITPERLLIB "$gitperllib" </ins> '' + (if svnSupport then
Change:
kup is currently still packaged for KDE Frameworks 5 only. A git build has to be used, since the project did no official release for years. The new naming scheme kdePackages is advised to be used.
There has been an official release since then:
Yeah, it has been since been included in the KDE project. They do regular releases.
I have startet trying to build kup for plasma 6, but two dependencies are still missing in kdePackages: and And I think that the current kup version mussed be moved to and the new should become . Am I right?` Maybe one of the KDE Experts can build these missing dependencies as I am not smart enough to do this: :sweat_smile: KDE Experts:
plasma-framework is libplasma now, kinit no longer exists. Don't just copy-paste the qt5 expression, start from scratch and see what it actually needs.
I would but the dependencies are not updated yet in the Kup repo. So there is no doc how to build for qt6.
Read the
Now I have this: But I got this error and dont understand how to solve:
Read the
I have read it. I have and removed all packages according to it. But I never have done anything with a So I dont find the issue. It seams, that it always want to use qt5, with I dont understand as I only import qt6 stuff. Sorry for annoying you with my missing knowledge.
What I'm really trying to say is that you need to do your own research. I can just write the expression for you, but that's not going to help long term. The answers are out there, and I've verified they're not difficult to find.

Discussion:
kio-fuse = self.callPackage ./misc/kio-fuse {}; ktextaddons = self.callPackage ./misc/ktextaddons {}; kunifiedpush = self.callPackage ./misc/kunifiedpush {}; <ins> kup = self.callPackage ./misc/kup {}; </ins> kweathercore = self.callPackage ./misc/kweathercore {}; marknote = self.callPackage ./misc/marknote {}; mpvqt = self.callPackage ./misc/mpvqt {};

<ins> { lib , mkKdeDerivation , fetchFromGitLab , libgit2 }: mkKdeDerivation rec { pname = "kup"; version = "0.10.0"; src = fetchFromGitLab { domain = "invent.kde.org"; owner = "system"; repo = "kup"; rev = "${pname}-${version}"; hash = "sha256-G/GXmcQI1OBnCE7saPHeHDAMeL2WR6nVttMlKV2e01I="; }; extraBuildInputs = [ libgit2 ]; meta = with lib; { license = licenses.gpl2Plus; maintainers = [ maintainers.pwoelfel ]; }; } </ins>
Change:
the strict commit history guidelines require frequent use of , a command which may be unfamiliar to those that are used to projects with more lenient commit guidelines. find or write a high-quality guide to and make it available in <!-- make sure this issue is not redundant or obsolete --- [x] checked [latest Nixpkgs manual] ([source][nixpkgs-source]) and [latest NixOS manual] ([source][nixos-source]) [x] checked [open documentation issues] for possible duplicates [x] checked [open documentation pull requests] for possible solutions [latest Nixpkgs manual]: [latest NixOS manual]: [nixpkgs-source]: [nixos-source]: [open documentation issues]: [open documentation pull requests]: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Discussion:
- Check for unnecessary whitespace with `git diff --check` before committing. - If you have commits `pkg-name: oh, forgot to insert whitespace`: squash commits in this case. Use `git rebase -i`. <ins> See [Squashing Commits](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History#_squashing) for additional information. </ins> - For consistency, there should not be a period at the end of the commit message's summary line (the first line of the commit message).
Change:
Currently nixos- uses to attach to containers. However this methods miss out some container context and does not create a pseudo tty. is the offical method recommended by upstream: Previous there was an attempt to use , which does not return the exit code. cc System: (NixOS: , Ubuntu/Fedora: , ...) Nix version: (run ) Nixpkgs version: (run ) Sandboxing enabled: (run )
Previous opinion on this:
Can be fixed by adding .
and don't give the complete container environment, so I'd consider and broken as of now. I agree with using for and for , which is also what systemd themselves recommend. From the : There is still a problem with merging / as , but I don't think that it's currently resolvable, since other container tools also just use a pty.
It is possible by using with the latest systemd release: However I still don't think exposing raw stdin/stdout by default is a good idea for the reason I have given here:
UPDATE I just read it possible to use and in conjunction and uses the more appropriate depending on the context.

Discussion:
use Cwd 'abs_path'; use Time::HiRes; <del> my $nsenter = "@utillinux@/bin/nsenter"; </del> my $su = "@su@"; # Ensure a consistent umask.

# Run a command in the container. sub runInContainer { my @args = @_; <del> my $leader = getLeader; exec($nsenter, "-t", $leader, "-m", "-u", "-i", "-n", "-p", "--", @args); die "cannot run ‘nsenter’: $!n"; </del> <ins> exec("systemd-run", "--machine", $containerName, "--pty", "--quiet", "--", @args); die "cannot run ‘systemd-run’: $!n"; </ins> } # Remove a directory while recursively unmounting all mounted filesystems within
Change:
There is a hash mismatch for kstars in nixpkgs-unstable Steps to reproduce the behavior: Add any other context about the problem here. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Last updated by
As was spotted during the PR review , the ref is a branch not a tag.
The source of the problem is (also mentionned in a comment) a typo in the name of the latest version of kstars files (). There's now a 3.7.0 version out. So I'll suggest a new PR with this version, using the official source

Discussion:
, stdenv , mkDerivation , extra-cmake-modules <del> , fetchFromGitHub </del> <ins> , fetchurl </ins> , kconfig , kdoctools , kguiaddons

stdenv.mkDerivation (finalAttrs: { pname = "kstars"; <del> version = "3.6.9"; </del> <ins> version = "3.7.0"; </ins> <del> src = fetchFromGitHub { owner = "KDE"; repo = "kstars"; rev = "stable-${finalAttrs.version}"; hash = "sha256-28RRW+ncMiQcBb/lybEKTeV08ZkF3IqLkeTHNW5nhls="; </del> <ins> src = fetchurl { url = "mirror://kde/stable/kstars/kstars-${finalAttrs.version}.tar.xz"; hash = "sha256-yvN1k0LqUi5Odb34Nk8UP5qoIbFUcvUiyESpoMKmuqg="; </ins> }; nativeBuildInputs = [
Change:
Project description TUI podcast client for the terminal Metadata homepage URL: - source URL: license: mit platforms: unix, linux, darwin, ...

Discussion:
<ins> { lib , fetchFromGitHub , python3 }: python3.pkgs.buildPythonApplication rec { pname = "castero"; version = "0.9.5"; pyproject = true; src = fetchFromGitHub { owner = "xgi"; repo = "castero"; rev = "v${version}"; hash = "sha256-6/7oCKBMEcQeJ8PaFP15Xef9sQRYCpigtzINv2M6GUY="; }; nativeBuildInputs = with python3.pkgs; [ setuptools wheel ]; propagatedBuildInputs = with python3.pkgs; [ requests grequests cjkwrap pytz beautifulsoup4 lxml mpv python-vlc ]; nativeCheckInputs = with python3.pkgs; [ pytestCheckHook ]; pytestFlagsArray = [ "tests" ]; disabledTests = [ "test_datafile_download" ]; pythonImportCheck = [ "castero" ]; # Resolve configuration tests, which access $HOME preCheck = '' export HOME=$(mktemp -d) ''; # Satisfy the python-mpv depedency, which is mpv within NixOS postPatch = '' substituteInPlace setup.py --replace-fail "python-mpv" "mpv" ''; # VLC currently doesn't support Darwin on NixOS meta = with lib; { mainProgram = "castero"; description = "TUI podcast client for the terminal"; homepage = "https://github.com/xgi/castero"; license = licenses.mit; platforms = platforms.linux; maintainers = with maintainers; [ keto ]; }; } </ins>
Change:
System: 18.03pre116572. (Impala) Nix version: nix-env (Nix) 1.11.15 Nixpkgs version: "18.03pre116572." Sandboxing enabled: false

Discussion:
{ stdenv, fetchurl, pkgconfig, intltool, gtk, libxfce4util, libxfce4ui , libxfce4ui_gtk3, libwnck, exo, garcon, xfconf, libstartup_notification , makeWrapper, xfce4mixer, hicolor_icon_theme <del> , withGtk3 ? false, gtk3 </del> <ins> , withGtk3 ? false, gtk3, gettext </ins> }: let inherit (stdenv.lib) optional;

patches = [ ./xfce4-panel-datadir.patch ]; patchFlags = "-p1"; <ins> postPatch = '' for f in $(find . -name *.sh); do substituteInPlace $f --replace gettext ${gettext}/bin/gettext done ''; </ins> outputs = [ "out" "dev" "devdoc" ]; buildInputs =
Change:
When a git repository has been initialized by a previous version of and that version is then garbage collected, any action in that repo which call will fail and leave it in a dirty state. For example: To fix it I would patch so that wouldn't set absolutes paths in but use instead. It is related to this from . System: 17.09beta1314. (Hummingbird) Nix version: nix-env (Nix) 1.11.15 Nixpkgs version: "17.09beta1314." Sandboxing enabled: build-use-sandbox = false
I've experienced this too, the workaround was just to edit to get rid of the absolute paths. Your patch looks good!

Discussion:
buildInputs = [ openssl makeWrapper ]; <ins> patchPhase = '' substituteInPlace commands.cpp  --replace '(escape_shell_arg(our_exe_path()))' '= "git-crypt"' ''; </ins> installPhase = '' make install PREFIX=$out wrapProgram $out/bin/* --prefix PATH : ${gnupg1compat}/bin
Change:
Steps to reproduce the behavior: following configuration: # nixos-rebuild switch <!-- 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]:
~ tells me the first bad commit was . I'm not sure if this is correct, because this commit is a qemu version bump (). This build failure can also be seen in the pull request: EDIT: I've tried building it again on another machine and it worked. I think a file somehow got corrupted on the other machine, because the build contains strange errors like and Additionally, was set to false.
Notify maintainers:
your are more then welcome to fix it and create a PR
The issue seems to be that we use a JDK that doesn't have anymore. See also: Can you check whether this PR ( ) fixes things for you? Ideally, if you could run on that PR, I'd be super grateful!
Sorry for the delay. The PR worked, I can with the configuration above. Thanks for the work.
Hi, I'm afraid I'm still experiencing this issue even though the changes landed in . Would anyone mind taking a look at my (shortened for brevity) to see what I did wrong? Thanks!

Discussion:
# See https://github.com/cyberus-technology/virtualbox-kvm/issues/12 assert enableKvm -> !enableHardening; <ins> # The web services use Java infrastructure. assert enableWebService -> javaBindings; </ins> with lib; let

virtualbox = libsForQt5.callPackage ../applications/virtualization/virtualbox { stdenv = stdenv_32bit; inherit (gnome2) libIDL; <del> jdk = openjdk17; </del> <ins> # VirtualBox uses wsimport, which was removed after JDK 8. jdk = jdk8; </ins> }; virtualboxKvm = lowPrio (virtualbox.override {