Can you remove azure-cli?

https://www.npmjs.com/package/azure-cli

It was deprecated by microsoft and no longer builds.

Apart from that I have opened tickets for all broken packages.

I'd also offer to have a look later tonight :)

All the packages were that I mentioned were also broken before.

From what I can see the builds for azure-cli were successful some weeks ago: https://hydra.nixos.org/job/nixos/trunk-combined/nixpkgs.azure-cli.x86_64-linux/all

It seems as shortly after the succeeding build most of the node packages have been moved to NodeJS 10 by default (25d6dc9), so I guess it's worth a try building this against Node 8 again (which is IMHO out of scope here though).

I'd propose to do the following:

• marking quassel-webserver, meguca and azure-cli as broken and merge this (the rest seems fine).
• file a new patch (I could do this as well unless one of you wants to take over) where I try to get azure-cli building with NodeJS 8 for now. The package itself is deprecated and should be replaced with a python-based azure-cli in the long term (IIRC some folks wanted to work on this), until then I'd prefer to have at least the old version support as it doesn't seem dead yet (at least as long as we don't have security-related concerns)

@Ma27 See: #36528 for azure-cli. I don't think we will able to get notified about security issues in our npm package set. That's why I would not include packages that are no longer upstream maintained.

I'll check if azure-cli works fine with node8Packages. Other than that, is there anything blocking this? :-)

Latest commit moves azure-cli to node--packages-v8.json and regenerates the package set.

I pushed a commit which marks the remaining to packages as broken, it seems fine for me now.

@Ma27 See: #36528 for azure-cli. I don't think we will able to get notified about security issues in our npm package set. That's why I would not include packages that are no longer upstream maintained.

Yeah, I've seen several tickets requesting the change as well, so I'm optimistic that this issue can be resolved soon. Regarding the package security issues: I agree for transitive dependencies deep inside the dependency tree, but this package doesn't seem to be dead yet and is the top-level package with a locked package set.

ah great! In that case I'd revert my commit and regenerate the package set (a.k.a resolve the conflicts)

@the-kenny FYI I rebased your changes onto master (where meguca got fixed and quassel-webserver got removed which resolves all merge conflicts btw).

To make the rebase easier, I squashed both regenerations into one commit and confirmed that it works by running nix-review rev 6d21e8d361157697dfe870f90eddceacecc3e576. I'll wait for ofBorg to evaluate, then this is mergable IMHO.

@the-kenny thanks!

Awesome! Thank you all :-)