Archivematica 1.18.0 and Storage Service 0.24.0 released

[Sarah Mason]

Hello Archivematica community members,

We’re pleased to let you know that Artefactual has released Archivematica version 1.18.0 and Storage Service version 0.24.0. You can find the release notes in GitHub and on the AM wiki. Version 1.18.0 updates ElasticSearch to 8.x and now includes support for Ubuntu 24.04. Other updates and improvements includes:

• New JHOVE validation commands

• JHOVE updated to v1.34.0

• PRONOM updated to v120

For instructions on migrating your Elasticsearch data, refer to the Upgrade Elasticsearch from 6.x to 8.x section of the Upgrade page in the documentation.

Release notes

Installation instructions

We would like to thank the community contributors, translators and members who reported issues and vulnerabilities in this release. If you would like to contribute to Archivematica, please see the contributing guidelines. For any other questions or feedback, please email the Community Team on contri...@artefactual.com.

If you would like to report issues, please visit the Archivematica Issues Repository. Guidance on how to report issues can be found here.

[Tatiana Canelhas]

Hi, the installation is not working for me on Ubuntu 24. 

I have a question regarding the installation instructions (image attached). 

Is that possible??

Thanks,

Tatiana Canelhas

[Douglas Cerna]

Hello,

It is not possible unfortunately. The 1.18.x Ubuntu packages do not work in Ubuntu 24.04.

See https://github.com/archivematica/Issues/issues/1766 where this was originally reported.

We are in the middle of publishing Ubuntu 24.04 packages at the moment with https://github.com/artefactual-labs/am-packbuild/pull/397 and we plan to update the installation documentation.

Hope this helps.

--
You received this message because you are subscribed to the Google Groups "archivematica" group.
To unsubscribe from this group and stop receiving emails from it, send an email to archivematic...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/archivematica/67cd8709-0c5c-4855-8795-2ec8f18d1bfen%40googlegroups.com.

--

Douglas Cerna (he/him),
Software Developer, Artefactual Systems Inc.
http://www.artefactual.com

[Tatiana Canelhas]

Hi Mr. Cerna, 

Thanks for your response :)
Tatiana Canelhas

[Douglas Cerna]

Hello,

We just published new 1.18.x packages for Ubuntu 22.04, Ubuntu 24.04 and Rocky Linux 9. And the Ubuntu installation and upgrade documentation has been updated to use the new distribution as well.

Let us know if you have any issues.

To view this discussion visit https://groups.google.com/d/msgid/archivematica/0864ffaf-71d3-47b7-8215-8fe96eec363bn%40googlegroups.com.

[Jens Steidl]

Hi Douglas,

I wanted to share some feedback regarding the version 1.18 update on our side. This thread seemed to be most fitting place :)

The upgrade from 1.17 to 1.18 now worked using the new packages for 22.04/24.04, thank you! Here is a small summary of my observations:

• starting Elasticsearch 8.x takes (quite a few seconds) longer, during this time the dashboard keeps crashing and restarting until ES is up 
  • scenario: Host restart, Archivematica restart
• required manual changes in /etc/defaults/archivematica-*** after the upgrade
  • "DJANGO_SETTINGS_MODULE" had still the old (and now outdated) module name, so most services failed to start
    • the exception was storage service packages, it performed an in-place change via "postinst" script
    • only the upgrade it effected, new installation defaults are fine
    • values
      • Dasboard → settings.production  → archivematica.dashboard.settings.production
      • MCP-Client → settings.common → archivematica.MCPClient.settings.common
      • MCP-Server → settings.common → archivematica.MCPServer.settings.common
      • Storage Service → archivematica.storage_service.storage_service.settings.production  
  • I also removed existing PYTHONPATH variables, they seem to be leftovers from older versions
• no issues with index migration from ES 6.x → ES 8.x, worked as described!
• a lesson from previous upgrades: I still use a playbook to reset DB passwords to their default values (expected by the Ubuntu packages) before doing the normal packages upgrade and setting new ones afterwards
  • prevents issues where packages are supposedly installed successfully although you can see python exceptions about DB access
  • no interactions needed (password input etc. for an automated package upgrade)
  • the need to change and harden passwords due do in-house policies

Best regards,

Jens