Skip to content
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

Closed
5 tasks
mamedin opened this issue Jan 16, 2020 · 6 comments
Closed
5 tasks

Problem: Bionic jhove package is newer than artefactual repo one #1065

mamedin opened this issue Jan 16, 2020 · 6 comments
Assignees
Labels
Type: bug A flaw in the code that causes the software to produce an incorrect or unexpected result.

Comments

@mamedin
Copy link

mamedin commented Jan 16, 2020

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:

  • All pull requests related to this issue are properly linked
  • All pull requests related to this issue have been merged
  • A testing plan for this issue has been implemented and passed (testing plan information should be included in the issue body or comments)
  • Documentation regarding this issue has been written and merged (if applicable)
  • Details about this issue have been added to the release notes (if applicable)
@mamedin mamedin self-assigned this Jan 16, 2020
@mamedin
Copy link
Author

mamedin commented Jan 16, 2020

Workaround is to downgrade the package with:

sudo apt-get install jhove=1.20.1-1~18.04 

But auto-upgrades will upgrade the package later.

@ablwr
Copy link
Contributor

ablwr commented Jan 16, 2020

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

@sromkey sromkey added triage-release-1.12 Type: bug A flaw in the code that causes the software to produce an incorrect or unexpected result. Status: refining The issue needs additional details to ensure that requirements are clear. labels Jan 20, 2020
@ablwr
Copy link
Contributor

ablwr commented Jan 20, 2020

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:
Me raising the bug when testing to determine if it was appropriate for Archivematica to upgrade to the then-latest 1.22 version: openpreserve/jhove#459
Someone else raising and patching the bug: openpreserve/jhove#502

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:
openpreserve/jhove#558
openpreserve/jhove#559

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.

@ablwr
Copy link
Contributor

ablwr commented Jan 20, 2020

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.

@sromkey
Copy link
Contributor

sromkey commented Jul 21, 2020

@mamedin it looks like the PR pins the version of Jhove, in your opinion does that resolve this issue?

@mamedin
Copy link
Author

mamedin commented Jul 21, 2020

@sromkey Yes, it fixed the issue. If Ubuntu releases a newer jhove package we can always create a new package with higher version or extraversion.

@sromkey sromkey removed triage-release-1.12 Status: refining The issue needs additional details to ensure that requirements are clear. labels Jul 21, 2020
@sromkey sromkey closed this as completed Jul 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: bug A flaw in the code that causes the software to produce an incorrect or unexpected result.
Projects
None yet
Development

No branches or pull requests

3 participants