-
Notifications
You must be signed in to change notification settings - Fork 92
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
Fiji versioning #177
Comments
Thanks! This looks like it works, so I've now rolled this into the Fiji download recipe. |
Hi Rich, you might need to read my edit. I originally sent the solution that used the So, I edited my original issue with a new solution based on the release date of the "latest" version. I guess you would not have seen that if you just read the email notification - sorry for the confusion! |
It appears that using the timestamp is giving
Full verbose run is attached. |
I'm guessing it's the dash in the version information ( |
Strangely, I do not get that error. I do get a "Bad descriptor" error, but it doesn't prevent the package from being built.
Same result with AutoPkg versions 2.4.1 and 2.7. |
I'm on AutoPkg 2.7.2. I can't tell from the output above if that's the same version you were running. |
Probably not, as I use a custom-build from the dev branch in order to utilise recipe-maps. Nonetheless, I can't see any changes to PkgCreator in any branches for 2 years. It's dumb that a dash breaks the build, but that is the current state of affairs, at least on your computer, so it's probably worth removing the Given the unlikelihood of Fiji getting two new "latest" releases in a single day, it should work to use https://github.com/autopkg/homebysix-recipes/blob/master/VersionSplitter/VersionSplitter.py. Alternatively https://github.com/autopkg/grahampugh-recipes/blob/master/CommonProcessors/StringReplacer.py can replace one character with a different one so could be used to make |
FWIW, I've used StringReplacer in my processor: https://github.com/eth-its/autopkg-mac-recipes-yaml/blob/main/PKG_Recipes/Fiji.pkg.recipe.yaml |
OK. For now, I'm reverting yesterday's commit so that the Fiji .download recipe goes back to the way it was. I'll figure out the best way forward. |
I've submitted a pull request with a possible solution - using https://maven.scijava.org/content/groups/public/sc/fiji/fiji/maven-metadata.xml to determine the current Fiji version. |
Hi Rich,
I've been taking a look at the Fiji.download recipe. The version that's reported is problematic in that the version you get from https://wsr.imagej.net/notes.html refers to ImageJ, not Fiji specifically. We can get Fiji versions from the tags at https://github.com/fiji/fiji/tags, but these go newer than the releases.
The release at https://downloads.imagej.net/fiji/latest/ is not versioned, but it also appears not to be the latest at all. The latest is available, with version string, from https://downloads.imagej.net/fiji/releases/
However, on further investigation, it seems that pushing the newest version in "releases" is risky.
Finally, I looked at what Homebrew are doing, and they've come up with the idea of grabbing the datestamp of the latest version. They note that a new folder is added to the "archive" folder shortly after the latest release is created, into which that release is copied. This happens around 30 minutes after the date stamp of the latest release, so is a good indicator, and easier to scrape than that actual date stamp.
I've built a recipe based on this for our own purposes but feel free to adapt your "official" one with the logic below.
The text was updated successfully, but these errors were encountered: