-
Notifications
You must be signed in to change notification settings - Fork 113
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
GraphicConverter.download is pulling a beta version #598
Comments
Hi @grahampugh - I'm not able to reproduce this. Could you provide the
|
Hi Elliot, sure, here is the output when running
This results in:
|
Are you running a custom branch of AutoPkg, or an older version? I'm on 2.7.2, and channel support was added to SparkleUpdateInfoProvider recently. |
Oh interesting, indeed we do use a custom version as we rely on recipe_maps. That would explain it. However, that would expose another problem. Your Sparkle feed is returning 2.0.2 as the latest version whereas the GC website is showing 2.0.3. So, I'm not sure of the update cadence of the Sparkle feed. |
I'm on the fence about whether that's a problem I need to solve. On one hand, it's ultimately the developer's responsibility to update the Sparkle feed, and using Sparkle as the source for AutoPkg offers easy major-version overrides and supports default/beta channels. On the other hand, it looks like multiple major versions and beta versions can probably be derived from the static URLs available on the download page too, so it wouldn't be difficult to implement your suggestion. |
Hi Elliot, we've noticed that the GC recipe is currently pulling down 12.0.4 beta version. This happens to be the latest version in the Sparkle feed. Unfortunately the sparkle channel is only set for beta, not for production, so you can't specify a channel to get the right version. We also can't see any other keys that would help.
I'm wondering if it would be better to scrape and pull the DMG directly from the webpage (https://www.lemkesoft.de/en/products/graphicconverter/download/)?
The text was updated successfully, but these errors were encountered: