"execv error: No such file or directory" on current version of the demo appimage #2
Comments
|
Thank you. I cannot repeat the problem here (running Fedora 37). Interesting. You say that PupNet-Deploy.x86_64.AppImage version 1.2.1 does not run on your system, but version 1.0.0 runs fine, along with the Avant Garde AppImage? There is one difference between how these were built, which is the runtime is explicitly provided in the later version. I.e. we call:
rather than:
This should make no difference tho. I'm going to test on a Ubuntu LTS and get back to you. Cheers Andy |
|
Update. Ref: AppImage/AppImageKit#1004 |
|
Thank you for the quick reply, I just tried the appimage version of pupnet-deploy and the first 2 releases (before fuse was included) works great and was able to use them instead of the dotnet tools version to build the appimages. The later versions gets Maybe it has something to do with the included fuse runtime? |
|
Hello @justbugs97 Can you try the test HelloWorld AppImage link below and let me know if it runs on your system? It is just the same, but without the explicit --runtime arg to the appimagetool. https://github.com/kuiperzone/PupNet-HelloWorld/releases/download/v1-temp/HelloWorld.x86_64.AppImage Cheers, thanks PS. I will have another to try shortly, as have an idea what the problem could be. |
|
That it does! I guess that's the culprit found |
|
Thank you. The problem with that as a solution, is that a package built on x86_64 for Arm64 will not run on the target system unless I explicitly supply the runtime during the build. That is why I did it. However, I was given a link to the fuse runtimes during a discussion with AppImageKit author concerning Arm. The thing is that the link he gave me points to a continuous build repository, hence the runtime I supply are not the same version as appimagetool expects. At least that's my thinking. So gonna try a new HelloWorld shortly. If that fails, I will need to go back to the AppImage guys. |
|
Alright, I'm off for a few hours but I'll try as soon as I get home |
|
OK. Try this one: If this works, the problem should be resolved and there'll be a patch release immediately. |
|
That works! Was in a bit of an accident, I'm mostly fine now. |
|
Hope the accident wasn't serious and you're OK. Thank you for raising this one. See: https://github.com/kuiperzone/PupNet-Deploy/releases/tag/v1.2.2 |
OS: Arch Linux 6.2.8-zen kernel
.NET: 7.0.103
PupNet: 1.2.1
My first attempts at running the demo appimage was by running
pupnet -k appimagefrom the cloned repo and while it was built successfully, when I tried to run it I was greeted by the above error. I made sure that the name was correct and that I had execution rights.I then tried to download the latest appimage from the "patch" release and it also failed to run, however when I tried the initial release version it finally worked without a hitch.
Out of curiosity I also tried your other app "AvantGarde", and the latest release appimage works fine as well, however when I try and build my own from the source I get the same error again when I try to run that version.
Here's the log of the build of helloworld demo:
The text was updated successfully, but these errors were encountered: