Cannot install dependencies for fresh clone repo. Encounter a checksum error.

Preflight Checklist

• I have read the Contributing Guidelines for this project.
• I have searched the issue tracker for an issue that matches the one I want to file, without success.

Issue Details

• Operating System: Mac OS Monterey 12.3
• Yarn version: 3.1.1
• NodeJs: 17.7.1

Expected Behavior

After I clone the repo and install dependencies using yarn, the dependencies should be successfully installed.

Actual Behavior

There is a checksum error while install dependencies in package remark-license.

➜  cloud-carbon-footprint git:(trunk) yarn install
➤ YN0000: ┌ Resolution step
➤ YN0002: │ @cloud-carbon-footprint/client@workspace:packages/client doesn't provide @mui/system (p634cd), requested by @mui/x-data-grid
➤ YN0060: │ @cloud-carbon-footprint/client@workspace:packages/client provides react (p81d5a) with version 17.0.2, which doesn't satisfy what react-dates and some of its descendants request
➤ YN0060: │ @cloud-carbon-footprint/client@workspace:packages/client provides react-dom (pf11c5) with version 17.0.2, which doesn't satisfy what react-dates and some of its descendants request
➤ YN0002: │ @cloud-carbon-footprint/create-app@workspace:packages/create-app doesn't provide @types/node (p1b472), requested by ts-node
➤ YN0002: │ @cloud-carbon-footprint/create-app@workspace:packages/create-app doesn't provide prettier (pce2c2), requested by eslint-plugin-prettier
➤ YN0002: │ @cloud-carbon-footprint/integration-tests@workspace:packages/integration-tests doesn't provide @babel/core (pe0805), requested by @babel/eslint-parser
➤ YN0002: │ eslint-config-react-app@npm:7.0.1 [896c2] doesn't provide @babel/plugin-syntax-flow (p648c1), requested by eslint-plugin-flowtype
➤ YN0002: │ eslint-config-react-app@npm:7.0.1 [896c2] doesn't provide @babel/plugin-transform-react-jsx (pcecbf), requested by eslint-plugin-flowtype
➤ YN0002: │ react-dev-utils@npm:12.0.1 doesn't provide typescript (p59348), requested by fork-ts-checker-webpack-plugin
➤ YN0002: │ react-dev-utils@npm:12.0.1 doesn't provide webpack (p1012e), requested by fork-ts-checker-webpack-plugin
➤ YN0002: │ root@workspace:. doesn't provide @types/node (p23cb6), requested by ts-node
➤ YN0002: │ testcafe-reporter-dashboard@npm:1.0.0-rc.1 doesn't provide fp-ts (pe5446), requested by io-ts-types
➤ YN0002: │ testcafe-reporter-dashboard@npm:1.0.0-rc.1 doesn't provide fp-ts (pe1a1d), requested by io-ts
➤ YN0002: │ testcafe-reporter-dashboard@npm:1.0.0-rc.1 doesn't provide fp-ts (p1dfe6), requested by monocle-ts
➤ YN0002: │ testcafe-reporter-dashboard@npm:1.0.0-rc.1 doesn't provide fp-ts (pc987e), requested by newtype-ts
➤ YN0002: │ ts-node-dev@npm:2.0.0 [88b31] doesn't provide @types/node (p1cab1), requested by ts-node
➤ YN0002: │ xo@npm:0.49.0 doesn't provide webpack (p35719), requested by eslint-import-resolver-webpack
➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
➤ YN0013: │ remark-license@https://github.com/niftylettuce/remark-license.git#commit=17ecb8f64f8f6082414d14f9267a12764e6ddbfb can't be found in the ca
➤ YN0013: │ remark-license@https://github.com/niftylettuce/remark-license.git#commit=17ecb8f64f8f6082414d14f9267a12764e6ddbfb can't be found in the ca
➤ YN0018: │ remark-license@https://github.com/niftylettuce/remark-license.git#commit=17ecb8f64f8f6082414d14f9267a12764e6ddbfb: The remote archive doesn't match the expected checksum
➤ YN0000: └ Completed in 3s 262ms
➤ YN0000: Failed with errors in 3s 406ms

To Reproduce

1. Clone new repo
2. yarn

Additional Information

For workaround:

YARN_CHECKSUM_BEHAVIOR=update yarn

But this going to update checksum in yarn.lock locally.

I think it would be great if we can update checksum in this repo so the installation is smooth.

© 2021 Thoughtworks, Inc.

[chrisza-tw]

@4upz The new lock file works for me. Thanks!

[4upz]

Great! I’ll go ahead and close this issue. Let us know if you have any other trouble! We also have other tasks that are open to contributors on our project board. Feel free to take a look and let us know if you’d like to contribute elsewhere. 😁