On Thursday, March 27, 2025 10:18:58 AM Mountain Standard Time Valentin Kleibel wrote: > > The other three plugin packages install without error, but they do > > not appear in the list of available plugins under Administration > > > Plugins. I assume that we need to adjust something about the > > their packaging before they will work. Does anyone know what > > needs to be done? > > Yes. The updated multitenancy patch only loads plugins that are in > <redmine_instance_dir>/plugins, if this directory exists. > See also the updated '/usr/share/redmine/bin/redmine-instances help' > Symlinking /usr/share/redmine/plugins/<plugin> to > <redmine_instance_dir>/plugins enables the plugin (the UI doesn't > allow to enable/disable plugins) > > As long as <redmine_instance_dir>/plugins is not created on upgrade > this should not affect existing installations.
Thanks for the explanation. I have revised README.Debian and NEWS with information that should be sufficient for those upgrading or installing fresh. > >> https://tracker.debian.org/pkg/redmine-plugin-custom-css > > loading to codemirror.css and codemirror.js doesn´t work, seems the > references need to be updated to work with propshaft. Thanks. I filed a bug report. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101466 > > I updated Salsa to 6.0.4+ds-1. I am running it on my production > > environment without issue (Apache + Passenger + no plugins). I > > think we will be ready to release once we figure out the Debian > > package plugin issue described above and get a working Nginx > > config file + test. > > I created a new MR with added config examples and an updated test. Thanks. We now have working tests for both Apache and nginx. I couldn’t have done it without you. I have uploaded 6.0.4+ds-1 to unstable. -- Soren Stoutner so...@debian.org
signature.asc
Description: This is a digitally signed message part.
