jiebi/CodeConvo huggingface dataset:
Code change:
Upgrading fails, seemingly because the existing systemd version is newer in 21.11 than unstable. Steps to reproduce the behavior: NixOS 21.11 21.11 channel, add unstable channel NixOS upgrades from 21.11 to unstable. is the commit upgrading systemd to 249.7, cherry picks it to 21.11. Adding the flag to the invocation would also solve this issue, albeit leaving the newer EFI files in place. <!-- 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.
I think the corresponding PR is
As pointed out above by this will be fixed when staging-next gets merged ().
This issue has been mentioned on NixOS Discourse. There might be relevant details there:

Related discussion:
text: buildPythonPackage rec { pname = "youtube-search-python"; <del> version = "1.5.2"; </del> <ins> version = "1.5.3"; </ins> disabled = pythonOlder "3.6"; src = fetchPypi { inherit pname version; <del> sha256 = "33f0d58f4803b0b2badf860cd31fb83d3f7edecdd2c01dd09cd6511abbf0e6b9"; </del> <ins> sha256 = "4bc39224d1f0915692101a7739289c41173de2eb88b445aabc7be284802b7489"; </ins> }; propagatedBuildInputs = [ httpx ];
Code change:
Upgrading fails, seemingly because the existing systemd version is newer in 21.11 than unstable. Steps to reproduce the behavior: NixOS 21.11 21.11 channel, add unstable channel NixOS upgrades from 21.11 to unstable. is the commit upgrading systemd to 249.7, cherry picks it to 21.11. Adding the flag to the invocation would also solve this issue, albeit leaving the newer EFI files in place. <!-- 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.
I think the corresponding PR is
As pointed out above by this will be fixed when staging-next gets merged ().
This issue has been mentioned on NixOS Discourse. There might be relevant details there:

Related discussion:
text: buildPythonPackage rec { pname = "zope-deferredimport"; <del> version = "4.3"; </del> <ins> version = "4.3.1"; </ins> src = fetchPypi { pname = "zope.deferredimport"; inherit version; <del> sha256 = "2ddef5a7ecfff132a2dd796253366ecf9748a446e30f1a0b3a636aec9d9c05c5"; </del> <ins> sha256 = "57b2345e7b5eef47efcd4f634ff16c93e4265de3dcf325afc7315ade48d909e1"; </ins> }; propagatedBuildInputs = [ zope_proxy ];
Code change:
Upgrading fails, seemingly because the existing systemd version is newer in 21.11 than unstable. Steps to reproduce the behavior: NixOS 21.11 21.11 channel, add unstable channel NixOS upgrades from 21.11 to unstable. is the commit upgrading systemd to 249.7, cherry picks it to 21.11. Adding the flag to the invocation would also solve this issue, albeit leaving the newer EFI files in place. <!-- 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.
I think the corresponding PR is
As pointed out above by this will be fixed when staging-next gets merged ().
This issue has been mentioned on NixOS Discourse. There might be relevant details there:

Related discussion:
text: buildPythonPackage rec { pname = "zope-hookable"; <del> version = "5.0.1"; </del> <ins> version = "5.1.0"; </ins> src = fetchPypi { pname = "zope.hookable"; inherit version; <del> sha256 = "0hc82lfr7bk53nvbxvjkibkarngyrzgfk2i6bg8wshl0ly0pdl19"; </del> <ins> sha256 = "8fc3e6cd0486c6af48e3317c299def719b57538332a194e0b3bc6a772f4faa0e"; </ins> }; checkInputs = [ zope_testing ];
Code change:
However, the following input is is rejected as "*: incorrect address specification": I expected kresd to listen on fe80::1 on port 53 on the ofborg interface, as the documentation suggests should be possible. I don't mind that it is impossible, but the documentation for this option isn't correct anymore. nixos-unstable-small, rev
Well, it no longer uses systemd sockets anymore, and instead there are a few in-nix regexps that convert them. It might not be perfect. Either way, the interface spec should surely be part of the IPv6 already, i.e. &ndash; and I think that should work (the generated lua config looks OK).
Ah, I see that systemd is weird here, at least in docs. So I don't know what we'll do with it. Either shuffle it in the in-nix regexps or document as a deviation, I suppose.

Related discussion:
text: # Convert systemd-style address specification to kresd config line(s). # On Nix level we don't attempt to precisely validate the address specifications. <ins> # The optional IPv6 scope spec comes *after* port, perhaps surprisingly. </ins> mkListen = kind: addr: let <del> al_v4 = builtins.match "([0-9.]+):([0-9]+)" addr; al_v6 = builtins.match "[(.+)]:([0-9]+)" addr; </del> <ins> al_v4 = builtins.match "([0-9.]+):([0-9]+)()" addr; al_v6 = builtins.match "[(.+)]:([0-9]+)(%.*|$)" addr; </ins> al_portOnly = builtins.match "([0-9]+)" addr; al = findFirst (a: a != null) (throw "services.kresd.*: incorrect address specification '${addr}'") [ al_v4 al_v6 al_portOnly ]; <del> port = last al; addrSpec = if al_portOnly == null then "'${head al}'" else "{'::', '0.0.0.0'}"; </del> <ins> port = elemAt al 1; addrSpec = if al_portOnly == null then "'${head al}${elemAt al 2}'" else "{'::', '0.0.0.0'}"; </ins> in # freebind is set for compatibility with earlier kresd services; # it could be configurable, for example. ''
Code change:
However, the following input is is rejected as "*: incorrect address specification": I expected kresd to listen on fe80::1 on port 53 on the ofborg interface, as the documentation suggests should be possible. I don't mind that it is impossible, but the documentation for this option isn't correct anymore. nixos-unstable-small, rev
Well, it no longer uses systemd sockets anymore, and instead there are a few in-nix regexps that convert them. It might not be perfect. Either way, the interface spec should surely be part of the IPv6 already, i.e. &ndash; and I think that should work (the generated lua config looks OK).
Ah, I see that systemd is weird here, at least in docs. So I don't know what we'll do with it. Either shuffle it in the in-nix regexps or document as a deviation, I suppose.

Related discussion:
text: <del> { lib, stdenv, fetchurl, fetchpatch </del> <ins> { lib, stdenv, fetchurl </ins> # native deps. , runCommand, pkg-config, meson, ninja, makeWrapper # build+runtime deps.
Code change:
However, the following input is is rejected as "*: incorrect address specification": I expected kresd to listen on fe80::1 on port 53 on the ofborg interface, as the documentation suggests should be possible. I don't mind that it is impossible, but the documentation for this option isn't correct anymore. nixos-unstable-small, rev
Well, it no longer uses systemd sockets anymore, and instead there are a few in-nix regexps that convert them. It might not be perfect. Either way, the interface spec should surely be part of the IPv6 already, i.e. &ndash; and I think that should work (the generated lua config looks OK).
Ah, I see that systemd is weird here, at least in docs. So I don't know what we'll do with it. Either shuffle it in the in-nix regexps or document as a deviation, I suppose.

Related discussion:
text: unwrapped = stdenv.mkDerivation rec { pname = "knot-resolver"; <del> version = "5.4.3"; </del> <ins> version = "5.4.4"; </ins> src = fetchurl { url = "https://secure.nic.cz/files/knot-resolver/${pname}-${version}.tar.xz"; <del> sha256 = "488729eb93190336b6bca10de0d78ecb7919f77fcab105debc0a644aa7d0a506"; </del> <ins> sha256 = "588964319e943679d391cc9c886d40ef858ecd9b33ae160023b4e2b5182b2cea"; </ins> }; outputs = [ "out" "dev" ]; <del> patches = [ (fetchpatch { # https://gitlab.nic.cz/knot/knot-resolver/-/merge_requests/1237 name = "console.aws.amazon.com-fix.patch"; url = "https://gitlab.nic.cz/knot/knot-resolver/-/commit/f4dabfbec9273703.diff"; sha256 = "3J+FDwNQ6CqIGo9pSzhrQZlHX99vXFDpPOBpwpCnOxs="; }) ]; </del> # Path fixups for the NixOS service. postPatch = '' patch meson.build <<EOF
Code change:
I get the following collision: What I don't understand is why this collision is happening in the first place? I'm installing this package into an empty profile!
That's a multiple-output problem. The derivation creates two of them, both containing the file. When installing into user profiles, currently the semantics is that all outputs are installed, so this creates the collision.
Vladimír Čunát writes: What's the reason for these semantics? I would expect only 'out' to get installed by default.
Well, as for build inputs, we normally want all to be available, because you need include, lib and possibly others. should know details. It hasn't been used much yet, so I suppose we still have to figure out how to do these best (and have the most usual setup as the default).
What I haven't figured out in these cases: why installing attempts to install both and .
I am getting this same error message. Fresh install of Nix 16. Could it have regressed? This happens when I run nix-env -iA nixos.openjdk but not when I dun nix-env -iA Though those both say they point to openjdk-8

Related discussion:
text: stdenv.mkDerivation rec { name = "singularity-${version}"; <del> version = "2.5.1"; </del> <ins> version = "2.5.2"; </ins> enableParallelBuilding = true;
Code change:
I get the following collision: What I don't understand is why this collision is happening in the first place? I'm installing this package into an empty profile!
That's a multiple-output problem. The derivation creates two of them, both containing the file. When installing into user profiles, currently the semantics is that all outputs are installed, so this creates the collision.
Vladimír Čunát writes: What's the reason for these semantics? I would expect only 'out' to get installed by default.
Well, as for build inputs, we normally want all to be available, because you need include, lib and possibly others. should know details. It hasn't been used much yet, so I suppose we still have to figure out how to do these best (and have the most usual setup as the default).
What I haven't figured out in these cases: why installing attempts to install both and .
I am getting this same error message. Fresh install of Nix 16. Could it have regressed? This happens when I run nix-env -iA nixos.openjdk but not when I dun nix-env -iA Though those both say they point to openjdk-8

Related discussion:
text: owner = "singularityware"; repo = "singularity"; rev = version; <del> sha256 = "1i029qs6dfpyirhbdz0nrx2sh5fddysk4wqkjqj5m60kxs4x8a3d"; </del> <ins> sha256 = "09wv8xagr5fjfhra5vyig0f1frfp97g99baqkh4avbzpg296q933"; </ins> }; nativeBuildInputs = [ autoreconfHook makeWrapper ];
Code change:
I think it should be marked as broken to avoid frustrating other people. This package is impossible to build without more than 4G address space due to linker memory exhaustion. It can be built only on 64-bit hosts (the same as Firefox). And that permanently breaks Gnome 3 on i686. It was possible to build it in the past using local modifications, though.
what modifications did you used in the past?
Only very few to some Gnome dependencies just to build Gnome itself, like . AFAIK, there were no modifications at all to webkitgtk. It just required huge swap and to free as much RAM as possible, e.g. running nix-build with only one thread. Last December I've tried to install NixOS 21.11 and it was impossible to build because of a linker exhausting all memory address space. I've tried both ld and gold. My investigations into other Linux distros revealed that they used cross-compiling tricks to build 32-bit webkitgtk on 64-bit host. I've spent a week before giving up. Right now I'm using only x86_64 arch because of that issue. I suppose it's impossible to fix on native 32-bit host just like Firefox.
I tried different configurations and was able to complete the building without any memory issue by setting separateDebugInfo to false.
I will now try to build firefox. Edit: it is markerd as broken on 32 bits.
Interesting. Thanks for trying this. It was very painful to experiment with different configurations as it required too many hours to build on my computer. AFAIK, Firefox had a different issue which didn't involve linker. It was probably a compiler. Do you think it's sustainable? I mean, will it still be possible to build next year? Because a year ago it didn't require that trick either. I'm quite pessimistic about browsers on 32-bit architecture as is already evident from Firefox :( Also, there were similar troubles with Haskell (Pandoc) and Qt. Considering that Hydra doesn't have most 32-bit software in a binary cache and that it's often required to set in order to build it, it's really a huge pain to install NixOS on i686 arch.
works great for me. Should we add a conditional for this derivation?

Related discussion:
text: outputs = [ "out" "dev" "devdoc" ]; <del> separateDebugInfo = stdenv.isLinux; </del> <ins> # https://github.com/NixOS/nixpkgs/issues/153528 # Can't be linked within a 4GB address space. separateDebugInfo = stdenv.isLinux && !stdenv.is32bit; </ins> src = fetchurl { url = "https://webkitgtk.org/releases/webkitgtk-${finalAttrs.version}.tar.xz";
Code change:
When attempting to add a Vim plugin, fails. It updates without error. I believe previous developers have this feature enabled in their system/user Nix configuration.

Related discussion:
text: def get_current_plugins(editor: Editor) -> List[Plugin]: with CleanEnvironment(): <del> cmd = ["nix", "eval", "--impure", "--json", "--expr", editor.get_plugins] </del> <ins> cmd = ["nix", "eval", "--extra-experimental-features", "nix-command", "--impure", "--json", "--expr", editor.get_plugins] </ins> log.debug("Running command %s", cmd) out = subprocess.check_output(cmd) data = json.loads(out)
Code change:
A follow up to It seems like is not getting updated when tmux sessions begin/end. Relevant links: Steps to reproduce the behavior: and note the results. a different shell, open a new tmux session: exiting tmux, run again and note that the results are the same. Tmux user sessions to show up in , , and , as is custom in other OSes. n/a n/a <!-- 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.

Related discussion:
text: description = lib.mdDoc "List of plugins to install."; example = lib.literalExpression "[ pkgs.tmuxPlugins.nord ]"; }; <ins> withUtempter = mkOption { description = lib.mdDoc '' Whether to enable libutempter for tmux. This is required so that tmux can write to /var/run/utmp (which can be queried with `who` to display currently connected user sessions). Note, this will add a guid wrapper for the group utmp! ''; default = true; type = types.bool; }; </ins> }; };
Code change:
A follow up to It seems like is not getting updated when tmux sessions begin/end. Relevant links: Steps to reproduce the behavior: and note the results. a different shell, open a new tmux session: exiting tmux, run again and note that the results are the same. Tmux user sessions to show up in , , and , as is custom in other OSes. n/a n/a <!-- 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.

Related discussion:
text: TMUX_TMPDIR = lib.optional cfg.secureSocket ''''${XDG_RUNTIME_DIR:-"/run/user/$(id -u)"}''; }; }; <ins> security.wrappers = mkIf cfg.withUtempter { utempter = { source = "${pkgs.libutempter}/lib/utempter/utempter"; owner = "root"; group = "utmp"; setuid = false; setgid = true; }; }; </ins> }; imports = [
Code change:
A follow up to It seems like is not getting updated when tmux sessions begin/end. Relevant links: Steps to reproduce the behavior: and note the results. a different shell, open a new tmux session: exiting tmux, run again and note that the results are the same. Tmux user sessions to show up in , , and , as is custom in other OSes. n/a n/a <!-- 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.

Related discussion:
text: stdenv.mkDerivation rec { pname = "libutempter"; <del> version = "1.1.6"; </del> <ins> version = "1.2.1"; </ins> src = fetchurl { <del> url = "mirror://ubuntu/pool/main/libu/libutempter/libutempter_${version}.orig.tar.bz2"; sha256 = "15y3xbgznjxnfmix4xg3bwmqdvghdw7slbhazb0ybmyf65gmd65q"; </del> <ins> url = "http://ftp.altlinux.org/pub/people/ldv/utempter/libutempter-${version}.tar.gz"; sha256 = "sha256-ln/vNy85HeUBhDrYdXDGz12r2WUfAPF4MJD7wSsqNMs="; </ins> }; buildInputs = [ glib ]; patches = [ ./exec_path.patch ]; <ins> patchFlags = [ "-p2" ]; </ins> prePatch = '' substituteInPlace Makefile --replace 2711 0711 '';
Code change:
A follow up to It seems like is not getting updated when tmux sessions begin/end. Relevant links: Steps to reproduce the behavior: and note the results. a different shell, open a new tmux session: exiting tmux, run again and note that the results are the same. Tmux user sessions to show up in , , and , as is custom in other OSes. n/a n/a <!-- 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.

Related discussion:
text: ]; meta = { <ins> homepage = "https://github.com/altlinux/libutempter"; </ins> description = "Interface for terminal emulators such as screen and xterm to record user sessions to utmp and wtmp files"; longDescription = '' The bundled utempter binary must be able to run as a user belonging to group utmp.
Code change:
A follow up to It seems like is not getting updated when tmux sessions begin/end. Relevant links: Steps to reproduce the behavior: and note the results. a different shell, open a new tmux session: exiting tmux, run again and note that the results are the same. Tmux user sessions to show up in , , and , as is custom in other OSes. n/a n/a <!-- 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.

Related discussion:
text: <del> diff -ur libutempter-1.1.6/iface.c libutempter-1.1.6.patched/iface.c --- libutempter-1.1.6/iface.c	2010-11-04 18:14:53.000000000 +0100 +++ libutempter-1.1.6.patched/iface.c	2018-06-06 15:09:11.417755549 +0200 @@ -60,9 +60,9 @@ </del> <ins> diff --git a/libutempter/iface.c b/libutempter/iface.c index 37c74a8..6f44c9a 100644 --- a/libutempter/iface.c +++ b/libutempter/iface.c @@ -43,7 +43,7 @@ __result; })) #endif -#define UTEMPTER_DEFAULT_PATHNAME	LIBEXECDIR "/utempter/utempter" +#define UTEMPTER_DEFAULT_PATHNAME	"utempter" static const char *utempter_pathname; static int saved_fd = -1; @@ -57,8 +57,8 @@ do_child(int master_fd, const char *path, char *const *argv) </ins> _exit(EXIT_FAILURE); } -	execv(path, argv); <ins> -	print_dbg("execv: %s", strerror(errno)); </ins> +	execvp(path, argv); <del> #ifdef	UTEMPTER_DEBUG -	fprintf(stderr, "libutempter: execv: %sn", strerror(errno)); +	fprintf(stderr, "libutempter: execvp: %sn", strerror(errno)); #endif </del> <ins> +	print_dbg("execvp: %s", strerror(errno)); </ins> <del> while (EACCES == errno) @@ -79,7 +79,7 @@ </del> <ins> while (EACCES == errno) { /* try saved group ID */ @@ -73,7 +73,7 @@ do_child(int master_fd, const char *path, char *const *argv) </ins> if (setgid(sgid)) break;
Code change:
A follow up to It seems like is not getting updated when tmux sessions begin/end. Relevant links: Steps to reproduce the behavior: and note the results. a different shell, open a new tmux session: exiting tmux, run again and note that the results are the same. Tmux user sessions to show up in , , and , as is custom in other OSes. n/a n/a <!-- 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.

Related discussion:
text: +		(void) execvp(path, argv); break; } <del> Only in libutempter-1.1.6.patched: result </del>
Code change:
A follow up to It seems like is not getting updated when tmux sessions begin/end. Relevant links: Steps to reproduce the behavior: and note the results. a different shell, open a new tmux session: exiting tmux, run again and note that the results are the same. Tmux user sessions to show up in , , and , as is custom in other OSes. n/a n/a <!-- 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.

Related discussion:
text: , pkg-config , withSystemd ? stdenv.isLinux && !stdenv.hostPlatform.isStatic, systemd , utf8proc <ins> , withUtempter ? stdenv.isLinux && !stdenv.hostPlatform.isMusl, libutempter </ins> }: let
Code change:
A follow up to It seems like is not getting updated when tmux sessions begin/end. Relevant links: Steps to reproduce the behavior: and note the results. a different shell, open a new tmux session: exiting tmux, run again and note that the results are the same. Tmux user sessions to show up in , , and , as is custom in other OSes. n/a n/a <!-- 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.

Related discussion:
text: ncurses libevent ] ++ lib.optionals withSystemd [ systemd ] <del> ++ lib.optionals stdenv.isDarwin [ utf8proc ]; </del> <ins> ++ lib.optionals stdenv.isDarwin [ utf8proc ] ++ lib.optionals withUtempter [ libutempter ]; </ins> configureFlags = [ "--sysconfdir=/etc" "--localstatedir=/var" ] ++ lib.optionals withSystemd [ "--enable-systemd" ] <ins> ++ lib.optionals withUtempter [ "--enable-utempter" ] </ins> ++ lib.optionals stdenv.isDarwin [ "--enable-utf8proc" ]; enableParallelBuilding = true;
Code change:
A follow up to It seems like is not getting updated when tmux sessions begin/end. Relevant links: Steps to reproduce the behavior: and note the results. a different shell, open a new tmux session: exiting tmux, run again and note that the results are the same. Tmux user sessions to show up in , , and , as is custom in other OSes. n/a n/a <!-- 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.

Related discussion:
text: patches = [ ./ssh_path.patch ./mosh-client_path.patch <del> ./utempter_path.patch </del> # Fix build with bash-completion 2.10 ./bash_completion_datadir.patch ];
Code change:
A follow up to It seems like is not getting updated when tmux sessions begin/end. Relevant links: Steps to reproduce the behavior: and note the results. a different shell, open a new tmux session: exiting tmux, run again and note that the results are the same. Tmux user sessions to show up in , , and , as is custom in other OSes. n/a n/a <!-- 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.

Related discussion:
text: <del> diff -ur mosh-1.3.2/src/frontend/mosh-server.cc mosh-1.3.2.patched/src/frontend/mosh-server.cc --- mosh-1.3.2/src/frontend/mosh-server.cc	2017-07-22 23:14:53.000000000 +0200 +++ mosh-1.3.2.patched/src/frontend/mosh-server.cc	2018-06-06 10:45:50.725352804 +0200 @@ -351,6 +351,10 @@ } } +#ifdef HAVE_UTEMPTER +    utempter_set_helper( "utempter" ); +#endif + try { return run_server( desired_ip, desired_port, command_path, command_argv, colors, verbose, with_motd ); } catch ( const Network::NetworkException &e ) { </del>
Code change:
I'm trying to start the service fusionInventory but it fails with the same error as , running the system command in a terminal also trigger the issue. Steps to reproduce the behavior: part in , this is the minimum to have fusioNInventory to start, the server doesn't need to be real, it fails before trying that. I have a real setup that also fail with the same error, I tried this one to be sure it's reproducible by everyone. note that this command line without works: the service is running fine
Solved in after debug with upstream

Related discussion:
text: cp -r bin $out cp -r lib $out <ins> cp -r share $out </ins> for cur in $out/bin/*; do if [ -x "$cur" ]; then