-
Notifications
You must be signed in to change notification settings - Fork 28
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
Recipe Robot 2.3.1 gives "[ERROR] Sorry, I can't tell what format this app downloads in" for a .pkg file dragged/dropped onto it #205
Comments
NetBird's repo provides an unusually large number of release asset download formats, and it's understandable that Recipe Robot is having a hard time choosing which one to use. Providing the pkg file directly was a good thing to try, but in this case the enclosed app doesn't have a Sparkle feed or anything else that would point Recipe Robot back to an alternative way to download. Figuring out which asset to download is the main failure point. One potential solution to this is to adjust Recipe Robot to take another input parameter for |
That would be a great feature if implemented. But yeah, kinda figured it was something along those lines. If I ever find myself with sufficient quiet time (unlikely), might look into that. For now, in the end, I actually took the output generated by RecipeRobot for another program (Moonlight), copied the folder over, renamed everything relevant, then adjusted as needed. And got it working quite nicely. Just needed to wrap my head around what was involved. (I don't live in this space but only tweak/add recipes when needed. At this point I have a Munki installation with ~100 apps, but it started with just one 7-8 years ago I think, and I slowly added apps as I got tired of manually updating them on family/friends' computers.) So RecipeRobot still helped out. Can't thank you enough for this tool. |
I've just seen similar behaviour with rorywalsh/cabbage. If passing the .pkg url recipe robot ignores this and defaults to the zip file which is for linux
|
Describe the bug
While trying to generate a recipe for NetBird using either
.pkg
file directly onto Recipe RobotRecipe Robot errors out. With OPTION 1, the error is due to
This is not entirely surprising, as I see it's pulling down the wrong file (a .zip). But if you first download the .pkg file and drag/drop that directly onto Recipe Robot, it gets further but then errors with
This occurs, as said, even when it is specifically a
.pkg
that is dropped on Recipe Robot! And even though that same file looks perfectly normal when viewed in Suspicious Package.It is a pretty vanilla package. Inside is a simple app. I know Recipe Robot likely won't succeed anyway further along, since it can't find where it would get updates from (since no Sparkle feed, etc.). But it's the fact it is failing to understand the format when the file is exactly of one of the formats that it says it supports in the error message.
To Reproduce
Steps to reproduce the behavior:
For OPTION 1
[Do It!]
For OPTION 2
netbird_<version>_darwin.pkg
to download this packagenetbird_<version>_darwin.pkg
onto Recipe Robot[Do It!]
Expected behavior
If OPTION 1, I expected Recipe Robot to generate the usual recipes as it does for other GitHub repos.
If OPTION 2, obviously something didn't go right with OPTION 1, and I'm simply looking for more info/further steps since I am handing it a
.pkg
file!Screenshots
For OPTION 1:


For OPTION 2: (after dragging/dropping the .pkg file)

Desktop (please complete the following information):
autopkg version
: 2.7.3/usr/local/autopkg/python --version
: 3.10.4Additional context
I also tried doing this from Terminal, where I added the
--debug
flag. This is the output:The text was updated successfully, but these errors were encountered: