jiebi/CodeConvo huggingface dataset:
Change:
{ description = "VMware vmblock fuse mount"; documentation = [ "https://github.com/vmware/open-vm-tools/blob/master/open-vm-tools/vmblock-fuse/design.txt" ]; <del> before = [ "vmware.service" ]; wants = [ "vmware.service" ]; </del> <ins> unitConfig.ConditionVirtualization = "vmware"; </ins> what = "${open-vm-tools}/bin/vmware-vmblock-fuse"; where = "/run/vmblock-fuse"; type = "fuse";

Discussion:
The service seems to be executed before the module is loaded, causing automatic modeswitching not to be enabled. The following is seen in the : Restarting after login resolves the problem, as does adding the following to the guest's configuration: Steps to reproduce the behavior: a nix guest with X11 enabled in vmware fusion windowed mode, resize window by dragging appears stretched/blurry or centered in window (dependent on host configuration). Display resolution is automatically switched to match dimensions of window. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Maintainer information:
Hey, I'm no longer using VMware with NixOS, so would be great to find new maintainers for the vmware-guest and open-vm-tools. you've worked on vmware support recently. Would any of you be able and interested in taking over?
Change:
let versions = [ { <ins> version = "14.0.0"; lang = "en"; language = "English"; sha256 = "sha256-NzMhGQZq6o6V4UdtJxUH/yyP2s7wjTR86SRA7lW7JfI="; installer = "Mathematica_14.0.0_LINUX.sh"; } { version = "14.0.0"; lang = "en"; language = "English"; sha256 = "sha256-UrcBEg6G6nbVX++X0z0oG5JjieXL0AquAqtjzY5EBn4="; installer = "Mathematica_14.0.0_BNDL_LINUX.sh"; } { </ins> version = "13.3.1"; lang = "en"; language = "English";

Discussion:
Package name: mathematica Latest released version: 14.0.0 <!-- Search your package here: --- Current version on the unstable channel: 13.3.1 Current version on the stable/release channel: 13.3.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! --- Notify maintainers <!-- 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]:
Hello! I just submitted a PR to update Mathematica to the new version. It seems to be working fine for me. However, as another user, your tests and feedback would be really appreciated, if possible. Thanks!
Change:
''; }; <ins> extraPackages = mkOption { type = with types; listOf package; default = [ ]; example = lib.literalExample '' [ pkgs.gvisor ] ''; description = '' Extra packages to be installed in the Podman wrapper. ''; }; </ins> libpod = mkOption { default = {}; description = "Libpod configuration";

Discussion:
Describe the bug Podman's packaging isn't following the spirit of Nix, as far as I can tell. It seems to pull in a bunch of run-time executable dependencies via PATH resolution instead of build-time resolution. To Reproduce nix-shell -p podman --run podman based on the module, it looks like several run-time executables are referenced through PATH resolution instead of build-time pinning: Expected behavior Nix's build products should have stable references to their run-time dependencies whenever possible. Given podman's rootless container support, I doubly expected to give a usable podman.
Maintainer cc
Hmm im not sure how I feel about this. Podman is agnostic of container runtime for example. So it not having a path to either runc or crun is a feature. But conmon should probably be referenced by nix path yes. And utillinux too. We could perhaps default to runc runtime and let people opt to crun?
check out this PR from
I see the issue here. We could also discuss if it generally would make sense to have a build-time config feature for podman. Having strong defaults without configuration could be achieved that way for NixOS, too.
Is this expected to work without registry and policy files in ?
I would like it to, and it sounds like there is upstream work to make that possible.
This already works with rootless podman if you have the appropriate subuib/subgids set up. If is merged will work out of the box on NixOS.
Change:
createrepo_c = callPackage ../tools/package-management/createrepo_c { }; <del> cringify = callPackage ../tools/text/cringify { }; </del> cromfs = callPackage ../tools/archivers/cromfs { }; cron = callPackage ../tools/system/cron { };

Discussion:
Package name: cringify Latest released version: 0.2.0 <!-- Search your package here: --- Current version on the unstable channel: 0.1.1 Current version on the stable/release channel: 0.1.1 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers Note for maintainers: Please tag this issue in your PR. NOTE: it seems that there are no tags on the upstream GitHub repository but it is released on with a new version 0.2.0
Change:
src = fetchFromGitLab { owner = "sublime-music"; repo = pname; <del> rev = "v${version}"; sha256 = "sha256-n77mTgElwwFaX3WQL8tZzbkPwnsyQ08OW9imSOjpBlg="; </del> <ins> rev = "refs/tags/v${version}"; hash = "sha256-n77mTgElwwFaX3WQL8tZzbkPwnsyQ08OW9imSOjpBlg="; </ins> }; nativeBuildInputs = [

Discussion:
Steps to reproduce the behavior: sublime-music Just the error: Full log: Add any other context about the problem here. Built OK as of rev . I tried bisecting but too many commits required me to build multiple versions of LLVM/GHC/god knows what else. I also tried applying patch from but that didn't change the error. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
Change:
collection-plaingeneric = orig.collection-plaingeneric // { deps = orig.collection-plaingeneric.deps // { inherit (tl) xdvi; }; }; <ins> # TODO revert for texlive 2020 arara = lib.recursiveUpdate orig.arara { postUnpack = let arara_jar_fix = fetchpatch { url = "https://github.com/TeX-Live/texlive-source/commit/dbaf12f4a47dcd62bcc96346f65493fda3fec2c8.diff"; sha256 = "148knr8k6sm6fpyj31kdq85yxvzvwp1prjha3f07q24kbar2l830"; }; in '' if [ -f "$out"/scripts/arara/arara.sh ]; then cd "$out"/scripts/ patch -p4 <${arara_jar_fix} fi ''; }; </ins> }); # overrides # tl =

Discussion:
Describe the bug The build tool (part of texlive) can't be started. The Error says To Reproduce Steps to reproduce the behavior: -env -iA nixos.jdk11 Expected behavior Arara should start. Additional context The Problem is in the script (texlive-arara-) which wraps the java app. It should use to strip the suffix and start the , but does not use the required argument, so the script tries to start The Problem was fixed by upstream here: But it is still in the snapshots of texlive 2019 which nixpkgs uses. 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 system: host os: multi-user?: sandbox: version: channels(alwin): channels(root): nixpkgs: Maintainer information:
Change:
, libepoxy , libva , libvdpau <ins> , libglvnd </ins> , numactl , amf-headers , intel-media-sdk

Discussion:
Sunshine fails to run when is unavailable () Run , observe warning about failure to load , then a segfault. Adding in an override with fixes it, but I don't know the area well enough to know if this is the correct fix, I just saw this was the package the previous versions had a normal dynamic link against, while 0.21 appears to only access it via . Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Thanks! I totally missed this warning. Working for me too -- opened to resolve.
Change:
diff --git a/xpra/x11/fakeXinerama.py b/xpra/x11/fakeXinerama.py <del> index d5c1c8bb10..88c77e8142 100755 </del> <ins> index a5289e0e43..527cdf90c9 100755 </ins> --- a/xpra/x11/fakeXinerama.py +++ b/xpra/x11/fakeXinerama.py <del> @@ -22,31 +22,7 @@ fakeXinerama_config_files = [ </del> <ins> @@ -23,31 +23,7 @@ fakeXinerama_config_files = [ </ins> ] def find_libfakeXinerama():

Discussion:
Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: Current version on the stable/release channel: <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. -- Note for maintainers: Please tag this issue in your PR. Priorities Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I've got a branch that would close this issue and update xpra to 5.0.3, the UI currently works as expected and a connection over SSH is possible however I've encountered an issue running and . The error output is similar to what can be found in some other python applications. I'll look into patching this and see if I can push this further.
Change:
mobile_broadband_provider_info modemmanager-qt networkmanager-qt openconnect qca-qt5 solid ]; <ins> enableParallelBuilding = true; </ins> }

Discussion:
I am unable to configure the Cipher field of an openvpn connection in networkmanager. The dropdown is greyed out, with the text "OpenVPN cipher lookup failed". This causes problems because OpenVPN defaults to a very weak cipher (BF-CBC) that most modern vpn servers reject. On a system with set and plasma5 installed, use to create an openvpn connection. On the VPN tab of the connection editor, click Advanced..., and then click on the Security tab in the Advanced OpenVPN Properties window that pops up. The top item should read Cipher: and the dropdown will be greyed out with the error message mentioned above. ! System: NixOS 17.03 at Nix version: 1.11.8 Nixpkgs version:
temporary workaround: use to manually edit the property and add to it
Change:
<ins> { lib, stdenv, fetchurl, cmake, StormLib }: stdenv.mkDerivation { pname = "smpq"; version = "1.6"; src = fetchurl { url = "https://launchpad.net/smpq/trunk/1.6/+download/smpq_1.6.orig.tar.gz"; sha256 = "1jqq5x3b17jy66x3kkf5hs5l322dx2v14djxxrqrnqp8bn5drlmm"; }; cmakeFlags = [ "-DWITH_KDE=OFF" ]; nativeBuildInputs = [ cmake ]; buildInputs = [ StormLib ]; meta = with lib; { description = "StormLib MPQ archiving utility"; homepage = "https://launchpad.net/smpq"; license = licenses.gpl3Only; platforms = platforms.all; maintainers = with maintainers; [ aanderse karolchmist ]; }; } </ins>

Discussion:
<!-- 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: devilutionx <!-- The current version can be found easily with the same process than above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 1.2.1 desired version: 1.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. There are a number of changes in the new version, many of which make it difficult to package for nixpkgs.
Change:
ograc = callPackage ../development/tools/rust/ograc { }; rhack = callPackage ../development/tools/rust/rhack { }; <del> inherit (rustPackages) rls; </del> roogle = callPackage ../development/tools/rust/roogle { }; rustfmt = rustPackages.rustfmt; rustracer = callPackage ../development/tools/rust/racer {

Discussion:
Steps to reproduce the behavior: from , commit Add any other context about the problem here. (maintainer) () Please run and paste the result.
RLS is unmaintained upstream and removed from rust at the end of the month so I will remove it from nixpkgs.
Makes a lot of sense, I forgot about this one. Thanks for the quick answer
Change:
b43FirmwareCutter ] ++ optional (pkgs.stdenv.hostPlatform.isi686 || pkgs.stdenv.hostPlatform.isx86_64) facetimehd-firmware; }) <ins> (mkIf cfg.wirelessRegulatoryDatabase { hardware.firmware = [ pkgs.wireless-regdb ]; }) </ins> ]; }

Discussion:
Newer kernels (4.15+) can look for wireless regulatory info from (for us this is I think?), replacing the need for user-space helper like . (at least in the common case, I believe) <-- latest CRDA git adds note about this Not the same as the regdb, although I'm not sure the difference is as important for NiXOS'ers compared to other distributions. Info on internal:
I don't want to hijack the thread but my problem may be related. Recently, not sure why, I can't connect to an AP I previously could connect to so I suspect it's my machne (my phone can still access it), thus I've been looking at wifi information. I used to have a plain error then I while now it at least attempt to connect: so I wonder if it's expected on nixos ? NB: it's annoying all these errors when building kernels. do others have it too (I should probably look at hydras rather...
To get the file loaded, you need to add to . ` to see the files. Then you should see the following in : I haven't quite figured out what the best way to set the correct regulatory domain is however... short of just using .
oh great thanks ! that was not obvious. I was looking for a setting to set on boot as a kernel parameter but haven't found it yet. Some interesting read suggests one can embed the kernel in the db as well ?!
Something like this should work: Admittedly not ideal since it only works at module load time though.
Thanks Setting the following gives me the correct wifi config (check with ): Looking through the documents on: It seems to be a bit of a mess.... is an 'old' option, but NetworkManager has no support for setting the reg domain. I think having a module (?) might be a very good idea, and such an option should be to. ArchLinux deals with it by using a custom rule to run when is loaded ([source][al]). [al]: Another idea would be to a option, though that doesn't fix NetworkManager.
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 .
This should not be stale I think. Should NixOS just add to as default?
cc
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
mirror://xorg/individual/lib/libpciaccess-0.16.tar.bz2 mirror://xorg/individual/lib/libSM-1.2.3.tar.bz2 mirror://xorg/individual/lib/libWindowsWM-1.0.1.tar.bz2 <del> mirror://xorg/individual/lib/libX11-1.8.3.tar.xz </del> <ins> mirror://xorg/individual/lib/libX11-1.8.4.tar.xz </ins> mirror://xorg/individual/lib/libXau-1.0.9.tar.bz2 mirror://xorg/individual/lib/libXaw-1.0.14.tar.bz2 mirror://xorg/individual/lib/libxcb-1.14.tar.xz

Discussion:
Here's the upstream bug in libX11 () which includes a link to a merged patch (). This is a request to either patch or upgrade libX11 in nixpkgs. was the last person to upgrade xorg.libX11
recently updated it to . says it's already in . Can you give it a go an check it it works fine there?
If I read this right, our stable 22.11 shouldn't be affected, as we still have libX11 in there.
Currently in the process of building my nixos configuration against Lots of building happening
don't do that. Use the latest branch. Most binaries for that should be on
Yeah, or even better pick latest commit with enough builds at Like, .
I had assumed (wrongly) all commits would have a gone through hydra, thanks for the pointer!
No, it would be very expensive to build everything on every commit. That's the reason why big rebuilds get merged to branch.
Sadly, I'm still trying to get a full build go through. firefox, linux and other big packages need building, and it's taking a while. I had to remount my tmp to disk because I was running out etc. EDIT: finally built through by disabling quite a bunch of things. I still need to build steam because, well, that's the whole reason I'm trying this out :D
I can confirm the issue is gone with libX11 1.8.4
That's great! Thank you to the test! This issue should close automatically once PR gets merged to automatically. Should take 1-2 weeks worst case.
Just out of curiosity, how could I specify this version of libX11 in my system meanwhile it is not merged to "nixos-unstable"? I tried override but seems not working. Here my nix config:
I've had no success fully building my system by just overriding my configuration with the new version of libX11. It rebuilds too many things, and some things didn't even build correctly against the new version. By far, it was easier to pin my system to as suggested above. I had to remove (until unstable channel catches up) some software which also didn't build from staging-next to make this go through. Concretely, in my :
Yes.

It's in branch already; I'd hope that could catch up later today, but we'll see.
Oh nice! I thought this issue would auto-close when that was the case, so I missed it.
Leaving this here if others are interested in the status of this change:
All the channels have this now.
Change:
wl-mirror = callPackage ../tools/wayland/wl-mirror { }; <ins> wl-screenrec = callPackage ../tools/wayland/wl-screenrec { }; </ins> wlogout = callPackage ../tools/wayland/wlogout { }; wlopm = callPackage ../tools/wayland/wlopm { };

Discussion:
Project description offers high performance wlroots screen recording, featuring hardware encoding. Metadata homepage URL: source URL: license: gpl2+ platforms: linux
made this a couple weeks ago, not sure if it works well, but here if anyone wants to work on top of this
that's pretty cool, I'll try when I have some time
Here's the correct way of packaging this:
Oh bindgen hook is a thing?
do you want to PR it? I don't want to just yoink and submit it if you want to.
I can but I don't care if you do it, it was basically all automated anyway. Would you like me to add you as maintainer?
sure, that's fine, I'm going to put it in nixpkgs-wayland so I can keep an eye on it anyway.
Change:
systemd.services.clamav-freshclam = mkIf cfg.updater.enable { description = "ClamAV virus database updater (freshclam)"; restartTriggers = [ freshclamConfigFile ]; <ins> after = [ "network-online.target" ]; </ins> preStart = '' mkdir -m 0755 -p ${stateDir} chown ${clamavUser}:${clamavGroup} ${stateDir}

Discussion:
When enabling the services and and the system is relying on wifi managed by networkmanager, freshclam will fails to get the database signature and then clamav will refuse to start because freshclam is in failed state. When using ethernet connection, internet connection is working at boot time, before an user log in and freshclam doesn't fail. I suspect if you configure wifi without networkmanager it would also work fine because there would be no delay for connecting. Steps to reproduce the behavior: if I restart freshclam and then clamav, both services work fine until reboot. clamav and freshclam service should be running, or at least try to restart automatically. Please run and paste the result.
Looks like we didn't follow the upstream units enough:
Change:
<del> { lib, stdenv, fetchFromGitHub, autoreconfHook, pkg-config, which , gettext, libffi, libiconv, libtasn1 </del> <ins> { lib , stdenv , fetchFromGitHub , autoreconfHook , docbook-xsl-nons , gtk-doc , installShellFiles , libxslt # for xsltproc , pkg-config , which , libffi , libiconv , libintl , libtasn1 </ins> }: stdenv.mkDerivation rec { pname = "p11-kit"; <del> version = "0.24.0"; </del> <ins> version = "0.24.1"; </ins> src = fetchFromGitHub { owner = "p11-glue"; repo = pname; rev = version; <del> sha256 = "sha256-jvUzOhMvbq05SxQ+kjKQHDDMzNwo4U6nFHu3JjygJHw="; </del> <ins> hash = "sha256-1QIMEGBZsqLYU3v5ZswD5K9VcIGLBovJlC10lBHhH7c="; </ins> }; <del> outputs = [ "out" "dev"]; outputBin = "dev"; </del> <ins> outputs = [ "out" "bin" "dev"]; </ins> <del> # for cross platform builds of p11-kit, libtasn1 in nativeBuildInputs </del> <ins> # For cross platform builds of p11-kit, libtasn1 in nativeBuildInputs </ins> # provides the asn1Parser binary on the hostPlatform needed for building. # at the same time, libtasn1 in buildInputs provides the libasn1 library # to link against for the target platform. <del> # hence, libtasn1 is required in both native and build inputs. nativeBuildInputs = [ autoreconfHook pkg-config which libtasn1 ]; buildInputs = [ gettext libffi libiconv libtasn1 ]; </del> <ins> # Hence, libtasn1 is required in both native and build inputs. nativeBuildInputs = [ autoreconfHook docbook-xsl-nons gtk-doc installShellFiles libtasn1 libxslt.bin pkg-config which ]; buildInputs = [ libffi libiconv libintl libtasn1 ]; </ins> autoreconfPhase = '' NOCONFIGURE=1 ./autogen.sh ''; configureFlags = [ <ins> "--enable-doc" </ins> "--sysconfdir=/etc" "--localstatedir=/var" "--with-trust-paths=${lib.concatStringsSep ":" [

Discussion:
Describe the bug does not provide the binary, while I would expect it to. To Reproduce Steps to reproduce the behavior: in Expected behavior (and ) are installed for operator usage of p11-kit. Screenshots See step 3. Additional context It turns out the binaries are present when I do . Debian ships the binaries as part of the base non-dev package. RHEL/CentOS ship the binary as part of and have separated out into . Notify maintainers (based on git history, there is no meta.maintainers for p11-kit) Metadata Please run and paste the result. Maintainer information:
p11-kit is a library as well, so it makes sense to have headers, library, and binaries in separate outputs. I think we can fixed this by setting: in the derivation.
If we do this we need to fix it in flatpak's patch to hardcode the path to the p11-kit binary.
I marked this as stale due to inactivity. &rarr;
Any updates on this?
I marked this as stale due to inactivity. &rarr;
Change:
{ stdenv, fetchurl, pkgconfig, freetype, cmake, python }: stdenv.mkDerivation rec { <del> version = "1.3.6"; </del> <ins> version = "1.3.13"; </ins> pname = "graphite2"; src = fetchurl { url = "https://github.com/silnrsi/graphite/releases/download/" <del> + "${version}/graphite-${version}.tgz"; sha256 = "0xdg6bc02bl8yz39l5i2skczfg17q4lif0qqan0dhvk0mibpcpj7"; </del> <ins> + "${version}/graphite2-${version}.tgz"; sha256 = "01jzhwnj1c3d68dmw15jdxly0hwkmd8ja4kw755rbkykn1ly2qyx"; </ins> }; nativeBuildInputs = [ pkgconfig cmake ];

Discussion:
, (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) Scanned versions: nixos-19.09: ; nixos-unstable: . May contain false positives.
The CVEs mentioned here are fixed in 1.3.10, but newer releases also mention more security fixes, e.g. shows various security bugs being fixed. I'll upgrade to the latest one.
PR at Should be backported to 19.09 afterwards