-
Notifications
You must be signed in to change notification settings - Fork 75
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
Latest LibreOffice.download.recipe failing due to version mismatch b/w tested release notes page and download version available #279
Comments
There’s not a lot Hannes can do about this. The developer has made it nearly impossible to find/discover the download URL. So the recipe “calculates” a download URL based on the version listed in the current release notes. If those are not accurate… |
An alternate approach would be to look at the directory listings here: http://downloadarchive.documentfoundation.org/libreoffice/old/latest/mac/x86_64/ But sadly, those are seemingly available only via http and not https. |
I take that back. There's some weird redirects going on from the download page, but https://downloadarchive.documentfoundation.org/libreoffice/old/latest/mac/x86_64/ do seem to work. One could then do a regex search looking for .dmg files... |
This proposed alternate approach really only helps with "latest". I don't see an easy way to get the previous/stable/whatever version from the download archive. |
Aaaand just this morning it looks like they must've updated the release notes page, as 24.2.1 came down. I realize this is always the challenge. Recipes are to finding the right info on webpages/etc. the way "screen scraping" is done in network automation. You are at the mercy of the site/NOS devs in that you try to RegEx/filter your way around their output. But it could change at any time. I have often thought (more like wished) how nice it would be if there were some well established, clearly defined way that software sites would all post their release information. Kind of like how websites have robots.txt files, only with some kind of standardized/API like way of providing version info. Possibly JSON or some other structured format that was easily consumable by software. But it is what it is I guess. I do appreciate you looking into this, though. I'm noticing this happening with some other recipes, too, of late, where the version info either isn't up-to-date, or in some cases (e.g., Python3) where they put out updates to two different trains, but the order they list them on the page isn't what is expected. |
Yeah, I had to contact the devs to get them to update the page. They hinted on a "new hompage" soon where they could list this in a better way. They should be aware now about our community and AutoPkg and roughly how AutoPkg works. I hope this is helpful! Similar issue: #275 |
The last versions from 7.6 and 24.2 can be seen here https://www.libreoffice.org/download/download-libreoffice/, I will try to create a processor to get the two last version info there |
Updated my Munki repos including the LibreOffice recipes after noticing it wasn't pulling latest.
But new version is failing. Digging into recipe, I see it does a regex on https://www.libreoffice.org/download/release-notes/
That page shows the latest version as 24.2.
So the final URL provided is
However, if you visit the actual site, you'll see the latest is actually 24.2.1, and at least on that site, the URL is then
And if I manually adjust the earlier URL to
that does, in fact, work.
So there appears to be an issue where the release notes page isn't being maintained/matching the actual version on the download page of the site, causing the error.
Here is the output from running
autopkg run -vv LibreOffice.munki.recipe
in case it helps:The text was updated successfully, but these errors were encountered: