Daniel Lo Nigro

Indeed, looks like `wget` is installed on a lot more Debian systems compared to `curl`, at least according to the (opt-in) popularity contest: https://qa.debian.org/popcon-graph.php?packages=wget+curl&show_installed=on&want_legend=on&want_ticks=on&from_date=&to_date=&hlght_date=&date_fmt=%25Y-%25m&beenhere=1  Would you like to submit...

@Haroenv Any ideas here?

@arye-dov-eidelman - Thanks for the report. I think that's due to some bad redirects on the new site. It's redirecting: - https://yarn.pm/react - https://yarnpkg.com/en/package/react - https://legacy.yarnpkg.com/lang/en/package/react - https://legacy.yarnpkg.com/en/lang/en/package/react The new...

Actually I just realised that the package listing DOES exist on the new site, just without the `/en/` in the URL. I'll update the redirect to go to the non-`/en/`...

Yeah, this was a command available in the original Yarn release, but it was removed at some point.

I started working on this in #592 but never finished it. Would you like to take a look and try to rebase it?

Oh, good point. Feel free to submit a pull request for this, otherwise I may do it at some point. 👍

Duplicating is fine. We already show the path stuff for RC and nightly releases for some Linux distros where you need to use the installer rather than the package (eg....

> The SHA-1 issue is open for 1.5 years I think that's being addressed in https://github.com/yarnpkg/yarn/pull/5042?

Using a custom keyring seems like a reasonable approach, depending on complexity.