jiebi/CodeConvo huggingface dataset:
Change:
, (nixos-19.03) (nixos-19.03) (nixos-19.03) Scanned versions: nixos-19.03: . May contain false positives.

Discussion:
{ stdenv, fetchurl, meson, ninja, pkgconfig, gettext, gnome3, dbus <del> , glib, libgudev, udisks2, libgcrypt, libcap, polkit </del> <ins> , glib, libgudev, udisks2, libgcrypt, libcap, polkit, fetchpatch </ins> , libgphoto2, avahi, libarchive, fuse, libcdio , libxml2, libxslt, docbook_xsl, docbook_xml_dtd_42, samba, libmtp , gnomeSupport ? false, gnome, gcr, wrapGAppsHook

sha256 = "0nw6mv5qq0d79d72x28db0vwihv4isny6m8q7vdim11ngk10hgwh"; }; <ins> patches = [ # CVE-2019-12448 (fetchpatch { url = "https://gitlab.gnome.org/GNOME/gvfs/commit/a1c2e7ecab0d6457fa2227d92e3569c08516eac5.patch"; sha256 = "03fwlpj1vbi80661bbhzv8ddx3czkzv9i1q4h3gqyxi5f1i0xfz4"; }) # CVE-2019-12447 (fetchpatch { url = "https://gitlab.gnome.org/GNOME/gvfs/commit/0f25dea30d01d920443ab72b0c254560ec40e14c.patch"; sha256 = "1p7c48nsx1lkv2qpkyrsm9qfa77xwd28gczwcpv2kbji3ws5qgj5"; }) (fetchpatch { url = "https://gitlab.gnome.org/GNOME/gvfs/commit/272e6bdac33309672955e8f8bf1b8f5f1e51fa0a.patch"; sha256 = "0zxbhmgqxxw987ag8fh6yjzjn9jl55fqbn814jh9kwrk7x4prx9x"; }) # CVE-2019-12449 (fetchpatch { url = "https://gitlab.gnome.org/GNOME/gvfs/commit/bed1e9685c9f65f6a3ff3b39dd8547db3e7e77f6.patch"; sha256 = "0hfybfaz2gfx3yyw5ymx6q0pqwkx2r1i7gzprfp80bplwslq0d4h"; }) # CVE-2019-12795 (fetchpatch { url = "https://gitlab.gnome.org/GNOME/gvfs/commit/e3808a1b4042761055b1d975333a8243d67b8bfe.patch"; sha256 = "1lx6yxykx24mnq5izijqk744zj6rgww6ba76z0qjal4y0z3gsdqp"; }) ]; </ins> postPatch = '' # patchShebangs requires executable file chmod +x codegen.py meson_post_install.py
Change:
, (nixos-unstable) Scanned versions: nixos-unstable: . May contain false positives.

Discussion:
./no-etc-install.patch ./fix-qemu-ga.patch ./9p-ignore-noatime.patch <ins> (fetchpatch { url = "https://git.qemu.org/?p=qemu.git;a=patch;h=d52680fc932efb8a2f334cc6993e705ed1e31e99"; name = "CVE-2019-12155.patch"; sha256 = "0h2q71mcz3gvlrbfkqcgla74jdg73hvzcrwr4max2ckpxx8x9207"; }) </ins> ] ++ optional nixosTestRunner ./force-uid0-on-9p.patch ++ optionals stdenv.hostPlatform.isMusl [ (fetchpatch {
Change:
It crashes with: Open the Keyboard settings option through the search bar. Gnome control center won't start up. Any subsequent starts will also crash.
This seems to be the same issue as but that is supposed to be fixed.
That is similar issue but this would not be fixed by that. We need to add mutter to as well.
Hmm, looks like it was already in the thread and I but for some reason I forgot to include it in the PR.
Any idea how I unbrick this in 19.03 ? I can't open gnome control center at all anymore since I triggered this. reboots don't seem to help
Either try to backport this, or open a different section of settings (from Shell or command line ).
Recompiling the world now for backport. hope it works :) PR incoming if it does
Is this related?
No. The error looks nothing like the reported in the OP. Please do not post unrelated comments to ancient issues that were already resolved.

Discussion:
gdk_pixbuf adwaita-icon-theme librsvg clutter clutter-gtk cheese networkmanager modemmanager gnome-bluetooth tracker udisks2 gsound libhandy <ins> mutter # schemas for the keybindings </ins> ]; patches = [
Change:
commit unbuildable on my machine. sqlite3.h cannot be found (race?). Zen architecture, 6c 12t. I reverted to previous commit and it built without issue. Build sqlite on zen architecture. I can't test whether zen+ or further works. Please run and paste the results. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
It's disabled in (currently in staging-next branch, soon to get in master). This wouldn't reproduce for me on a few tries with 16-threaded Ryzen, but that doesn't really need to mean anything.
Is this in master? I still get: So I can't update my system :smile:
It is. BTW, when you click a commit on GitHub, it will show from which branches it's reachable.
Thanks! Now how can I know the status of the nixos-unstable channel? Edit: nevermind, I finally found what I have been searching for weeks: :smile:

Discussion:
in stdenv.mkDerivation rec { <del> name = "sqlite-${version}"; </del> <ins> pname = "sqlite"; </ins> version = "3.28.0"; # NB! Make sure to update analyzer.nix src (in the same directory).

sed -i $out/lib/libsqlite3.la -e "s/dependency_libs=.*/dependency_libs='''/" ''; <ins> enableParallelBuilding = true; </ins> doCheck = false; # fails to link against tcl meta = {
Change:
I get lots of warnings while evaluating nixos/release- on nixos-unstable : nix-instantiate nixos/release- system: host os: multi-user?: sandbox: version: nixpkgs:
This must be the source of the warning: the original option has been removed () so now only the dummy option is left and has no description. I don't see any other occurance of so I guess it's safe to remove.
Is this correct?

Discussion:
# # One particular example are the boot tests where we want instrumentation # within the images but not other stuff like setting up 9p filesystems. <del> options.virtualisation.qemu.program = mkOption { type = types.path; }; </del> <ins> options.virtualisation.qemu = { }; </ins> config = {
Change:
, (nixos-19.03) Scanned versions: nixos-19.03: . May contain false positives.
See also

Discussion:
{ stdenv, fetchurl, meson, ninja, pkgconfig, gettext, gnome3, dbus <del> , glib, libgudev, udisks2, libgcrypt, libcap, polkit </del> <ins> , glib, libgudev, udisks2, libgcrypt, libcap, polkit, fetchpatch </ins> , libgphoto2, avahi, libarchive, fuse, libcdio , libxml2, libxslt, docbook_xsl, docbook_xml_dtd_42, samba, libmtp , gnomeSupport ? false, gnome, gcr, wrapGAppsHook

sha256 = "0nw6mv5qq0d79d72x28db0vwihv4isny6m8q7vdim11ngk10hgwh"; }; <ins> patches = [ # CVE-2019-12448 (fetchpatch { url = "https://gitlab.gnome.org/GNOME/gvfs/commit/a1c2e7ecab0d6457fa2227d92e3569c08516eac5.patch"; sha256 = "03fwlpj1vbi80661bbhzv8ddx3czkzv9i1q4h3gqyxi5f1i0xfz4"; }) # CVE-2019-12447 (fetchpatch { url = "https://gitlab.gnome.org/GNOME/gvfs/commit/0f25dea30d01d920443ab72b0c254560ec40e14c.patch"; sha256 = "1p7c48nsx1lkv2qpkyrsm9qfa77xwd28gczwcpv2kbji3ws5qgj5"; }) (fetchpatch { url = "https://gitlab.gnome.org/GNOME/gvfs/commit/272e6bdac33309672955e8f8bf1b8f5f1e51fa0a.patch"; sha256 = "0zxbhmgqxxw987ag8fh6yjzjn9jl55fqbn814jh9kwrk7x4prx9x"; }) # CVE-2019-12449 (fetchpatch { url = "https://gitlab.gnome.org/GNOME/gvfs/commit/bed1e9685c9f65f6a3ff3b39dd8547db3e7e77f6.patch"; sha256 = "0hfybfaz2gfx3yyw5ymx6q0pqwkx2r1i7gzprfp80bplwslq0d4h"; }) # CVE-2019-12795 (fetchpatch { url = "https://gitlab.gnome.org/GNOME/gvfs/commit/e3808a1b4042761055b1d975333a8243d67b8bfe.patch"; sha256 = "1lx6yxykx24mnq5izijqk744zj6rgww6ba76z0qjal4y0z3gsdqp"; }) ]; </ins> postPatch = '' # patchShebangs requires executable file chmod +x codegen.py meson_post_install.py
Change:
, (nixos-19.03) Scanned versions: nixos-19.03: . May contain false positives.
See also

Discussion:
{ stdenv, fetchurl, meson, ninja, pkgconfig, gettext, gnome3, dbus <del> , glib, libgudev, udisks2, libgcrypt, libcap, polkit </del> <ins> , glib, libgudev, udisks2, libgcrypt, libcap, polkit, fetchpatch </ins> , libgphoto2, avahi, libarchive, fuse, libcdio , libxml2, libxslt, docbook_xsl, docbook_xml_dtd_42, samba, libmtp , gnomeSupport ? false, gnome, gcr, wrapGAppsHook

sha256 = "1cfnzamr4mvgpf6yhm28lh9cafy9z6842s8jpbqnfizfxybg8ylj"; }; <ins> patches = [ # CVE-2019-12448 (fetchpatch { url = "https://gitlab.gnome.org/GNOME/gvfs/commit/464bbc7e4e7fdfc3cb426557562038408b6108c5.patch"; sha256 = "03fwlpj1vbi80661bbhzv8ddx3czkzv9i1q4h3gqyxi5f1i0xfz4"; }) # CVE-2019-12447 (fetchpatch { url = "https://gitlab.gnome.org/GNOME/gvfs/commit/cf2f9c4020bbdd895485244b70e9442a80062cbe.patch"; sha256 = "1p7c48nsx1lkv2qpkyrsm9qfa77xwd28gczwcpv2kbji3ws5qgj5"; }) (fetchpatch { url = "https://gitlab.gnome.org/GNOME/gvfs/commit/64156459a366d64ab19187455016929b1026189a.patch"; sha256 = "0zxbhmgqxxw987ag8fh6yjzjn9jl55fqbn814jh9kwrk7x4prx9x"; }) # CVE-2019-12449 (fetchpatch { url = "https://gitlab.gnome.org/GNOME/gvfs/commit/ec939a01c278d1aaa47153f51b5c5f0887738dd9.patch"; sha256 = "0hfybfaz2gfx3yyw5ymx6q0pqwkx2r1i7gzprfp80bplwslq0d4h"; }) # CVE-2019-12795 (fetchpatch { url = "https://gitlab.gnome.org/GNOME/gvfs/commit/d8c9138bf240975848b1c54db648ec4cd516a48f.patch"; sha256 = "1lx6yxykx24mnq5izijqk744zj6rgww6ba76z0qjal4y0z3gsdqp"; }) ]; </ins> postPatch = '' # patchShebangs requires executable file chmod +x meson_post_install.py
Change:
We should package . It is a federated blogging engine and written in Golang.
The [AUR package][1] may be of help. [1]:
Waiting on
I've managed to get a running binary with version 0.11.2 on I later noticed that there is still a lot of work to do... apparently their CSS also needs compiling with a special compiler.
my nur repo contains a working version now, but it's still kind of ugly, as it builds the go binary and then imports the assets from their pre-built binaries.
Hello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use or on the relevant files to find them. Lastly, you can always ask for help at or at .
a
I marked this as stale due to inactivity. &rarr;
b

Discussion:
<ins> { lib, buildGoModule, fetchFromGitHub, go-bindata }: buildGoModule rec { pname = "writefreely"; version = "0.12.0"; src = fetchFromGitHub { owner = "writeas"; repo = pname; rev = "v${version}"; sha256 = "sha256-6LpRfDu3xvE1eIRLfZliKnzsrrG5pjjf2ydxn9HQJJU="; }; vendorSha256 = "sha256-U17AkMJQr/OIMED0i2ThcNVw3+aOvRLbpLNP/wEv6k8="; nativeBuildInputs = [ go-bindata ]; preBuild = '' make assets export buildFlagsArray=( "-ldflags=-s -w -X github.com/writeas/writefreely.softwareVer=${version}" "-tags='sqlite'" ) ''; subPackages = [ "cmd/writefreely" ]; meta = with lib; { description = "Build a digital writing community"; homepage = "https://github.com/writeas/writefreely"; license = licenses.agpl3Only; maintainers = with maintainers; [ SuperSandro2000 ]; }; } </ins>

inherit (darwin.apple_sdk.frameworks) Cocoa CoreGraphics Foundation; }; <ins> writefreely = callPackage ../applications/misc/writefreely { }; </ins> x3270 = callPackage ../applications/terminal-emulators/x3270 { }; xterm = callPackage ../applications/terminal-emulators/xterm { };
Change:
has custom filters, and the default behaviour on first launch is to put the data directory in the file, like so: These paths will break on an update to aerc. I'm the maintainer, but I'm not exactly sure what the best way to fix this with Nix is.
It's part of the build A level of function and structure would probably need to be changed to remove this. Probably a good bug to report at This wouldn't just be a problem for nix.
Currently, is put in for aerc so in the case for text/html you can simply do (in your ): But as for and the default config now uses respecively which will need a different solution. EDIT: I just saw you are the maintainer, so you probably already knew all this. The latter two filters can maybe be wrapped in bash scipts that can be executed from path, like in the case of .

Discussion:
python3.pkgs.wrapPython ]; <ins> patches = [ ./runtime-sharedir.patch ]; </ins> pythonPath = [ python3.pkgs.colorama ];

<ins> From 7ea68a2eef026723903d72f54ca54b629881ec06 Mon Sep 17 00:00:00 2001 From: Tadeo Kondrak <me@tadeo.ca> Date: Mon, 28 Oct 2019 08:36:36 -0600 Subject: [PATCH] Fix aerc breaking every time the package is rebuilt. On NixOS, the SHAREDIR changes on every rebuild to the package, but aerc fills it in as part of the default config. Fix this by not substituting @SHAREDIR@ in the default config until runtime. --- Makefile         | 2 +- config/config.go | 3 +++ 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/Makefile b/Makefile index d3072d3..17ca0be 100644 --- a/Makefile +++ b/Makefile @@ -24,7 +24,7 @@ aerc: $(GOSRC) -o $@ aerc.conf: config/aerc.conf.in -	sed -e 's:@SHAREDIR@:$(SHAREDIR):g' > $@ < config/aerc.conf.in +	cat config/aerc.conf.in > $@ DOCS :=  aerc.1  diff --git a/config/config.go b/config/config.go index bfcbecf..2f4e703 100644 --- a/config/config.go +++ b/config/config.go @@ -377,6 +377,9 @@ func LoadConfigFromFile(root *string, sharedir string) (*AercConfig, error) { if err = config.LoadConfig(file); err != nil { return nil, err } +	for i, filter := range config.Filters { +		config.Filters[i].Command = strings.ReplaceAll(filter.Command, "@SHAREDIR@", sharedir) +	} if ui, err := file.GetSection("general"); err == nil { if err := ui.MapTo(&config.General); err != nil { return nil, err -- 2.23.0 </ins>
Change:
tests fails on Darwin in sandbox mode: system: host os: multi-user?: sandbox: version: channels(smaret): nixpkgs:
CC
Oddly, the tests run fine on Hydra:
I doubt this has anything to do with black but rather with networking on mac OS in the sandbox. This sounds related:
I think you're right. Thanks for pointing the sandbox issue.

Discussion:
checkInputs =  [ pytest glibcLocales ]; <ins> # Necessary for the tests to pass on Darwin with sandbox enabled. # Black starts a local server and needs to bind a local address. __darwinAllowLocalNetworking = true; </ins> # Don't know why these tests fails checkPhase = '' LC_ALL="en_US.UTF-8" pytest
Change:
Caused by the pytest update in . Upstream issue filed at
Adding this from my overlay solves it (but still waiting for a release):
Couldn't we just backport that for now instead of bumping the whole package?
I was mentioning this as a quickfifx, backporting the commit seems more sensible. Let's ask the maintainer

Discussion:
<del> { lib, buildPythonPackage, fetchPypi, isPy3k, pytest, mock, setuptools_scm }: </del> <ins> { lib, buildPythonPackage, fetchPypi, fetchpatch, isPy3k, pytest, mock, setuptools_scm }: </ins> buildPythonPackage rec { pname = "pytest-mock";

propagatedBuildInputs = lib.optional (!isPy3k) mock; nativeBuildInputs = [ setuptools_scm pytest ]; <ins> patches = [ # Fix tests for pytest 4.6. Remove with the next release (fetchpatch { url = "https://github.com/pytest-dev/pytest-mock/commit/189cc599d3bfbe91a17c93211c04237b6c5849b1.patch"; sha256 = "13nk75ldab3j8nfzyd9w4cgfk2fxq4if1aqkqy82ar7y7qh07a7m"; }) ]; </ins> checkPhase = '' py.test '';
Change:
Seems to be related to /. Makes it so I can't use , which depends on it for some reason Update to latest git master nixpkgs Please run and paste the results. system: host os: multi-user?: sandbox: version: nixpkgs:
Got the same error when rebuilding my system on nixos-unstable channel relevant log:
I think previously this was fixed by using gcc6 instead of gcc7. Something like this for qtbase:
I am also having this problem. I have bisected it to
I attempted to apply 's suggestion to only qt packages. The failure is the same. Perhaps a dependency also needs to compile with gcc6? Is there a way to default the i686 packages to gcc6?
Maybe that would be a usable workaround. EDIT: at least it does make build again (for me). In any case, more in-depth discussion of this was in
that worked for almost everything. Except packages using . That causes a failure. EG: dhcp: I've overrideAttr the dhcp to confirm. There are ~10 other derivations using that warning. Is it necessary to override each individually?
FWIW, works around this, assuming you don't need gstreamer support of course...
gstreamerSupport in wine cause more problems than solve (concretely -- wrapper with gstreamer specific variables for wine64), but it completely unrelated for this case
it is unrelated to the ultimate cause, yes. It is still a useful workaround for the symptom that tadeokondrak was dealing with (being unable to build wine). I mis-judged whether or not that would be clear from context...
qtbase still fails to build on latest unstable and latest unstable-small.
Perhaps we can use that fix for now? Otherwise I'm not sure how to handle it without breaking something else.
That might solve on symptom of the problem but not the root cause. If I try to build wine on my x64 machine it wants to build some version of and that fails. Even with vcunat's patch it doesn't build.
I was able to compile (almost) the full plasma 5 desktop with: However, while that passes the plasma5 test on my branch I can't actually get plasma to run on my desktop. Nor can I get many QT apps to run. Those issues may be regressions from until that's verified I'm reluctant to open a PR with those workarounds. Tho compiling and failing is better than not compiling for dev I suppose...

Discussion:
sed -i mkspecs/common/linux.conf  -e "/^QMAKE_INCDIR_OPENGL/ s|$|${libGL.dev or libGL}/include|"  -e "/^QMAKE_LIBDIR_OPENGL/ s|$|${libGL.out}/lib|" <ins> '' + lib.optionalString (stdenv.hostPlatform.isx86_32 && stdenv.cc.isGNU) '' sed -i mkspecs/common/gcc-base-unix.conf  -e "/^QMAKE_LFLAGS_SHLIB/ s/-shared/-shared -static-libgcc/" </ins> '' );
Change:
I can't build bazel-watcher on the latest master <details<summaryShell session</summary</detailsPlease run and paste the results. system: host os: multi-user?: sandbox: version: channels(root): channels(kalbasit): channels(yl): nixpkgs: cc

Discussion:
{ buildBazelPackage , fetchFromGitHub <ins> , fetchpatch </ins> , git , go , python , stdenv }: <ins> let patches = [ ./use-go-in-path.patch # update rules_go to fix the build. Remove these when updating past 0.10.3 (fetchpatch { url = "https://github.com/bazelbuild/bazel-watcher/commit/686130f50cea274f7453f6abc8c5249654047462.patch"; sha256 = "0rzs01sfiinl5d3dq9sx1bhl8kkzppdwh964fr7bzafqcxv5llmb"; }) (fetchpatch { url = "https://github.com/bazelbuild/bazel-watcher/commit/18bdb44832ccc533e0ab3923ef80060eeb24582d.patch"; sha256 = "0k5hvlxlg4n092d53cbfxqqhzc6f1jv4licdhhi1dhckkhb4sdk6"; }) ]; in </ins> buildBazelPackage rec { name = "bazel-watcher-${version}"; version = "0.10.3";

bazelTarget = "//ibazel"; fetchAttrs = { <ins> inherit patches; </ins> preBuild = '' patchShebangs . <del> # tell rules_go to use the Go binary found in the PATH sed -e 's:go_register_toolchains():go_register_toolchains(go_version = "host"):g' -i WORKSPACE </del> ''; preInstall = ''

sed -e '/^FILE:@bazel_gazelle_go_repository_tools.*/d' -i $bazelOut/external/@*.marker ''; <del> sha256 = "1ck1rsg5msd77abs889nl2n2i3jlah4d4vjz5wbsb3jyhzn8n5ny"; </del> <ins> sha256 = "01d4m4kb2mhz8fxl9apzsdq0pd7i79w3q49x51rwa524caml9zfv"; </ins> }; buildAttrs = { <ins> inherit patches; </ins> preBuild = '' patchShebangs . <del> # tell rules_go to use the Go binary found in the PATH sed -e 's:go_register_toolchains():go_register_toolchains(go_version = "host"):g' -i WORKSPACE </del> ''; installPhase = ''

<ins> diff --git a/WORKSPACE b/WORKSPACE index 51273b6..fcf9ffb 100644 --- a/WORKSPACE +++ b/WORKSPACE @@ -61,7 +61,7 @@ load("@io_bazel_rules_go//go:deps.bzl", "go_register_toolchains", "go_rules_depe go_rules_dependencies() -go_register_toolchains() +go_register_toolchains(go_version = "host") load("@bazel_gazelle//:deps.bzl", "gazelle_dependencies", "go_repository") </ins>
Change:
For visibility of our project it would be good if Steam can detect NixOS. Then it might appear in their stats: Error on console: Related to Currently detected system informations: steam system informations system: host os: multi-user?: sandbox: version: channels(davidak): channels(root): nixpkgs:
NixOS isn't configured to have . Kinda surprised they don't fallback to in favor of .
They actually do fall back but our doesn't support any files besides deprecated . We had a discussion before about correctness of providing on NixOS but I think we could do that, just print some error when supported LSB version is requested. Maybe we could steal Debian's modern implementation - I think they even use .

Discussion:
commonTargetPkgs = pkgs: with pkgs; [ steamPackages.steam-fonts <ins> # Needed for operating system detection until # https://github.com/ValveSoftware/steam-for-linux/issues/5909 is resolved lsb-release </ins> # Errors in output without those pciutils python2
Change:
Looks like the current is 9+ months old. I took a crack at just updating the rev and sha256, but it looks like it might need a bit more attention (maybe just switching the derivation over to using the Go module functionality?). Leaving this mostly as a reminder to come back and look at this again soon. Please run and paste the results.

Discussion:
<del> { stdenv, buildGo110Package, fetchFromGitHub }: </del> <ins> { stdenv, buildGoModule, fetchFromGitHub }: </ins> <del> buildGo110Package rec { name = "gomuks-${version}"; version = "2018-07-10"; </del> <ins> buildGoModule rec { pname = "gomuks"; version = "2019-06-28"; </ins> goPackagePath = "maunium.net/go/gomuks"; src = fetchFromGitHub { owner = "tulir"; <del> repo = "gomuks"; rev = "68db26bcace31297471641fe95f8882e301f5699"; sha256 = "0dagdvsvn8nwqsvjbqk1c6gg2q1m40869nayrkwm3ndg2xkfdpm6"; </del> <ins> repo = pname; rev = "37df8eb454088e61db7a14f382851205bc1806ad"; sha256 = "1hr15d9sbq6mddaxv3pwz86qp1hhzssgrvakfpc49xl4h04dq33g"; </ins> }; <ins> modSha256 = "1qrqgzzsxqvmy4m9shypa94bzw34mc941jhmyccip9grk9fzsxws"; </ins> meta = with stdenv.lib; { <del> homepage = https://maunium.net/go/gomuks/; </del> <ins> homepage = "https://maunium.net/go/gomuks/"; </ins> description = "A terminal based Matrix client written in Go"; license = licenses.gpl3; maintainers = with maintainers; [ tilpner ];
Change:
Could we drop way-cooler package? I've tested it and it doesn't look like a finished product at this moment. Any users that will be against that? I'm for to re-add it once they make a new release. Currently way-cooler is in a mass rewrite state. New version will use wlroots library instead of deprecated wlc, but what's more it will not be compatible with old version (in behaviour and Lua libraries). See cc Please run and paste the results.
An alternative could be to mark it with , so it's relatively easy to access in case someone really wants it. (But I don't know the particular situation of this package.)
I think is a better idea; we don't want to prevent any diehard users(?) from upgrading their system. Is it actually broken, or do you just mean it's not very good?
From the readme of the project: I'd vote for marking it as broken.
Sounds like a good idea, thanks! In that case Sway might be more suitable anyway. Not very good, from comment: In my case it is even completely broken (doesn't launch if I just enable it and execute - either that's due to a different GPU/configuration/etc. or I might be missing something). Anyway, it's not in a good shape and the package is probably unmaintained ( isn't the maintainer (at least not in ) but was so kind as to do the last updates and improvements). cc FYI, but I don't think you're using way-cooler anymore.

Discussion:
homepage = http://way-cooler.org/; license = with licenses; [ mit ]; maintainers = [ maintainers.miltador ]; <del> broken = stdenv.hostPlatform.isAarch64; # fails to build wc-bg (on aarch64) </del> platforms = platforms.all; <ins> broken = true; </ins> }; }