Question:
Describe the bug addon in chromium does not work. After install addon show errors: "Failed to connect to the main process." "Verify the installation of the plasma-browser-integration package. The running environment of the Plasma desktop environment must be at least version 5.13." "Specified native messaging host not found." Manually run from console not help. To Reproduce Steps to reproduce the behavior: Add to : Expected behavior No errors. Additional context I found issue Everything looks like the same problem but in chromium 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 Please run nix-shell -p nix-info --run "nix-info -m" and paste the result. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
Try adding the following line to your configuration:
now And also does not work. Maybe I need to reboot?
That issue is actually unrelated, it has to do with a patch only in our source build of firefox.
I make test with: in . The same error.
I can't reproduce this issue. I just tested in a vm using with this configuration: Are you using plasma5?
Yes plasma5. Looks like it worked for me too. Now all errors are gone. Thanks !
Why are we adding to systemPackages when using the chromium program module? It does this for you.
Just an oversight on my part. You're right, adding chromium to systemPackages is not necessary.
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 .
Thanks - the fix worked for me! Can you please comment on what's the role of package that you install?
I marked this as stale due to inactivity. →
Proposed fix in

"PasswordManagerEnabled" = false; "SpellcheckEnabled" = true; "SpellcheckLanguage" = [ <del> "de" "en-US" ]; </del> <ins> "de" "en-US" ]; </ins> } ''; };


Question:
Describe the bug addon in chromium does not work. After install addon show errors: "Failed to connect to the main process." "Verify the installation of the plasma-browser-integration package. The running environment of the Plasma desktop environment must be at least version 5.13." "Specified native messaging host not found." Manually run from console not help. To Reproduce Steps to reproduce the behavior: Add to : Expected behavior No errors. Additional context I found issue Everything looks like the same problem but in chromium 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 Please run nix-shell -p nix-info --run "nix-info -m" and paste the result. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
Try adding the following line to your configuration:
now And also does not work. Maybe I need to reboot?
That issue is actually unrelated, it has to do with a patch only in our source build of firefox.
I make test with: in . The same error.
I can't reproduce this issue. I just tested in a vm using with this configuration: Are you using plasma5?
Yes plasma5. Looks like it worked for me too. Now all errors are gone. Thanks !
Why are we adding to systemPackages when using the chromium program module? It does this for you.
Just an oversight on my part. You're right, adding chromium to systemPackages is not necessary.
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 .
Thanks - the fix worked for me! Can you please comment on what's the role of package that you install?
I marked this as stale due to inactivity. →
Proposed fix in

###### implementation <del> config = lib.mkIf cfg.enable { # for chromium environment.etc."chromium/policies/managed/default.json".text = builtins.toJSON defaultProfile; environment.etc."chromium/policies/managed/extra.json".text = builtins.toJSON cfg.extraOpts; # for google-chrome https://www.chromium.org/administrators/linux-quick-start environment.etc."opt/chrome/policies/managed/default.json".text = builtins.toJSON defaultProfile; environment.etc."opt/chrome/policies/managed/extra.json".text = builtins.toJSON cfg.extraOpts; # for brave environment.etc."brave/policies/managed/default.json".text = builtins.toJSON defaultProfile; environment.etc."brave/policies/managed/extra.json".text = builtins.toJSON cfg.extraOpts; </del> <ins> config = { environment.etc = lib.mkIf cfg.enable { # for chromium "chromium/native-messaging-hosts/org.kde.plasma.browser_integration.json" = lib.mkIf cfg.enablePlasmaBrowserIntegration { source = "${cfg.plasmaBrowserIntegrationPackage}/etc/chromium/native-messaging-hosts/org.kde.plasma.browser_integration.json"; }; "chromium/policies/managed/default.json" = lib.mkIf (defaultProfile != {}) { text = builtins.toJSON defaultProfile; }; "chromium/policies/managed/extra.json" = lib.mkIf (cfg.extraOpts != {}) { text = builtins.toJSON cfg.extraOpts; }; # for google-chrome https://www.chromium.org/administrators/linux-quick-start "opt/chrome/native-messaging-hosts/org.kde.plasma.browser_integration.json" = lib.mkIf cfg.enablePlasmaBrowserIntegration { source = "${cfg.plasmaBrowserIntegrationPackage}/etc/opt/chrome/native-messaging-hosts/org.kde.plasma.browser_integration.json"; }; "opt/chrome/policies/managed/default.json" = lib.mkIf (defaultProfile != {}) { text = builtins.toJSON defaultProfile; }; "opt/chrome/policies/managed/extra.json" = lib.mkIf (cfg.extraOpts != {}) { text = builtins.toJSON cfg.extraOpts; }; # for brave "brave/policies/managed/default.json" = lib.mkIf (defaultProfile != {}) { text = builtins.toJSON defaultProfile; }; "brave/policies/managed/extra.json" = lib.mkIf (cfg.extraOpts != {}) { text = builtins.toJSON cfg.extraOpts; }; }; </ins> }; }


Question:
Describe the bug addon in chromium does not work. After install addon show errors: "Failed to connect to the main process." "Verify the installation of the plasma-browser-integration package. The running environment of the Plasma desktop environment must be at least version 5.13." "Specified native messaging host not found." Manually run from console not help. To Reproduce Steps to reproduce the behavior: Add to : Expected behavior No errors. Additional context I found issue Everything looks like the same problem but in chromium 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 Please run nix-shell -p nix-info --run "nix-info -m" and paste the result. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
Try adding the following line to your configuration:
now And also does not work. Maybe I need to reboot?
That issue is actually unrelated, it has to do with a patch only in our source build of firefox.
I make test with: in . The same error.
I can't reproduce this issue. I just tested in a vm using with this configuration: Are you using plasma5?
Yes plasma5. Looks like it worked for me too. Now all errors are gone. Thanks !
Why are we adding to systemPackages when using the chromium program module? It does this for you.
Just an oversight on my part. You're right, adding chromium to systemPackages is not necessary.
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 .
Thanks - the fix worked for me! Can you please comment on what's the role of package that you install?
I marked this as stale due to inactivity. →
Proposed fix in

system.userActivationScripts.plasmaSetup = activationScript; programs.firefox.nativeMessagingHosts.packages = [ pkgs.plasma5Packages.plasma-browser-integration ]; <ins> programs.chromium.enablePlasmaBrowserIntegration = true; </ins> }) (mkIf (cfg.kwinrc != {}) {


Question:
To Reproduce Additional context I am building the package on an x8664 machine via distributed build, if that makes any difference. I have also tried to build with llvmPackages8 through 10 and I got the same result. Notify maintainers Metadata Maintainer information:
This looks just like Unsure why it's reoccurring.
Caused by
This is native linux i868? Interesting, it is deciding to build nothing but headers, and then only the dev output is present. I am curious what it decided to build before that filled .
Ah! I bet it was auto-detecting and that gave it something to build, but now the correct arch is manually specified.
I can confirm that reverting fixed this issue.
hopefully fixed in
I'm seeing something similar for 32-bit arm on recent master () , ([build log][]). Do we need to make a version of for ? [build log]:
I suspect that since (and previously ) on i686 is really only building the bare minimum: whereas on : Missing are asan, ubsan related libs and much more. I should probably open a new issue for this.

# can build this. If we didn't do it, basically the entire nixpkgs on Darwin would have an unfree dependency and we'd # get no binary cache for the entire platform. If you really find yourself wanting the TSAN, make this controllable by # a flag and turn the flag off during the stdenv build. <del> postPatch = stdenv.lib.optionalString stdenv.isDarwin '' </del> <ins> postPatch = '' substituteInPlace cmake/builtin-config-ix.cmake  --replace 'set(X86 i386)' 'set(X86 i386 i486 i586 i686)' '' + stdenv.lib.optionalString stdenv.isDarwin '' </ins> substituteInPlace cmake/config-ix.cmake  --replace 'set(COMPILER_RT_HAS_TSAN TRUE)' 'set(COMPILER_RT_HAS_TSAN FALSE)' '' + stdenv.lib.optionalString (useLLVM) ''


Question:
Project description is already packaged in nixpkgs, but the upstream project has been taken over by new maintainers who have ported it to Python 3 and are continuing development. As far as I know this new version is also used by Debian/Ubuntu (it has python3 dependencies in those distros). I have a local attempt at a new derivation and it Works For Me, but it has a patch in it which I don't think it should need. Also, maybe the original maintainer may want to do the update? If desired I can open a PR with my current state of affairs. Metadata homepage URL: license: GPL2 platforms: Linux
I have limited spare time these days (months), so please be my guest

<del> { stdenv, fetchurl, python2, keybinder3, intltool, file, gtk3, gobject-introspection , libnotify, wrapGAppsHook, vte </del> <ins> { stdenv , fetchFromGitHub , python , keybinder3 , intltool , file , gtk3 , gobject-introspection , libnotify , wrapGAppsHook , vte </ins> }: <del> python2.pkgs.buildPythonApplication rec { </del> <ins> python.pkgs.buildPythonApplication rec { </ins> name = "terminator-${version}"; <del> version = "1.91"; </del> <ins> version = "1.92"; </ins> <del> src = fetchurl { url = "https://launchpad.net/terminator/gtk3/${version}/+download/${name}.tar.gz"; sha256 = "95f76e3c0253956d19ceab2f8da709a496f1b9cf9b1c5b8d3cd0b6da3cc7be69"; </del> <ins> src = fetchFromGitHub { owner = "gnome-terminator"; repo = "terminator"; rev = "bb24273eb40dc5eac97de74064488701fa40a743"; sha256 = "105f660wzf9cpn24xzwaaa09igg5h3qhchafv190v5nqck6g1ssh"; </ins> }; <del> nativeBuildInputs = [ file intltool wrapGAppsHook gobject-introspection ]; buildInputs = [ gtk3 vte libnotify keybinder3 </del> <ins> nativeBuildInputs = [ file intltool gobject-introspection wrapGAppsHook ]; buildInputs = [ gtk3 </ins> gobject-introspection # Temporary fix, see https://github.com/NixOS/nixpkgs/issues/56943 <ins> keybinder3 libnotify python vte ]; propagatedBuildInputs = with python.pkgs; [ configobj dbus-python pygobject3 psutil pycairo </ins> ]; <del> propagatedBuildInputs = with python2.pkgs; [ pygobject3 psutil pycairo ]; </del> postPatch = '' patchShebangs . <ins> # dbus-python is correctly passed in propagatedBuildInputs, but for some reason setup.py complains. # The wrapped terminator has the correct path added, so ignore this. substituteInPlace setup.py --replace "'dbus-python'," "" </ins> ''; checkPhase = ''


Question:
Project description is already packaged in nixpkgs, but the upstream project has been taken over by new maintainers who have ported it to Python 3 and are continuing development. As far as I know this new version is also used by Debian/Ubuntu (it has python3 dependencies in those distros). I have a local attempt at a new derivation and it Works For Me, but it has a patch in it which I don't think it should need. Also, maybe the original maintainer may want to do the update? If desired I can open a PR with my current state of affairs. Metadata homepage URL: license: GPL2 platforms: Linux
I have limited spare time these days (months), so please be my guest

quadkonsole, etc. in that the main focus is arranging terminals in grids (tabs is the most common default method, which Terminator also supports). ''; <del> homepage = "https://gnometerminator.blogspot.no/p/introduction.html"; </del> <ins> homepage = "https://github.com/gnome-terminator/terminator"; </ins> license = licenses.gpl2; maintainers = with maintainers; [ bjornfor ]; platforms = platforms.linux;


Question:
Project description is already packaged in nixpkgs, but the upstream project has been taken over by new maintainers who have ported it to Python 3 and are continuing development. As far as I know this new version is also used by Debian/Ubuntu (it has python3 dependencies in those distros). I have a local attempt at a new derivation and it Works For Me, but it has a patch in it which I don't think it should need. Also, maybe the original maintainer may want to do the update? If desired I can open a PR with my current state of affairs. Metadata homepage URL: license: GPL2 platforms: Linux
I have limited spare time these days (months), so please be my guest

terminal-notifier = callPackage ../applications/misc/terminal-notifier {}; <del> terminator = callPackage ../applications/misc/terminator { }; </del> <ins> terminator = callPackage ../applications/misc/terminator { python = python3; }; </ins> terminus = callPackage ../applications/misc/terminus { };


Question:
Describe the bug Edit: After looking at it for a while, it seems the real problem is that this function is too strict: I think it should be something like this instead: To Reproduce Because comes before alphabetically, it's mounted first (which fails). You can read the file using: Expected behavior The list of file systems to be topologically sorted. Additional context Originally found this while trying to try out root-on-tmpfs. Notify maintainers Couldn't find anyone. <!-- 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(root): channels(jakob): nixpkgs: Maintainer information:
This is also a problem when using since the dependencies are specified in not or and for this problem is not enough to fix the issue. The option sugested by in would solve it. Actually the only reason the current ISO and netboot images aren't broken because of this (they use ) is solely because and comes alphabetically before .
I marked this as stale due to inactivity. →
This is still an issue, and for me a fairly big one, since I can't generate secrets with agenix with my current setup:

fsNeededForBoot = fs: fs.neededForBoot || elem fs.mountPoint pathsNeededForBoot; # Check whenever `b` depends on `a` as a fileSystem <del> fsBefore = a: b: a.mountPoint == b.device || hasPrefix "${a.mountPoint}${optionalString (!(hasSuffix "/" a.mountPoint)) "/"}" b.mountPoint; </del> <ins> fsBefore = a: b: let # normalisePath adds a slash at the end of the path if it didn't already # have one. # # The reason slashes are added at the end of each path is to prevent `b` # from accidentally depending on `a` in cases like #    a = { mountPoint = "/aaa"; ... } #    b = { device     = "/aaaa"; ... } # Here a.mountPoint *is* a prefix of b.device even though a.mountPoint is # *not* a parent of b.device. If we add a slash at the end of each string, # though, this is not a problem: "/aaa/" is not a prefix of "/aaaa/". normalisePath = path: "${path}${optionalString (!(hasSuffix "/" path)) "/"}"; normalise = mount: mount // { device = normalisePath mount.device; mountPoint = normalisePath mount.mountPoint; depends = map normalisePath mount.depends; }; a' = normalise a; b' = normalise b; in hasPrefix a'.mountPoint b'.device || hasPrefix a'.mountPoint b'.mountPoint || any (hasPrefix a'.mountPoint) b'.depends; </ins> # Escape a path according to the systemd rules, e.g. /dev/xyzzy # becomes dev-xyzzy.  FIXME: slow.


Question:
Describe the bug Edit: After looking at it for a while, it seems the real problem is that this function is too strict: I think it should be something like this instead: To Reproduce Because comes before alphabetically, it's mounted first (which fails). You can read the file using: Expected behavior The list of file systems to be topologically sorted. Additional context Originally found this while trying to try out root-on-tmpfs. Notify maintainers Couldn't find anyone. <!-- 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(root): channels(jakob): nixpkgs: Maintainer information:
This is also a problem when using since the dependencies are specified in not or and for this problem is not enough to fix the issue. The option sugested by in would solve it. Actually the only reason the current ISO and netboot images aren't broken because of this (they use ) is solely because and comes alphabetically before .
I marked this as stale due to inactivity. →
This is still an issue, and for me a fairly big one, since I can't generate secrets with agenix with my current setup:

"upperdir=/nix/.rw-store/store" "workdir=/nix/.rw-store/work" ]; <ins> depends = [ "/nix/.ro-store" "/nix/.rw-store/store" "/nix/.rw-store/work" ]; </ins> }; boot.initrd.availableKernelModules = [ "squashfs" "iso9660" "uas" "overlay" ];


Question:
Describe the bug Edit: After looking at it for a while, it seems the real problem is that this function is too strict: I think it should be something like this instead: To Reproduce Because comes before alphabetically, it's mounted first (which fails). You can read the file using: Expected behavior The list of file systems to be topologically sorted. Additional context Originally found this while trying to try out root-on-tmpfs. Notify maintainers Couldn't find anyone. <!-- 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(root): channels(jakob): nixpkgs: Maintainer information:
This is also a problem when using since the dependencies are specified in not or and for this problem is not enough to fix the issue. The option sugested by in would solve it. Actually the only reason the current ISO and netboot images aren't broken because of this (they use ) is solely because and comes alphabetically before .
I marked this as stale due to inactivity. →
This is still an issue, and for me a fairly big one, since I can't generate secrets with agenix with my current setup:

"upperdir=/nix/.rw-store/store" "workdir=/nix/.rw-store/work" ]; <ins> depends = [ "/nix/.ro-store" "/nix/.rw-store/store" "/nix/.rw-store/work" ]; </ins> }; boot.initrd.availableKernelModules = [ "squashfs" "overlay" ];


Question:
Describe the bug Edit: After looking at it for a while, it seems the real problem is that this function is too strict: I think it should be something like this instead: To Reproduce Because comes before alphabetically, it's mounted first (which fails). You can read the file using: Expected behavior The list of file systems to be topologically sorted. Additional context Originally found this while trying to try out root-on-tmpfs. Notify maintainers Couldn't find anyone. <!-- 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(root): channels(jakob): nixpkgs: Maintainer information:
This is also a problem when using since the dependencies are specified in not or and for this problem is not enough to fix the issue. The option sugested by in would solve it. Actually the only reason the current ISO and netboot images aren't broken because of this (they use ) is solely because and comes alphabetically before .
I marked this as stale due to inactivity. →
This is still an issue, and for me a fairly big one, since I can't generate secrets with agenix with my current setup:

specialFSTypes = [ "proc" "sysfs" "tmpfs" "ramfs" "devtmpfs" "devpts" ]; <ins> nonEmptyWithoutTrailingSlash = addCheckDesc "non-empty without trailing slash" types.str (s: isNonEmpty s && (builtins.match ".+/" s) == null); </ins> coreFileSystemOpts = { name, config, ... }: { options = { mountPoint = mkOption { example = "/mnt/usb"; <del> type = addCheckDesc "non-empty without trailing slash" types.str (s: isNonEmpty s && (builtins.match ".+/" s) == null); </del> <ins> type = nonEmptyWithoutTrailingSlash; </ins> description = "Location of the mounted the file system."; };


Question:
Describe the bug Edit: After looking at it for a while, it seems the real problem is that this function is too strict: I think it should be something like this instead: To Reproduce Because comes before alphabetically, it's mounted first (which fails). You can read the file using: Expected behavior The list of file systems to be topologically sorted. Additional context Originally found this while trying to try out root-on-tmpfs. Notify maintainers Couldn't find anyone. <!-- 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(root): channels(jakob): nixpkgs: Maintainer information:
This is also a problem when using since the dependencies are specified in not or and for this problem is not enough to fix the issue. The option sugested by in would solve it. Actually the only reason the current ISO and netboot images aren't broken because of this (they use ) is solely because and comes alphabetically before .
I marked this as stale due to inactivity. →
This is still an issue, and for me a fairly big one, since I can't generate secrets with agenix with my current setup:

type = types.listOf nonEmptyStr; }; <ins> depends = mkOption { default = [ ]; example = [ "/persist" ]; type = types.listOf nonEmptyWithoutTrailingSlash; description = '' List of paths that should be mounted before this one. This filesystem's <option>device</option> and <option>mountPoint</option> are always checked and do not need to be included explicitly. If a path is added to this list, any other filesystem whose mount point is a parent of the path will be mounted before this filesystem. The paths do not need to actually be the <option>mountPoint</option> of some other filesystem. ''; }; </ins> }; config = {


Question:
Describe the bug When receiving email notifications from , for example after a scrub, the hostname is missing from the subject and from the body of the email: To Reproduce Steps to reproduce the behavior: up ZFS and zed ( and ) a scrub for the email Expected behavior Hostname should be present in the subject and body of the email. Additional context Try adding the following in your configuration and notice how the returns nothing: Notify maintainers Metadata Please run and paste the result. Maintainer information:
I just noticed in my logs: So the environment is probably missing something for the command to be available.
Requires net-tools
Please make a PR to add it to the ZED path as we did for the other tools required in ZED.
I will but I have never committed to this repo so it may take time before I learn what is required.
Also, it would have been nice if such a problem would not have been silent, maybe by using in bash scripts.
you need to add it here: You can rebuild your own NixOS using the instructions from here:
I submitted the PR

services.zfs.zed.settings = { ZED_EMAIL_PROG = mkDefault "${pkgs.mailutils}/bin/mail"; <del> PATH = lib.makeBinPath [ packages.zfsUser pkgs.utillinux pkgs.gawk pkgs.gnused pkgs.gnugrep pkgs.coreutils pkgs.curl ]; </del> <ins> PATH = lib.makeBinPath [ packages.zfsUser pkgs.coreutils pkgs.curl pkgs.gawk pkgs.gnugrep pkgs.gnused pkgs.nettools pkgs.utillinux ]; </ins> }; environment.etc = genAttrs


Question:
Describe the bug does not start up. To Reproduce Install and run in the terminal. Expected behavior A TypeScript REPL should start up. Additional context It's possible that the peer dependency on TypeScript is not handled properly. Notify maintainers Metadata Please run and paste the result.
I am not sure how to fix this as it is not a dependency of the tsun package, it is defined as a peer dependency and this expression is generated from a simple JSON file. Of course it should be fixable with overriding and specifying typescript as a dependency, but I don't see any other packages that have these kind of overrides, thus I am not sure how to do it for node packages. I know some other generated packages have some overrides that adds missing dependencies/applies patches and things like that. For now you should be able to include both packages (typescript and tsun) to get it to work.
I've tried , but this yields the same error message as above, which I produced with my main , where I have Is there a more idiomatic way of installing , either locally or globally?
Ah, it is a bit confusing, but seems you need nodejs as well, this works for me: It seems without nodejs it won't setup the which is used for the modules to be found.
In this works for me. But when I have all this in my and install a new generation, fails with the same error as before. I've tried having in but then I get after installing from .
It is the that needs to be set, so this would work: I see now that there are other overrides in the so I should update this package with this code there.
The correct fix might also be this: As the reason why it is not included by the autogenerated expression is due to it being part of peerDependencies which is not included by default in the node2nix command.

''; }; <ins> tsun = super.tsun.overrideAttrs (oldAttrs: { buildInputs = oldAttrs.buildInputs ++ [ pkgs.makeWrapper ]; postInstall = '' wrapProgram "$out/bin/tsun"  --prefix NODE_PATH : ${self.typescript}/lib/node_modules ''; }); </ins> stf = super.stf.override { meta.broken = since "10"; };


Question:
To reproduce: create new (ethernet) connection, with ip4 set to link-local. When ing the connection, the following errors are thrown: An reveals the problem: I thought the following would fix it (): but this creates a new problem:
add that new user when NM is enabled in the nixos module.
Did suggestion work? I was just bitten by this issue.
Did not try it futher yet. If you want you can try it.

gammu-smsd = 228; pdnsd = 229; octoprint = 230; <ins> avahi-autoipd = 231; </ins> # When adding a uid, make sure it doesn't match an existing gid. And don't use uids above 399!


Question:
To reproduce: create new (ethernet) connection, with ip4 set to link-local. When ing the connection, the following errors are thrown: An reveals the problem: I thought the following would fix it (): but this creates a new problem:
add that new user when NM is enabled in the nixos module.
Did suggestion work? I was just bitten by this issue.
Did not try it futher yet. If you want you can try it.

users.extraUsers = [{ name = "nm-openvpn"; uid = config.ids.uids.nm-openvpn; <ins> } { # to enable link-local connections name = "avahi-autoipd"; uid = config.ids.uids.avahi-autoipd; </ins> }]; systemd.packages = cfg.packages;


Question:
To reproduce: create new (ethernet) connection, with ip4 set to link-local. When ing the connection, the following errors are thrown: An reveals the problem: I thought the following would fix it (): but this creates a new problem:
add that new user when NM is enabled in the nixos module.
Did suggestion work? I was just bitten by this issue.
Did not try it futher yet. If you want you can try it.

--replace /bin/sh ${stdenv.shell}  --replace /usr/sbin/ethtool ${ethtool}/sbin/ethtool  --replace /bin/sed ${gnused}/bin/sed <ins> # to enable link-local connections substituteInPlace src/devices/nm-device.c --replace '("avahi-autoipd", NULL, NULL)' '("avahi-autoipd", &"${avahi}/sbin/avahi-autoipd", NULL)' </ins> configureFlags="$configureFlags --with-udev-dir=$out/lib/udev" '';


Question:
The metasploit package no longer builds. I've updating it myself, but I haven't been very successful. If someone could point out my mistake I would gladly correct it and submit a PR.
Is this issue still relevant? , (pinging you because you are able to close this if necessary)
Looks relevant to me, as there was no commit to metasploit that updates or fixes it. Why do you think I isn't relevant anymore?
Current version: 3.3.1 Last stable version: 4.12 We definitely need a maintainer. is there a tag for ?

, libiconv, postgresql, v8_3_16_14, clang, sqlite, zlib, imagemagick , pkgconfig , ncurses, xapian_1_2_22, gpgme, utillinux, fetchpatch, tzdata, icu, libffi , cmake, libssh2, openssl, mysql, darwin, git, perl, gecode_3, curl <del> , libmsgpack, qt48, libsodium, snappy, libossp_uuid, lxc </del> <ins> , libmsgpack, qt48, libsodium, snappy, libossp_uuid, lxc, libpcap </ins> }@args: let


Question:
The metasploit package no longer builds. I've updating it myself, but I haven't been very successful. If someone could point out my mistake I would gladly correct it and submit a PR.
Is this issue still relevant? , (pinging you because you are able to close this if necessary)
Looks relevant to me, as there was no commit to metasploit that updates or fixes it. Why do you think I isn't relevant anymore?
Current version: 3.3.1 Last stable version: 4.12 We definitely need a maintainer. is there a tag for ?

buildInputs = [ curl ]; }; <ins> pcaprub = attrs: { buildInputs = [ libpcap ]; }; </ins> pg = attrs: { buildFlags = [ "--with-pg-config=${postgresql}/bin/pg_config"


Question:
The metasploit package no longer builds. I've updating it myself, but I haven't been very successful. If someone could point out my mistake I would gladly correct it and submit a PR.
Is this issue still relevant? , (pinging you because you are able to close this if necessary)
Looks relevant to me, as there was no commit to metasploit that updates or fixes it. Why do you think I isn't relevant anymore?
Current version: 3.3.1 Last stable version: 4.12 We definitely need a maintainer. is there a tag for ?

''; }; <ins> rb-readline = attrs: { dontBuild = false; postPatch = '' substituteInPlace lib/rbreadline.rb  --replace 'infocmp' '${ncurses.dev}/bin/infocmp' ''; }; </ins> timfel-krb5-auth = attrs: { buildInputs = [ kerberos ]; };


Question:
The metasploit package no longer builds. I've updating it myself, but I haven't been very successful. If someone could point out my mistake I would gladly correct it and submit a PR.
Is this issue still relevant? , (pinging you because you are able to close this if necessary)
Looks relevant to me, as there was no commit to metasploit that updates or fixes it. Why do you think I isn't relevant anymore?
Current version: 3.3.1 Last stable version: 4.12 We definitely need a maintainer. is there a tag for ?

<ins> # frozen_string_literal: true source "https://rubygems.org" gem "metasploit-framework", git: "https://github.com/rapid7/metasploit-framework", ref: "refs/tags/4.14.17" </ins>


Question:
The metasploit package no longer builds. I've updating it myself, but I haven't been very successful. If someone could point out my mistake I would gladly correct it and submit a PR.
Is this issue still relevant? , (pinging you because you are able to close this if necessary)
Looks relevant to me, as there was no commit to metasploit that updates or fixes it. Why do you think I isn't relevant anymore?
Current version: 3.3.1 Last stable version: 4.12 We definitely need a maintainer. is there a tag for ?

<ins> GIT remote: https://github.com/rapid7/metasploit-framework revision: fd3da8f3350d6cf7f0449bf0ead4d51747525c0a ref: refs/tags/4.14.17 specs: metasploit-framework (4.14.17) actionpack (~> 4.2.6) activerecord (~> 4.2.6) activesupport (~> 4.2.6) bcrypt bit-struct filesize jsobfu json metasm metasploit-concern metasploit-credential metasploit-model metasploit-payloads (= 1.2.29) metasploit_data_models metasploit_payloads-mettle (= 0.1.9) msgpack nessus_rest net-ssh network_interface nexpose nokogiri octokit openssl-ccm openvas-omp packetfu patch_finder pcaprub pg railties rb-readline recog redcarpet rex-arch (= 0.1.4) rex-bin_tools rex-core rex-encoder rex-exploitation rex-java rex-mime rex-nop rex-ole rex-powershell rex-random_identifier rex-registry rex-rop_builder rex-socket rex-sslscan rex-struct2 rex-text rex-zip robots ruby_smb rubyntlm rubyzip sqlite3 sshkey tzinfo tzinfo-data windows_error xmlrpc GEM remote: https://rubygems.org/ specs: actionpack (4.2.8) actionview (= 4.2.8) activesupport (= 4.2.8) rack (~> 1.6) rack-test (~> 0.6.2) rails-dom-testing (~> 1.0, >= 1.0.5) rails-html-sanitizer (~> 1.0, >= 1.0.2) actionview (4.2.8) activesupport (= 4.2.8) builder (~> 3.1) erubis (~> 2.7.0) rails-dom-testing (~> 1.0, >= 1.0.5) rails-html-sanitizer (~> 1.0, >= 1.0.3) activemodel (4.2.8) activesupport (= 4.2.8) builder (~> 3.1) activerecord (4.2.8) activemodel (= 4.2.8) activesupport (= 4.2.8) arel (~> 6.0) activesupport (4.2.8) i18n (~> 0.7) minitest (~> 5.1) thread_safe (~> 0.3, >= 0.3.4) tzinfo (~> 1.1) addressable (2.5.1) public_suffix (~> 2.0, >= 2.0.2) arel (6.0.4) arel-helpers (2.3.0) activerecord (>= 3.1.0, < 6) bcrypt (3.1.11) bindata (2.4.0) bit-struct (0.16) builder (3.2.3) erubis (2.7.0) faraday (0.12.1) multipart-post (>= 1.2, < 3) filesize (0.1.1) i18n (0.8.1) jsobfu (0.4.2) rkelly-remix json (2.1.0) loofah (2.0.3) nokogiri (>= 1.5.9) metasm (1.0.3) metasploit-concern (2.0.4) activemodel (~> 4.2.6) activesupport (~> 4.2.6) railties (~> 4.2.6) metasploit-credential (2.0.9) metasploit-concern metasploit-model metasploit_data_models pg railties rubyntlm rubyzip metasploit-model (2.0.4) activemodel (~> 4.2.6) activesupport (~> 4.2.6) railties (~> 4.2.6) metasploit-payloads (1.2.29) metasploit_data_models (2.0.14) activerecord (~> 4.2.6) activesupport (~> 4.2.6) arel-helpers metasploit-concern metasploit-model pg postgres_ext railties (~> 4.2.6) recog (~> 2.0) metasploit_payloads-mettle (0.1.9) mini_portile2 (2.1.0) minitest (5.10.2) msgpack (1.1.0) multipart-post (2.0.0) nessus_rest (0.1.6) net-ssh (4.1.0) network_interface (0.0.1) nexpose (6.0.0) nokogiri (1.7.2) mini_portile2 (~> 2.1.0) octokit (4.7.0) sawyer (~> 0.8.0, >= 0.5.3) openssl-ccm (1.2.1) openvas-omp (0.0.4) packetfu (1.1.13) pcaprub patch_finder (1.0.2) pcaprub (0.12.4) pg (0.20.0) pg_array_parser (0.0.9) postgres_ext (3.0.0) activerecord (>= 4.0.0) arel (>= 4.0.1) pg_array_parser (~> 0.0.9) public_suffix (2.0.5) rack (1.6.6) rack-test (0.6.3) rack (>= 1.0) rails-deprecated_sanitizer (1.0.3) activesupport (>= 4.2.0.alpha) rails-dom-testing (1.0.8) activesupport (>= 4.2.0.beta, < 5.0) nokogiri (~> 1.6) rails-deprecated_sanitizer (>= 1.0.1) rails-html-sanitizer (1.0.3) loofah (~> 2.0) railties (4.2.8) actionpack (= 4.2.8) activesupport (= 4.2.8) rake (>= 0.8.7) thor (>= 0.18.1, < 2.0) rake (12.0.0) rb-readline (0.5.4) recog (2.1.6) nokogiri redcarpet (3.4.0) rex-arch (0.1.4) rex-text rex-bin_tools (0.1.3) metasm rex-arch rex-core rex-struct2 rex-text rex-core (0.1.10) rex-encoder (0.1.4) metasm rex-arch rex-text rex-exploitation (0.1.14) jsobfu metasm rex-arch rex-encoder rex-text rex-java (0.1.5) rex-mime (0.1.5) rex-text rex-nop (0.1.1) rex-arch rex-ole (0.1.6) rex-text rex-powershell (0.1.72) rex-random_identifier rex-text rex-random_identifier (0.1.2) rex-text rex-registry (0.1.3) rex-rop_builder (0.1.3) metasm rex-core rex-text rex-socket (0.1.6) rex-core rex-sslscan (0.1.4) rex-socket rex-text rex-struct2 (0.1.2) rex-text (0.2.15) rex-zip (0.1.3) rex-text rkelly-remix (0.0.7) robots (0.10.1) ruby_smb (0.0.12) bindata rubyntlm windows_error rubyntlm (0.6.2) rubyzip (1.2.1) sawyer (0.8.1) addressable (>= 2.3.5, < 2.6) faraday (~> 0.8, < 1.0) sqlite3 (1.3.13) sshkey (1.9.0) thor (0.19.4) thread_safe (0.3.6) tzinfo (1.2.3) thread_safe (~> 0.1) tzinfo-data (1.2017.2) tzinfo (>= 1.0.0) windows_error (0.1.2) xmlrpc (0.3.0) PLATFORMS ruby DEPENDENCIES metasploit-framework! BUNDLED WITH 1.14.6 </ins>


Question:
The metasploit package no longer builds. I've updating it myself, but I haven't been very successful. If someone could point out my mistake I would gladly correct it and submit a PR.
Is this issue still relevant? , (pinging you because you are able to close this if necessary)
Looks relevant to me, as there was no commit to metasploit that updates or fixes it. Why do you think I isn't relevant anymore?
Current version: 3.3.1 Last stable version: 4.12 We definitely need a maintainer. is there a tag for ?

<del> { stdenv, fetchurl, makeWrapper, ruby }: stdenv.mkDerivation rec { </del> <ins> { stdenv, fetchFromGitHub, makeWrapper, ruby, bundlerEnv, ncurses }: # Maintainer notes for updating: # 1. increment version number in expression and in Gemfile # 2. run $ nix-shell --command "bundler install && bundix" #    in metasploit in nixpkgs let env = bundlerEnv { inherit ruby; name = "metasploit-bundler-env"; gemdir = ./.; }; in stdenv.mkDerivation rec { </ins> name = "metasploit-framework-${version}"; <del> version = "3.3.1"; </del> <ins> version = "4.14.17"; </ins> <del> src = fetchurl { url = "http://downloads.metasploit.com/data/releases/archive/framework-${version}.tar.bz2"; sha256 = "07clzw1zfnqjhyydsc4mza238isai58p7aygh653qxsqb9a0j7qw"; </del> <ins> src = fetchFromGitHub { owner = "rapid7"; repo = "metasploit-framework"; rev = version; sha256 = "0g666lxin9f0v9vhfh3s913ym8fnh32rpfl1rpj8d8n1azch5fn0"; </ins> }; <del> buildInputs = [makeWrapper]; </del> <ins> buildInputs = [ makeWrapper ]; dontPatchelf = true; # stay away from exploit executables </ins> installPhase = '' <del> mkdir -p $out/share/msf mkdir -p $out/bin </del> <ins> mkdir -p $out/{bin,share/msf} </ins> cp -r * $out/share/msf for i in $out/share/msf/msf*; do <del> makeWrapper $i $out/bin/$(basename $i) --prefix RUBYLIB : $out/share/msf/lib </del> <ins> bin=$out/bin/$(basename $i) cat > $bin <<EOF #!/bin/sh -e exec ${env}/bin/bundle exec ${ruby}/bin/ruby $i "$@" EOF chmod +x $bin </ins> done ''; <del> postInstall = '' patchShebangs $out/share/msf ''; meta = { </del> <ins> meta = with stdenv.lib; { </ins> description = "Metasploit Framework - a collection of exploits"; homepage = https://github.com/rapid7/metasploit-framework/wiki; <del> platforms = stdenv.lib.platforms.unix; </del> <ins> platforms = platforms.unix; license = licenses.bsd3; maintainers = [ maintainers.makefu ]; </ins> }; }


Question:
The metasploit package no longer builds. I've updating it myself, but I haven't been very successful. If someone could point out my mistake I would gladly correct it and submit a PR.
Is this issue still relevant? , (pinging you because you are able to close this if necessary)
Looks relevant to me, as there was no commit to metasploit that updates or fixes it. Why do you think I isn't relevant anymore?
Current version: 3.3.1 Last stable version: 4.12 We definitely need a maintainer. is there a tag for ?

<ins> { actionpack = { source = { remotes = ["https://rubygems.org"]; sha256 = "09fbazl0ja80na2wadfp3fzmdmdy1lsb4wd2yg7anbj0zk0ap7a9"; type = "gem"; }; version = "4.2.8"; }; actionview = { source = { remotes = ["https://rubygems.org"]; sha256 = "1mg4a8143q2wjhjq4mngl69jkv249z5jvg0jkdribdv4zkg586rp"; type = "gem"; }; version = "4.2.8"; }; activemodel = { source = { remotes = ["https://rubygems.org"]; sha256 = "11vhh7zmp92880s5sx8r32v2p0b7xg039mfr92pjynpkz4q901ld"; type = "gem"; }; version = "4.2.8"; }; activerecord = { source = { remotes = ["https://rubygems.org"]; sha256 = "1kk4dhn8jfhqfsf1dmb3a183gix6k46xr6cjkxj0rp51w2za1ns0"; type = "gem"; }; version = "4.2.8"; }; activesupport = { source = { remotes = ["https://rubygems.org"]; sha256 = "0wibdzd2f5l5rlsw1a1y3j3fhw2imrrbkxggdraa6q9qbdnc66hi"; type = "gem"; }; version = "4.2.8"; }; addressable = { source = { remotes = ["https://rubygems.org"]; sha256 = "1i8q32a4gr0zghxylpyy7jfqwxvwrivsxflg9mks6kx92frh75mh"; type = "gem"; }; version = "2.5.1"; }; arel = { source = { remotes = ["https://rubygems.org"]; sha256 = "0nfcrdiys6q6ylxiblky9jyssrw2xj96fmxmal7f4f0jj3417vj4"; type = "gem"; }; version = "6.0.4"; }; arel-helpers = { source = { remotes = ["https://rubygems.org"]; sha256 = "0k8hqa2505b2s3w6gajh2lvi2mn832yqldiy2z4c55phzkmr08sr"; type = "gem"; }; version = "2.3.0"; }; bcrypt = { source = { remotes = ["https://rubygems.org"]; sha256 = "1d254sdhdj6mzak3fb5x3jam8b94pvl1srladvs53j05a89j5z50"; type = "gem"; }; version = "3.1.11"; }; bindata = { source = { remotes = ["https://rubygems.org"]; sha256 = "10sii2chgnkp2jw830sbr2wb20p8p1wcwrl9jhadkw94f505qcyg"; type = "gem"; }; version = "2.4.0"; }; bit-struct = { source = { remotes = ["https://rubygems.org"]; sha256 = "1w7x1fh4a6inpb46imhdf4xrq0z4d6zdpg7sdf8n98pif2hx50sx"; type = "gem"; }; version = "0.16"; }; builder = { source = { remotes = ["https://rubygems.org"]; sha256 = "0qibi5s67lpdv1wgcj66wcymcr04q6j4mzws6a479n0mlrmh5wr1"; type = "gem"; }; version = "3.2.3"; }; erubis = { source = { remotes = ["https://rubygems.org"]; sha256 = "1fj827xqjs91yqsydf0zmfyw9p4l2jz5yikg3mppz6d7fi8kyrb3"; type = "gem"; }; version = "2.7.0"; }; faraday = { source = { remotes = ["https://rubygems.org"]; sha256 = "1wkx9844vacsk2229xbc27djf6zw15kqd60ifr78whf9mp9v6l03"; type = "gem"; }; version = "0.12.1"; }; filesize = { source = { remotes = ["https://rubygems.org"]; sha256 = "061qmg82mm9xnmnq3b7gbi24g28xk62w0b0nw86gybd07m1jn989"; type = "gem"; }; version = "0.1.1"; }; i18n = { source = { remotes = ["https://rubygems.org"]; sha256 = "1s6971zmjxszdrp59vybns9gzxpdxzdklakc5lp8nl4fx5kpxkbp"; type = "gem"; }; version = "0.8.1"; }; jsobfu = { source = { remotes = ["https://rubygems.org"]; sha256 = "1hchns89cfj0gggm2zbr7ghb630imxm2x2d21ffx2jlasn9xbkyk"; type = "gem"; }; version = "0.4.2"; }; json = { source = { remotes = ["https://rubygems.org"]; sha256 = "01v6jjpvh3gnq6sgllpfqahlgxzj50ailwhj9b3cd20hi2dx0vxp"; type = "gem"; }; version = "2.1.0"; }; loofah = { source = { remotes = ["https://rubygems.org"]; sha256 = "109ps521p0sr3kgc460d58b4pr1z4mqggan2jbsf0aajy9s6xis8"; type = "gem"; }; version = "2.0.3"; }; metasm = { source = { remotes = ["https://rubygems.org"]; sha256 = "0gss57q4lv6l0jkih77zffrpjjzgkdcsy7b9nvvawyzknis9w4s5"; type = "gem"; }; version = "1.0.3"; }; metasploit-concern = { source = { remotes = ["https://rubygems.org"]; sha256 = "0kqby5ycxhr0jfzvjqkdgjbqqjrg8jlmcxw8myrm0875hybyl1mq"; type = "gem"; }; version = "2.0.4"; }; metasploit-credential = { source = { remotes = ["https://rubygems.org"]; sha256 = "1y36f1f4nw0imhfbckl213ah7qgfldrkv2fpv2acslb6iqiaa3gk"; type = "gem"; }; version = "2.0.9"; }; metasploit-framework = { source = { fetchSubmodules = false; rev = "fd3da8f3350d6cf7f0449bf0ead4d51747525c0a"; sha256 = "1r04drq34qfbhmhp0mqnm13vrycr7dcq670zk8xqiif5rhbij6qv"; type = "git"; url = "https://github.com/rapid7/metasploit-framework"; }; version = "4.14.17"; }; metasploit-model = { source = { remotes = ["https://rubygems.org"]; sha256 = "05pnai1cv00xw87rrz38dz4s3ss45s90290d0knsy1mq6rp8yvmw"; type = "gem"; }; version = "2.0.4"; }; metasploit-payloads = { source = { remotes = ["https://rubygems.org"]; sha256 = "0c6wvnxgwdiryz5skzrp2wcfbxp57icaclckjcaxlw63v09wgjii"; type = "gem"; }; version = "1.2.29"; }; metasploit_data_models = { source = { remotes = ["https://rubygems.org"]; sha256 = "0hb2wsz3d4xgjf6dlf7nzxlv6q7rcdgn1pj79xs3g8al38zi129g"; type = "gem"; }; version = "2.0.14"; }; metasploit_payloads-mettle = { source = { remotes = ["https://rubygems.org"]; sha256 = "058ijqznh4xqx3d6dph5gwdsmj96z4n46rl1mm85fyxpgpkifqd1"; type = "gem"; }; version = "0.1.9"; }; mini_portile2 = { source = { remotes = ["https://rubygems.org"]; sha256 = "1y25adxb1hgg1wb2rn20g3vl07qziq6fz364jc5694611zz863hb"; type = "gem"; }; version = "2.1.0"; }; minitest = { source = { remotes = ["https://rubygems.org"]; sha256 = "11my86fnihvpndyknn3c14hc82nhsgggnhlxh8h3bdjpmfsvl0my"; type = "gem"; }; version = "5.10.2"; }; msgpack = { source = { remotes = ["https://rubygems.org"]; sha256 = "0ck7w17d6b4jbb8inh1q57bghi9cjkiaxql1d3glmj1yavbpmlh7"; type = "gem"; }; version = "1.1.0"; }; multipart-post = { source = { remotes = ["https://rubygems.org"]; sha256 = "09k0b3cybqilk1gwrwwain95rdypixb2q9w65gd44gfzsd84xi1x"; type = "gem"; }; version = "2.0.0"; }; nessus_rest = { source = { remotes = ["https://rubygems.org"]; sha256 = "1allyrd4rll333zbmsi3hcyg6cw1dhc4bg347ibsw191nswnp8ci"; type = "gem"; }; version = "0.1.6"; }; net-ssh = { source = { remotes = ["https://rubygems.org"]; sha256 = "013p5jb4wy0cq7x7036piw2a3s1i9p752ki1srx2m289mpz4ml3q"; type = "gem"; }; version = "4.1.0"; }; network_interface = { source = { remotes = ["https://rubygems.org"]; sha256 = "0ir4c1vbz1y0gxyih024262i7ig1nji1lkylcrn9pjzx3798p97a"; type = "gem"; }; version = "0.0.1"; }; nexpose = { source = { remotes = ["https://rubygems.org"]; sha256 = "0jdhhzzs3b3rav6imx8jn9920cjj83yjvz35q169y0ppla2xzqbg"; type = "gem"; }; version = "6.0.0"; }; nokogiri = { source = { remotes = ["https://rubygems.org"]; sha256 = "0jd8q3pr5rkrxx1vklvhcqcgl8kmfv5c8ny36ni3z5mirw6cm70c"; type = "gem"; }; version = "1.7.2"; }; octokit = { source = { remotes = ["https://rubygems.org"]; sha256 = "0h6cm7bi0y7ysjgwws3paaipqdld6c0m0niazrjahhpz88qqq1g4"; type = "gem"; }; version = "4.7.0"; }; openssl-ccm = { source = { remotes = ["https://rubygems.org"]; sha256 = "18h5lxv0zh4j2f0wnhdmfz63x02vbzbq2k1clz6kzr0q83h8kj9c"; type = "gem"; }; version = "1.2.1"; }; openvas-omp = { source = { remotes = ["https://rubygems.org"]; sha256 = "14xf614vd76qjdjxjv14mmjar6s64fwp4cwb7bv5g1wc29srg28x"; type = "gem"; }; version = "0.0.4"; }; packetfu = { source = { remotes = ["https://rubygems.org"]; sha256 = "16ppq9wfxq4x2hss61l5brs3s6fmi8gb50mnp1nnnzb1asq4g8ll"; type = "gem"; }; version = "1.1.13"; }; patch_finder = { source = { remotes = ["https://rubygems.org"]; sha256 = "1md9scls55n1riw26vw1ak0ajq38dfygr36l0h00wqhv51cq745m"; type = "gem"; }; version = "1.0.2"; }; pcaprub = { source = { remotes = ["https://rubygems.org"]; sha256 = "0pl4lqy7308185pfv0197n8b4v20fhd0zb3wlpz284rk8ssclkvz"; type = "gem"; }; version = "0.12.4"; }; pg = { source = { remotes = ["https://rubygems.org"]; sha256 = "03xcgwjs6faxis81jxf2plnlalg55dhhafqv3kvjxfr8ic7plpw5"; type = "gem"; }; version = "0.20.0"; }; pg_array_parser = { source = { remotes = ["https://rubygems.org"]; sha256 = "1034dhg8h53j48sfm373js54skg4vpndjga6hzn2zylflikrrf3s"; type = "gem"; }; version = "0.0.9"; }; postgres_ext = { source = { remotes = ["https://rubygems.org"]; sha256 = "1lbp1qf5s1addhznm7d4bzks9adh7jpilgcsr8k7mbd0a1ailcgc"; type = "gem"; }; version = "3.0.0"; }; public_suffix = { source = { remotes = ["https://rubygems.org"]; sha256 = "040jf98jpp6w140ghkhw2hvc1qx41zvywx5gj7r2ylr1148qnj7q"; type = "gem"; }; version = "2.0.5"; }; rack = { source = { remotes = ["https://rubygems.org"]; sha256 = "073d6rjgqfb4xjhbshyrflqgbdvxqvx4b907j2d4mi5qgbv8y2ax"; type = "gem"; }; version = "1.6.6"; }; rack-test = { source = { remotes = ["https://rubygems.org"]; sha256 = "0h6x5jq24makgv2fq5qqgjlrk74dxfy62jif9blk43llw8ib2q7z"; type = "gem"; }; version = "0.6.3"; }; rails-deprecated_sanitizer = { source = { remotes = ["https://rubygems.org"]; sha256 = "0qxymchzdxww8bjsxj05kbf86hsmrjx40r41ksj0xsixr2gmhbbj"; type = "gem"; }; version = "1.0.3"; }; rails-dom-testing = { source = { remotes = ["https://rubygems.org"]; sha256 = "1ny7mbjxhq20rzg4pivvyvk14irmc7cn20kxfk3vc0z2r2c49p8r"; type = "gem"; }; version = "1.0.8"; }; rails-html-sanitizer = { source = { remotes = ["https://rubygems.org"]; sha256 = "138fd86kv073zqfx0xifm646w6bgw2lr8snk16lknrrfrss8xnm7"; type = "gem"; }; version = "1.0.3"; }; railties = { source = { remotes = ["https://rubygems.org"]; sha256 = "0bavl4hj7bnl3ryqi9rvykm410kflplgingkcxasfv1gdilddh4g"; type = "gem"; }; version = "4.2.8"; }; rake = { source = { remotes = ["https://rubygems.org"]; sha256 = "01j8fc9bqjnrsxbppncai05h43315vmz9fwg28qdsgcjw9ck1d7n"; type = "gem"; }; version = "12.0.0"; }; rb-readline = { source = { remotes = ["https://rubygems.org"]; sha256 = "170m6d2298s9kfbd4y3zzj4irsnd15qlbgi6kk93m88lkh9qzy3a"; type = "gem"; }; version = "0.5.4"; }; recog = { source = { remotes = ["https://rubygems.org"]; sha256 = "08ypzrn40jbjbzwdbbjkcqdm74zlsc0yr2iqs0yn479fa5k8ajw4"; type = "gem"; }; version = "2.1.6"; }; redcarpet = { source = { remotes = ["https://rubygems.org"]; sha256 = "0h9qz2hik4s9knpmbwrzb3jcp3vc5vygp9ya8lcpl7f1l9khmcd7"; type = "gem"; }; version = "3.4.0"; }; rex-arch = { source = { remotes = ["https://rubygems.org"]; sha256 = "1y2mzv6wkqgclxl1x65mdq4d0lcgbbny4r1v24c16gi4jg9nsnc1"; type = "gem"; }; version = "0.1.4"; }; rex-bin_tools = { source = { remotes = ["https://rubygems.org"]; sha256 = "0skrbpyal6anh4g1nsaf9ypg5sd2ghxxmghasxw4p1s1i1xbmhwr"; type = "gem"; }; version = "0.1.3"; }; rex-core = { source = { remotes = ["https://rubygems.org"]; sha256 = "09xbslrwbc9d0rp24y1pdgc6650ciwicq4q7skjz74rprr9wj16f"; type = "gem"; }; version = "0.1.10"; }; rex-encoder = { source = { remotes = ["https://rubygems.org"]; sha256 = "1zm5jdxgyyp8pkfqwin34izpxdrmglx6vmk20ifnvcsm55c9m70z"; type = "gem"; }; version = "0.1.4"; }; rex-exploitation = { source = { remotes = ["https://rubygems.org"]; sha256 = "0gbj28jqaaldpk4qzysgcl6m0wcqx3gcldarqdk55p5z9zasrk19"; type = "gem"; }; version = "0.1.14"; }; rex-java = { source = { remotes = ["https://rubygems.org"]; sha256 = "0j58k02p5g9snkpak64sb4aymkrvrh9xpqh8wsnya4w7b86w2y6i"; type = "gem"; }; version = "0.1.5"; }; rex-mime = { source = { remotes = ["https://rubygems.org"]; sha256 = "15a14kz429h7pn81ysa6av3qijxjmxagjff6dyss5v394fxzxf4a"; type = "gem"; }; version = "0.1.5"; }; rex-nop = { source = { remotes = ["https://rubygems.org"]; sha256 = "0aigf9qsqsmiraa6zvfy1a7cyvf7zc3iyhzxi6fjv5sb8f64d6ny"; type = "gem"; }; version = "0.1.1"; }; rex-ole = { source = { remotes = ["https://rubygems.org"]; sha256 = "1pnzbqfnvbs0vc0z0ryszk3fxhgxrjd6gzwqa937rhlphwp5jpww"; type = "gem"; }; version = "0.1.6"; }; rex-powershell = { source = { remotes = ["https://rubygems.org"]; sha256 = "0nl60fdd1rlckk95d3s3y873w84vb0sgwvwxdzv414qxz8icpjnm"; type = "gem"; }; version = "0.1.72"; }; rex-random_identifier = { source = { remotes = ["https://rubygems.org"]; sha256 = "0cksrljaw61mdjvbmj9vqqhd8nra7jv466w5nim47n73rj72jc19"; type = "gem"; }; version = "0.1.2"; }; rex-registry = { source = { remotes = ["https://rubygems.org"]; sha256 = "0wv812ghnz143vx10ixmv32ypj1xrzr4rh4kgam8d8wwjwxsgw1q"; type = "gem"; }; version = "0.1.3"; }; rex-rop_builder = { source = { remotes = ["https://rubygems.org"]; sha256 = "0xjd3d6wnbq4ym0d0m268md8fb16f2hbwrahvxnl14q63fj9i3wy"; type = "gem"; }; version = "0.1.3"; }; rex-socket = { source = { remotes = ["https://rubygems.org"]; sha256 = "0r39782f2qpq83wsi72213v344gq4rccch98i376fx8bayh0dygh"; type = "gem"; }; version = "0.1.6"; }; rex-sslscan = { source = { remotes = ["https://rubygems.org"]; sha256 = "0r5cy1kng1ggjycn7a8vpval7clhr0yxhd7rgn2hasxl2p3c7i8v"; type = "gem"; }; version = "0.1.4"; }; rex-struct2 = { source = { remotes = ["https://rubygems.org"]; sha256 = "1nbdn53264a20cr2m2nq2v4mg0n33dvrd1jj1sixl37qjzw2k452"; type = "gem"; }; version = "0.1.2"; }; rex-text = { source = { remotes = ["https://rubygems.org"]; sha256 = "024miva867h4wv4y1lnxxrw2d7p51va32ismxqf3fsz4s9cqc88m"; type = "gem"; }; version = "0.2.15"; }; rex-zip = { source = { remotes = ["https://rubygems.org"]; sha256 = "1mbfryyhcw47i7jb8cs8vilbyqgyiyjkfl1ngl6wdbf7d87dwdw7"; type = "gem"; }; version = "0.1.3"; }; rkelly-remix = { source = { remotes = ["https://rubygems.org"]; sha256 = "1g7hjl9nx7f953y7lncmfgp0xgxfxvgfm367q6da9niik6rp1y3j"; type = "gem"; }; version = "0.0.7"; }; robots = { source = { remotes = ["https://rubygems.org"]; sha256 = "141gvihcr2c0dpzl3dqyh8kqc9121prfdql2iamaaw0mf9qs3njs"; type = "gem"; }; version = "0.10.1"; }; ruby_smb = { source = { remotes = ["https://rubygems.org"]; sha256 = "1v2acyx6csndb08sidb1pbixn2dlx9s75cpnjv4riwj0qlp8blli"; type = "gem"; }; version = "0.0.12"; }; rubyntlm = { source = { remotes = ["https://rubygems.org"]; sha256 = "1p6bxsklkbcqni4bcq6jajc2n57g0w5rzn4r49c3lb04wz5xg0dy"; type = "gem"; }; version = "0.6.2"; }; rubyzip = { source = { remotes = ["https://rubygems.org"]; sha256 = "06js4gznzgh8ac2ldvmjcmg9v1vg9llm357yckkpylaj6z456zqz"; type = "gem"; }; version = "1.2.1"; }; sawyer = { source = { remotes = ["https://rubygems.org"]; sha256 = "0sv1463r7bqzvx4drqdmd36m7rrv6sf1v3c6vswpnq3k6vdw2dvd"; type = "gem"; }; version = "0.8.1"; }; sqlite3 = { source = { remotes = ["https://rubygems.org"]; sha256 = "01ifzp8nwzqppda419c9wcvr8n82ysmisrs0hph9pdmv1lpa4f5i"; type = "gem"; }; version = "1.3.13"; }; sshkey = { source = { remotes = ["https://rubygems.org"]; sha256 = "0g02lh50jd5z4l9bp7xirnfn3n1dh9lr06dv3xh0kr3yhsny059h"; type = "gem"; }; version = "1.9.0"; }; thor = { source = { remotes = ["https://rubygems.org"]; sha256 = "01n5dv9kql60m6a00zc0r66jvaxx98qhdny3klyj0p3w34pad2ns"; type = "gem"; }; version = "0.19.4"; }; thread_safe = { source = { remotes = ["https://rubygems.org"]; sha256 = "0nmhcgq6cgz44srylra07bmaw99f5271l0dpsvl5f75m44l0gmwy"; type = "gem"; }; version = "0.3.6"; }; tzinfo = { source = { remotes = ["https://rubygems.org"]; sha256 = "05r81lk7q7275rdq7xipfm0yxgqyd2ggh73xpc98ypngcclqcscl"; type = "gem"; }; version = "1.2.3"; }; tzinfo-data = { source = { remotes = ["https://rubygems.org"]; sha256 = "1n83rmy476d4qmzq74qx0j7lbcpskbvrj1bmy3np4d5pydyw2yky"; type = "gem"; }; version = "1.2017.2"; }; windows_error = { source = { remotes = ["https://rubygems.org"]; sha256 = "0kbcv9j5sc7pvjzf1dkp6h69i6lmj205zyy2arxcfgqg11bsz2kp"; type = "gem"; }; version = "0.1.2"; }; xmlrpc = { source = { remotes = ["https://rubygems.org"]; sha256 = "1s744iwblw262gj357pky3d9fcx9hisvla7rnw29ysn5zsb6i683"; type = "gem"; }; version = "0.3.0"; }; } </ins>


Question:
The metasploit package no longer builds. I've updating it myself, but I haven't been very successful. If someone could point out my mistake I would gladly correct it and submit a PR.
Is this issue still relevant? , (pinging you because you are able to close this if necessary)
Looks relevant to me, as there was no commit to metasploit that updates or fixes it. Why do you think I isn't relevant anymore?
Current version: 3.3.1 Last stable version: 4.12 We definitely need a maintainer. is there a tag for ?

<ins> # Env to update Gemfile.lock / gemset.nix with import <nixpkgs> {}; stdenv.mkDerivation { name = "env"; buildInputs = [ sqlite libpcap postgresql libxml2 libxslt pkgconfig bundix ]; } </ins>


Question:
The metasploit package no longer builds. I've updating it myself, but I haven't been very successful. If someone could point out my mistake I would gladly correct it and submit a PR.
Is this issue still relevant? , (pinging you because you are able to close this if necessary)
Looks relevant to me, as there was no commit to metasploit that updates or fixes it. Why do you think I isn't relevant anymore?
Current version: 3.3.1 Last stable version: 4.12 We definitely need a maintainer. is there a tag for ?

mscgen = callPackage ../tools/graphics/mscgen { }; <del> msf = callPackage ../tools/security/metasploit { }; </del> <ins> metasploit = callPackage ../tools/security/metasploit { }; msf = metasploit; </ins> ms-sys = callPackage ../tools/misc/ms-sys { };


Question:
Project description This flag is available in most other major distros. It is necessary to enable screen sharing on wayland inside of chromium, combined with xlr-desktop-portal-wlr and pipewire. It requires the build flag and a dependency on libpipewire02. See as an example. Metadata homepage URL: source URL: license: mit, bsd, gpl2+ , ... platforms: unix, linux, darwin, ...
that would definitely be nice to have :) I actually also noticed this but unfortunately cannot test this easily as I'm not using screen sharing. If you could contribute a PR that would be awesome (but be aware that Chromium does unfortunately take quite some time to compile). Alternatively (but less preferably) we could make the required changes with the next update and test the core functionality (as always) and you could test screen sharing after the new version is available in the binary caches. Additionally we would need to package in Nixpkgs to make this work on wlroots based compositors. On Gnome/KDE this might work out-of-the-box, but I don't know what they currently implement/provide.
was just merged w/ . I'll try building chromium w/ the flag - as you say it takes a while, so I can leave it overnight and give it a shot.
how does the situation look like with ? Is the flag available there, as in, screensharing with wayland already works there?
yes, it's available in google-chrome. ! I'm still trying to get it to work with xlr-desktop-portal-wlr - I've done this in the past, but it's not working out of the box yet with
And just to make sure, you also did set as described there?
yes I did. I'm almost got it working I think. There are a few issues out of the box: -chrome is missing the pipewire 0.2 runtime dependency, so I it as (I'm on 20.03 so pkgs.pipewire is 0.2): .pipewire service doesn't work - it doesn't seem to be setting up the path correctly. I'm trying to fix this now: My current config on 20.03 looks like: Where is the same package that was recently merged.
yeah, I'm currently already looking at it - pipewire wants to execute , but it's not in . We can patch to contain the absolute path. I'll check if it works and will get back to you.
Btw, we /really/ need a sway NixOS test, and better documentation on how to use sway. I was trying stuff until it worked, and does autologin me into a sway, but there might be a smarter way to do this, without also starting X.
The sway recommendation is to just run sway from the terminal after login - that's how I do it at least. I was able to workaround the environment issue by doing (but this is a kludge I think and shouldn't be necessary). But unfortunately it's now crashing and I'm not sure why:
Yeah, even my sddm config I also had to , otherwise pipewire complained about not being able to reach dbus: Afterwards, it segfaulted, as it wasn't able to find ; I patched to be able to find the path to , and that error message is gone. Now (apart from not being able to find bluez or rtkit) it /might/ only be some version incompatibilities, not sure: I'll see if I can get as far with your chromium PR, will merge that then, and also submit the pipewire patch.
Okay, with the pipewire patch and , It seems I'm able to share at least my own application window :tada:. I don't know yet why the alacritty window nearby isn't shown, and why "Entire Screen" is black, but that's probably due to me running sway inside X via ssdm.
pipewire PRs:
I don't think you're using pipewire in that case. xdg-desktop-portal-wlr only supports full screen sharing atm. If it is black that means it's not working. By the way I had to add pipewire02 to my system packages to prevent xdg-desktop-portal from crashing. But now there seems to be some incompatibility in the pipewire service logs when chrome tries to connect:
you should be able to cherry-pick the to not have to manually add this to $PATH.
Thanks! I'm suspecting google-chrome is compiled with a too old version of pipewire. Enabling pipewire debug logs, it seems to be sending an incompatible format to the pipewire server (similar to ). I have got this working with chromium compiled against pipewire 0.2.7 in the past, so I'm pretty sure it should work assuming the client library is recent enough. Once the chromium package has that flag enabled I'll try to retest.
I just confirmed my last comment by building chromium locally w/ rtcusepipewire=true. It works perfectly for fullscreen sharing.
Hmm take that back - it worked the first time but not anymore :/. Not sure what lib is missing where.
Seems like xdg-desktop-portal is crashing:
This might be yet another version incompatibility problem. I propose merging (as it's built with 0.2 everywhere else too), and then see if we can get it to work if the system pipewire also is 0.2. I asked upstream about these problems in - maybe 0.3 needs to support 0.2 clients for some time until we should switch.
Heads-up: the bad client situation should have been fixed with the latest pipewire release, PR at
Thanks for your help! I'm still getting the xdg-desktop-portal crash, however. I'm guessing there is something missing from my dbus environment - or perhaps it's trying to access a file/directory not available in nixos.
could you open a new issue with some more details, like logs etc.?
Okay, I made

, protobuf, speechd, libXdamage, cups , ffmpeg, libxslt, libxml2, at-spi2-core , jre <ins> , pipewire_0_2 </ins> # optional dependencies , libgcrypt ? null # gnomeSupport || cupsSupport


Question:
Project description This flag is available in most other major distros. It is necessary to enable screen sharing on wayland inside of chromium, combined with xlr-desktop-portal-wlr and pipewire. It requires the build flag and a dependency on libpipewire02. See as an example. Metadata homepage URL: source URL: license: mit, bsd, gpl2+ , ... platforms: unix, linux, darwin, ...
that would definitely be nice to have :) I actually also noticed this but unfortunately cannot test this easily as I'm not using screen sharing. If you could contribute a PR that would be awesome (but be aware that Chromium does unfortunately take quite some time to compile). Alternatively (but less preferably) we could make the required changes with the next update and test the core functionality (as always) and you could test screen sharing after the new version is available in the binary caches. Additionally we would need to package in Nixpkgs to make this work on wlroots based compositors. On Gnome/KDE this might work out-of-the-box, but I don't know what they currently implement/provide.
was just merged w/ . I'll try building chromium w/ the flag - as you say it takes a while, so I can leave it overnight and give it a shot.
how does the situation look like with ? Is the flag available there, as in, screensharing with wayland already works there?
yes, it's available in google-chrome. ! I'm still trying to get it to work with xlr-desktop-portal-wlr - I've done this in the past, but it's not working out of the box yet with
And just to make sure, you also did set as described there?
yes I did. I'm almost got it working I think. There are a few issues out of the box: -chrome is missing the pipewire 0.2 runtime dependency, so I it as (I'm on 20.03 so pkgs.pipewire is 0.2): .pipewire service doesn't work - it doesn't seem to be setting up the path correctly. I'm trying to fix this now: My current config on 20.03 looks like: Where is the same package that was recently merged.
yeah, I'm currently already looking at it - pipewire wants to execute , but it's not in . We can patch to contain the absolute path. I'll check if it works and will get back to you.
Btw, we /really/ need a sway NixOS test, and better documentation on how to use sway. I was trying stuff until it worked, and does autologin me into a sway, but there might be a smarter way to do this, without also starting X.
The sway recommendation is to just run sway from the terminal after login - that's how I do it at least. I was able to workaround the environment issue by doing (but this is a kludge I think and shouldn't be necessary). But unfortunately it's now crashing and I'm not sure why:
Yeah, even my sddm config I also had to , otherwise pipewire complained about not being able to reach dbus: Afterwards, it segfaulted, as it wasn't able to find ; I patched to be able to find the path to , and that error message is gone. Now (apart from not being able to find bluez or rtkit) it /might/ only be some version incompatibilities, not sure: I'll see if I can get as far with your chromium PR, will merge that then, and also submit the pipewire patch.
Okay, with the pipewire patch and , It seems I'm able to share at least my own application window :tada:. I don't know yet why the alacritty window nearby isn't shown, and why "Entire Screen" is black, but that's probably due to me running sway inside X via ssdm.
pipewire PRs:
I don't think you're using pipewire in that case. xdg-desktop-portal-wlr only supports full screen sharing atm. If it is black that means it's not working. By the way I had to add pipewire02 to my system packages to prevent xdg-desktop-portal from crashing. But now there seems to be some incompatibility in the pipewire service logs when chrome tries to connect:
you should be able to cherry-pick the to not have to manually add this to $PATH.
Thanks! I'm suspecting google-chrome is compiled with a too old version of pipewire. Enabling pipewire debug logs, it seems to be sending an incompatible format to the pipewire server (similar to ). I have got this working with chromium compiled against pipewire 0.2.7 in the past, so I'm pretty sure it should work assuming the client library is recent enough. Once the chromium package has that flag enabled I'll try to retest.
I just confirmed my last comment by building chromium locally w/ rtcusepipewire=true. It works perfectly for fullscreen sharing.
Hmm take that back - it worked the first time but not anymore :/. Not sure what lib is missing where.
Seems like xdg-desktop-portal is crashing:
This might be yet another version incompatibility problem. I propose merging (as it's built with 0.2 everywhere else too), and then see if we can get it to work if the system pipewire also is 0.2. I asked upstream about these problems in - maybe 0.3 needs to support 0.2 clients for some time until we should switch.
Heads-up: the bad client situation should have been fixed with the latest pipewire release, PR at
Thanks for your help! I'm still getting the xdg-desktop-portal crash, however. I'm guessing there is something missing from my dbus environment - or perhaps it's trying to access a file/directory not available in nixos.
could you open a new issue with some more details, like logs etc.?
Okay, I made

libXScrnSaver libXcursor libXtst libGLU libGL pciutils protobuf speechd libXdamage at-spi2-core jre <ins> pipewire_0_2 </ins> ] ++ optional useVaapi libva ++ optional gnomeKeyringSupport libgnome-keyring3 ++ optionals gnomeSupport [ gnome.GConf libgcrypt ]


Question:
Project description This flag is available in most other major distros. It is necessary to enable screen sharing on wayland inside of chromium, combined with xlr-desktop-portal-wlr and pipewire. It requires the build flag and a dependency on libpipewire02. See as an example. Metadata homepage URL: source URL: license: mit, bsd, gpl2+ , ... platforms: unix, linux, darwin, ...
that would definitely be nice to have :) I actually also noticed this but unfortunately cannot test this easily as I'm not using screen sharing. If you could contribute a PR that would be awesome (but be aware that Chromium does unfortunately take quite some time to compile). Alternatively (but less preferably) we could make the required changes with the next update and test the core functionality (as always) and you could test screen sharing after the new version is available in the binary caches. Additionally we would need to package in Nixpkgs to make this work on wlroots based compositors. On Gnome/KDE this might work out-of-the-box, but I don't know what they currently implement/provide.
was just merged w/ . I'll try building chromium w/ the flag - as you say it takes a while, so I can leave it overnight and give it a shot.
how does the situation look like with ? Is the flag available there, as in, screensharing with wayland already works there?
yes, it's available in google-chrome. ! I'm still trying to get it to work with xlr-desktop-portal-wlr - I've done this in the past, but it's not working out of the box yet with
And just to make sure, you also did set as described there?
yes I did. I'm almost got it working I think. There are a few issues out of the box: -chrome is missing the pipewire 0.2 runtime dependency, so I it as (I'm on 20.03 so pkgs.pipewire is 0.2): .pipewire service doesn't work - it doesn't seem to be setting up the path correctly. I'm trying to fix this now: My current config on 20.03 looks like: Where is the same package that was recently merged.
yeah, I'm currently already looking at it - pipewire wants to execute , but it's not in . We can patch to contain the absolute path. I'll check if it works and will get back to you.
Btw, we /really/ need a sway NixOS test, and better documentation on how to use sway. I was trying stuff until it worked, and does autologin me into a sway, but there might be a smarter way to do this, without also starting X.
The sway recommendation is to just run sway from the terminal after login - that's how I do it at least. I was able to workaround the environment issue by doing (but this is a kludge I think and shouldn't be necessary). But unfortunately it's now crashing and I'm not sure why:
Yeah, even my sddm config I also had to , otherwise pipewire complained about not being able to reach dbus: Afterwards, it segfaulted, as it wasn't able to find ; I patched to be able to find the path to , and that error message is gone. Now (apart from not being able to find bluez or rtkit) it /might/ only be some version incompatibilities, not sure: I'll see if I can get as far with your chromium PR, will merge that then, and also submit the pipewire patch.
Okay, with the pipewire patch and , It seems I'm able to share at least my own application window :tada:. I don't know yet why the alacritty window nearby isn't shown, and why "Entire Screen" is black, but that's probably due to me running sway inside X via ssdm.
pipewire PRs:
I don't think you're using pipewire in that case. xdg-desktop-portal-wlr only supports full screen sharing atm. If it is black that means it's not working. By the way I had to add pipewire02 to my system packages to prevent xdg-desktop-portal from crashing. But now there seems to be some incompatibility in the pipewire service logs when chrome tries to connect:
you should be able to cherry-pick the to not have to manually add this to $PATH.
Thanks! I'm suspecting google-chrome is compiled with a too old version of pipewire. Enabling pipewire debug logs, it seems to be sending an incompatible format to the pipewire server (similar to ). I have got this working with chromium compiled against pipewire 0.2.7 in the past, so I'm pretty sure it should work assuming the client library is recent enough. Once the chromium package has that flag enabled I'll try to retest.
I just confirmed my last comment by building chromium locally w/ rtcusepipewire=true. It works perfectly for fullscreen sharing.
Hmm take that back - it worked the first time but not anymore :/. Not sure what lib is missing where.
Seems like xdg-desktop-portal is crashing:
This might be yet another version incompatibility problem. I propose merging (as it's built with 0.2 everywhere else too), and then see if we can get it to work if the system pipewire also is 0.2. I asked upstream about these problems in - maybe 0.3 needs to support 0.2 clients for some time until we should switch.
Heads-up: the bad client situation should have been fixed with the latest pipewire release, PR at
Thanks for your help! I'm still getting the xdg-desktop-portal crash, however. I'm guessing there is something missing from my dbus environment - or perhaps it's trying to access a file/directory not available in nixos.
could you open a new issue with some more details, like logs etc.?
Okay, I made

# added later in the wrapped -wv build or downloaded from Google. enable_widevine = true; use_cups = cupsSupport; <ins> # Provides the enable-webrtc-pipewire-capturer flag to support Wayland screen capture. rtc_use_pipewire = true; </ins> treat_warnings_as_errors = false; is_clang = stdenv.cc.isClang;


Question:
Project description This flag is available in most other major distros. It is necessary to enable screen sharing on wayland inside of chromium, combined with xlr-desktop-portal-wlr and pipewire. It requires the build flag and a dependency on libpipewire02. See as an example. Metadata homepage URL: source URL: license: mit, bsd, gpl2+ , ... platforms: unix, linux, darwin, ...
that would definitely be nice to have :) I actually also noticed this but unfortunately cannot test this easily as I'm not using screen sharing. If you could contribute a PR that would be awesome (but be aware that Chromium does unfortunately take quite some time to compile). Alternatively (but less preferably) we could make the required changes with the next update and test the core functionality (as always) and you could test screen sharing after the new version is available in the binary caches. Additionally we would need to package in Nixpkgs to make this work on wlroots based compositors. On Gnome/KDE this might work out-of-the-box, but I don't know what they currently implement/provide.
was just merged w/ . I'll try building chromium w/ the flag - as you say it takes a while, so I can leave it overnight and give it a shot.
how does the situation look like with ? Is the flag available there, as in, screensharing with wayland already works there?
yes, it's available in google-chrome. ! I'm still trying to get it to work with xlr-desktop-portal-wlr - I've done this in the past, but it's not working out of the box yet with
And just to make sure, you also did set as described there?
yes I did. I'm almost got it working I think. There are a few issues out of the box: -chrome is missing the pipewire 0.2 runtime dependency, so I it as (I'm on 20.03 so pkgs.pipewire is 0.2): .pipewire service doesn't work - it doesn't seem to be setting up the path correctly. I'm trying to fix this now: My current config on 20.03 looks like: Where is the same package that was recently merged.
yeah, I'm currently already looking at it - pipewire wants to execute , but it's not in . We can patch to contain the absolute path. I'll check if it works and will get back to you.
Btw, we /really/ need a sway NixOS test, and better documentation on how to use sway. I was trying stuff until it worked, and does autologin me into a sway, but there might be a smarter way to do this, without also starting X.
The sway recommendation is to just run sway from the terminal after login - that's how I do it at least. I was able to workaround the environment issue by doing (but this is a kludge I think and shouldn't be necessary). But unfortunately it's now crashing and I'm not sure why:
Yeah, even my sddm config I also had to , otherwise pipewire complained about not being able to reach dbus: Afterwards, it segfaulted, as it wasn't able to find ; I patched to be able to find the path to , and that error message is gone. Now (apart from not being able to find bluez or rtkit) it /might/ only be some version incompatibilities, not sure: I'll see if I can get as far with your chromium PR, will merge that then, and also submit the pipewire patch.
Okay, with the pipewire patch and , It seems I'm able to share at least my own application window :tada:. I don't know yet why the alacritty window nearby isn't shown, and why "Entire Screen" is black, but that's probably due to me running sway inside X via ssdm.
pipewire PRs:
I don't think you're using pipewire in that case. xdg-desktop-portal-wlr only supports full screen sharing atm. If it is black that means it's not working. By the way I had to add pipewire02 to my system packages to prevent xdg-desktop-portal from crashing. But now there seems to be some incompatibility in the pipewire service logs when chrome tries to connect:
you should be able to cherry-pick the to not have to manually add this to $PATH.
Thanks! I'm suspecting google-chrome is compiled with a too old version of pipewire. Enabling pipewire debug logs, it seems to be sending an incompatible format to the pipewire server (similar to ). I have got this working with chromium compiled against pipewire 0.2.7 in the past, so I'm pretty sure it should work assuming the client library is recent enough. Once the chromium package has that flag enabled I'll try to retest.
I just confirmed my last comment by building chromium locally w/ rtcusepipewire=true. It works perfectly for fullscreen sharing.
Hmm take that back - it worked the first time but not anymore :/. Not sure what lib is missing where.
Seems like xdg-desktop-portal is crashing:
This might be yet another version incompatibility problem. I propose merging (as it's built with 0.2 everywhere else too), and then see if we can get it to work if the system pipewire also is 0.2. I asked upstream about these problems in - maybe 0.3 needs to support 0.2 clients for some time until we should switch.
Heads-up: the bad client situation should have been fixed with the latest pipewire release, PR at
Thanks for your help! I'm still getting the xdg-desktop-portal crash, however. I'm guessing there is something missing from my dbus environment - or perhaps it's trying to access a file/directory not available in nixos.
could you open a new issue with some more details, like logs etc.?
Okay, I made

, makeWrapper, ed , glib, gtk3, gnome3, gsettings-desktop-schemas, gn, fetchgit , libva ? null <ins> , pipewire_0_2 </ins> , gcc, nspr, nss, patchelfUnstable, runCommand , lib


Question:
Project description This flag is available in most other major distros. It is necessary to enable screen sharing on wayland inside of chromium, combined with xlr-desktop-portal-wlr and pipewire. It requires the build flag and a dependency on libpipewire02. See as an example. Metadata homepage URL: source URL: license: mit, bsd, gpl2+ , ... platforms: unix, linux, darwin, ...
that would definitely be nice to have :) I actually also noticed this but unfortunately cannot test this easily as I'm not using screen sharing. If you could contribute a PR that would be awesome (but be aware that Chromium does unfortunately take quite some time to compile). Alternatively (but less preferably) we could make the required changes with the next update and test the core functionality (as always) and you could test screen sharing after the new version is available in the binary caches. Additionally we would need to package in Nixpkgs to make this work on wlroots based compositors. On Gnome/KDE this might work out-of-the-box, but I don't know what they currently implement/provide.
was just merged w/ . I'll try building chromium w/ the flag - as you say it takes a while, so I can leave it overnight and give it a shot.
how does the situation look like with ? Is the flag available there, as in, screensharing with wayland already works there?
yes, it's available in google-chrome. ! I'm still trying to get it to work with xlr-desktop-portal-wlr - I've done this in the past, but it's not working out of the box yet with
And just to make sure, you also did set as described there?
yes I did. I'm almost got it working I think. There are a few issues out of the box: -chrome is missing the pipewire 0.2 runtime dependency, so I it as (I'm on 20.03 so pkgs.pipewire is 0.2): .pipewire service doesn't work - it doesn't seem to be setting up the path correctly. I'm trying to fix this now: My current config on 20.03 looks like: Where is the same package that was recently merged.
yeah, I'm currently already looking at it - pipewire wants to execute , but it's not in . We can patch to contain the absolute path. I'll check if it works and will get back to you.
Btw, we /really/ need a sway NixOS test, and better documentation on how to use sway. I was trying stuff until it worked, and does autologin me into a sway, but there might be a smarter way to do this, without also starting X.
The sway recommendation is to just run sway from the terminal after login - that's how I do it at least. I was able to workaround the environment issue by doing (but this is a kludge I think and shouldn't be necessary). But unfortunately it's now crashing and I'm not sure why:
Yeah, even my sddm config I also had to , otherwise pipewire complained about not being able to reach dbus: Afterwards, it segfaulted, as it wasn't able to find ; I patched to be able to find the path to , and that error message is gone. Now (apart from not being able to find bluez or rtkit) it /might/ only be some version incompatibilities, not sure: I'll see if I can get as far with your chromium PR, will merge that then, and also submit the pipewire patch.
Okay, with the pipewire patch and , It seems I'm able to share at least my own application window :tada:. I don't know yet why the alacritty window nearby isn't shown, and why "Entire Screen" is black, but that's probably due to me running sway inside X via ssdm.
pipewire PRs:
I don't think you're using pipewire in that case. xdg-desktop-portal-wlr only supports full screen sharing atm. If it is black that means it's not working. By the way I had to add pipewire02 to my system packages to prevent xdg-desktop-portal from crashing. But now there seems to be some incompatibility in the pipewire service logs when chrome tries to connect:
you should be able to cherry-pick the to not have to manually add this to $PATH.
Thanks! I'm suspecting google-chrome is compiled with a too old version of pipewire. Enabling pipewire debug logs, it seems to be sending an incompatible format to the pipewire server (similar to ). I have got this working with chromium compiled against pipewire 0.2.7 in the past, so I'm pretty sure it should work assuming the client library is recent enough. Once the chromium package has that flag enabled I'll try to retest.
I just confirmed my last comment by building chromium locally w/ rtcusepipewire=true. It works perfectly for fullscreen sharing.
Hmm take that back - it worked the first time but not anymore :/. Not sure what lib is missing where.
Seems like xdg-desktop-portal is crashing:
This might be yet another version incompatibility problem. I propose merging (as it's built with 0.2 everywhere else too), and then see if we can get it to work if the system pipewire also is 0.2. I asked upstream about these problems in - maybe 0.3 needs to support 0.2 clients for some time until we should switch.
Heads-up: the bad client situation should have been fixed with the latest pipewire release, PR at
Thanks for your help! I'm still getting the xdg-desktop-portal crash, however. I'm guessing there is something missing from my dbus environment - or perhaps it's trying to access a file/directory not available in nixos.
could you open a new issue with some more details, like logs etc.?
Okay, I made

buildCommand = let browserBinary = "${chromiumWV}/libexec/chromium/chromium"; getWrapperFlags = plugin: "$(< "${plugin}/nix-support/wrapper-flags")"; <del> libPath = stdenv.lib.makeLibraryPath [ libva ]; </del> <ins> libPath = stdenv.lib.makeLibraryPath [ libva pipewire_0_2 ]; </ins> in with stdenv.lib; '' mkdir -p "$out/bin"


Question:
Project description Cross platform chewing user phrase editor Chewing editor is a widely-used bopomofo input method for traditional Chinese, and chewing-editor is the tool to edit the database of user phrases stored by the input method. Users of chewing will need chewing-editor sooner or later. NixOS have chewing include as a fcitx engine () that can be used in the module, but not chewing-editor. Metadata homepage URL: source URL: license: gpl2 platforms: unix
The corresponding pull request is merged. Closing.

githubId = 24496705; name = "Scott Hamilton"; }; <ins> ShamrockLee = { name = "Shamrock Lee"; email = "44064051+ShamrockLee@users.noreply.github.com"; github = "ShamrockLee"; githubId = 44064051; }; </ins> shanemikel = { email = "shanepearlman@pm.me"; github = "shanemikel";


Question:
Project description Cross platform chewing user phrase editor Chewing editor is a widely-used bopomofo input method for traditional Chinese, and chewing-editor is the tool to edit the database of user phrases stored by the input method. Users of chewing will need chewing-editor sooner or later. NixOS have chewing include as a fcitx engine () that can be used in the module, but not chewing-editor. Metadata homepage URL: source URL: license: gpl2 platforms: unix
The corresponding pull request is merged. Closing.

<ins> { stdenv, mkDerivation, fetchFromGitHub, cmake, pkgconfig, libchewing, qtbase , qttools }: mkDerivation rec { pname = "chewing-editor"; version = "0.1.1"; src = fetchFromGitHub { owner = "chewing"; repo = "${pname}"; rev = "${version}"; sha256 = "0kc2hjx1gplm3s3p1r5sn0cyxw3k1q4gyv08q9r6rs4sg7xh2w7w"; }; doCheck = true; nativeBuildInputs = [ cmake pkgconfig ]; buildInputs = [ libchewing qtbase qttools ]; meta = with stdenv.lib; { description = "Cross platform chewing user phrase editor"; longDescription = '' chewing-editor is a cross platform chewing user phrase editor. It provides a easy way to manage user phrase. With it, user can customize their user phrase to increase input performance. ''; homepage = "https://github.com/chewing/chewing-editor"; license = licenses.gpl2Plus; maintainers = [ maintainers.ShamrockLee ]; platforms = platforms.all; }; } </ins>


Question:
Project description Cross platform chewing user phrase editor Chewing editor is a widely-used bopomofo input method for traditional Chinese, and chewing-editor is the tool to edit the database of user phrases stored by the input method. Users of chewing will need chewing-editor sooner or later. NixOS have chewing include as a fcitx engine () that can be used in the module, but not chewing-editor. Metadata homepage URL: source URL: license: gpl2 platforms: unix
The corresponding pull request is merged. Closing.

fcitx-configtool = callPackage ../tools/inputmethods/fcitx/fcitx-configtool.nix { }; <ins> chewing-editor = libsForQt5.callPackage ../applications/misc/chewing-editor { }; </ins> fcppt = callPackage ../development/libraries/fcppt { }; fcrackzip = callPackage ../tools/security/fcrackzip { };


Question:
Describe the bug pitivi crashes with gtk errors on startup. To Reproduce Steps to reproduce the behavior: in terminal and press enter the error message: Additional context This happens at least on wayland/sway. Notify maintainers as he did the last change to the packet and no maintainer is defined. Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
I get a different error with nix on Ubuntu on commit : On on Ubuntu it works.
PR in .

mv data/org.pitivi.Pitivi-mime.xml data/org.pitivi.Pitivi-mime.xml.in ''; <ins> # Fixes error #     Couldn’t recognize the image file format for file ".../share/pitivi/pixmaps/asset-proxied.svg" # at startup, see https://github.com/NixOS/nixpkgs/issues/56943 # and https://github.com/NixOS/nixpkgs/issues/89691#issuecomment-714398705. strictDeps = false; </ins> passthru = { updateScript = gnome3.updateScript { packageName = "pitivi";


Question: Describe the bug cannot be built from current master due to failing tests. To Reproduce Additional context Relevant logs: Notify maintainers Metadata Please run and paste the result. Maintainer information:

<ins> From acab088fd6af0b2ef2df1396aeb93bfc2e020fa5 Mon Sep 17 00:00:00 2001 From: "Yukihiro "Matz" Matsumoto" <matz@ruby.or.jp> Date: Mon, 27 Apr 2020 18:52:43 +0900 Subject: [PATCH 1/2] Updating `parse.y for recent `bison` (retry). --- mrbgems/mruby-compiler/core/parse.y | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mrbgems/mruby-compiler/core/parse.y b/mrbgems/mruby-compiler/core/parse.y index 6a1faf4e..2a4f740e 100644 --- a/mrbgems/mruby-compiler/core/parse.y +++ b/mrbgems/mruby-compiler/core/parse.y @@ -1323,7 +1323,7 @@ heredoc_end(parser_state *p) %} -%pure-parser +%define api.pure %parse-param {parser_state *p} %lex-param {parser_state *p} -- 2.27.0 From 3cc682d943b29e84928a847a23f411ddbace74b7 Mon Sep 17 00:00:00 2001 From: "Yukihiro "Matz" Matsumoto" <matz@ruby.or.jp> Date: Fri, 15 May 2020 12:30:13 +0900 Subject: [PATCH 2/2] Remove `YYERROR_VERBOSE` which no longer supported since `bison 3.6`. Instead we added `%define parse.error verbose`. --- mrbgems/mruby-compiler/core/parse.y | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mrbgems/mruby-compiler/core/parse.y b/mrbgems/mruby-compiler/core/parse.y index 2a4f740e..eee6a5e5 100644 --- a/mrbgems/mruby-compiler/core/parse.y +++ b/mrbgems/mruby-compiler/core/parse.y @@ -9,7 +9,6 @@ #ifdef PARSER_DEBUG # define YYDEBUG 1 #endif -#define YYERROR_VERBOSE 1 #define YYSTACK_USE_ALLOCA 1 #include <ctype.h> @@ -1323,6 +1322,7 @@ heredoc_end(parser_state *p) %} +%define parse.error verbose %define api.pure %parse-param {parser_state *p} %lex-param {parser_state *p} -- 2.27.0 </ins>


Question: Describe the bug cannot be built from current master due to failing tests. To Reproduce Additional context Relevant logs: Notify maintainers Metadata Please run and paste the result. Maintainer information:

<del> { stdenv, ruby, bison, fetchFromGitHub }: </del> <ins> { stdenv, ruby, bison, rake, fetchFromGitHub }: </ins> stdenv.mkDerivation rec { pname = "mruby"; <del> version = "2.1.0"; </del> <ins> version = "2.1.1"; </ins> src = fetchFromGitHub { owner   = "mruby"; repo    = "mruby"; rev     = version; <del> sha256  = "1y072c7dh9jf8xwy7kia6cb4dkpspq4zf24ssn7zm5f46p4waxni"; </del> <ins> sha256  = "gEEb0Vn/G+dNgeY6r0VP8bMSPrEOf5s+0GoOcnIPtEU="; </ins> }; <del> nativeBuildInputs = [ ruby bison ]; </del> <ins> nativeBuildInputs = [ ruby bison rake ]; patches = [ ./bison-36-compat.patch ]; </ins> # Necessary so it uses `gcc` instead of `ld` for linking. # https://github.com/mruby/mruby/blob/35be8b252495d92ca811d76996f03c470ee33380/tasks/toolchains/gcc.rake#L25


Question:
Describe the bug All last builds on Hydra have failed because of (top level package). E.g. Nr Status -- -- 1 Cached failure (log, raw, tail) (propagated from build ) First broken build 2020-06-05 19:14:56: Nr Status -- -- 1 Failed (log, raw, tail) (propagated from build ) Log: To Reproduce I can't reproduce the issue locally though, does compile. Expected behavior Hydra job should not fail on mariadb. 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 $ nix-shell -p nix-info --run "nix-info -m" system: host os: multi-user?: sandbox: version: channels(theo): channels(root): channels(arsleust): nixpkgs: Maintainer information:
Reproduction: are you sure you tried it on darwin? (That's what fails on Hydra.)
Probably caused by , Darwin doesn't have .so 's right? cc

chmod +x "$out"/bin/wsrep_sst_common rm "$out"/bin/{mariadb-client-test,mariadb-test,mysql_client_test,mysqltest} rm -r "$out"/data # Don't need testing data <del> mv "$out"/OFF/suite/plugins/pam/pam_mariadb_mtr.so "$out"/share/pam/lib/security mv "$out"/OFF/suite/plugins/pam/mariadb_mtr "$out"/share/pam/etc/security rm -r "$out"/OFF </del> '' + optionalString withStorageMroonga '' mv "$out"/share/{groonga,groonga-normalizer-mysql} "$out"/share/doc/mysql '' + optionalString (!stdenv.hostPlatform.isDarwin) '' <ins> mv "$out"/OFF/suite/plugins/pam/pam_mariadb_mtr.so "$out"/share/pam/lib/security mv "$out"/OFF/suite/plugins/pam/mariadb_mtr "$out"/share/pam/etc/security rm -r "$out"/OFF </ins> sed -i 's/-mariadb/-mysql/' "$out"/bin/galera_new_cluster '';


Question:
Describe the bug Size of aarch64 sd_image has suddenly blown up a lot. whereas on commit it was To Reproduce Hydra: - - This blocks the channel ATM.
It seems this is caused by my PR here: We switched to , but does not erase the original file, while does. I created PR which hopefully fixes this by passing to .

if test -n "$compressImage"; then echo "Compressing image..." <del> zstd -T$NIX_BUILD_CORES $out/iso/$isoName </del> <ins> zstd -T$NIX_BUILD_CORES --rm $out/iso/$isoName </ins> fi mkdir -p $out/nix-support


Question:
Describe the bug Size of aarch64 sd_image has suddenly blown up a lot. whereas on commit it was To Reproduce Hydra: - - This blocks the channel ATM.
It seems this is caused by my PR here: We switched to , but does not erase the original file, while does. I created PR which hopefully fixes this by passing to .

fsck.vfat -vn firmware_part.img dd conv=notrunc if=firmware_part.img of=$img seek=$START count=$SECTORS if test -n "$compressImage"; then <del> zstd -T$NIX_BUILD_CORES $img </del> <ins> zstd -T$NIX_BUILD_CORES --rm $img </ins> fi ''; }) {};


Question:
Project description Caprine is an unofficial and privacy-focused Facebook Messenger app with many useful features. Metadata homepage URL: URL: mit platforms: linux, darwin
I marked this as stale due to inactivity. →
I'd love to have this, too. I tried to take a stab at it a while back (using Atom and other Electron apps as a base) but it kept core dumping. I'm going to have to give it another try soon.
I have a binary package PR ( ) dangling for a long time. You may want to take a look.

<ins> { lib , fetchurl , appimageTools , gtk3 , gsettings-desktop-schemas , xorg , pname , version , sha256 , metaCommon ? { } }: let name = "${pname}-${version}"; src = fetchurl { url = "https://github.com/sindresorhus/caprine/releases/download/v${version}/Caprine-${version}.AppImage"; name = "Caprine-${version}.AppImage"; inherit sha256; }; extracted = appimageTools.extractType2 { inherit name src; }; in (appimageTools.wrapType2 { inherit name src; profile = '' export LC_ALL=C.UTF-8 export XDG_DATA_DIRS=${gsettings-desktop-schemas}/share/gsettings-schemas/${gsettings-desktop-schemas.name}:${gtk3}/share/gsettings-schemas/${gtk3.name}:$XDG_DATA_DIRS ''; extraPkgs = pkgs: appimageTools.defaultFhsEnvArgs.multiPkgs pkgs; extraInstallCommands = '' mv $out/bin/{${name},caprine} mkdir -p $out/share "${xorg.lndir}/bin/lndir" -silent "${extracted}/usr/share" "$out/share" ln -s ${extracted}/caprine.png $out/share/icons/caprine.png mkdir $out/share/applications cp ${extracted}/caprine.desktop $out/share/applications/ substituteInPlace $out/share/applications/caprine.desktop  --replace AppRun caprine ''; meta = metaCommon // { platforms = [ "x86_64-linux" ]; mainProgram = "caprine"; }; }) // { inherit pname version; } </ins>


Question:
Project description Caprine is an unofficial and privacy-focused Facebook Messenger app with many useful features. Metadata homepage URL: URL: mit platforms: linux, darwin
I marked this as stale due to inactivity. →
I'd love to have this, too. I tried to take a stab at it a while back (using Atom and other Electron apps as a base) but it kept core dumping. I'm going to have to give it another try soon.
I have a binary package PR ( ) dangling for a long time. You may want to take a look.

<ins> { stdenvNoCC , lib , fetchurl , undmg , pname , version , sha256 , metaCommon ? { } }: stdenvNoCC.mkDerivation { inherit pname version; src = fetchurl { url = "https://github.com/sindresorhus/caprine/releases/download/v${version}/Caprine-${version}.dmg"; name = "Caprine-${version}.dmg"; inherit sha256; }; sourceRoot = "Caprine.app"; nativeBuildInputs = [ undmg ]; installPhase = '' mkdir -p "$out/Applications/Caprine.app" cp -R . "$out/Applications/Caprine.app" mkdir "$out/bin" ln -s "$out/Applications/Caprine.app/Contents/MacOS/Caprine" "$out/bin/caprine" ''; meta = metaCommon // { platforms = with lib.platforms; darwin; mainProgram = "caprine"; }; } </ins>


Question:
Project description Caprine is an unofficial and privacy-focused Facebook Messenger app with many useful features. Metadata homepage URL: URL: mit platforms: linux, darwin
I marked this as stale due to inactivity. →
I'd love to have this, too. I tried to take a stab at it a while back (using Atom and other Electron apps as a base) but it kept core dumping. I'm going to have to give it another try soon.
I have a binary package PR ( ) dangling for a long time. You may want to take a look.

<ins> { lib, callPackage, stdenvNoCC }: let pname = "caprine"; version = "2.55.2"; metaCommon = with lib; { description = "An elegant Facebook Messenger desktop app"; homepage = "https://sindresorhus.com/caprine"; license = licenses.mit; maintainers = with maintainers; [ ShamrockLee ]; }; x86_64-appimage = callPackage ./build-from-appimage.nix { inherit pname version metaCommon; sha256 = "J7eHVXjWSIcTpLMM8FlGKZzVh6XgpQ0d82kxfMbPyZ4="; }; x86_64-dmg = callPackage ./build-from-dmg.nix { inherit pname version metaCommon; sha256 = "du/9N1BFq1s7spPiEDgDbjjcnkA0x1ExhAEpQvmO3aA="; }; in (if stdenvNoCC.isDarwin then x86_64-dmg else x86_64-appimage).overrideAttrs (oldAttrs: { passthru = (oldAttrs.passthru or { }) // { inherit x86_64-appimage x86_64-dmg; }; meta = oldAttrs.meta // { platforms = x86_64-appimage.meta.platforms ++ x86_64-dmg.meta.platforms; }; }) </ins>