<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><br class=""></div>I usually test out migrations and local plugins on my Mac laptop first before installing on a test server. <div class="">I ran into a couple of issues with 3.2.0 release. </div><div class=""><br class=""></div><div class="">Using the release downloaded from</div><div class=""><a href="https://github.com/archivesspace/archivesspace/releases/tag/v3.2.0" class="">https://github.com/archivesspace/archivesspace/releases/tag/v3.2.0</a></div><div class=""><br class=""></div><div class="">Backend and frontend appeared to work and communicate with the separately installed Solr instance however the PUI gave system errors from the bundler relating to sassc-2.4.0 </div><div class=""><br class=""></div><div class="">Looking at the log file, there were a number of messages about that and other gems:</div><div class=""><br class=""></div><div class="">Ignoring bindex-0.8.1 because its extensions are not built. Try: gem pristine bindex --version 0.8.1</div><div class="">Ignoring llhttp-ffi-0.3.1 because its extensions are not built. Try: gem pristine llhttp-ffi --version 0.3.1<br class="">Ignoring sassc-2.4.0 because its extensions are not built. Try: gem pristine sassc --version 2.4.0<br class=""><br class=""></div><div class="">I attempted to run ‘gem pristine’ after setting GEM_HOME, which seemed to do something, but didn’t fix the issue. ( Doing these sorts of fixes are a bit confusing due to the way that JRuby is packaged in ArchivesSpace, so I may not have been doing it correctly. ) </div><div class=""><br class=""></div><div class="">I finally tried building my own distribution from GitHub tag v3.2.0, and unpacking that zip file and running it appears to work ( so far! Still indexing PUI ) </div><div class=""><br class=""></div><div class="">So I’m guessing that there is something in these gem extensions that is architecture or java version specific and the distributions on GitHub are not universal. </div><div class=""><br class=""></div><div class="">We may require a fixup script that runs the bundler similar to the way it’s done in initialize-plugins script. </div><div class=""><br class=""></div><div class="">Has anyone else run into this issue ? </div><div class=""><br class=""></div><div class="">— Steve Majewski</div><div class=""><br class=""></div><div class=""><br class=""></div></body></html>