Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Inconsistent usage of appimagetool in release distributations
See original GitHub issueI’ve run into a problem where the continuous version of appimagetool-x86_64.AppImage (built Apr 03, 2022) is causing my appimage to crash with the error: APPRUN_ERROR: Bad address (I’ll be creating an issue in appimagetool for this problem).
I had a manual install of appimage-builder but I noticed that this project recently released v1.0.0 as a pre-built appimage. So downloaded that and tried it and I get the same error.
- I did a little digging and I can see that for the v1.0.0 tag of AppImage-builder there is the recipes/AppImageBuilder.yaml file which I assume is what is used to build the prebuilt appimage. That file references the continuous version of appimagetool-x86_64.AppImage (this seems like bad practice to me).
- I can also see that the Dockerfile,which is how I assume you create the Docker image, it references version 13 of appimagetool-x86_64.AppImage, that seems like good practice but is inconsistent with the pre-built appimage.
It seems that release version of appimage-builder should be consistent from one distribution method to another and it should probably reference released software not pre-release software that is likely to change from build to build and to have bugs.
Issue Analytics
- State:
- Created a year ago
- Comments:12 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
And to the point of consistency it looks like your Dockerfile is pulling appimagetool version 13.
https://github.com/AppImageCrafters/appimage-builder/blob/dd041050e65f8eff28f878a092fd07bcf3ec5a4d/Dockerfile#L12
@azubieta so it sounds like you’ve reversed course from your statement a few days ago:
Which I suppose is fine as long as your consistent and are relatively confident that the continuous build of appimagetool is free of problems at the time the that you create your release. I would be a bit concerned that older continuous builds are not saved as released so if a new continuous build of appimagetool occurs you will not be able to rebuild v1.0.2 of appimage-builder.