jiebi/CodeConvo huggingface dataset:
Change:
Since commit the command is missing. It is used by xscreensaver to display text inside the screensavers like system information and kernel versions. It used to be in the package, as can be seen from this diff: The same applies to which was also removed by that commit Steps to reproduce the behavior: Text is printed when running instead of If applicable, add screenshots to help explain your problem. Add any other context about the problem here. system: host os: multi-user?: sandbox: version: channels(root): channels(pinpox): nixpkgs: Maintainer information:
«removed» here means «same lack of special measures as before» (the lines you cite are just fixes for the installed stuff), but upstream underwent a major rewrite. (Not saying that fix is not most welcome, just that this was not a removal as much as lack of finding out what to do now) Apparently the scripts are there in the tarball, maybe they need manual copying now, not sure
I just noticed it seems to work fine in the previewer application that comes with xscreensaver . E.g.: ! The same screensaver does not work though, when it starts "on it's own" after some idle time. The text then only reads Not sure what the difference is.
xscreensaver-text and others are in $out/libexec/xscreensaver btw speeds up the build of xscreensaver by a lot
Hm, is not in my path, but hacks launched via XScreenSaver proper find text just fine. And the daemon source code implies that is indeed to PATH in a normal situation.
Not sure if it's related, but it is also missing commands like and (output is shown in some of the screensavers). I have enabled xsceensaver with the home-manager option

Discussion:
<del> { lib, stdenv, fetchurl </del> <ins> { lib, stdenv, fetchurl, makeWrapper </ins> , pkg-config, intltool , perl, gettext, libX11, libXext, libXi, libXt , libXft, libXinerama, libXrandr, libXxf86vm, libGL, libGLU, gle , gtk2, gdk-pixbuf, gdk-pixbuf-xlib, libxml2, pam <del> , systemd </del> <ins> , systemd, coreutils </ins> , forceInstallAllHacks ? false , withSystemd ? stdenv.isLinux }:

}; nativeBuildInputs = [ <del> pkg-config intltool </del> <ins> pkg-config intltool makeWrapper </ins> ]; buildInputs = [

"--with-app-defaults=${placeholder "out"}/share/xscreensaver/app-defaults" ]; <del> postInstall = lib.optionalString forceInstallAllHacks '' </del> <ins> postInstall = '' for bin in $out/bin/*; do wrapProgram "$bin"  --prefix PATH : "$out/libexec/xscreensaver"  --prefix PATH : "${lib.makeBinPath [ coreutils ]}" done '' + lib.optionalString forceInstallAllHacks '' </ins> make -j$NIX_BUILD_CORES -C hacks/glx dnalogo cat hacks/Makefile.in  | grep -E '([a-z0-9]+):[[:space:]]*1[.]o' | cut -d : -f 1 | xargs make -j$NIX_BUILD_CORES -C hacks
Change:
<!-- 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: <!-- 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: 6.2.0 desired version: 6.3.0 <!-- 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.

Discussion:
}; self = mkDerivation rec { <del> version = "6.2.0"; </del> <ins> version = "6.3.0"; </ins> pname = "octave"; src = fetchurl { url = "mirror://gnu/octave/${pname}-${version}.tar.gz"; <del> sha256 = "sha256-RX0f2oY0qDni/Xz8VbmL1W82tq5z0xu530Pd4wEsqnw="; </del> <ins> sha256 = "sha256-IyBl86cvwwE/6fF/Qpo99p1nLB9rYHcCmjHI881Ypm4="; </ins> }; buildInputs = [
Change:
It seems that all nix expressions for gnome3 applications need revision regarding environment variables wrapping. For instance on my unstable NixOS system I have on on my configuration. All of them (except , which I have already fixed), when run outside of gnome3, are giving error messages like I think they may be fixed by replacing uses of to explicitly fix binaries, by , which automatically fixes them wrapping environment variables. EDIT: In some cases it also needs to add a dependency on .
Related: (also includes a few fixes)
cc
I think the last instances of this were fixed by
In the core GNOME, I only came across two not wrapped executables. from package and from . Unfortunately the former cannot be wrapped due to depending on .

Discussion:
, ninja , pkgconfig , gobject-introspection <ins> , gsettings-desktop-schemas , makeWrapper </ins> , dbus , glib

outputs = [ "out" "dev" ]; <del> nativeBuildInputs = [ meson ninja pkgconfig gobject-introspection ] </del> <ins> nativeBuildInputs = [ meson ninja pkgconfig gobject-introspection makeWrapper ] </ins> # Fixup rpaths because of meson, remove with meson-0.47 ++ stdenv.lib.optional stdenv.isDarwin fixDarwinDylibNames; buildInputs = [ dbus glib libX11 libXtst libXi ];

}; }; <ins> postFixup = '' # Cannot use wrapGAppsHook'due to a dependency cycle wrapProgram $out/libexec/at-spi-bus-launcher  --prefix GIO_EXTRA_MODULES : "${stdenv.lib.getLib gnome3.dconf}/lib/gio/modules"  --prefix XDG_DATA_DIRS : ${gsettings-desktop-schemas}/share/gsettings-schemas/${gsettings-desktop-schemas.name} ''; </ins> meta = with stdenv.lib; { description = "Assistive Technology Service Provider Interface protocol definitions and daemon for D-Bus"; homepage = https://gitlab.gnome.org/GNOME/at-spi2-core;
Change:
Project description ... because if that title doesn't excite, I don't know what will... This would be the userspace side of Linux 5.15's kernel samba support (). Metadata homepage URL: source URL: license: gpl2 platforms: linux
I marked this as stale due to inactivity. &rarr;

Discussion:
<ins> { lib , stdenv , fetchFromGitHub , autoconf , automake , glib , libkrb5 , libnl , libtool , pkg-config , withKerberos ? false }: stdenv.mkDerivation rec { pname = "ksmbd-tools"; version = "3.4.5"; src = fetchFromGitHub { owner = "cifsd-team"; repo = pname; rev = version; sha256 = "sha256-sSCLXNdVUAdk+GnFlVx/BsAzyfz0KDdugJ1isrOztgs="; }; buildInputs = [ glib libnl ] ++ lib.optional withKerberos libkrb5; nativeBuildInputs = [ autoconf automake libtool pkg-config ]; preConfigure = "./autogen.sh"; configureFlags = lib.optional withKerberos "--enable-krb5"; meta = with lib; { description = "Userspace utilities for the ksmbd kernel SMB server"; homepage = "https://www.kernel.org/doc/html/latest/filesystems/cifs/ksmbd.html"; license = licenses.gpl2; platforms = platforms.linux; maintainers = with maintainers; [ elohmeier ]; }; } </ins>

kanata-with-cmd = callPackage ../tools/system/kanata { withCmd = true; }; <ins> ksmbd-tools = callPackage ../os-specific/linux/ksmbd-tools { }; </ins> ksnip = libsForQt5.callPackage ../tools/misc/ksnip { }; kubevirt = callPackage ../tools/virtualization/kubevirt { };
Change:
The and packages both provide an implementation of that is incompatible. This is leading to some trouble when having both packages installed and executing shell scripts that expect to be present in the path. Since isn't that widely used I would recommend to either remove from (it is a symbolic link anyway) or to rename it to . Steps to reproduce the behavior: and on a gzip compressed file (example: some ) There might be valid use cases where from is used, for example for very old shell scripts dating back to the early 1990s or earlier. These days the default is expected to be from and other distributions (like Fedora) do not seem to be creating the symlink for .

Discussion:
, stdenv , zlib , xz <del> , ncompress </del> , gzip , bzip2 , gnutar

sha256 = "sha256-lfHXutAp06Xr/TSBpDwBUBC/mWI9XuyImoKwA3inqgU="; }; <del> propagatedBuildInputs = [ zlib xz ncompress gzip bzip2 gnutar p7zip cabextract squashfsTools xz pycrypto ] </del> <ins> propagatedBuildInputs = [ zlib xz gzip bzip2 gnutar p7zip cabextract squashfsTools xz pycrypto ] </ins> ++ lib.optionals visualizationSupport [ matplotlib pyqtgraph ] ++ lib.optionals (!stdenv.isDarwin) [ cramfsprogs cramfsswap sasquatch ];

<del> source $stdenv/setup installFlags="PREFIX=$out" preBuild() { cp Makefile.def Makefile sed -i GNUmakefile -e 's/compress %/%/g' } postInstall() { rm $out/bin/uncompress* $out/bin/zcat* ln -s compress $out/bin/uncompress ln -s compress $out/bin/zcat } genericBuild </del>

<del> {lib, stdenv, fetchurl}: </del> <ins> { lib, stdenv, fetchFromGitHub }: </ins> stdenv.mkDerivation rec { pname = "ncompress"; version = "5.0"; <del> builder = ./builder.sh; src = fetchurl { url = "mirror://sourceforge/project/ncompress/${pname}-${version}.tar.gz"; sha256 = "004r086c11sw9vg2j3srgxpz98w8pycjl33bk3pgqnd0s92igrn4"; </del> <ins> src = fetchFromGitHub { owner = "vapier"; repo = "ncompress"; rev = "v${version}"; sha256 = "sha256-Yhs3C5/kR7Ve56E84usYJprxIMAIwXVahLi1N9TIfj0="; </ins> }; <del> meta = { </del> <ins> makeFlags = [ "PREFIX=$(out)" ]; installTargets = "install_core"; postInstall = '' mv $out/bin/uncompress $out/bin/uncompress-ncompress ''; meta = with lib; { </ins> homepage = "http://ncompress.sourceforge.net/"; <del> license = lib.licenses.publicDomain; </del> <ins> license = licenses.publicDomain; </ins> description = "A fast, simple LZW file compressor"; <del> platforms = lib.platforms.unix; </del> <ins> platforms = platforms.unix; </ins> }; }
Change:
Nix-shell doesn't work if is in the package list. Version info:
I wonder why this has been closed. The problem still remains: That is on OSX but I assume the problem is going to be the same on NixOS/Linux. Could someone please verify and then re-open this?
I verified that the issue exist on latest NixOS. I think the problem is that the jenkins package installs the war as out, but simply as the file $out.
Would be easy enough to fix - What would be an idiomatic solution to this ? What should be ?
if I understood comment, you'd simply do . EDIT: what should be depends on what is ..., if it's a binary you'd expect to show up in your path upon installing it into your environment, you'd use , for example.
D'OH - okay.
I don't know if there is a canonical location for .war files. But whatever directory is chosen, beware that there are some places in nixpkgs that expects the "jenkins" attribute to be the war file itself. Those references must be fixed up in the same commit that moves the file.
A .war file is apparently a .jar file. And .jar files appear mostly in or in nixpkgs.
I have a commit that should fix this. I will push it when it's ready (tested).
Done:
Copied from commit comment:
Copied from commit comment: :-)

Discussion:
maintainers = [ maintainers.coconnor ]; }; <del> buildCommand = "ln -s $src $out"; </del> <ins> buildCommand = "cp $src $out"; </ins> }
Change:
Nix-shell doesn't work if is in the package list. Version info:
I wonder why this has been closed. The problem still remains: That is on OSX but I assume the problem is going to be the same on NixOS/Linux. Could someone please verify and then re-open this?
I verified that the issue exist on latest NixOS. I think the problem is that the jenkins package installs the war as out, but simply as the file $out.
Would be easy enough to fix - What would be an idiomatic solution to this ? What should be ?
if I understood comment, you'd simply do . EDIT: what should be depends on what is ..., if it's a binary you'd expect to show up in your path upon installing it into your environment, you'd use , for example.
D'OH - okay.
I don't know if there is a canonical location for .war files. But whatever directory is chosen, beware that there are some places in nixpkgs that expects the "jenkins" attribute to be the war file itself. Those references must be fixed up in the same commit that moves the file.
A .war file is apparently a .jar file. And .jar files appear mostly in or in nixpkgs.
I have a commit that should fix this. I will push it when it's ready (tested).
Done:
Copied from commit comment:
Copied from commit comment: :-)

Discussion:
# TODO add plugins having various licenses, see http://www.vamp-plugins.org/download.html <del> { stdenv, fetchurl, alsaLib, bzip2, fftw, jackaudio, libX11, liblo, libmad, libogg, librdf, librdf_raptor, librdf_rasqal, libsamplerate, libsndfile, makeWrapper, pulseaudio, qt4, redland, rubberband, vampSDK </del> <ins> { stdenv, fetchurl, alsaLib, bzip2, fftw, jackaudio, libX11, liblo , libmad, libogg, librdf, librdf_raptor, librdf_rasqal, libsamplerate , libsndfile, makeWrapper, pkgconfig, pulseaudio, qt4, redland , rubberband, vampSDK </ins> }: <del> stdenv.mkDerivation { name = "sonic-visualiser-1.8"; </del> <ins> stdenv.mkDerivation rec { name = "sonic-visualiser-${version}"; version = "1.9"; </ins> src = fetchurl { <del> url = http://downloads.sourceforge.net/sv1/sonic-visualiser-1.8.tar.gz; sha256 = "16ik6q9n92wljvnqcv7hyzb9v3yp3ixxp6df9kasf53fii973dh7"; </del> <ins> url = "http://code.soundsoftware.ac.uk/attachments/download/194/${name}.tar.gz"; sha256 = "00igf7j6s8xfyxnlkbqma0yby9pknxqzy8cmh0aw95ix80cw56fq"; </ins> }; buildInputs = [ libsndfile qt4 fftw /* should be fftw3f ??*/ bzip2 librdf rubberband libsamplerate vampSDK alsaLib librdf_raptor librdf_rasqal redland <ins> pkgconfig </ins> # optional jackaudio # portaudio

description = "View and analyse contents of music audio files"; homepage = http://www.sonicvisualiser.org/; license = "GPLv2"; <del> maintainers = [ stdenv.lib.maintainers.marcweber stdenv.lib.maintainers.goibhniu ]; </del> <ins> maintainers = [ stdenv.lib.maintainers.marcweber stdenv.lib.maintainers.goibhniu ]; </ins> platforms = stdenv.lib.platforms.linux; }; }
Change:
The repo URL is missing for: To fix it, you can fork (I forked it for preservation but neither of us made changes: ) then change the GitHub username in the nix file to yours. I don't have NixOS or have any way to test this. I ran into your nix file while trying to find the maintainer: I asked whether the repo has moved because it is deleted from GitHub. I contacted him via 's contact form and I'm awaiting a response (I didn't try an e-mail address found here yet: ).
Recently I have read somewhere that the author was absent from some social media, and that for personal reasons he has removed his account on github, and that this software is still available on launchpad. Github was just a second home for it. But I am not finding this info anymore.
Ok, the author responded to me via e-mail that the launchpad URL is correct, but that he isn't maintaining it. He says he's more likely to rewrite it in Rust rather than update it. The nix file can be corrected to use launchpad, but in light of that information, using one of the GitHub forks or forking one of them yourself and turning on the "Issues" feature is probably the best route to a future for it, even to a minimal extent of getting bugfixes.
I am changing the upstream source to the launchpad repository, as it is the most correct. I am also watching the two forks on github, so that I will be notified of new actions on them.

Discussion:
<del> { lib, stdenv, fetchFromGitHub, cmake, pkg-config, gettext, libXpm, libGL, fltk, hicolor-icon-theme, glib, gnome2, which }: </del> <ins> { lib, stdenv, fetchbzr, cmake, pkg-config, gettext, libXpm, libGL, fltk, hicolor-icon-theme, glib, gnome2, which }: </ins> <del> stdenv.mkDerivation { </del> <ins> stdenv.mkDerivation rec { </ins> pname = "jwm-settings-manager"; <del> version = "2018-10-19"; </del> <ins> version = "2019-01-27"; </ins> <del> src = fetchFromGitHub { owner = "Israel-D"; repo = "jwm-settings-manager"; rev = "cb32a70563cf1f3927339093481542b85ec3c8c8"; sha256 = "0d5bqf74p8zg8azns44g46q973blhmp715k8kcd73x88g7sfir8s"; </del> <ins> src = fetchbzr { url = "lp:${pname}"; rev = "292"; sha256 = "1yqc1ac2pbkc88z7p1qags1jygdlr5y1rhc5mx6gapcf54bk0lmi"; </ins> }; nativeBuildInputs = [

--replace 'DESTINATION usr/share' "DESTINATION share" ''; <ins> postConfigure = '' substituteInPlace cmake_install.cmake  --replace "/var/empty" "/usr" ''; </ins> meta = with lib; { description = "A full configuration manager for JWM"; homepage = "https://joewing.net/projects/jwm";
Change:
no longer compiles with GLib 2.70: The failure looks patchable: We'd need to replace the use of in by an equivalent call to . However I'm not quite confident about the right place to call it, since we need to avoid calling it twice (which is UB according to the GLib documentation) and it looks like there are two different intialization routines that'd need to initialize the lock, and . Therefore I think should try to make an effort to finally get rid of this vulnerable version of fluidsynth (). Remaining uses: [x] , fixed in [x] (cc fixed in [x] (cc fixed in

Discussion:
will no longer work and must be updated. </para> </listitem> <ins> <listitem> <para> The <literal>fluidsynth_1</literal> attribute has been removed, as this legacy version is no longer needed in nixpkgs. The actively maintained 2.x series is available as <literal>fluidsynth</literal> unchanged. </para> </listitem> </ins> </itemizedlist> </section> <section xml:id="sec-release-21.11-notable-changes">

- The `services.mosquitto` module has been rewritten to support multiple listeners and per-listener configuration. Module configurations from previous releases will no longer work and must be updated. <ins> - The `fluidsynth_1` attribute has been removed, as this legacy version is no longer needed in nixpkgs. The actively maintained 2.x series is available as `fluidsynth` unchanged. </ins> ## Other Notable Changes {#sec-release-21.11-notable-changes}

{ stdenv, lib, fetchFromGitHub, pkg-config, cmake , alsa-lib, glib, libjack2, libsndfile, libpulseaudio , AudioUnit, CoreAudio, CoreMIDI, CoreServices <del> , version ? "2" </del> }: <del> let versionMap = { "1" = { fluidsynthVersion = "1.1.11"; sha256 = "0n75jq3xgq46hfmjkaaxz3gic77shs4fzajq40c8gk043i84xbdh"; }; "2" = { fluidsynthVersion = "2.2.3"; sha256 = "0x5808d03ym23np17nl8gfbkx3c4y3d7jyyr2222wn2prswbb6x3"; }; }; in with versionMap.${version}; stdenv.mkDerivation  { name = "fluidsynth-${fluidsynthVersion}"; version = fluidsynthVersion; </del> <ins> stdenv.mkDerivation rec { pname = "fluidsynth"; version = "2.2.3"; </ins> src = fetchFromGitHub { owner = "FluidSynth"; repo = "fluidsynth"; <del> rev = "v${fluidsynthVersion}"; inherit sha256; </del> <ins> rev = "v${version}"; sha256 = "0x5808d03ym23np17nl8gfbkx3c4y3d7jyyr2222wn2prswbb6x3"; </ins> }; nativeBuildInputs = [ pkg-config cmake ];

fluidsynth = callPackage ../applications/audio/fluidsynth { inherit (darwin.apple_sdk.frameworks) AudioUnit CoreAudio CoreMIDI CoreServices; }; <del> fluidsynth_1 = fluidsynth.override { version = "1"; }; </del> fmit = libsForQt5.callPackage ../applications/audio/fmit { };
Change:
Looks like after expiration of root certificate used by letsencrypt pidgin can't connect to jabbers servers that use letsencrypt. At least I can't connect to with the following error: At the same time it works fine under Arch Linux. Try to connect to account. It should connect. Maintainer information:
Hmm, various kinds of SW have apparently problem with the LE defaulting to a chain that still contains the expired cert (even though there's also another one that's among the normally trusted root set).
Looks like it happens because pidgin has its own certs in . So it could be fixed in a similar way with (but not sure which of files should be replaced)
arch has an additional key for this:
Yep, this fixes the problem. Made PR.

Discussion:
, gnutls ? null , libgcrypt ? null , plugins, symlinkJoin <ins> , cacert </ins> }: # FIXME: clean the mess around choosing the SSL library (nss by default)

"--with-nss-includes=${nss.dev}/include/nss" "--with-nss-libs=${nss.out}/lib" "--with-ncurses-headers=${ncurses.dev}/include" <ins> "--with-system-ssl-certs=${cacert}/etc/ssl/certs" </ins> "--disable-meanwhile" "--disable-nm" "--disable-tcl"
Change:
Project description Small Gotify daemon to receive messages and forward them as desktop notifications. Metadata homepage URL: source URL: license: GPLv3 platforms: linux, bsd, macOS, Windows
can you give a try? I failed to make it work in a with the quick start from Gotify, it fails to connect, but otherwise the package looks OK. Also, you want to me a maintainer?
nice, thank you - works for me with and my server (which has an open registration): does we like to promote a user file? either? it would be okay for me, that you add me as maitainer, but i am reallly a nix beginner ....
So do I :) Usually updating existing expressions is easier than creating it, a bump in version and SHAs does the trick. About the service I was thinking the same but by rule of thumb services that depends on something in $HOME is handled by home manager rather than NixOS modules. So I think a future PR can go there to enable a user service. EDIT: I asked for review on the PR, if you want to add yourself as maintainer wait once it's merged then add your info to the maintainers list () and in the package. NOTE: you can check the maintainers- for an example of this process.
this way: ?
Yeap! Just format and squash as bobby285271 asked and welcome aboard!

Discussion:
<ins> { lib, fetchFromGitHub, rustPlatform, openssl, pkg-config}: rustPlatform.buildRustPackage rec { pname = "gotify-desktop"; version = "1.2.0"; src = fetchFromGitHub { owner = "desbma"; repo = pname; rev = version; sha256 = "sha256-QQpZeXFv8BqFOQ+7ANWmtsgNlMakAL2ML4rlG2cFZJE="; }; cargoSha256 = "sha256-zcSAsI/yGGJer7SPKDKZ6NQ3UgTdBcDighS6VTNITMo="; nativeBuildInputs = [ pkg-config ]; buildInputs = [ openssl ]; meta = with lib; { description = "Small Gotify daemon to send messages as desktop notifications"; homepage = "https://github.com/desbma/gotify-desktop"; license = licenses.gpl3Plus; maintainers = [ maintainers.bryanasdev000 ]; }; } </ins>

gotify-cli = callPackage ../tools/misc/gotify-cli { }; <ins> gotify-desktop = callPackage ../tools/misc/gotify-desktop { }; </ins> gping = callPackage ../tools/networking/gping { }; gpu-burn = callPackage ../applications/misc/gpu-burn { };
Change:
<!-- 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: dendrite <!-- 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: 0.4.1 desired version: 0.5.0 <!-- 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.

Discussion:
buildGoModule rec { pname = "matrix-dendrite"; <del> version = "0.4.1"; </del> <ins> version = "0.5.0"; </ins> src = fetchFromGitHub { owner = "matrix-org"; repo = "dendrite"; rev = "v${version}"; <del> sha256 = "sha256-F2e+peM7DBihmos/oPar36UDHkibmlzIknCjMauOph8="; </del> <ins> sha256 = "iCxfsIOZqPQjY0u2Zw3PCe0IJDczqDjcTUA3U5zXbgM="; </ins> }; <del> vendorSha256 = "sha256-M6mnFO+SInZNvtwMa02TvHIg14Ve7swlGcYfsQFioxQ="; </del> <ins> vendorSha256 = "sha256-XS1B6Nl5zGevxE1SohpoTwT/bXn5udYV5ANVFn7eTyA="; </ins> passthru.tests = { inherit (nixosTests) dendrite;