Infos:
- Used Zammad version: 5.3.0 → 5.3.1
- Used Zammad installation type: source
- Operating system: Arch
Behavior:
After reading the security advisory, I tried upgrading to Zammad 5.3.1 immediately. I run a source installation exactly according to the documentation.
Attempting to run Step 6, rake assets:precompile resulted in an error:
yarn install v1.22.19
[1/5] Validating package.json...
[2/5] Resolving packages...
success Already up-to-date.
$ node script/fix-node-modules.mjs
Done in 1.65s.
rake aborted!
LoadError: cannot load such file -- uglifier
/home/zammad/.rvm/gems/ruby-3.0.4/gems/bootsnap-1.13.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:29:in `require'
/home/zammad/.rvm/gems/ruby-3.0.4/gems/zeitwerk-2.6.6/lib/zeitwerk/kernel.rb:38:in `require'
/home/zammad/.rvm/gems/ruby-3.0.4/gems/sprockets-3.7.2/lib/sprockets/autoload/uglifier.rb:1:in `<main>'
/home/zammad/.rvm/gems/ruby-3.0.4/gems/bootsnap-1.13.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
/home/zammad/.rvm/gems/ruby-3.0.4/gems/bootsnap-1.13.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
/home/zammad/.rvm/gems/ruby-3.0.4/gems/zeitwerk-2.6.6/lib/zeitwerk/kernel.rb:38:in `require'
/home/zammad/.rvm/gems/ruby-3.0.4/gems/sprockets-3.7.2/lib/sprockets/uglifier_compressor.rb:39:in `initialize'
/home/zammad/.rvm/gems/ruby-3.0.4/gems/sprockets-3.7.2/lib/sprockets/uglifier_compressor.rb:24:in `new'
/home/zammad/.rvm/gems/ruby-3.0.4/gems/sprockets-3.7.2/lib/sprockets/uglifier_compressor.rb:24:in `instance'
/home/zammad/.rvm/gems/ruby-3.0.4/gems/sprockets-3.7.2/lib/sprockets/uglifier_compressor.rb:28:in `call'
/home/zammad/.rvm/gems/ruby-3.0.4/gems/sprockets-3.7.2/lib/sprockets/processor_utils.rb:75:in `call_processor'
/home/zammad/.rvm/gems/ruby-3.0.4/gems/sprockets-3.7.2/lib/sprockets/processor_utils.rb:57:in `block in call_processors'
/home/zammad/.rvm/gems/ruby-3.0.4/gems/sprockets-3.7.2/lib/sprockets/processor_utils.rb:56:in `reverse_each'
/home/zammad/.rvm/gems/ruby-3.0.4/gems/sprockets-3.7.2/lib/sprockets/processor_utils.rb:56:in `call_processors'
/home/zammad/.rvm/gems/ruby-3.0.4/gems/sprockets-3.7.2/lib/sprockets/loader.rb:134:in `load_from_unloaded'
/home/zammad/.rvm/gems/ruby-3.0.4/gems/sprockets-3.7.2/lib/sprockets/loader.rb:60:in `block in load'
/home/zammad/.rvm/gems/ruby-3.0.4/gems/sprockets-3.7.2/lib/sprockets/loader.rb:317:in `fetch_asset_from_dependency_cache'
/home/zammad/.rvm/gems/ruby-3.0.4/gems/sprockets-3.7.2/lib/sprockets/loader.rb:44:in `load'
/home/zammad/.rvm/gems/ruby-3.0.4/gems/sprockets-3.7.2/lib/sprockets/cached_environment.rb:20:in `block in initialize'
/home/zammad/.rvm/gems/ruby-3.0.4/gems/sprockets-3.7.2/lib/sprockets/cached_environment.rb:47:in `load'
/home/zammad/.rvm/gems/ruby-3.0.4/gems/sprockets-3.7.2/lib/sprockets/base.rb:66:in `find_asset'
/home/zammad/.rvm/gems/ruby-3.0.4/gems/sprockets-3.7.2/lib/sprockets/base.rb:73:in `find_all_linked_assets'
/home/zammad/.rvm/gems/ruby-3.0.4/gems/sprockets-3.7.2/lib/sprockets/manifest.rb:134:in `block in find'
/home/zammad/.rvm/gems/ruby-3.0.4/gems/sprockets-3.7.2/lib/sprockets/manifest.rb:133:in `each'
/home/zammad/.rvm/gems/ruby-3.0.4/gems/sprockets-3.7.2/lib/sprockets/manifest.rb:133:in `find'
/home/zammad/.rvm/gems/ruby-3.0.4/gems/sprockets-3.7.2/lib/sprockets/manifest.rb:186:in `compile'
/home/zammad/.rvm/gems/ruby-3.0.4/gems/sprockets-rails-3.4.2/lib/sprockets/rails/task.rb:67:in `block (3 levels) in define'
/home/zammad/.rvm/gems/ruby-3.0.4/gems/sprockets-3.7.2/lib/rake/sprocketstask.rb:147:in `with_logger'
/home/zammad/.rvm/gems/ruby-3.0.4/gems/sprockets-rails-3.4.2/lib/sprockets/rails/task.rb:66:in `block (2 levels) in define'
/home/zammad/.rvm/gems/ruby-3.0.4/gems/rake-13.0.6/exe/rake:27:in `<top (required)>'
/home/zammad/.rvm/gems/ruby-3.0.4/bin/ruby_executable_hooks:22:in `eval'
/home/zammad/.rvm/gems/ruby-3.0.4/bin/ruby_executable_hooks:22:in `<main>'
Tasks: TOP => assets:precompile
I tried looking into the relevant line, LoadError: cannot load such file -- uglifier, but couldn’t find anything.
To make sure I didn’t miss anything, I reset to the working install and repeated the procedure, to the same results, whereas running the same steps with 5.3.0 is successful for me.
Running the official docs update guide should work. Ignoring the failure in the precompile step predictably leads nowhere, Zammad just shows an error page.
Steps to reproduce the behavior:
- Run 5.3.0, attempt to upgrade