Having resolved the initial issue of “stupid typo” in my last post, I have now encountered a new error:
Composing metadata...
Run failed, some data was ignored.
Errors were raised during this compose run:
general
E: filters-but-no-output
io.github.evilsupahfly.amulet_flatpak
E: file-read-error
Refer to the generated issue report data for details on the individual problems.
Error: ERROR: appstreamcli compose failed: Child process exited with code 1
[2024-10-14 09:58:15] ERROR: flatpak-builder failed.
I fixed the mismatched ID and tried to build the flatpak again, but it started complaining about not having a .desktop or icon, so I added them and updated my XML and YML sources accordingly (pasted below).
I’ve read through the Desktop Integration docs, the Metainfo Guidelines pages, and to be sure I was following the expected conventions, I read through Requirements & Conventions, but I’m still somehow missing something.
I initially didn’t change the YML, but that caused an error, so I added the .desktop and icon lines to the existing metadata-xml section. When that failed, I gave them their own sections, and that too failed.
New XML:
<?xml version="1.0" encoding="UTF-8"?>
<component type="desktop-application">
<id>io.github.evilsupahfly.amulet_flatpak</id>
<name>Amulet Map Editor - Flatpak Edition</name>
<summary>Amulet is a Minecraft world editor that allows users to modify and create worlds with ease</summary>
<metadata_license>FTL</metadata_license>
<project_license>AGPL-3.0-or-later</project_license>
<description>
<p>
Amulet is a simple, yet powerful, world editor for modifying Minecraft saved worlds.
</p>
</description>
<developer id="io.github.evilsupahfly.amulet_flatpak">
<name>Amulet Developer: Team Amulet</name>
<name>Flatpak Developer: EvilSupahFly</name>
</developer>
<url type="homepage">https://github.com/amulet-Team/Amulet-Map-Editor/</url>
<url type="vcs-browser">https://github.com/EvilSupahFly/Amulet-Flatpak/</url>
<releases>
<release version="0.10.36" date="2024-01-18">
<url type="details">https://github.com/EvilSupahFly/Amulet-Flatpak/releases/tag/0.10.36</url>
</release>
</releases>
<launchable type="desktop-id">io.github.evilsupahfly.amulet_flatpak.desktop</launchable>
<icon type="stock">io.github.evilsupahfly.amulet_flatpak.png</icon>
<content_rating type="oars-1.0">
<content_attribute id="social-chat">moderate</content_attribute>
</content_rating>
<categories>
<category>Game</category>
<category>KidsGame</category>
</categories>
</component>
New YML:
id: io.github.evilsupahfly.amulet_flatpak
name: Amulet Map Editor
version: 0.10.36
runtime: org.freedesktop.Platform
runtime-version: '24.08'
sdk: org.freedesktop.Sdk
command: amulet_map_editor
finish-args:
- --device=all
- --share=network
- --share=ipc
- --socket=fallback-x11
- --socket=wayland
- --filesystem=home:persistent
- --filesystem=~/.cache:persistent
- --filesystem=host:create
- --env=LIBGL_ALWAYS_SOFTWARE="0"
- --env=OPENGL_VERSION=3.3
- --env=OPENGL_LIB=/usr/lib/x86_64-linux-gnu/libGL.so
- --env=PYTHONDEBUG=3
- --env=PYTHONVERBOSE=3
- --env=PYTHONTRACEMALLOC=10
modules:
- shared-modules/glew/glew.json
- shared-modules/glu/glu-9.json
- pip-gen.yaml
- name: metainfo-xml
buildsystem: simple
build-commands:
- install -Dm644 io.github.evilsupahfly.amulet_flatpak.metainfo.xml -t ${FLATPAK_DEST}/share/metainfo/
sources:
- type: file
path: io.github.evilsupahfly.amulet_flatpak.metainfo.xml
- name: metainfo-ico
buildsystem: simple
build-commands:
- install -Dm644 io.github.evilsupahfly.amulet_flatpak.png -t ${FLATPAK_DEST}/share/icons/hicolor/256x256/apps/io.github.evilsupahfly.amulet_flatpak.png
sources:
- type: file
path: io.github.evilsupahfly.amulet_flatpak.png
- name: metainfo-desktop
buildsystem: simple
build-commands:
- install -Dm755 io.github.evilsupahfly.amulet_flatpak.desktop -t ${FLATPAK_DEST}/share/applications/io.github.evilsupahfly.amulet_flatpak.desktop
sources:
- type: file
path: io.github.evilsupahfly.amulet_flatpak.desktop
versioning:
auto-increment: true
The files exist in the root folder of the project, along side the XML file. I also created the directory structures under share thinking that would resolve this, but that didn’t help either.
Please tell me I didn’t miss something stupidly obvious again like last time… Is there a means by which I can obtain a more detailed log upon failure?