[DRE-maint] Bug#995073: gitlab: yarnpkg fails with error An unexpected error occurred: "Release not found: 2.4.2".

Pirate Praveen praveen at onenetbeyond.org
Mon Sep 27 21:23:44 BST 2021



On 26 September 2021 8:14:08 pm IST, Ondrej Zary <ondrej at zary.sk> wrote:
>> yarn 3.0 needs nodejs 12. So this was a work around used to force yarn
>> 2.x. Looks like there is no way to install 2.x versions of yarn anymore :(
>>
>> So we will have to update minimum version of nodejs to 12 (already done
>> for latest versions in bullseye) and use yarn set version berry. I guess
>> you will have to use nodejs from official repos or we will have to
>> backport nodejs 12 to buster.
>
>I've built nodejs 12 and added "yarnpng set version berry" before
>"yarnpkg set version 2.4.2".
>It downloaded tons of random crap from somewhere during the "fetch step".
>Is that normal?

Not sure which packages it pulls in that step.

>Otherwise it seems to work.
>Webpack failed, as always...3 kinds of errors this time.
>
>Installing node modules...
>(node:22064) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
>Resolving berry to a url...
>Downloading https://github.com/yarnpkg/berry/raw/master/packages/berry-cli/bin/berry.js...
>Saving it into /var/lib/gitlab/.yarn/releases/yarn-berry.js...
>Updating /var/lib/gitlab/.yarnrc.yml...
>Done!
>➤ YN0000: Retrieving https://repo.yarnpkg.com/2.4.2/packages/yarnpkg-cli/bin/yarn.js
>➤ YN0000: Saving the new release in .yarn/releases/yarn-2.4.2.cjs
>➤ YN0000: Done in 1s 327ms
>➤ YN0000: ┌ Resolution step
>➤ YN0061: │ document-register-element at npm:1.14.3 is deprecated: V0 is gone and the best V1 polyfill is now @ungap/custom-elements
>➤ YN0061: │ axios at npm:0.20.0 is deprecated: Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410
>➤ YN0061: │ urix at npm:0.1.0 is deprecated: Please see https://github.com/lydell/urix#deprecated
>➤ YN0061: │ smooshpack at npm:0.0.62 is deprecated: Package moved to @codesandbox/sandpack-client
>➤ YN0061: │ resolve-url at npm:0.2.1 is deprecated: https://github.com/lydell/resolve-url#deprecated
>➤ YN0061: │ uuid at npm:3.3.2 is deprecated: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
>➤ YN0061: │ popper.js at npm:1.16.1 is deprecated: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1
>➤ YN0061: │ querystring at npm:0.2.0 is deprecated: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
>➤ YN0032: │ fsevents at npm:2.3.2: Implicit dependencies on node-gyp are discouraged
>➤ YN0032: │ fsevents at npm:2.3.2: Implicit dependencies on node-gyp are discouraged
>➤ YN0032: │ evp_bytestokey at npm:1.0.3: Implicit dependencies on node-gyp are discouraged
>➤ YN0002: │ apollo-link-batch at npm:1.1.15 doesn't provide graphql (pf2c3f), requested by apollo-link
>➤ YN0002: │ bootstrap-vue at npm:2.17.3 doesn't provide jquery (p8724c), requested by bootstrap
>➤ YN0002: │ bootstrap-vue at npm:2.17.3 doesn't provide vue (p74d19), requested by portal-vue
>➤ YN0060: │ root-workspace-0b6124 at workspace:. provides @babel/core (p8d5b6) with version 0.0.0, which doesn't satisfy what babel-loader requests
>➤ YN0060: │ root-workspace-0b6124 at workspace:. provides popper.js (pb3b3d) with version 0.0.0, which doesn't satisfy what bootstrap requests
>➤ YN0060: │ root-workspace-0b6124 at workspace:. provides vue (p02edf) with version 0.0.0, which doesn't satisfy what portal-vue requests
>➤ YN0060: │ root-workspace-0b6124 at workspace:. provides vue (pa125f) with version 0.0.0, which doesn't satisfy what tiptap requests
>➤ YN0060: │ root-workspace-0b6124 at workspace:. provides vue (p6c5ff) with version 0.0.0, which doesn't satisfy what @gitlab/ui requests
>➤ YN0060: │ root-workspace-0b6124 at workspace:. provides vue (p4a08d) with version 0.0.0, which doesn't satisfy what @tiptap/vue-2 requests
>➤ YN0060: │ root-workspace-0b6124 at workspace:. provides vue (pc6a59) with version 0.0.0, which doesn't satisfy what @toast-ui/vue-editor requests
>➤ YN0060: │ root-workspace-0b6124 at workspace:. provides vue (p082e1) with version 0.0.0, which doesn't satisfy what tiptap-extensions requests
>➤ YN0060: │ root-workspace-0b6124 at workspace:. provides vue (paa947) with version 0.0.0, which doesn't satisfy what vue-resize requests
>➤ YN0060: │ root-workspace-0b6124 at workspace:. provides vue (p1dfac) with version 0.0.0, which doesn't satisfy what vuex requests
>➤ YN0060: │ root-workspace-0b6124 at workspace:. provides vue-template-compiler (pb49ea) with version 0.0.0, which doesn't satisfy what tiptap requests
>➤ YN0060: │ root-workspace-0b6124 at workspace:. provides vue-template-compiler (p659ff) with version 0.0.0, which doesn't satisfy what tiptap-extensions requests
>➤ 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 in 11s 268ms
>➤ YN0000: ┌ Fetch step
>➤ YN0013: │ yargs at npm:13.3.2 can't be found in the cache and will be fetched from the remote registry
>➤ YN0013: │ yocto-queue at npm:0.1.0 can't be found in the cache and will be fetched from the remote registry
>➤ YN0013: │ zen-observable-ts at npm:0.8.21 can't be found in the cache and will be fetched from the remote registry
>➤ YN0013: │ zen-observable at npm:0.8.15 can't be found in the cache and will be fetched from the remote registry
>➤ YN0013: │ zrender at npm:4.3.2 can't be found in the cache and will be fetched from the remote registry
>➤ YN0000: └ Completed in 3m 54s
>➤ YN0000: ┌ Link step
>➤ YN0062: │ fsevents at patch:fsevents at npm%3A2.3.2#builtin<compat/fsevents>::version=2.3.2&hash=11e9ea The platform linux is incompatible with this module, link skipped.
>➤ YN0006: │ root-workspace-0b6124 at workspace:. lists build scripts, but is referenced through a soft link. Soft links don't support build scripts, so they'll be ignored.
>➤ YN0007: │ aws-sdk at npm:2.995.0 must be built because it never did before or the last one failed
>➤ YN0007: │ core-js at npm:3.18.0 must be built because it never did before or the last one failed
>➤ YN0007: │ document-register-element at npm:1.14.3 must be built because it never did before or the last one failed
>➤ YN0007: │ bootstrap-vue at npm:2.17.3 must be built because it never did before or the last one failed
>➤ YN0007: │ root-workspace-0b6124 at workspace:. must be built because it never did before or the last one failed
>➤ YN0000: └ Completed in 22s
>➤ YN0000: Done with warnings in 4m 28s
>
>
>ERROR in ./pages/projects/new/components/app.vue
>Module Error (from /var/lib/gitlab/node_modules/vue-loader/lib/index.js):
>
>
>Vue packages version mismatch:
>
>- vue at 2.6.10 (/var/lib/gitlab/.node_modules/vue/dist/vue.runtime.common.js)
>- vue-template-compiler at 2.6.12 (/usr/share/nodejs/vue-template-compiler/package.json)

This seems problematic. vue and vue-template-compiler versions should match.

>This may cause things to work incorrectly. Make sure to use the same version for both.
>If you are using vue-loader@>=10.0, simply update vue-template-compiler.
>If you are using vue-loader@<10.0 or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the latest.
>
> @ ./pages/projects/new/index.js 5:0-57 28:29-50 32:15-36
> @ multi ./main ./pages/projects/index.js ./pages/projects/new/index.js
>
>
>
>ERROR in ./access_tokens/index.js
>Module build failed (from /var/lib/gitlab/node_modules/babel-loader/lib/index.js):
>TypeError: /usr/share/gitlab/app/assets/javascripts/access_tokens/index.js: helpers(...).ensure is not a function
>    at File.addHelper (/usr/share/nodejs/@babel/core/lib/transformation/file/file.js:186:15)
>    at Scope.toArray (/var/lib/gitlab/.node_modules/@babel/traverse/lib/scope/index.js:419:40)
>    at DestructuringTransformer.toArray (/var/lib/gitlab/.node_modules/@babel/plugin-transform-destructuring/lib/index.js:130:27)
>    at DestructuringTransformer.pushArrayPattern (/var/lib/gitlab/.node_modules/@babel/plugin-transform-destructuring/lib/index.js:289:28)
>    at DestructuringTransformer.push (/var/lib/gitlab/.node_modules/@babel/plugin-transform-destructuring/lib/index.js:118:14)
>    at DestructuringTransformer.init (/var/lib/gitlab/.node_modules/@babel/plugin-transform-destructuring/lib/index.js:326:12)
>    at PluginPass.VariableDeclaration (/var/lib/gitlab/.node_modules/@babel/plugin-transform-destructuring/lib/index.js:469:27)
>    at newFn (/var/lib/gitlab/.node_modules/@babel/traverse/lib/visitors.js:193:21)
>    at NodePath._call (/var/lib/gitlab/.node_modules/@babel/traverse/lib/path/context.js:53:20)
>    at NodePath.call (/var/lib/gitlab/.node_modules/@babel/traverse/lib/path/context.js:40:17)
>    at NodePath.visit (/var/lib/gitlab/.node_modules/@babel/traverse/lib/path/context.js:88:12)
>    at TraversalContext.visitQueue (/var/lib/gitlab/.node_modules/@babel/traverse/lib/context.js:118:16)
>    at TraversalContext.visitMultiple (/var/lib/gitlab/.node_modules/@babel/traverse/lib/context.js:85:17)
>    at TraversalContext.visit (/var/lib/gitlab/.node_modules/@babel/traverse/lib/context.js:144:19)
>    at Function.traverse.node (/var/lib/gitlab/.node_modules/@babel/traverse/lib/index.js:94:17)
>    at NodePath.visit (/var/lib/gitlab/.node_modules/@babel/traverse/lib/path/context.js:95:18)
>    at TraversalContext.visitQueue (/var/lib/gitlab/.node_modules/@babel/traverse/lib/context.js:118:16)
>    at TraversalContext.visitSingle (/var/lib/gitlab/.node_modules/@babel/traverse/lib/context.js:90:19)
>    at TraversalContext.visit (/var/lib/gitlab/.node_modules/@babel/traverse/lib/context.js:146:19)
>    at Function.traverse.node (/var/lib/gitlab/.node_modules/@babel/traverse/lib/index.js:94:17)
>    at NodePath.visit (/var/lib/gitlab/.node_modules/@babel/traverse/lib/path/context.js:95:18)
>    at TraversalContext.visitQueue (/var/lib/gitlab/.node_modules/@babel/traverse/lib/context.js:118:16)
>    at TraversalContext.visitMultiple (/var/lib/gitlab/.node_modules/@babel/traverse/lib/context.js:85:17)
>    at TraversalContext.visit (/var/lib/gitlab/.node_modules/@babel/traverse/lib/context.js:144:19)
>    at Function.traverse.node (/var/lib/gitlab/.node_modules/@babel/traverse/lib/index.js:94:17)
>    at NodePath.visit (/var/lib/gitlab/.node_modules/@babel/traverse/lib/path/context.js:95:18)
>    at TraversalContext.visitQueue (/var/lib/gitlab/.node_modules/@babel/traverse/lib/context.js:118:16)
>    at TraversalContext.visitSingle (/var/lib/gitlab/.node_modules/@babel/traverse/lib/context.js:90:19)
>    at TraversalContext.visit (/var/lib/gitlab/.node_modules/@babel/traverse/lib/context.js:146:19)
>    at Function.traverse.node (/var/lib/gitlab/.node_modules/@babel/traverse/lib/index.js:94:17)
>    at NodePath.visit (/var/lib/gitlab/.node_modules/@babel/traverse/lib/path/context.js:95:18)
>    at TraversalContext.visitQueue (/var/lib/gitlab/.node_modules/@babel/traverse/lib/context.js:118:16)
>    at TraversalContext.visitSingle (/var/lib/gitlab/.node_modules/@babel/traverse/lib/context.js:90:19)
>    at TraversalContext.visit (/var/lib/gitlab/.node_modules/@babel/traverse/lib/context.js:146:19)
>    at Function.traverse.node (/var/lib/gitlab/.node_modules/@babel/traverse/lib/index.js:94:17)
>    at NodePath.visit (/var/lib/gitlab/.node_modules/@babel/traverse/lib/path/context.js:95:18)
> @ ./pages/admin/impersonation_tokens/index.js 1:0-53 2:0-18
> @ multi ./main ./pages/admin/index.js ./pages/admin/impersonation_tokens/index.js
>
>
>ERROR in ./pages/projects/new/components/app.vue
>Module build failed (from /var/lib/gitlab/node_modules/vue-loader/lib/index.js):
>TypeError: Cannot read property 'parseComponent' of undefined
>    at parse (/var/lib/gitlab/node_modules/@vue/component-compiler-utils/dist/parse.js:15:23)
>    at Object.module.exports (/var/lib/gitlab/node_modules/vue-loader/lib/index.js:67:22)
> @ ./pages/projects/new/index.js 5:0-57 28:29-50 32:15-36
> @ multi ./main ./pages/projects/index.js ./pages/projects/new/index.js
>

If you are not able to figure this out, may be moving to bullseye is a better option. Once database migrations succeed, front end failures should not affect the upgrade.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.



More information about the Pkg-ruby-extras-maintainers mailing list