Thanks! I’ll patch the version number in the source code.
I’m not sure what to do about the trailing BUILD (here “2”). It’s really designed to count upstream binary release builds, I think. It’s exposed to plugins but I’m not sure if any use it. Still, that keeps me from wanting to stuff the entire RPM “release” string in there, e.g., 1.fc36, lest some plugin expect it to be a decimal representation. Maybe I’ll just use the RPM packages numeric pkgrel field.
I also discovered that I introduced a regression in which broken symlinks named * could be created by the launcher script in ~/.imagej/luts and ~/.imagej/plugins. That was relatively harmless, but I’ll update this with a fix for that, as well.
This update has been submitted for testing by music.
This update's test gating status has been changed to 'ignored'.
music edited this update.
The About ImageJ panel reports the version as 1.53s2 but aside from that, everything seems to work fine.
Thanks! I’ll patch the version number in the source code.
I’m not sure what to do about the trailing
BUILD(here “2”). It’s really designed to count upstream binary release builds, I think. It’s exposed to plugins but I’m not sure if any use it. Still, that keeps me from wanting to stuff the entire RPM “release” string in there, e.g.,1.fc36, lest some plugin expect it to be a decimal representation. Maybe I’ll just use the RPM packages numericpkgrelfield.I also discovered that I introduced a regression in which broken symlinks named
*could be created by the launcher script in~/.imagej/lutsand~/.imagej/plugins. That was relatively harmless, but I’ll update this with a fix for that, as well.music edited this update.
New build(s):
Removed build(s):
Karma has been reset.
Updated with a new build to fix the “*” symlink regression mentioned above, and to fix the self-reported version number.
This update has been pushed to testing.
This update has been submitted for stable by bodhi.
This update has been pushed to stable.