jiebi/CodeConvo huggingface dataset:
Change:
RemainAfterExit = true; }; environment.ZFS_FORCE = optionalString force "-f"; <del> script = (importLib { </del> <ins> script = let keyLocations = getKeyLocations pool; in (importLib { </ins> # See comments at importLib definition. zpoolCmd = "${cfgZfs.package}/sbin/zpool"; awkCmd = "${pkgs.gawk}/bin/awk";

Discussion:
When multiple ZFS filesystems are present and configured to import, each individual attempts to load the keys for ALL pools/datasets, instead of just its own. A clear and concise description of what the bug is. Steps to reproduce the behavior: encrypted zfs filesystems in your NixOS configuration. & Reboot All targets complete successfully The below snippet from the services's script. It's 'ing, and just looping over all pools/datasets. Instead, it should just specify the name directly in the command. (Generated in ) Please run and paste the result. system: host os: multi-user?: sandbox: version: nixpkgs:
Can you post the relevant Nix config you used? Do you have set to anything?
Yep, here's my zfs config. uses (unlocked at boot) is unencrypted and have on-disk
Ok, I think this is fundamentally the same issue as . Basically, when there are multiple pools and is a list, we accidentally run with no dataset argument in the import service for pools that have no datasets in the list. So those services end up iterating over all datasets on all pools instead of none.

Steps to reproduce the behavior: to a list. (in my case, these are backup pools to which I raw-send encrypted datasets, none of their content is expected to be mounted under normal circumstances). boot process still requests the keys for datasets that are not in the list from step 1. I should only ever see decryption prompts for datasets that I want decrypted. system: host os: multi-user?: sandbox: version: channels(novenary): channels(root): nixpkgs:
Change:
<ins> diff --git a/src/slic3r/Utils/Http.cpp b/src/slic3r/Utils/Http.cpp index 11a36dfabc..77a44e699b 100644 --- a/src/slic3r/Utils/Http.cpp +++ b/src/slic3r/Utils/Http.cpp @@ -88,9 +88,13 @@ std::mutex g_mutex; struct form_file { -    fs::ifstream ifs; +    fs::ifstream                          ifs; boost::filesystem::ifstream::off_type init_offset; size_t                                content_length; + +    form_file(fs::path const& p, const boost::filesystem::ifstream::off_type offset, const size_t content_length) +        : ifs(p, std::ios::in | std::ios::binary), init_offset(offset), content_length(content_length) +    {} }; struct Http::priv @@ -314,7 +318,7 @@ void Http::priv::form_add_file(const char *name, const fs::path &path, const cha filename = path.string().c_str(); } -	form_files.emplace_back(form_file{{path, std::ios::in | std::ios::binary}, offset, length}); +	form_files.emplace_back(path, offset, length); auto &f = form_files.back(); size_t size = length; if (length == 0) { @@ -381,7 +385,7 @@ void Http::priv::set_put_body(const fs::path &path) boost::system::error_code ec; boost::uintmax_t filesize = file_size(path, ec); if (!ec) { -        putFile = std::make_unique<form_file>(form_file{{path, std::ios_base::binary | std::ios_base::in}, 0, 0}); +        putFile = std::make_unique<form_file>(path, 0, 0); ::curl_easy_setopt(curl, CURLOPT_UPLOAD, 1L); ::curl_easy_setopt(curl, CURLOPT_READDATA, (void *) (putFile.get())); ::curl_easy_setopt(curl, CURLOPT_INFILESIZE, filesize); </ins>

Discussion:
Package name: orca-slicer Latest released version: 2.1.1 <!-- Search your package here: --- Current version on the unstable channel: 2.0.0 Current version on the stable/release channel: 2.0.0 <!-- 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! --- <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
please change update from 2.0.0 to 2.1.1 due to some major bugs in 2.1.0
Change:
}: stdenv.mkDerivation (finalAttrs: { pname = "ticktick"; <del> version = "1.0.80"; </del> <ins> version = "2.0.0"; </ins> src = fetchurl { url = "https://d2atcrkye2ik4e.cloudfront.net/download/linux/linux_deb_x64/${finalAttrs.pname}-${finalAttrs.version}-amd64.deb"; <del> hash = "sha256-EK+8NFEim2gcFj9t6AGYdGVlyFj9Yq7NaOia3XKy3cc="; </del> <ins> hash = "sha256-LOllYdte+Y+pbjXI2zOQrwptmUo4Ck6OyYoEX6suY08="; </ins> }; nativeBuildInputs = [

Discussion:
Package name: ticktick Latest released version: 2.0.0 Current version on the unstable channel: 1.0.80 Notify maintainers Please update to the latest version. Thanks
Change:
units = [ pkgs.udunits ]; V8 = [ pkgs.v8 ]; XBRL = with pkgs; [ zlib libxml2.dev ]; <ins> XLConnect = [ pkgs.jdk ]; </ins> xml2 = [ pkgs.libxml2.dev ] ++ lib.optionals stdenv.isDarwin [ pkgs.perl ]; XML = with pkgs; [ libtool libxml2.dev xmlsec libxslt ]; affyPLM = [ pkgs.zlib.dev ];

Discussion:
Steps to reproduce the behavior: 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. system: host os: multi-user?: sandbox: version: channels(hervyqa): channels(root): nixpkgs:
Change:
systemd.timers.nixos-upgrade = { timerConfig = { RandomizedDelaySec = cfg.randomizedDelaySec; <ins> FixedRandomDelay = cfg.fixedRandomDelay; </ins> Persistent = cfg.persistent; }; };

Discussion:
Right now, only supports passing a schedule of dates with or without a . This means that either: machine that uses the same module will update simultaneously () need to override the on every machine to something different (machine a is , machine b is , ...), which is manual effort can build jitter into it with a value of greater than zero, but since every run re-rolls the randomness, updates can now be extremely non-uniform - for example, a system set to update daily with up to 23 hours of randomness may update twice within two hours, and then not for 46 hours. Of course, all of (1)-(3) are adequate enough for most general circumstances. However, systemd 247 introduced which generates a stable random offset (up to ) which is different for each machine ID. This allows for the consistent periodicity of (2) automatically instead of manually. Please consider whether (default ) would be an appropriate new option to add. Until then, I'll be setting it myself through .
Change:
<del> { stdenv, fetchurl, makeWrapper, makeDesktopItem, autoPatchelfHook, env </del> <ins> { stdenv, fetchurl, mkDerivation, makeWrapper, makeDesktopItem, autoPatchelfHook , wrapQtAppsHook </ins> # Dynamic libraries , dbus, glib, libGL, libX11, libXfixes, libuuid, libxcb, qtbase, qtdeclarative , qtimageformats, qtlocation, qtquickcontrols, qtquickcontrols2, qtscript, qtsvg

Discussion:
Describe the bug zoom-us appears to be broken. Caused by a change between .... To Reproduce Steps to reproduce the behavior: Expected behavior Success Additional context Logs: Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(root): channels(mbauer): nixpkgs: Maintainer information: /cc
I'll try using the new Qt infrastructure and see how it interacts with binaries, I guess.
Just using doesn't change anything, but removing from allows it to build. I had to replace with as well. Unfortunately, the application doesn't create a window, but the terminal output is normal. Still investigating.
Fix incoming.
Change:
<ins> { cabal, filepath }: cabal.mkDerivation (self: { pname = "xdg-basedir"; version = "0.2.2"; sha256 = "0azlzaxp2dn4l1nr7shsxah2magk1szf6fx0mv75az00qsjw6qg4"; buildDepends = [ filepath ]; meta = { homepage = "http://github.com/willdonnelly/xdg-basedir"; description = "A basic implementation of the XDG Base Directory specification"; license = self.stdenv.lib.licenses.bsd3; platforms = self.ghc.meta.platforms; }; }) </ins>

Discussion:
I'm planning to use nix as a package manager for my development toolchain, but not do the actual development in nix, is that a supported use case? I've hit some issues and have been sending in PRs to resolve them, but looking into it more the issues I've been hitting might have been derivations just working as intended. explains that library derivations in Nix only work when used in a nix environment, be it nix-shell or within nixpkgs. Is the same true for all development derivations, for example compilers and build tools? Examples: ++ doesn't work outside of nix-shell on darwin, but it does on linux, and I'm not sure which of the two is correct (). creates compiler wrappers to handle the way flags from dependencies are propagated in nixpkgs, but those wrappers are unnecessary when using the compilers from profiles. the bazel derivation is a script that wraps bazel to make it use clang and java from nix, instead of resolving it from the caller's , so that it can be used from within nixpkgs, but it results in a bazel that doesn't function correctly when installed. If existing development derivations are meant to be only used in a nix environment, would it be ok to add new derivations for use outside of a nix environment?
Nixpkgs do not explicitly support C++ compilers outside Nix environment, but this is a valuable use case and it would be great if you could work towards it.
It won't be helpful if there's no convention around it, how would someone find out which specific compilers work outside a Nix environment and which don't?
Either the default compilers will work (, ), or people will discover the new compilers (e.g. ) in the list of packages, in Nixpkgs issues, on the wiki, on IRC etc.
I have managed to work around this issue by creating wrappers for the compilers tailored to the specific use cases I have. It works very well, and it seems it's what others are doing as well. I'll close this issue since it's not relevant anymore.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
asl20 ]; maintainers = with maintainers; [ hexa ]; <ins> mainProgram = "pretix-manage"; platforms = platforms.linux; </ins> }; }

Discussion:
The pretix package does not contain generated locales for , causing internal server errors when trying to select this language (concretely when clients try to access ). Steps to reproduce the behavior: the pretix module with an organizer and select german-informal in the localisation settings. the organiser profile, be greeted by an "Internal Server Error" page. Be present with the actual requested page instead of an http/500 one. The E-Mail sent out to the admin contains more details: This seems to be related to the of django. Looking in the requested is missing. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
The pypi wheel is missing it as well, but the hosted version does have it. :thinking:
The locale is seen by , but not by , which originates in Happens to as well.
It's also noteworthy that is compiling e.g. , which is not in the output of :thinking:
This list seems more reasonable, no? :laughing:
I do have the feeling, that this happens because there is not pretix configuration at build time. From checking just a couple of languages, the ones showing up in appear to match the ones in And whilst pretix has it's own , they do not set defaults for . To my understanding (based on heavy use of ;)), pretix only sets based on the user-provided settings (see ).
Yep, that's why. I'm preparing a patch.
Indeed, that looks purrfect!
Change:
<del> { config, lib, ... }: </del> <ins> { config, lib, pkgs, ... }: </ins> with lib; {

Discussion:
A clear and concise description of what the bug is. Steps to reproduce the behavior: install Nixos enabling Gnome An option to Exclude Gnome-Tour package or to exclude some Gnome-shell packages I would like to exclude some useless Gnome-shell packages that if i exclude them will not break my whole system. You can not exclude packages from Gnome-shell with this option and this not work because is required by this <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
This should be resolved in , but it is not part of 22.05, Edit:
How do I do a backport ? Thank you for your fast response.
It works. = with pkgs; [ gnome-tour ];
After doing this commands gnome tour still in my system. Do i need to do something more ? ! Maybe that ballon is not Gnome tour but i think it is.
It works in unstable channel, you need waitting for Backport 22.05 merge.
Thank you
I merged , not sure why the issue is not auto-closed. You should get the fix when the backport reaches the channel you uses, feel free to re-open this if the issue persists.
After waiting for being in Nixos 22.05, Writing this in And executing. That deleted Gnome-tour from my system. Thank you for your support.
Change:
<ins> { lib , rustPlatform , fetchFromGitHub }: rustPlatform.buildRustPackage rec { pname = "rustywind"; version = "0.16.0"; src = fetchFromGitHub { owner = "avencera"; repo = "rustywind"; rev = "v${version}"; hash = "sha256-xDpRS8WrFu5uPtbXJGXrxElJinxl1lkpYZ1tGrNrBHA="; }; cargoHash = "sha256-2bo6KkHVw1lyLD4iWidAyxZzQMRTO5DWvYmqUQld15g="; meta = with lib; { description = "CLI for organizing Tailwind CSS classes"; homepage = "https://github.com/avencera/rustywind"; changelog = "https://github.com/avencera/rustywind/blob/${src.rev}/CHANGELOG.md"; license = licenses.asl20; maintainers = with maintainers; [ figsoda ]; }; } </ins>

Discussion:
Project description CLI for organizing Tailwind CSS classes Metadata homepage URL: source URL: license: Apache License 2.0 platforms: unix, linux, darwin, ...
Change:
<ins> { lib , buildPythonPackage , fetchFromGitHub , hatchling , bdffont , pytestCheckHook , nix-update-script }: buildPythonPackage rec { pname = "pcffont"; version = "0.0.11"; pyproject = true; src = fetchFromGitHub { owner = "TakWolf"; repo = "pcffont"; rev = "refs/tags/${version}"; hash = "sha256-gu9niWxYTw3rcA++z8B+MdKp5XaqAGjmvd+PdSDosfg="; }; build-system = [ hatchling ]; dependencies = [ bdffont ]; nativeCheckInputs = [ pytestCheckHook ]; pythonImportsCheck = [ "pcffont" ]; passthru.updateScript = nix-update-script { }; meta = { description = "Library for manipulating Portable Compiled Format (PCF) fonts"; homepage = "https://github.com/TakWolf/pcffont"; license = lib.licenses.mit; maintainers = with lib.maintainers; [ ]; }; } </ins>

Discussion:
looking over broken python packages for ZHF and pixel-font-builder is missing a python module and needs a dependency relaxed. Steps to reproduce the behavior: *pixel-font-builder" pcffont not part of nixpkgs would add it but no longer a maintainer <!-- 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]:
Change:
<del> { lib , stdenv , fetchFromGitHub , xz , autoPatchelfHook }: # Assets for fishnet: A collection of pre-built compressed stockfish binaries. # We have to decompress them, patch them using auto-patchelf and compress them # again so that a selection of them can be embedded into the fishnet binary. stdenv.mkDerivation rec { pname = "fishnet-assets"; version = "unstable-2020-03-27"; src = fetchFromGitHub { owner = "niklasf"; repo = pname; rev = "a1fe3ec6074ad9dc43e6d46e0d42fab5d7cce12c"; sha256 = "1548wj2bs89b5w42z3c98hpnbln5w8p1909wyl7a63d8vkvnyn5l"; }; relAssetsPath = "share/${pname}"; nativeBuildInputs = [ xz autoPatchelfHook ]; postPatch = '' # Delete packed .exe files and all non .xz files (documentation and readme) rm *.exe.xz find ! -name "*.xz" -delete # Extract .xz files, except *.nnue.xz # We don't have to unpack the latter and it takes ages to repack find -name "*.xz" ! -name "*.nnue.xz" | xargs unxz -v ''; dontBuild = true; installPhase = '' mkdir -p $out/${relAssetsPath} cp ./* $out/${relAssetsPath} ''; preFixup = '' gatherLibraries '${stdenv.cc.cc.lib}' ''; doDist = true; distPhase = '' # repack assets find $out/${relAssetsPath} -type f ! -name "*.xz" | xargs xz -v ''; meta = with lib; { description = "Assets for fishnet, only required during build"; homepage = "https://github.com/niklasf/fishnet-assets"; license = licenses.gpl3Only; maintainers = with maintainers; [ tu-maurice ]; platforms = [ "x86_64-linux" ]; }; } </del>

Discussion:
fails to build as: Maintainer information:
fishnet-assets is archived; fishnet's builtin stockfish and fairy-stockfish are now submodules built from source. So I think we can just get rid of entirely. I think the only hard part is adjusting their build script so it doesn't try to download the NNUE file.
Change:
postgresql_11 = self.callPackage generic { version = "11.2"; <del> psqlSchema = "11.2"; </del> <ins> psqlSchema = "11.1"; # should be 11, but changing it is invasive </ins> sha256 = "01clq2lw0v83zh5dc89xdr3mmap0jr37kdkh401ph6f2177bjxi6"; this = self.postgresql_11; inherit self;

Discussion:
updates postgresql11 from 11.1 to 11.2. <delIt seems like this includes breaking changes, since neither my Gitea nor my Quassel servers can properly work with 11.2.</delWhen upgrading, the new service is configured to use a different storage directory, because the psqlSchema version was changed: /var/lib/postgresql/11.2/ instead of /var/lib/postgresql/11.1/. This means when upgrading to 11.2, the data is not transferred and applications crash because their databases don't exist anymore. <delI'm also confused as to why postgresql96 has an own package as a minor version, while postgresql 11.x share one package. Shouldn't there be postgresql111 and postgresql112 if 11.2 includes breaking changes?</delRebuild a system with postgresql with the current unstable channel. postgresql 11.1 will be updated to postgresql 11.2, and all databases will not exist with the new versions, applications will crash. system: host os: multi-user?: sandbox: version: channels(pbb): channels(root): nixpkgs:
Thanks for report. PG changed it's version schema since v10. Previously v9.6.1 and 9.6.2 were considered compatible, but 9.5 and 9.6 - not compatible. Now 11.1 and 11.2 are considered compatible, but 10 and 11 - are not. In case they really have introduced a breaking change, it should be reported upstream. We can add old PG as workaround. Can you describe what exactly was broken (test case)?
I was running Quassel and Gitea with postgresql_11 pinned in my config. Last night the nixos-upgrade ran and updated from 11.1 to 11.2. After restarting, both Gitea and Quassel could not access their databases properly. For Gitea it just looked like the database was empty, all repositories and users were missing. I could not see any related messages in the log. For Quassel, the log looked like this:
As a quickfix I have my own postgresql111 package in my system configuration. After downgrading, everything works as expected again.

Okay, I can now tell what causes this behaviour: When upgrading, the new service is configured to use a different storage directory: /var/lib/postgresql/11.2/ instead of /var/lib/postgresql/11.1/. This means when upgrading to 11.2, the data is not transferred. Both applications failed, because their databases were missing.
Probably the psqlSchema version for 11.1 and 11.2 should be 11.0.
Change:
<del> { lib , python3 , fetchFromGitHub }: python3.pkgs.buildPythonApplication rec { pname = "flexget"; version = "3.11.39"; pyproject = true; # Fetch from GitHub in order to use `requirements.in` src = fetchFromGitHub { owner = "Flexget"; repo = "Flexget"; rev = "refs/tags/v${version}"; hash = "sha256-saNxs+Xdf6OTRRcMTceU8/ITcYzwtP8VqRKxsWyas+o="; }; postPatch = '' # remove dependency constraints but keep environment constraints sed 's/[~<>=][^;]*//' -i requirements.txt ''; build-system = with python3.pkgs; [ setuptools wheel ]; dependencies = with python3.pkgs; [ # See https://github.com/Flexget/Flexget/blob/master/requirements.txt apscheduler beautifulsoup4 click colorama commonmark feedparser guessit html5lib jinja2 jsonschema loguru more-itertools packaging pendulum psutil pynzb pyrsistent pyrss2gen python-dateutil pyyaml rebulk requests rich rpyc sqlalchemy typing-extensions # WebUI requirements cherrypy flask-compress flask-cors flask-login flask-restful flask-restx flask pyparsing werkzeug zxcvbn # Plugins requirements transmission-rpc ]; pythonImportsCheck = [ "flexget" "flexget.plugins.clients.transmission" ]; # ~400 failures doCheck = false; meta = with lib; { homepage = "https://flexget.com/"; changelog = "https://github.com/Flexget/Flexget/releases/tag/v${version}"; description = "Multipurpose automation tool for all of your media"; license = licenses.mit; maintainers = with maintainers; [ pbsds ]; }; } </del>

Discussion:
Flexget is not building on python3.12 on NixOS Unstable since nose 1.3.7 does not run on python 3.12 According to flexget website only pything versions 3.7 to 3.11 are supported: Steps to reproduce the behavior: to nixos unstable to install flex A clear and concise description of what you expected to happen. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
, openssl, libuuid, gnu-efi, libbfd }: <del> stdenv.mkDerivation { </del> <ins> stdenv.mkDerivation rec { </ins> pname = "sbsigntool"; <del> version = "0.9.1"; </del> <ins> version = "0.9.4"; </ins> src = fetchgit { url = "https://git.kernel.org/pub/scm/linux/kernel/git/jejb/sbsigntools.git"; <del> rev = "v0.9.1"; sha256 = "098gxmhjn8acxjw5bq59wq4xhgkpx1xn8kjvxwdzpqkwq9ivrsbp"; </del> <ins> rev = "v${version}"; sha256 = "sha256-dbjdA+hjII/k7wABTTJV5RBdy4KlNkFlBWEaX4zn5vg="; </ins> }; patches = [ ./autoconf.patch ];

Discussion:
The systemd-boot image built in nixpkgs has gaps in the section table. This leads to signature verification failure with some UEFI Secure Boot implementations (e.g. Dell XPS 13 9310) Using NixOS 22.05 @ Using some old version from NixOS 21.11 that I still have in the store: N/A Allegedly something like this was fixed in systemd upstream and the commit is present in v250.4 but for some reason it still appears and Secure Boot 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. system: host os: multi-user?: sandbox: version: nixpkgs:
Relevant:
This commit might be the culprit: I will try confirm this, but since it requires rebuilding systemd, it'll take a while.
It's more likely a problem of sbsigntools:
Does your hardware still correctly validate the signature with this patch applied?
Yes, signature verification works with this patch (and only with this patch). Hardware is Dell XPS 13 9310. See also