Package Details: imagej 2:1.50i-3

Git Clone URL: (read-only)
Package Base: imagej
Description: Image manipulation software for scientists
Upstream URL:
Licenses: Public Domain
Submitter: skarn
Maintainer: mschu
Last Packager: mschu
Votes: 59
Popularity: 0.865345
First Submitted: 2009-05-18 15:59
Last Updated: 2017-07-03 23:07

Latest Comments

mschu commented on 2017-07-03 23:08

From now on I will only include versioned .jar files to patch the main distribution.

This should alleviate the problem of breaking checksums.

I will only update to the unversioned .jar if there is a strong reason to do so.

fordprefect commented on 2017-02-23 21:07

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

SammysHP commented on 2017-02-17 20:49

AFAIK version 2 is a completely different piece of software. I don't know if it will replace the 1.x branch.

PS: checksums still not updated.

ArchangeGabriel commented on 2017-02-16 00:46

@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! ( So it’s not definitively ready for packaging.

greyltc commented on 2017-02-16 00:04

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

mschu commented on 2017-02-15 00:54

All fixed for v1, will have a closer look for v2.

However, as far as I am aware there should be a *direct* email to the maintainer and 2 weeks time to respond before disowning. Please respect that, or point me to where the guidelines have changed.

The orphan request sent is nonsense, the package has not been flagged before yesterday.

ArchangeGabriel commented on 2017-02-15 00:49

@mschu: Thanks for the update, just one little thing: with the ij.jar updating, the version number should be 1.51j. ;)

ArchangeGabriel commented on 2017-02-14 14:03

So, in conclusion, if no update happens and someone proposes a fixed PKGBUILD, I’ll disown this package so that it can be fixed by that person.

ArchangeGabriel commented on 2017-02-14 14:01

This way of updating versions doesn’t make sense (that ij.jar thing), but if that’s how upstream works…

Anyway, upstream URL should be :

Next, the latest zip file is here: (which is 1.50i)

Then, the upgrade path should also be changed to this one:

And finally, should reflects those ij.jar changes in the version number, because that’s what they correspond to: currently, it’s the file for 1.51j, you can see it here, and here if you want to see history of releases.

And finally, all those files are ImageJ 1.x, but now ImageJ 2 is out, a portable version is available here:

greyltc commented on 2017-02-13 18:21

Please update the md5sums for ij.jar

All comments