jiebi/CodeConvo huggingface dataset:
Code change:
# A target remains active. Use this to probe the fact that # a service fired eventhough it is not RemainAfterExit <del> systemd.targets."acme-finished-a.example.test" = {}; systemd.services."acme-a.example.test" = { wants = [ "acme-finished-a.example.test.target" ]; before = [ "acme-finished-a.example.test.target" ]; after = [ "nginx.service" ]; </del> <ins> systemd.targets."acme-finished-a.example.test" = { after = [ "acme-a.example.test.service" ]; wantedBy = [ "acme-a.example.test.service" ]; </ins> }; services.nginx.enable = true;

Related discussion:
text: I use enabled. I also have a web server service that specifies: Because my web server is a bit long to start, the timeout and its systemd unit fails. To Reproduce Use the following example module: Expected behavior The acme systemd units created by  should wait that nginx is started before starting. Metadata Maintainer information:
Should adding to what is already to  fix the issue?
Making a note that has the same code and presumably the same issue so any fix on should likely be ported to .
Thank you for the issue and reproducer. I'll have a closer look at this today
what exactly do you mean by "timeout" here by the way. could you provide some journal logs of this failure? I can try reproduce when I'm home, but maybe the logs are enough to understand what is going wrong
I mean "Timeout during connect (likely firewall problem)" in the logs below. Note that the hostname, email and domain have been redacted. Also notice the long time between and . nginx was not started when the Let's Encrypt tried to retrieve the challenge:
I'm scared that won't work. The lack of here is very deliberate pulls in (Through and ) to create fake certs, as nginx crashes hard when certificate paths aren't present. We want to start up before the acme challenge is initiated, as nginx is responsible for serving the director to complete it. If starts before nginx, it will always fail. It's all a bit mind-boggling and the dependencies are a bit complicated. I wish it was a bit more simpler too. However; isn't what we want here instead? We want to guarentee that is running before the certificate request is fired off. So adding a to might work? I'll see if that fixes it..
Absolutely, that is what I meant but I wrote it wrongly.
Should we go for the solution proposed?
Yep. I have a PR in the works on my machine. I'll try to get it out this week
Code change:
patches = [ ./fedora-fixes.patch ]; <ins> # Fix for #40213, probably permanent, because upstream doesn't seem to be # developed anymore. Alternatively, gcc7Stdenv could be used. NIX_CFLAGS_COMPILE = "-Wno-error=array-bounds"; </ins> meta = with stdenv.lib; { homepage = https://sourceforge.net/projects/omxil/; description = "An opensource implementation of the Khronos OpenMAX Integration Layer API to access multimedia components";

Related discussion:
text: On the , quite a few jobs are failing because libomxil-bellagio fails to build (, for an example). cc (as the package maintainer)
Copy-paste from IRC (for the record)
Code change:
<del> { lib, stdenv, pixie, fetchFromGitHub }: </del> <ins> { lib, stdenv, fetchFromGitHub , pixie, rlwrap }: </ins> stdenv.mkDerivation rec { pname = "dust";

Related discussion:
text: Running reports: To Reproduce on NixOS 19.09. . Metadata I ran but got .
Hello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use or on the relevant files to find them. Lastly, you can always ask for help at or at .
I had this same problem today.
I marked this as stale due to inactivity. &rarr;
Not stale; this is still a problem on a flakes based NixOS system using
Code change:
rich-rst = callPackage ../development/python-modules/rich-rst { }; <ins> rich-theme-manager = callPackage ../development/python-modules/rich-theme-manager { }; </ins> ring-doorbell = callPackage ../development/python-modules/ring-doorbell { }; rio-tiler = callPackage ../development/python-modules/rio-tiler { };

Related discussion:
text: Project description Python app to work with pictures and associated metadata from Apple Photos on macOS. Also includes a package to provide programmatic access to the Photos library, pictures, and metadata. Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
This was the most complex package i ever tried to write :sweat_smile:
Code change:
./programs/nm-applet.nix ./programs/npm.nix ./programs/oblogout.nix <ins> ./programs/partition-manager.nix </ins> ./programs/plotinus.nix ./programs/proxychains.nix ./programs/qt5ct.nix

Related discussion:
text: Describe the bug and failed to build on current master (). (The former depends on the latter.) Build log: To Reproduce Steps to reproduce the behavior: nixpkgs master. (or ) the build error. Expected behavior It builds. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata Please run and paste the result. Maintainer information:
Code change:
./programs/nm-applet.nix ./programs/npm.nix ./programs/oblogout.nix <ins> ./programs/partition-manager.nix </ins> ./programs/plotinus.nix ./programs/proxychains.nix ./programs/qt5ct.nix

Related discussion:
text: Describe the bug If you open KDE Partition Manager using its file, it tells you that you aren't running it as root, and you won't be able to make any changes with it (rendering the program useless). The only workaround is running (which is probably unintuitive to people with less linux experience) or changing the file (a bad idea when you want Nix to manage your system) To Reproduce Steps to reproduce the behavior: by adding it to your the file (e.g. in KDE, click on the start menu in the bottom left, type in partition manager, and click on the program) Expected behavior Use when clicking the file for a seamless experience Screenshots ! Additional context The message mentions so I tried adding it to by hand, but that did not work. Metadata Maintainer information:
Looks like the package is out of date. This dialogue does not appear to be part of the latest version:
This might work
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 .
Code change:
<ins> diff --git a/meson.build b/meson.build index 5030d0c..6de7a20 100644 --- a/meson.build +++ b/meson.build @@ -32,10 +32,11 @@ transmission_dep = declare_dependency( meson.get_compiler('c').find_library('dht'), meson.get_compiler('c').find_library('natpmp'), meson.get_compiler('c').find_library('event'), -				meson.get_compiler('c').find_library('libcurl'), -				meson.get_compiler('c').find_library('libcrypto'), +				meson.get_compiler('c').find_library('curl'), +				meson.get_compiler('c').find_library('crypto'), +				meson.get_compiler('c').find_library('ssl'), meson.get_compiler('c').find_library('libpthread'), -				meson.get_compiler('c').find_library('libz'), +				meson.get_compiler('c').find_library('z'), transmission_vapi, transmission_lib ]) @@ -45,4 +46,4 @@ subdir('data') subdir('po') subdir('src') -meson.add_install_script('build-aux/postinstall.py') +meson.add_install_script('python3', '../build-aux/postinstall.py') </ins>

Related discussion:
text: Project description Fragments is a modern, responsive and graphical Gnome bittorrent client Metadata homepage URL: source URL: license: gpl3 platforms: linux The new version of Fragments depends on libutp which hopefully gets merged soon. I've opened a pull request for it . for Fragments.
We have transmission and torrential. Maybe that's something for you.
That's true but Fragments is a really neat, easy and modern looking torrent client. It has an adaptive interface which would also work quite well on mobile devices, for example NixOS mobile :+1:
Code change:
+ +case $1 in +    ""|"repl") <del> +        rlwrap_cmd="" +        if [ -n "`which rlwrap`" ]; then +            rlwrap_cmd="rlwrap -aignored -n" +        fi +        $rlwrap_cmd $pixie_path $load_path </del> <ins> +        $rlwrap_cmd -aignored -n $pixie_path $load_path </ins> +        ;; +    "run") +        shift

Related discussion:
text: Running reports: To Reproduce on NixOS 19.09. . Metadata I ran but got .
Hello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use or on the relevant files to find them. Lastly, you can always ask for help at or at .
I had this same problem today.
I marked this as stale due to inactivity. &rarr;
Not stale; this is still a problem on a flakes based NixOS system using
Code change:
--replace /usr/bin/perl "${perl}/bin/perl" substituteInPlace src/lib/Gitolite/Hooks/Update.pm  --replace /usr/bin/perl "${perl}/bin/perl" <ins> substituteInPlace src/lib/Gitolite/Setup.pm  --replace hostname "${nettools}/bin/hostname" </ins> ''; installPhase = ''

Related discussion:
text: I don't know much more than this: and but I don't know how to fix this.
I was bit by this as well. It fails on other key for me -- looks like it would fail on any.
How did you solve this issue?
Can someone tell me where this "keydir" should be located? I cannot find it in my !
The keydir should be in your gitolite datadir, which is /var/lib/gitolite in the default settings.
Okay. My shows:
oh it should be in "/var/lib/gitolite/.gitolite/keydir", my bad.
Okay, everything is there. How to check why it fails?
It failed for me for every key on v3.6.2. So, besides upgrading gitolite to v3.6.3, there is not really much you can do.
Update solved the issue.
Code change:
environment.systemPackages = [ alsaUtils ]; <del> environment.etc = mkIf (config.sound.extraConfig != "") </del> <ins> environment.etc = mkIf (!pulseaudioEnabled && config.sound.extraConfig != "") </ins> [ { source = pkgs.writeText "asound.conf" config.sound.extraConfig; target = "asound.conf";

Related discussion:
text: Setting to while setting to any non-empty value will cause a build failure because and both attempt to create The correct result would be for the contents of to be written out at the end of , after the stanzas provided by pulseaudio. Somewhat relatedly, the in and in pulseaudio's generated config doesn't make a whole lot of sense. means "override", currently there is nothing for it to override, and we would like user config to override generated config, not the other way around. However, as long as user config is placed in the file after generated config then I don't think the actually makes any difference.
I am having this issue as well. Easily replicated by setting those two options.
Can you make a pull request?
Should be fixed with . If there still is a problem, please reopen this issue.
Code change:
<ins> diff --git a/setup.py b/setup.py index 62db8af..4a980c1 100755 --- a/setup.py +++ b/setup.py @@ -52,7 +52,7 @@ setuptools.setup( 'ruamel.yaml>0.15.69', 'jsonschema>=4.1.2', 'rfc3987', -        'pylibfdt', +        'libfdt', ], classifiers=[ </ins>

Related discussion:
text: <!-- 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 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: dt-schema <!-- The current version can be found easily with the same process as 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: 2022.1 desired version: 2022.12 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.
A new version is out: Should I just update this and my PR to make use of this new version?
Code change:
enableExtraPlugins = true; }; <del> asciidoctor = callPackage ../tools/typesetting/asciidoctor { }; </del> <ins> asciidoctor = callPackage ../tools/typesetting/asciidoctor { bundlerApp = bundlerApp.override { # asciidoc supports both ruby 2 and 3, # but we don't want to be stuck on it: ruby = ruby_3_1; }; }; </ins> asciidoctor-with-extensions = callPackage ../tools/typesetting/asciidoctor-with-extensions { };

Related discussion:
text: Building this package twice does not produce the bit-by-bit identical result each time, making it harder to detect CI breaches. You can read more about this at https://reproducible- . nix-build '<nixpkgs' -A ... --check --keep-failed You can use to analyze the differences in the output of the two builds. To view the build log of the build that produced the artifact in the binary cache: nix-store --read-log $(nix-instantiate '<nixpkgs' -A ...) Seems to be a file ordering issue while generating : vs
Looks like this list is generated with the standard Ruby function, which in 2.x leaves the sorting up to the filesystem, but from 3.x onwards itself. So perhaps we should just update to Ruby 3.x. In general 2.7 is in mode, so it will only receive security updates and we should probably plan to move things to 3.x
Code change:
sha256 = "00cq03cy5dyghmibsdsq5sdqv3bzkzhshsng74bpnb5lasxp3ia5"; }; <del> pythonPath = with python3.pkgs; [ </del> <ins> nativeBuildInputs = with python3.pkgs; [ setuptools_scm docutils ]; propagatedBuildInputs = with python3.pkgs; [ </ins> musicbrainzngs mutagen pycdio pygobject3 <del> requests </del> ruamel_yaml <del> setuptools setuptools_scm </del> <ins> discid pillow </ins> ]; buildInputs = [ libsndfile ]; checkInputs = with python3.pkgs; [ twisted <del> ]; patches = [ (substituteAll { src = ./paths.patch; inherit cdparanoia; }) ]; </del> <ins> ] ++ bins; </ins> makeWrapperArgs = [ <del> "--prefix" "PATH" ":" (lib.makeBinPath [ accuraterip-checksum cdrdao util-linux flac sox ]) </del> <ins> "--prefix" "PATH" ":" (lib.makeBinPath bins) </ins> ]; preBuild = '' export SETUPTOOLS_SCM_PRETEND_VERSION="${version}" ''; <del> # some tests require internet access # https://github.com/JoeLametta/whipper/issues/291 doCheck = false; preCheck = '' HOME=$TMPDIR </del> <ins> checkPhase = '' runHook preCheck # disable tests that require internet access # https://github.com/JoeLametta/whipper/issues/291 substituteInPlace whipper/test/test_common_accurip.py  --replace "test_AccurateRipResponse" "dont_test_AccurateRipResponse" HOME=$TMPDIR ${python3.interpreter} -m unittest discover runHook postCheck </ins> ''; meta = with lib; {

Related discussion:
text: Describe the bug throws an error when attempting to generate the musicbrainz disc id: Notify maintainers recently updated the package in listed as maintainer Maintainer information:
Code change:
<del> { stdenv, lib, fetchFromGitHub, fetchurl, pkg-config, makeWrapper, allegro5, libGL }: </del> <ins> { stdenv, lib, fetchFromGitHub, fetchurl, pkg-config, allegro5, libGL, wrapGAppsHook }: </ins> stdenv.mkDerivation rec { pname = "liberation-circuit"; <del> version = "unstable-2022-01-02"; </del> <ins> version = "1.3-unstable-2022-01-02"; </ins> src = fetchFromGitHub { owner = "linleyh"; <del> repo = pname; </del> <ins> repo = "liberation-circuit"; </ins> rev = "19e3363547793e931fd9419b61ebc2cd8e257714"; <del> sha256 = "zIwjh4CBSmKz7pF7GM5af+VslWho5jHOLsulbW4C8TY="; </del> <ins> hash = "sha256-zIwjh4CBSmKz7pF7GM5af+VslWho5jHOLsulbW4C8TY="; </ins> }; <del> nativeBuildInputs = [ pkg-config makeWrapper ]; </del> <ins> nativeBuildInputs = [ pkg-config wrapGAppsHook ]; </ins> buildInputs = [ allegro5 libGL ]; <ins> dontWrapGApps = true; </ins> installPhase = '' runHook preInstall mkdir -p $out/opt cp -r bin $out/opt/liberation-circuit chmod +x $out/opt/liberation-circuit/launcher.sh <del> makeWrapper $out/opt/liberation-circuit/launcher.sh $out/bin/liberation-circuit </del> install -D linux-packaging/liberation-circuit.desktop $out/share/applications/liberation-circuit.desktop install -D linux-packaging/liberation-circuit.appdata.xml $out/share/metainfo/liberation-circuit.appdata.xml

Related discussion:
text: When trying to load a multi-binary, a GLib error occurs on the terminal, and liberation-circuit crashes. In fact, this appears when interacting with anything using files: Saving a code, loading a code, and saving a multi-binary. This causes the player to have no way to program his processes. Steps to reproduce the behavior: multi-binary A window should appear to select a file This is the error appearing in the terminal : Please run and paste the result.
Code change:
makeWrapper ${python3Packages.python.interpreter} $out/bin/onedrivegui  --prefix PATH : ${lib.makeBinPath [ onedrive ]}  <del> --prefix PYTHONPATH : ${python3Packages.makePythonPath (propagatedBuildInputs ++ [(placeholder "out")])}  </del> <ins> --prefix PYTHONPATH : ${ python3Packages.makePythonPath (propagatedBuildInputs ++ [ (placeholder "out") ]) }  </ins> --add-flags $out/${python3Packages.python.sitePackages}/OneDriveGUI.py '';

Related discussion:
text: A recent update on unstable broke compatibility between OneDriveGui and OneDrive client. Steps to reproduce the behavior: unstable to current version ( ) a OneDrive profile configured in OneDriveGui OneDriveGui window OneDriveGui correctly recognizing the cli client ! After some investigation on their respective repos, it appears that OneDriveGui 1.0.3 is not compatible with OneDrive 2.5.x, now in rc (and in Nixos unstable) so this is going to stay broken until OneDriveGui releases their 1.1.0 version. There's an open issue on their repository... which points to an alpha release of the new gui... it might be of interest to package that one on unstable. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
FYI , v2.5.0 will GA 16th September 2024 AEST
Code change:
] ++ lib.optionals stdenv.targetPlatform.isiOS [ autoreconfHook ]; <del> buildInputs = [ zlib ]; </del> <ins> buildInputs = [ zlib gettext ]; </ins> inherit noSysDirs;

Related discussion:
text: I'm not really sure why this would happen or how to go about dealing with this. Any tips?
(triage) still a problem?
Unsure, I don't use nix on my mac anymore.
This was a coreutil, right? If so, it’s probably fixed by now.
Probably safe to assume so.
I'm actually hitting the same thing right now.
Code change:
<del> { lib, stdenv, fetchFromGitHub </del> <ins> { lib, stdenv, fetchFromGitHub, fetchpatch </ins> , doxygen, fontconfig, graphviz-nox, libxml2, pkg-config, which , systemd }: <del> let version = "2019-12-08"; in stdenv.mkDerivation { </del> <ins> stdenv.mkDerivation rec { </ins> pname = "openzwave"; <del> inherit version; </del> <ins> version = "1.6"; </ins> <del> # Use fork by Home Assistant because this package is mainly used for python.pkgs.homeassistant-pyozw. # See https://github.com/OpenZWave/open-zwave/compare/master...home-assistant:hass for the difference. </del> src = fetchFromGitHub { <del> owner = "home-assistant"; </del> <ins> owner = "OpenZWave"; </ins> repo = "open-zwave"; <del> rev = "2cd2137025c529835e4893a7b87c3d56605b2681"; sha256 = "04g8fb4f4ihakvvsmzcnncgfdd2ikmki7s22i9c6layzdwavbwf1"; </del> <ins> rev = "v${version}"; sha256 = "0xgs4mmr0480c269wx9xkk67ikjzxkh8xcssrdx0f5xcl1lyd333"; </ins> }; <ins> patches = [ (fetchpatch { name = "fix-strncat-build-failure.patch"; url = "https://github.com/OpenZWave/open-zwave/commit/601e5fb16232a7984885e67fdddaf5b9c9dd8105.patch"; sha256 = "1n1k5arwk1dyc12xz6xl4n8yw28vghzhv27j65z1nca4zqsxgza1"; }) (fetchpatch { name = "fix-text-uninitialized.patch"; url = "https://github.com/OpenZWave/open-zwave/commit/3b029a467e83bc7f0054e4dbba1e77e6eac7bc7f.patch"; sha256 = "183mrzjh1zx2b2wzkj4jisiw8br7g7bbs167afls4li0fm01d638"; }) ]; outputs = [ "out" "doc" ]; </ins> nativeBuildInputs = [ doxygen fontconfig graphviz-nox libxml2 pkg-config which ]; buildInputs = [ systemd ];

Related discussion:
text: Hi, i need to use open-zwave as a dependency for a build, but the version built in the Nix package is a specific fork for supporting home-assistant, which does not work for my package build due to linking errors. I will happily contribute a new package, but I'm not sure how to proceed, with regards to how it would fit in with this package, or if indeed the best way would be to modify this package to use the upstream repo. Pinging people who have maintained the package, apologies for the noise!
Hello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use or on the relevant files to find them. Lastly, you can always ask for help at or at .
We should replace the package with an official version and make use the fork.