Skip to content

Public Build Artifact: Linux 241416612

Pre-release
Pre-release
Compare
Choose a tag to compare
@github-actions github-actions released this 06 Sep 06:53
241416612_linux
7ad1851
This commit was signed with the committer’s verified signature. The key has expired.
maltfield Michael Altfield
GPG key ID: F8550ED542C2C919
Expired
Verified
Learn about vigilant mode. 
switching to pip install directly in AppImage

The previous solution of doing the `pip install` with the system's python, then rsync'ing into the AppImage had a couple issues:

 1. It was overwriting bin/python3.7 with a symlink back outside the AppImage, totally defeating the purpose of the AppImage and causing issues with systems that don't have python3.7 installed (see https://github.com/maltfield/cross-platform-python-gui/issues/4)

 2. It means that the system must have the same python version as the python version that's in our base python AppImage

I'm attempting to do this the proper way, but it's currently failing on my local system with this error:

	+ /tmp/appimagetool.AppImage /tmp/kivy_appdir dist/helloWorld.AppImage
	appimagetool, continuous build (commit effcebc), build 2084 built on 2019-05-01 21:02:41 UTC
	WARNING: appstreamcli command is missing, please install it if you want to use AppStream metadata
	Using architecture x86_64
	/tmp/kivy_appdir should be packaged as dist/helloWorld.AppImage
	AppStream upstream metadata found in usr/share/metainfo/python3.7.8.appdata.xml
	Generating squashfs...
	Parallel mksquashfs: Using 4 processors
	Creating 4.0 filesystem on dist/helloWorld.AppImage, block size 131072.
	[===========================================-                  ] 3820/5306  71%
	FATAL ERROR:gzip uncompress failed with error code -3
	Embedding ELF...
	Not able to open the AppImage for writing, aborting

I'm hoping that this is a memory-bound issue and it will "just work" on the GitHub shared runner cloud *fingers crossed*

 * https://github.com/AppImage/AppImageKit/issues/398#issuecomment-421107262
Assets 3
Loading