jiebi/CodeConvo huggingface dataset:
Code change:
pname = "steam-runtime"; # from https://repo.steampowered.com/steamrt-images-scout/snapshots/ <del> version = "0.20210317.0"; </del> <ins> version = "0.20210527.0"; </ins> src = fetchurl { url = "https://repo.steampowered.com/steamrt-images-scout/snapshots/${version}/steam-runtime.tar.xz"; <del> sha256 = "061z2r33n2017prmhdxm82cly3qp3bma2q70pqs57adl65yvg7vw"; </del> <ins> sha256 = "1880d1byn265w0vy5p98d8w8virnbywj707ydybj7rixhid2gzdc"; </ins> name = "scout-runtime-${version}.tar.gz"; };

Related discussion:
text: yields CPU: Intel i7 4790k GPU: AMD RX 5500 XT Configuration is
Updating completely (completely as in like 30m ago) resulted in broken vscode as well. Full reboots after each update. No dice.
Logs:
Nevermind. Apparently something broke my steam profile. fixed the issue. Time to copy all my games over...
move the games its faster also steam automatically detects the games so you dont have to go through and install them all again for it detect them
Yea, I think valve just oof'ed on this one
if anyone is still stuck with the command that I had above, you might be able to use: which will add pipewire, and make the steam check happy
So it just corrupts the profile every time I close and re-open Steam. So much for it being fixed.
did you try the one I just posted?
Yes :(
Interesting, your channels are quite old, if you don't use flakes, it might be worth while to
I use flakes :) Nothing is really installed from those channels.
that's what I assumed when your installation said something significantly newer
Same issue right?
Looks like it. Good catch!
Unfortunately, the linked issue doesn't seem to actually have a fix that works, but I think it's still out of scope for this issue, so it can probably stay closed. I'll just have to use the flatpak until Valve fixes whatever they broke. Update: broken in flatpak too :/
The patch seems insufficient for my system
Ditto previous comment. Running 20.09 steam still not happy.
That also doesn't work for me: Full log: EDIT: Sorry wrong ping! x.x
It's not that the issue is not fixed, but the system API (seem to be X11 here or libc) is not compatible with the package. Try this for 20.09 until it's available in the channel ():
I still think we should move forward with as it's current needed for the beta runtime, and will eventually be needed when the runtime gets bumped
works for me. But I've done 2 channel updates and nixos rebuilds and my vanilla steam install is still broken. shows it was last built 08/06 with commit .
Code change:
pname = "steam-runtime"; # from https://repo.steampowered.com/steamrt-images-scout/snapshots/ <del> version = "0.20210317.0"; </del> <ins> version = "0.20210527.0"; </ins> src = fetchurl { url = "https://repo.steampowered.com/steamrt-images-scout/snapshots/${version}/steam-runtime.tar.xz"; <del> sha256 = "061z2r33n2017prmhdxm82cly3qp3bma2q70pqs57adl65yvg7vw"; </del> <ins> sha256 = "1880d1byn265w0vy5p98d8w8virnbywj707ydybj7rixhid2gzdc"; </ins> name = "scout-runtime-${version}.tar.gz"; };

Related discussion:
text: That commit is exactly the commit for this issue: Forgive my ignorance, but shouldn't a channel update + nixos-rebuild pull this in and 'just work' ?
Run nix-channel with sudo Or rebuild with --upgrade which does it for you
Do games run with Proton anymore for you? I can get Yooka-Laylee to work using the nix-shell command, but not Foxhole, which requires Proton. I'm on unstable, if that changes anything.
For those who are like me and install user software with , this workaround works, at /home/[username]
Your snippet helped me get steam running in my flakes based setup. Thank you! Properly learning nix averted for yet another day. Hooray!
My crasher was solved by adding to . It's a different, unrelated bug, so I will create a separate issue tonight probably.
I did a and steam started working for me again. Thanks for fixing this!
... Ironically, all channels have updated with fixes except unstable...
Latest unstable now has this fix and my steam is working again. Thanks folks.
cc (Apologies for the ping, please let me know if it's inappropriate) I've encountered some strange behavior trying to get this to work. Steam will notably fail with the following error despite running to bump the and channels: I've also tried using and attempted to add the override to both channels, like: Unfortunately, none of these approaches worked. In a surprising twist, the following does work, although I can't figure out how it's different :thinking::
Do you have a stale installed under your user account, or otherwise have a stale in your path somewhere? Try a to see where is coming from.
I don't think so, unless I've done so accidentally.
That is installed in your user account via . only upgrades "declarative-style" packages referenced by your . It will not update packages installed via . Do one of the following: If you want to manage steam declaratively, enable in your , for example, by setting and then run to uninstall older versions installed via If you want to manage via , remember to periodically to upgrade those packages. I recommend picking one strategy or the other exclusively for managing your packages.
great eye, thank you for the advice and thorough explanation! After running , I can see it now uses the updated path and loads correctly.
Code change:
makeWrapperArgs = [ "--prefix PATH : ${lib.makeBinPath [ <ins> bash </ins> steam-run (winetricks.override { # Remove default build of wine to reduce closure size.

Related discussion:
text: This issue is mainly a note to myself since the upgrade won't be trivial and will need a lot of testing. Protontricks is now using the Pressure Vessel runtime, so I have to refactor my patches with steam-run to account for this. <!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on github to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the the current version of the package --- <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- name: protontricks <!-- The current version can be found easily with the same process than above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 1.4.4 desired version: 1.5.0 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: myself
Code change:
githubId = 687218; name = "averelld"; }; <del> avery = { email = "averyl+nixos@protonmail.com"; github = "AveryLychee"; githubId = 9147625; name = "Avery Lychee"; }; </del> avh4 = { email = "gruen0aermel@gmail.com"; github = "avh4";

Related discussion:
text: I became marked as a maintainer on the package many years ago, but since then I have changed careers and have slowly stopped using nixos as much. I don't currently have git installed (and I don't really remember how to use it) Please remove me from the maintainer list I am in the maintainer list as follows:
Code change:
flootty = callPackage ../development/tools/flootty { }; <ins> fffuu = haskell.lib.justStaticExecutables (haskellPackages.callPackage ../tools/misc/fffuu { }); </ins> flow = callPackage ../development/tools/analysis/flow { inherit (darwin.apple_sdk.frameworks) CoreServices; };

Related discussion:
text: The ffuu tool analyses iptable rules and dumps them. I thought it would be pretty cool to try it out on NixOS.
Looks like has done this:
Code change:
<ins> { lib , buildPythonPackage , fetchFromGitHub , setuptools , pyglet , pytestCheckHook , mock }: buildPythonPackage rec { pname = "PyWavefront"; version = "1.3.3"; pyproject = true; src = fetchFromGitHub { owner = "pywavefront"; repo = "PyWavefront"; rev = version; hash = "sha256-ci40L2opJ+NYYtaAeX1Y5pzkdK+loFspTriX/xv4KR8="; }; nativeBuildInputs = [ setuptools ]; passthru.optional-dependencies.visualization = [ pyglet ]; nativeCheckInputs = [ pytestCheckHook mock ]; pythonImportsCheck = [ "pywavefront" ]; meta = with lib; { description = "Python library for importing Wavefront .obj files"; homepage = "https://github.com/pywavefront/PyWavefront"; changelog = "https://github.com/pywavefront/PyWavefront/blob/${src.rev}/CHANGELOG.md"; license = licenses.bsd3; maintainers = with maintainers; [ pbsds ]; }; } </ins>

Related discussion:
text: Project description Metadata homepage URL: source URL: license: BSD-3-Clause license platforms: linux The version compatible with NixOS 23.11 is 1.3.3. Below is the code for this Python package, which might be useful: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
please test edit: i tried to add a quippy command to test this, but the new nix cli doesn't construct python environments like the old cli did, and the old cli can't trivially use github pull as input...
Code change:
checkstyle = callPackage ../development/tools/analysis/checkstyle { }; flex = callPackage ../development/tools/parsing/flex { }; <ins> flex_2_5_35 = callPackage ../development/tools/parsing/flex/2.5.35.nix { }; </ins> m4 = gnum4;

Related discussion:
text: grub fails with nixos-rebuild switch -I nixpkgs=/home/lethal/nixpkgs
The issue title here is highly uninformative, which is why I didn't find this when checking for duplicates. :P
Code change:
}; buildScript = pkgs.writeText "build-stumpwm.lisp" '' (load "${super.stumpwm.asdfFasl}/asdf.${super.stumpwm.faslExt}") <del> (asdf:load-system 'stumpwm/build) </del> <ins> (asdf:load-system 'stumpwm) ;; Prevents package conflict error (when (uiop:version<= "3.1.5" (asdf:asdf-version)) (uiop:symbol-call '#:asdf '#:register-immutable-system :stumpwm) (dolist (system-name (uiop:symbol-call '#:asdf '#:system-depends-on (asdf:find-system :stumpwm))) (uiop:symbol-call '#:asdf '#:register-immutable-system system-name))) ;; Prevents "cannot create /homeless-shelter" error (asdf:disable-output-translations) </ins> (sb-ext:save-lisp-and-die "stumpwm" :executable t <ins> :purify t </ins> #+sb-core-compression :compression #+sb-core-compression t <del> :toplevel #'stumpwm:main) </del> <ins> :toplevel #'stumpwm:stumpwm) </ins> ''; installPhase = '' mkdir -p $out/bin

Related discussion:
text: Since PM stumpwm is now up to date but I have an issue in stumpwm module loading. SBCL will return the a package conflict error between packages "CLOSER-COMMON-LISP" and "DYNAMIC-MXINS" Steps to reproduce the behavior: to your stumpwm contrib modules in an appropriate directory a minimal file: reboot using stumpwm or refresh the stumpwm config using command (by default keystrokes are: ) Modules are loaded as expected Results of :
Hm, indeed. And maybe for debugging we should provide access to the «library» version of StumpWM…
We could try building using the Makefile instead of save-lisp-and-die. I did, but then there were problems with missing HOME. Then the problem was that the stumpwm build script seems to want to remember the value of HOME from compile-time on run-time (something like "/build") How did stumpwm work previously in nixpkgs?
Can you try with this?
Code change:
unitConfig = { ConditionPathExists = [ # Skip this service if the database already exists <del> "!$STATE_DIRECTORY/honk.db" </del> <ins> "!%S/honk/honk.db" </ins> ]; }; };

Related discussion:
text: honk-initdb.service attempts tu run even though already exists, causing it to fail and prevent honk.service from starting. I think honk-initdb.service is supposed to be skipped since already exists? Please run and paste the result.
Hi, Thanks for the bug report. That's weird, because that service shouldn't run since the file already exists. I will try to investigate during the week.
Do you know if there is any way I can make honk.service believe its dependencies are met, as a workaround?
What I did precisely in I have no clue why this is not working yet.
I pushed a PR here: Could you try it and let me know if this is fixing the issue ?
Dear is your issue fixed now ?
Ping ^^
The condition seems to work but the issue remains?
Code change:
let description = "A secure and free password manager for all of your devices"; icon = "bitwarden"; <del> electron = electron_25; </del> <ins> electron = electron_26; </ins> in buildNpmPackage rec { pname = "bitwarden"; <del> version = "2023.10.1"; </del> <ins> version = "2023.12.0"; # TODO add back Electron version check below </ins> src = fetchFromGitHub { owner = "bitwarden"; repo = "clients"; rev = "desktop-v${version}"; <del> hash = "sha256-cwSIMN40d1ySUSxBl8jXLVndnJJvPnLiTxkYnA3Pqws="; </del> <ins> hash = "sha256-WYhLKV3j3Ktite5u1H4fSku38hCCrMzKoxtjq6aT9yo="; </ins> }; patches = [

Related discussion:
text: Steps to reproduce the behavior: bitwarden Please run and paste the result.
Will be fixed by
Code change:
(mkBuildInputs wineUnstable.pkgArches pkgNames) ++ extra; in assert stdenv.lib.getVersion wineUnstable == patch.version; <del> stdenv.lib.overrideDerivation wineUnstable (self: { </del> <ins> (stdenv.lib.overrideDerivation wineUnstable (self: { </ins> buildInputs = build-inputs [ "perl" "utillinux" "autoconf" ] self.buildInputs; name = "${self.name}-staging";

Related discussion:
text: Describe the bug repology reports some issues with the package name and version. It should end with the version, not "staging". So we could just call the package . But we should be consistent here! All the wine versions and attribute names are messed up. wine-4.0.2 | wine wine-4.0.2 | wine-4.14 | winePackages.unstable wine-4.14-staging | wine-staging wine-4.14-staging | winePackages.staging Why is "staging" in the package name but "unstable" not? Is there even a difference? So i would remove "staging" from "wine-4.14-staging". Metadata master Maintainer information:
Adding to this: I locally built and without issues with the current packages but I'm not sure what's actually required for a PR here. Seems odd that it was so easy and nobody else already PRed it.
Mind doing the PR then? :)
I'm not sure what's actually required for a PR here. I also don't know what the wine maintainers want. My motivation is to get the repology error fixed. So i would remove "staging" from "wine-4.14-staging". Seems odd that it was so easy and nobody else already PRed it. There is a lot that can be improved in nixpkgs that is quiet easy! For example i'm currently fixing package versions that produce errors in repology. There are 586 known problems left to fix: There are 4997 outdated packages in nixpkgs unstable: Most of them probably quiet easy to update, but someone has to invest the time. Maybe there is already a PR that is not merged yet. A review can help to speed it up! But we are already the best distro when it comes to up-to-date packages! And we might supersede AUR in the future with total number of packages. But at the same time, many common packages are not in nixpkgs...
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".
Code change:
(mkBuildInputs wineUnstable.pkgArches pkgNames) ++ extra; in assert stdenv.lib.getVersion wineUnstable == patch.version; <del> stdenv.lib.overrideDerivation wineUnstable (self: { </del> <ins> (stdenv.lib.overrideDerivation wineUnstable (self: { </ins> buildInputs = build-inputs [ "perl" "utillinux" "autoconf" ] self.buildInputs; name = "${self.name}-staging";

Related discussion:
text: 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 . 3. Ask on the on .
issue still exists cc maintainers
There is a difference between unstable and staging. Staging is the staging patches on top of unstable.
That makes sense. Can we add it to Long description? Repology seem to recognise the version now: !
Added to description, but if you think longDescription is better, or think the wording is not clear — please comment or PR.
Code change:
sha256 = "0xm3jw8ll49akr4fxa5qjbsglcgb6fq6nc54zppannxdlfkqj5jk"; }; <ins> buildInputs = with pkgs; [ makeWrapper ]; </ins> propagatedBuildInputs = with pkgs; [ mono sqlite

Related discussion:
text: Emby uses ffmpeg for transcoding media and for generating thumbnails. Emby fails to find the FFmpeg binary during the setup wizard but can be specified manually if FFmpeg has been installed separately. Add to , browse to , and advance through the wizard. System: 17.03pre92039. (Gorilla) Nix version:nix-env (Nix) 1.11.4 Nixpkgs version: 17.03pre92039.
cc
Funny thing is that I was just watching a movie when I was mentioned on a system without any ffmpeg/ffprobe binary. My system was upgraded from an older version (config was already existing so no check was done by the wizard). I was able to reproduce the issue. Will take a more detailed look at it sometime tomorrow :)
Code change:
--skip util::test_get_rust_src_path_not_rust_source_tree  --skip extern --skip completes_pub_fn --skip find_crate_doc  --skip follows_use_local_package --skip follows_use_for_reexport  <del> --skip follows_rand_crate --skip get_completion_in_example_dir </del> <ins> --skip follows_rand_crate --skip get_completion_in_example_dir  --skip test_resolve_global_path_in_modules </ins> ''; doInstallCheck = true;

Related discussion:
text: Current version of rustracer 2.1.22 does not build with latest stable rust (see ). Please update rustracer to the newest version 2.1.27
Code change:
"--with-iconv=${libiconv}" "--with-dbm=gdbm" "--with-zlib=${zlib}" <del> "--with-ca-bundle=$NIX_SSL_CERT_FILE" </del> <ins> "--with-ca-bundle=${cacert}/etc/ssl/certs/ca-bundle.crt" </ins> # TODO: Enable slib #       Current slib in nixpkgs is specialized to Guile # "--with-slib=${slibGuile}/lib/slib"

Related discussion:
text: Describe the bug It should be the path to ca- To Reproduce Expected behavior No error happens. Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(mnacamura): nixpkgs:
Code change:
_Default:_ the output path's hash. ``` <ins> #### Examples To define a referenceable figure use the following fencing: ```markdown :::{.example #an-attribute-set-example} # An attribute set example You can add text before ```nix { a = 1; b = 2;} ``` and after code fencing ::: ``` Defining examples through the `example` fencing class adds them to a "List of Examples" section after the Table of Contents. Though this is not shown in the rendered documentation on nixos.org. #### Figures To define a referencable figure use the following fencing: ```markdown ::: {.figure #nixos-logo} # NixOS Logo ![NixOS logo](./nixos_logo.png) ::: ``` Defining figures through the `figure` fencing class adds them to a `List  of Figures` after the `Table of Contents`. Though this is not shown in the rendered documentation on nixos.org. #### Footnotes To add a foonote explanation, use the following syntax: ```markdown Sometimes it's better to add context [^context] in a footnote. [^context]: This explanation will be rendered at the end of the chapter. ``` #### Inline comments Inline comments are supported with following syntax: ```markdown <!-- This is an inline comment --> ``` The comments will not be rendered in the rendered HTML. #### Link reference definitions Links can reference a label, for example, to make the link target reusable: ```markdown ::: {.note} Reference links can also be used to [shorten URLs][url-id] and keep the markdown readable. ::: [url-id]: https://github.com/NixOS/nixpkgs/blob/19d4f7dc485f74109bd66ef74231285ff797a823/doc/README.md ``` This syntax is taken from [CommonMark](https://spec.commonmark.org/0.30/#link-reference-definitions). #### Typographic replacements Typographic replacements are enabled. Check the [list of possible replacement patterns check](https://github.com/executablebooks/markdown-it-py/blob/3613e8016ecafe21709471ee0032a90a4157c2d1/markdown_it/rules_core/replacements.py#L1-L15). </ins> ## Getting help If you need documentation-specific help or reviews, ping [@NixOS/documentation-reviewers](https://github.com/orgs/nixos/teams/documentation-reviewers) on your pull request.

Related discussion:
text: Contributors working on improving the nixpkgs manual would be redirected to the . This section is not up-to-date with all the syntax features supported by , forcing contributors to look for use examples over the whole manual. The same markdown syntax is used to write and generate the NixOS manual. However, this manual does not make any mention of the supported syntax. This makes it hard to contribute to the NixOS manual with relative isolation from the nixpkgs manual. Update in Nixpkgs manual to include reference material and examples on all the syntax features supported by . Link in Nixos manual for completion. [x] remove references to in the . : [x] remove references to in the . [x] add a redirecting to the syntax section in . [x] add reference to lack of support for [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support () () )
Code change:
sha256 = "sha256-0S7Dj6PMSbZkEAY6ZLUpKVfe/tFxsq60TTAFj0Qhtv0="; }; <del> # See https://github.com/NixOS/nixpkgs/issues/156957. postPatch = '' substituteInPlace setup.py  --replace "dill>=0.3.1.1,<0.3.2" "dill"  --replace "pyarrow>=0.15.1,<8.0.0" "pyarrow"  --replace "numpy>=1.14.3,<1.23.0" "numpy"  --replace "pymongo>=3.8.0,<4.0.0" "pymongo" ''; </del> <ins> pythonRelaxDeps = [ # See https://github.com/NixOS/nixpkgs/issues/156957 "dill" "numpy" "pyarrow" "pymongo" # See https://github.com/NixOS/nixpkgs/issues/193613 "protobuf" ]; </ins> sourceRoot = "source/sdks/python";

Related discussion:
text: Build of failed on x86_64-linux as of . This is currently breaking . python39Packages.tensorflow-datasets maintainers cc: maintainers cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tags:
Code change:
, gnome3 , libhandy , librsvg <ins> , rustc , cargo </ins> }: <del> rustPlatform.buildRustPackage rec { </del> <ins> stdenv.mkDerivation rec { </ins> pname = "gnome-tour"; version = "3.38.0";

Related discussion:
text: Describe the bug fails to compile with Additional context See for a possible cause. Notify maintainers cc (sorry for notifying you here and in the PR!)
Gonna try to just switch it to . We should probably update gnome docs for Rust+Gnome packages
Yeah, I think that would be best. The idea of the hooks is that is not necessary anymore in mixed projects. I will also do a PR for cargoBuildHook, since it should not be used when is set explicitly.
Code change:
''; installPhase = let <del> pythonPath = python.pkgs.makePythonPath propagatedBuildInputs; </del> <ins> pythonPath = python.pkgs.makePythonPath dependencies; </ins> in '' runHook preInstall

Related discussion:
text: Package name: paperless-ngx Latest released version: 2.12.1 <!-- Search your package here: --- Current version on the unstable channel: 2.11.6 <!-- 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. --
Code change:
curl fmt_9 glm <ins> glslang </ins> gtk3 hidapi imgui'

Related discussion:
text: Steps to reproduce the behavior: cemu Adding and to buildInputs might fix it <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]: