jiebi/CodeConvo huggingface dataset:
Change:
"hash": "sha256:1hbva5vsfi48h82ll4kmhzm5hxp7340bj2smwgvjikam26icaj54" }, "6.5": { <del> "version": "6.5.4", "hash": "sha256:0s8nzd8yaq06bq8byk7aakbk95gh0rhlif26h1biw94v48anrxxx" </del> <ins> "version": "6.5.5", "hash": "sha256:15gg8sb6cfgk1afwj7fl7mj4nkj14w43vzwvw0qsg3nzyxwh7wcc" </ins> }, "6.4": { "version": "6.4.16", "hash": "sha256:0zgj1z97jyx7wf12zrnlcp0mj4cl43ais9qsy6dh1jwylf2fq9ln" }, "6.1": { <del> "version": "6.1.54", "hash": "sha256:09sfrq2l8f777mx2n9mhb6bgz1064bl04921byqnmk87si31w653" </del> <ins> "version": "6.1.55", "hash": "sha256:1h0mzx52q9pvdv7rhnvb8g68i7bnlc9rf8gy9qn4alsxq4g28zm8" </ins> }, "5.15": { <del> "version": "5.15.132", "hash": "sha256:1b0qjsaqjw2rk86shmmrj2aasblkn27acjmc761vnjg7sv2baxs1" </del> <ins> "version": "5.15.133", "hash": "sha256:1paxzzcagc7s8i491zjny43rxhfamafyly438kj8hyw96iwmx17g" </ins> }, "5.10": { <del> "version": "5.10.195", "hash": "sha256:0n4vg2i9sq89wnz85arlyvwysh9s83cgzs5bk2wh98bivi5fwfs1" </del> <ins> "version": "5.10.197", "hash": "sha256:1awkm7lln5gf6kld9z5h4mg39bd778jsdswwlwb7iv7bn03lafhq" </ins> }, "5.4": { <del> "version": "5.4.256", "hash": "sha256:0fim5q9xakwnjfg48bpsic9r2r8dvrjlalqqkm9vh1rml9mhi967" </del> <ins> "version": "5.4.257", "hash": "sha256:1w1x91slzg9ggakqhyxnmvz77v2cwfk8bz0knrpgz9qya9q5jxrf" </ins> }, "4.19": { <del> "version": "4.19.294", "hash": "sha256:03x0xsb8a369zdr81hg6xdl5n5v48k6iwnhj6r29725777lvvbfc" </del> <ins> "version": "4.19.295", "hash": "sha256:1b1qslpk1kka7nxam48s22xsqd9qmp716hmibgfsjxl5y3jc4cmp" </ins> }, "4.14": { <del> "version": "4.14.325", "hash": "sha256:117p1mdha57f6d3kdwac9jrbmib7g77q4xhir8ghl6fmrs1f2sav" </del> <ins> "version": "4.14.326", "hash": "sha256:0y0lvzidw775mgx211wnc1c6223iqv8amz5y9jkz9h7l3l7y8p2m" </ins> } }

Discussion:
Mounting NFS volumes stopped working without configuration change other than updates. Steps to reproduce the behavior: updated system as of 2023-09-18 from stable to mount a nfs volume Get the error The volume to be mounted Please run and paste the result.
I am having the same issue, with very similar messages: I am running: It happened between ..., the only suspicious changes are kernel changes. In particular, both 6.5.2-6.5.3 and 6.1.52-6.1.53 include the patch "vfs, security: Fix automount superblock LSM init problem, preventing NFS sb sharing" which I think seems suspicious, but I don't know enough to dig any further. Any help would be appreciated.
Gentoo . In that bug, someone bisected the kernel and identified the patch that mentioned as the culprit. This link to a kernel patch that fixes the issue was also posted and verified to work:
I hit this as well, hoping it gets fixed promptly. For now I've worked around it by using an older stable kernel on affected clients:
I am guessing it will be fixed in upstream soonish, will it be fixed in NixOS like the gentoo folks did? For now, I have confirmed the above patch works on my configuration: nevivurn/nixos-config
The patch worked for me, didn't know it was that easy to apply one
cc
This patch works great! This issue still appears in , but the patch still seems to works if applied to that version.
Change:
meta = with lib; { description = "Reimplementation of the DFT-D3 program"; <del> license = with licenses; [lgpl3Only gpl3Only]; </del> <ins> license = with licenses; [ lgpl3Only gpl3Only ]; </ins> homepage = "https://github.com/dftd3/simple-dftd3"; platforms = [ "x86_64-linux" ]; maintainers = [ maintainers.sheepforce ];

Discussion:
tblite is unusable in python at the moment, failing with I think this is due to incorrect pkgconfig setups - look at which is correct and outputs vs which is missing the trailing Which results in a pkgconfig of Steps to reproduce the behavior: a nix environment with the python interpreter, run failure A clear and concise description of what you expected to happen. If applicable, add screenshots to help explain your problem. Add any other context about the problem here. Please run and paste the result.
i'm having the exact same issue as well :'(
Change:
buildGo112Module = throw "buildGo112Module has been removed"; # added 2020-04-26 bundler_HEAD = bundler; # added 2015-11-15 caddy1 = throw "caddy 1.x has been removed from nixpkgs, as it's unmaintained: https://github.com/caddyserver/caddy/blob/master/.github/SECURITY.md#supported-versions"; # added 2020-10-02 <ins> calibre-py2 = throw "calibre-py2 has been removed from nixpkgs, as calibre has upgraded to python 3. Please use calibre as replacement."; # added 2021-01-12 calibre-py3 = throw "calibre-py3 has been removed from nixpkgs, as calibre's default python version is now 3. Please use calibre as replacement."; # added 2021-01-12 </ins> cantarell_fonts = cantarell-fonts; # added 2018-03-03 cargo-tree = throw "cargo-tree has been removed, use the builtin `cargo tree` command instead."; # added 2020-08-20 casperjs = throw "casperjs has been removed, it was abandoned by upstream and broken.";

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: calibre <!-- 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: 4.23.0 desired version: 5.6 <!-- 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.
Change:
<del> { config, pkgs ,lib ,... }: </del> <ins> { config, pkgs, lib, ... }: </ins> with lib;

Discussion:
When in a KDE wayland session with pipewire enabled nor firefox nor OBS' pipewire screen sharing does not show. Weirdly only Spectacle works for screen capture. Steps to reproduce the behavior: KDE plasma session and fail to screen capture ! suggest "compiling in an environment with pipewire" but adding pipewire to does not fix this system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
Does it work in chrome?
Sharing the full screen no, but individual windows can be shared without problems
Have you checked the build log? What is the output of ?
So the reason it's not making any effect is because it already includes pipewire in its buildDependencies.
Neither patching works
And patching wayland-protocols straight up gives infinite recursion
please add this to the waayland board
So here is what I've found following
Here my thoughts: is suspect,especially after also look suspect
Suggest that the screencast plugin is loaded
The seems to originate from
90% sure does not get reached.
I've opened a bug in kde
<delSemms like whatever qml is needed for screencast is not included </delNope that is normal
Overall it seems like the screen selection window does not get displayed for whatever reason despite
This seems to be the same problem that was previously discussed in and related issues? Guess it makes sense to continue here since that issue is pretty cluttered at this point + mostly sway-related.
Change:
<ins> diff --git a/go.mod b/go.mod index 2d396a4..c4fea4b 100644 --- a/go.mod +++ b/go.mod @@ -1,14 +1,19 @@ module gitlab.com/WhyNotHugo/darkman -go 1.16 +go 1.18 require ( github.com/adrg/xdg v0.3.3 github.com/godbus/dbus/v5 v5.0.4 -	github.com/kr/pretty v0.2.0 // indirect github.com/rxwycdh/rxhash v0.0.0-20230131062142-10b7a38b400d github.com/sj14/astral v0.1.2 -	github.com/spf13/cobra v1.7.0 // indirect -	gopkg.in/check.v1 v1.0.0-20190902080502-41f04d3bba15 // indirect +	github.com/spf13/cobra v1.7.0 gopkg.in/yaml.v3 v3.0.1 ) + +require ( +	github.com/inconshreveable/mousetrap v1.1.0 // indirect +	github.com/kr/pretty v0.2.0 // indirect +	github.com/spf13/pflag v1.0.5 // indirect +	gopkg.in/check.v1 v1.0.0-20190902080502-41f04d3bba15 // indirect +) </ins>

Discussion:
Package name: darkman Latest released version: 2.0.1 Current version on the unstable channel: 1.5.4 Current version on the stable/release channel: 1.5.4 Notify maintainers Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Updating this package will resolve nix-community/home-manager too.
I've had a go at updating this but failed at the same point as . I don't know enough about nix or go to take it any further right now though. The part of the go language framework seems to be using a really old version of go (1.16) to try to build the package, which is not able to compile the code:
Change:
homepage    = http://llvm.org/; license     = stdenv.lib.licenses.bsd3; platforms   = stdenv.lib.platforms.all; <del> broken      = true; </del> }; }

Discussion:
Trying to build clang35 with nixpkgs HEAD () fails. The build log:
Is this still a problem?
Never mind, it has been marked as broken. You guys appear to be the clang experts. Do you have time to look into this?
That's a pretty strange compilation failure. Seems like it would be easy to patch if it came down to that. I'm not sure why that would be happening though.
Would it be fine to merge that patch? It's really ugly but if you aren't developing visibility isn't too important.
There is also the option that the old version of clang has been marked broken for a couple of months so it might be worth dropping it? I'm not sure if there is large value to fixing the old release.
I'm generally in favor of ditching the old in favor of the new if we can get away with it. You have my approval, for what it's worth. It seems fair to drop support for it, but if someone wants it enough to submit a working build for it, then that's fine we could accept that.
I'll see if wants to fix it otherwise I will create a PR to drop it this week.
Clang 3.5 is required for running the Terra compiler, so removing Clang 3.5 does have wider ranging repercussions. I'd be happy for my horrible patch to be merged (I can submit a PR if you want). I've not had any problems personally using this version of Clang. I'm not invested enough to implement a proper fix though :)
Would you be prepared to accept that patch? Or what would your preferred course of action be?
I'd be happy to accept it but I'm not an official collaborator of nixpkgs. On Tue, Aug 2, 2016, 2:05 PM Kevin Cox wrote:
Well if you open a PR there will be at least 2 :+1:s so I would go for it. On Tue, Aug 2, 2016, 18:43 Andrew Kelley wrote:
Interesting. I wonder why they're stuck on such an old version. I wonder if there were JIT regressions.
I've opened the PR
Change:
uid = ids.uids.root; description = "System administrator"; home = "/root"; <del> shell = cfg.defaultUserShell; </del> <ins> shell = mkDefault cfg.defaultUserShell; </ins> group = "root"; extraGroups = [ "grsecurity" ]; hashedPassword = mkDefault config.security.initialRootPassword;

Discussion:
set inside and it fails with something like this: also, I tried inside a container to minimize the chance of conflicts (saved to and I am using reContain because it was easier for me at time of debugging) and run it with
Try
I smell possible fix, making pull request...
Is this really a bug? It's just defined elsewhere, so override looks like a sane option.  Matej Cotman wrote: Version: GnuPG v1.4.11 (GNU/Linux) mQENBFEY1PEBCADPOfERF2wo4qeoq9L1m2z4pKfWqNd4B6BsoFUWPNd7BXmY+9JG jJddSkmYobWec7XjAFTBL0Xbttt+rK9SIED2dCOmU1FYMQElhGlM3PNA3kaiQFeV ijgH318GCfZzDd0dWa5TN/IshVeWXwgngsIEmZTVf1VSeb3eO3B8Fxe3zsSLUq0b 71MmU5eLVP9pMkm5V5BTYp+lV70FIekKygkKq+uTDo1csWUatbs4Qvgv37Bymy2t oTwOBXGoinQk5N/6asR1jWs3vKv0L0SruoZy/kEG/jXb4l2OZUP85EVMganYKouE OchVmcmhBdWV+t3HK4r2ATfyEcMRzvzSflA1ABEBAAG0Jkpha2EgSHVkb2tsaW4g PGpha2FodWRva2xpbkBnbWFpbC5jb20+iQE+BBMBAgAoBQJRGNTxAhsDBQkB4TOA BgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRD6Zxi5hZclKnXNCACLOKa8abQp

eTWv9SXUwC7LVM5pP2mXcgn+Ipqr6YWBdLx4Iij0YlvUok9VeKvwTpUlT+cx++o3 wCM3AYrUyJE+zrtw49lInUmutz9seqJLU895oq+D+UuGoORrLBpEZrYR5f83uUmQ E3Z1ZmWrNGXYtITWDtVZD/KauMF2nkPcmy/XaYXhd4WHD81DGNlKtGAHig6A3Phc 8Mr0A4yLDeRQJm8lCFEsxMJUNTupgY+ybbsMfVGx1gQvvGOTioV8CLCoRchUCCcm YPArFg40KzIDSNjwdo9EVZDnlPx1hbOppfQydxP+JVnZsqoYmVY4UhIWi/NfOl3V UMjl338INW1zuQENBFEY1PEBCADRSIfelOMjaTH7IfpMFFUc5Gys//njFnW9QAUg wyfs2AFxUp6vKQ7nxXQiJXVhKTwe9iqo+oGxaHp4AeTjC7vXsfMuF5g5lfttbAo3 YEobEe6OG5so41nbwan6SyeIIQ2AmQqJBw8TKKMSec2qUN0Pw7iZRs0o9uJM/obG DPsAsMOQgNLxJyMCP7X2jBtDXxkMFVHMmk50Tl3h3Fi9qWuNxgTXjs0tUvKkXiu2 Pco952jnm7HpCIKBek2pqR/UJXXb5qxy5G6Lc0qaMWZ5GKnSMTJmTY6Xl44EnaLK zh0rqgF9qpoWck470ZbiGASMtB008hy2l0cyxUfvDaS3tY4hABEBAAGJASUEGAEC

AA8FAlEY1PECGwwFCQHhM4AACgkQ+mcYuYWXJSoT6AgAkvzvC0EGmeCR3cn9O3Gf yG00Kqk9/1gJvlphis7AAce8iUgU+4xd94Vp0u8rghpdy88xKN5lF1W2YZQmmBaf AVe6b7TOg6kxc3GKkVsWDxNyQKkpB46BwefIGaSljH7502X9aEWosrqWyJJNYCtt QDit4BysX0Ww3Ka5Rx6ZFhC9ybPKoW2i8JwpyBaXDt7R2k+PC/ClBf9qzL+sb2es zh/zCMVKNdm8KUITHU/5lgn2qZpUFZwiASPCMGGFP9u8g6UKeUTYTPD+GWaHIW63 RAgNIAffxx0M1r3P/2ipkAdI3NX/1iBKDQNG8Odsf+BswFKrNCnyUDdLPvJAhODS gw== =tmrm -----END PGP PUBLIC KEY BLOCK-----
I had a the same issue but that was because I was setting the home of root: Don't set the home of root. you can set however. Commented because this is showing up in google.
Change:
# This may also need msbuild (instead of xbuild) which isn't in nixpkgs # See -> https://github.com/NixOS/nixpkgs/issues/29817 src = fetchurl { <del> url = "https://github.com/MediaBrowser/Emby.Releases/releases/download/${version}/embyserver-mono_${version}.zip"; sha256 = "12f9skvnr9qxnrvr3q014yggfwvkpjk0ynbgf0fwk56h4kal7fx8"; </del> <ins> url = "https://github.com/MediaBrowser/Emby.Releases/releases/download/${version}/embyserver-netcore_${version}.zip"; sha256 = "0311af3q813cx0ykbdk9vkmnyqi2l8rx66jnvdkw927q6invnnpj"; </ins> }; buildInputs = [

Discussion:
The latest version of Emby is only available in the dotnet core version : I can't find any documentation on how to package a dotnet app in NixOS. Help would be much appreciated ! I found that the dotnet-sdk package is providing the dotnet executable, is it a simple swap between mono and this ?
I am interested in using dotnet with nixpkgs. The dotnet-sdk is up to date and can build and run applications but there is also , which is just the runtime. It might be a good practice to use dotnet-sdk for building but build the wrapper with coreclr. This should result in smaller runtime closures. There is also which is actually using mono.
Change:
# Dictionaries we want dicts = f aspellDicts; <del> # A tree containing the dictionaries dictEnv = symlinkJoin { name = "aspell-dicts"; paths = dicts; }; in runCommand "aspell-env" { </del> <ins> in buildEnv { name = "aspell-env"; </ins> buildInputs = [ makeWrapper ]; <del> } '' # Construct wrappers in /bin mkdir -p $out/bin pushd "${aspell}/bin" for prg in *; do if [ -f "$prg" ]; then makeWrapper "${aspell}/bin/$prg" "$out/bin/$prg" --set ASPELL_CONF "dict-dir ${dictEnv}/lib/aspell" fi done popd '' </del> <ins> paths = [ aspell ] ++ dicts; postBuild = '' # Construct wrappers in /bin unlink "$out/bin" mkdir -p "$out/bin" pushd "${aspell}/bin" for prg in *; do if [ -f "$prg" ]; then makeWrapper "${aspell}/bin/$prg" "$out/bin/$prg" --set ASPELL_CONF "dict-dir $out/lib/aspell" fi done popd ''; } </ins>  No newline at end of file

Discussion:
Enchant cannot find any aspell dictionaries when aspellWithDicts was used to install aspell. The command on its own works fine. Put the following into your : succeeds, i.e. does not output any errors outputs: "Couldn't create a dictionary for en_US.UTF-8"; however, I expected it to succeed just like aspell System: NixOS: 17.09beta581. (Hummingbird) Nix version: 1.11.14 Nixpkgs version: 17.09beta581. Sandboxing enabled: false
I looked at the aspell wrapper: With the system-wide export of ASPELL_CONF, enchant works fine: So the problem seems to be that the wrapper only fixes the issue for the binary, but not for any other application that uses the aspell API directly.
Could you check ?
I'd love to help you, but I have just started using NixOS two days ago and do not yet know how to integrate your proposed change into my system. I downloaded your new to and the following to my : But gave me: error: value is a function while a set was expected, at Line 64 is: If you could show me how to do this most efficiently (possibly without needing to clone nixpkgs or rebuilding my whole system ^^), I would be most grateful! :)
you can pass with your original config; no need to import.
Thank you for your assistance, this worked perfectly. I have commented on . Out of curiosity, is it possible to integrate single packages like I wanted to do with in ?
You can indeed import Nix expressions, however, if you want to import packages from say another Nixpkgs version/tree, then you best import that Nixpkgs, and then the correct attribute from that set. Fixed with so closing.
Change:
}; in newPython.pkgs.buildPythonApplication rec { <del> version = "1.25.0"; </del> <ins> version = "1.27.0"; </ins> pname = "conan"; <del> src = newPython.pkgs.fetchPypi { inherit pname version; sha256 = "1wgmx6s4h5m6zixb3wlaicy56rsqcy2srzmvii80xdx9g5wvi9pv"; </del> <ins> src = fetchFromGitHub { owner = "conan-io"; repo = "conan"; rev = version; sha256 = "0ncqs1p4g23fmzgdmwppgxr8w275h38hgjdzs456cgivz8xs9rjl"; </ins> }; propagatedBuildInputs = with newPython.pkgs; [

Discussion:
Describe the bug Conan fails to build due to the fact that six was updated in pull request To Reproduce Expected behavior Conan should be updated to use the 1.15 version of six to build correctly. 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(narice): channels(root): nixpkgs: Maintainer information:
I'm not actually the maintainer, is, but I'll see if I can see if there's a quick fix
woaw! that was fast! thank you very much
You even got a package update in the bargain :D
Change:
python3.pkgs.buildPythonApplication rec { pname = "jrnl"; <del> version = "2.8.4"; </del> <ins> version = "3.0"; </ins> format = "pyproject"; src = fetchFromGitHub { owner = "jrnl-org"; repo = pname; rev = "v${version}"; <del> sha256 = "sha256-Edu+GW/D+R5r0R750Z1f8YUVPMYbm9PK4D73sTDzDEc="; </del> <ins> sha256 = "sha256-wyN7dlAbQwqvES8qEJ4Zo+fDMM/Lh9tNjf215Ywop10="; </ins> }; nativeBuildInputs = with python3.pkgs; [

Discussion:
Steps to reproduce the behavior: jrnl test errors 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.
I have opened a PR for fix and upgrade, but I still fail to run tests at the moment.
Change:
postPatch = '' sed -i "/--cov/d" setup.cfg sed -i "/--no-cov-on-fail/d" setup.cfg <ins> # https://github.com/sublime-music/sublime-music/commit/f477659d24e372ed6654501deebad91ae4b0b51c sed -i "s/python-mpv/mpv/g" pyproject.toml </ins> ''; buildInputs = [

Discussion:
Steps to reproduce the behavior: sublime-music Bisected the failure to . <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- (for python-mpv)
Looking at in the build directory, I see that is on the PYTHONPATH for the build. Do we need substitute the version in ?
Thank you for reporting, going to look into it
Looks like is probably why it is failing now. I think should fix it upstream in Sublime Music.
Change:
}; dns = mkOption { <del> type = types.enum [ "default" "dnsmasq" "unbound" "systemd-resolved" "none" ]; </del> <ins> type = types.enum [ "default" "dnsmasq" "systemd-resolved" "none" ]; </ins> default = "default"; description = lib.mdDoc '' Set the DNS (`resolv.conf`) processing mode.

Discussion:
I see the following warning in my syslog: I guess it has got to do with me setting as my dns resolver, but it is listed as an option for , so i don’t understand why the log warning says that it has been removed. In my i've set: Steps to reproduce the behavior: the above settings in I don't understand the severity of the warning but i guess it shouldn't be there. Also open on <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Upstream dropped unbound almost a year ago but I guess no one bothered, I'll drop the unbound option.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
<del> { lib , stdenv , fetchurl , undmg , dpkg , autoPatchelfHook , wrapGAppsHook3 , makeWrapper , alsa-lib , at-spi2-atk , gdk-pixbuf , glibc , nss , udev , xorg , gnome-keyring , mesa , gtk3 , libusb1 , libsecret , libappindicator , xdotool }: let pname = "keeweb"; version = "1.18.7"; srcs = { x86_64-linux = fetchurl { url = "https://github.com/keeweb/keeweb/releases/download/v${version}/KeeWeb-${version}.linux.x64.deb"; hash = "sha256-/U+vn5TLIU9/J6cRFjuAdyGzlwC04mp4L2X2ETp+ZSE="; }; x86_64-darwin = fetchurl { url = "https://github.com/keeweb/keeweb/releases/download/v${version}/KeeWeb-${version}.mac.x64.dmg"; hash = "sha256-+ZFGrrw0tZ7F6lb/3iBIyGD+tp1puVhkPv10hfp6ATU="; }; aarch64-darwin = fetchurl { url = "https://github.com/keeweb/keeweb/releases/download/v${version}/KeeWeb-${version}.mac.arm64.dmg"; hash = "sha256-bkhwsWYLkec16vMOfXUce7jfrmI9W2xHiZvU1asebK4="; }; }; src = srcs.${stdenv.hostPlatform.system} or (throw "Unsupported system: ${stdenv.hostPlatform.system}"); libraries = [ alsa-lib at-spi2-atk gdk-pixbuf nss udev xorg.libX11 xorg.libXcomposite xorg.libXext xorg.libXrandr xorg.libXScrnSaver xorg.libXtst xorg.libxshmfence gnome-keyring mesa gtk3 libusb1 libsecret libappindicator xdotool ]; meta = with lib; { description = "Free cross-platform password manager compatible with KeePass"; mainProgram = "keeweb"; homepage = "https://keeweb.info/"; changelog = "https://github.com/keeweb/keeweb/blob/v${version}/release-notes.md"; sourceProvenance = with sourceTypes; [ binaryNativeCode ]; license = licenses.mit; maintainers = with maintainers; [ sikmir ]; platforms = builtins.attrNames srcs; }; in if stdenv.isDarwin then stdenv.mkDerivation { inherit pname version src meta; nativeBuildInputs = [ undmg ]; sourceRoot = "."; installPhase = '' mkdir -p $out/Applications cp -r *.app $out/Applications ''; } else stdenv.mkDerivation { inherit pname version src meta; nativeBuildInputs = [ autoPatchelfHook wrapGAppsHook3 makeWrapper ]; buildInputs = libraries; unpackPhase = '' ${dpkg}/bin/dpkg-deb --fsys-tarfile $src | tar --extract ''; installPhase = '' runHook preInstall mkdir -p $out/bin cp -r usr/share $out/share makeWrapper $out/share/keeweb-desktop/keeweb $out/bin/keeweb  --argv0 "keeweb"  --add-flags "$out/share/keeweb-desktop/resources/app.asar"  --prefix LD_LIBRARY_PATH : "${lib.makeLibraryPath libraries}" runHook postInstall ''; } </del>

Discussion:
Keeweb opens an empty window, hangs for a few seconds and then the program simply crashes. Looks like a missing libGL dependency. <details<summaryLog without libGL</summary</detailsSteps to reproduce the behavior: Keeweb from Terminal or .desktop file. Keeweb not crashing. Just an empty window with only an icon and title. Can be started with following Command: <details<summaryUsing this overlay to launch it without having to use the terminal.</summary</details<!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
preConfigure = '' ln -s ${sqlite-amalgamation}/* sqlite/ <ins> sed -ie 's| restrict| _restrict|g' dumb/include/dumb.h  dumb/src/it/*.c </ins> ''; cmakeFlags =

Discussion:
zandronum fails to build on NixOS 16.03 Pinging maintainer System: 16.03.887. (Emu) Nix version: nix-env (Nix) 1.11.2 Nixpkgs version: 16.03.887.
Could be fallout from the gcc5 update.