Custom package installation gives error

[skip]

• Used Zammad version: 6.4.1-1735815640.3ddf2933.noble
• Used Zammad installation type: package
• Operating system: Ubuntu 24.04
• Browser + version: Firefox latest

Expected behavior:

• Run zammad run rake zammad:package:post_install without issues after installing custom package

Actual behavior:

• Running zammad run rake zammad:package:post_install gives the following error output

Executing all pending package migrations...
done.

> zammad run rake zammad:package:precompile
/opt/zammad/.heroku/node/lib/node_modules/corepack/dist/lib/corepack.cjs:23509
              throw new UsageError(`This project is configured to use ${result.spec.name} because ${result.target} has a "packageManager" field`);
                    ^

UsageError: This project is configured to use pnpm because /opt/zammad/package.json has a "packageManager" field
    at Engine.findProjectSpec (/opt/zammad/.heroku/node/lib/node_modules/corepack/dist/lib/corepack.cjs:23509:21)
    at async Engine.executePackageManagerRequest (/opt/zammad/.heroku/node/lib/node_modules/corepack/dist/lib/corepack.cjs:23539:24)
    at async Object.runMain (/opt/zammad/.heroku/node/lib/node_modules/corepack/dist/lib/corepack.cjs:24232:5) {
  clipanion: { type: 'usage' }
}

Node.js v22.1.0

Steps to reproduce the behavior:

• Install a custom package
• Run zammad run rake zammad:package:post_install
• Get the error

Thanks,
Skip

[skip]

I am getting this error every time I run zammad run rake assets:precompile too

[MrGeneration]

You really should read the release notes.

[skip]

I must be blind, I cannot see any reference to that here

Security Release 6.4.1 | Zammad

Any pointer?

Thanks

[MrGeneration]

How about going chronologically

New Minor Release: Zammad 6.4

[skip]

Thanks for the hint.

Given the highlighted text I am not sure how that is relevant as I am using a package installation

Is any more specific clarification available? Does that mean that since I am using a package I can ignore the error? I cannot see anything in this regard in the release notes.

Thanks

[7qubit]

I believe this conflict occurs because Yarn is no longer being used, and Corepack is trying to start via yarn.js. To prevent conflicts with pnpm or npm, I removed the Yarn modules. After that, the error message no longer appeared.

rm -rf /opt/zammad/.heroku/node/lib/node_modules/yarn
rm -rf /opt/zammad/.heroku/node/bin/yarn
rm -rf /opt/zammad/.heroku/node/bin/yarnpkg

I hope this is the correct approach, but everything is at your own risk. Please make a backup before proceeding.

After removing Yarn, try running the following command again:

zammad run rake assets:precompile && systemctl restart zammad-web

[rolfschmidt]

You can ignore the error. It is a false positive which isn’t resolved. The team did not find a way to suppress that error yet. The error should not impact the functionality of your system.