← Back to issue list

appstream parsing fails when comments exist

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1852329
Type
issue
State
open
Author
~ken-vandine
Labels
Created
Updated
Closed

Current evaluation

Snapcraft fails to parse the appstream description when translator comments are present in the metainfo XML. Unlabelled, zero comments, no maintainer interaction, inactive for ~6.8 years.

Suggested action: needs triage

Reason: The report is a genuine bug with a concrete reproducer (a metainfo.xml.in containing a translator comment) but shows no sign of ever being assessed: no labels, zero comments, no maintainer response in ~6.8 years. I could not inspect the current snapcraft source (repo tooling returned no pinned SHA), so there is no evidence the bug is fixed or obsolete, which rules out close_stale; a maintainer should verify whether the parsing still fails on the current code before deciding.

Impact: 40 Quick Win: 28.0 Staleness: 95 Complexity: 30 Confidence: 50 Support Request: 10

Issue body

Snapcraft is failing to parse description from the appstream data when there is a translators comment present. For example: https://gitlab.gnome.org/kenvandine/gnome-firmware-updater/blob/snap/data/appdata/org.gnome.Firmware.metainfo.xml.in

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 40
Quick Win: 28.0
Staleness: 95
Complexity: 30
Confidence: 50
Support Request: 10
needs triage Snapcraft fails to parse the appstream description when translator comments are present in the metainfo XML. Unlabelled, zero comments, no maintainer interaction, inactive for ~6.8 years.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 20
Confidence: 90
Support Request: 10
close stale Snapcraft fails to parse AppStream descriptions when translator comments are present in the XML. The report is unlabelled, has zero comments, and has been inactive for over six years.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 25
Confidence: 90
Support Request: 10
close stale Snapcraft fails to parse appstream descriptions when translator comments are present in the XML. The issue has been open for over six years with no maintainer response or activity.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 20
Confidence: 90
Support Request: 5
close stale Snapcraft fails to parse AppStream descriptions when translator comments are present in the XML. The issue has been completely inactive for over six years with no maintainer response or labels.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 35
Confidence: 90
Support Request: 10
close stale Snapcraft fails to parse AppStream descriptions when translator comments are present in the XML. The issue has been inactive for over six years with no maintainer engagement or labels.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#1778719 appstream support lacking provided ids (impairing backwards compat) snapcraft (launchpad) open Snapcraft's appstream extractor and common-id mapping assume a single id per appstream file, ignoring <provides> ids needed for backwards compatibility and de-duplication. No maintainer response, no labels, 0 comments, last activity 2463 days ago.
71%
#1694 Develop appstream handler snapcraft closed Closed without implementation. Zero comments or pull requests were created, indicating the appstream metadata extraction feature was abandoned. Snapcraft continues to require manual metadata specification in snapcraft.yaml.
71%