-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem: Bionic jhove package is newer than artefactual repo one #1065
Comments
Workaround is to downgrade the package with:
But auto-upgrades will upgrade the package later. |
Will upgrading to an even-later version of JHOVE stop the conflicts with auto-upgrades? I remember this issue coming up when testing which version of JHOVE to bump us up to, and couldn't use 1.22 because of a similar-or-same error when trying to move to the latest. I filed an issue which ended up being a duplicate of this one, where it was resolved: openpreserve/jhove#502 |
Here's a little more information (and some of these links provide more detailed examples into how JHOVE is behaving). I want to emphasize that this is affecting every Archivematica instance that uses Ubuntu 18.04 and has auto-updates turned on, which is most users. So the severity of this issue shouldn't be understated. I think anyone using Archivematica in these conditions will have to perform the above rollback. (I have no idea how often these updates happen -- "periodically") It is only affecting users with JPEGs that contain any ANSI/NISO metadata. I don't have a test file that I can provide publicly to replicate this issue, but I can point Artefactual staff to where one exists. It seems that this bug appeared in the above version and still may be present in 1.24-RC, so this doesn't appear to be stable enough to move forward with a fix, but rather we need to stay locked into the above specific version @mamedin mentions. This is likely to be resolved by the time 1.12 is getting ready, so we should consider an upgrade to 1.24 for that release. Here is a brief history: Someone else raising a different in 1.22, but should be considered: openpreserve/jhove#456 This issue relates to the relationship between JHOVE and Java, and an auto-update of Java should be considered when making decisions around this issue. 1.22 is the latest official version of JHOVE, given there doesn't seem to have been a 1.23 version, and 1.24 is still listed as a release candidate (releases here: https://github.com/openpreserve/jhove/releases) This issue coming up as tested in the GUI for 1.24, a few days ago: There also seems to be many PDF-associated bugs found in the 1.24-RC, so I don't think a new version will be right around the corner. |
Following up on this a bit -- the Jhove 1.24 RC seems to resolve this issue, in the sense that it no longer crashes out. When the RC graduates to a standard release, we can do the analysis work as to whether or not we should upgrade. By-and-by, general users can test using this image, which embeds Z39.87 metadata. |
@mamedin it looks like the PR pins the version of Jhove, in your opinion does that resolve this issue? |
@sromkey Yes, it fixed the issue. If Ubuntu releases a newer |
Expected behaviour
We should use jhove=1.20.1-1~18.04
Current behaviour
Bionic installs the latest one from its repository: 1.20.1-5~18.04.1ubuntu1
Steps to reproduce
Install archivematica on bionic or upgrade packages.
Your environment (version of Archivematica, operating system, other relevant details)
AM1.10.1
Ubuntu Bionic
For Artefactual use:
Before you close this issue, you must check off the following:
The text was updated successfully, but these errors were encountered: