Package dependencies should be for jre8-openjdk, or something other than java-runtime because ImageJ does not run with jre10-openjdk. on my recently installed arch system I originally only had jre10-openjdk, and it fails until installing and setting the default environment to jre8-openjdk

I notified upstream also: https://github.com/imagej/imagej/issues/195

in PKGBUILD please replace: md5sums=('a2e52e97b1c683cb4f614b4d570fb972' with: md5sums=('3defd05424a3e0c99253aec3b6724e95'

Just want to mention that the md5sum for ij150.zip seems to be outdated. Thanks for maintaining this package!

checksum for ij.jar changed, please update. thank you.

@mschu: Latest update was from November while one comment from early January was already asking for an update. Granted, they didn’t flag the package, but given how the version number are used here, it makes out-of-date a bit confusing. But an existing non-adressed issue from a comment is equivalent to me as flagged out-of-date.

Now, regarding the orphan: I never said I didn’t intend to respect the rules. An orphan request was filed, so I took a look at the package. Because I, at least, do not automatically orphan even after no answers for 14 days, I want that plus a proof that the next maintainer knows how to fix things.

When looking at the PKGBUILD, I saw the bad shape it was in, I saw no updates since November while evidences suggest that upstream made a release in the meantime (from early December), and thus, I said that if *no updates happens* (which didn’t included a time span, but it implicitly implied the 14 days window at least for me) and someone was actually proposing a fix (which wasn’t the case with only users wanting to bump md5sums), I would indeed accept the orphan request (that I worded disown it, but that is equivalent).

But you’ve update it and now it’s fine, excepted the version number still.

For v2, a closer look at upstream GitHub made me see they’re still not in the final release, but RC58! (https://github.com/imagej/imagej/releases) So it’s not definitively ready for packaging.

Hi mschu, it looks to me like the checksums are still not right here (maybe you've not cleared the old source files before recomputing the checksums?). I'm getting a disagreement for ij.jar. I think it should be a659180b574f80d2704dc1b60a8f19a1