Stable publish validation failed for io.github.maddecoder.Classic-RBDOOM-3-BFG
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
Research direction
Inspect the appstream diagnostic for io.github.maddecoder.Classic-RBDOOM-3-BFG.metainfo.xml at line 29, where description markup has an invalid attribute. Read the AppStream validation guidance linked in the issue, then check the publication build log. Done means the metadata passes validation; the issue asks contributors not to modify or close it until an admin responds.
Written by the indexing model from the issue text.
Description
The build for io.github.maddecoder.Classic-RBDOOM-3-BFG failed validation during publication in the stable repository.
Build Information:
- Commit SHA: 1c17df4f66d41b1761d01557314ed8a73b1c2a23
- Build ID: 335367
- Build log: https://github.com/flathub-infra/vorarbeiter/actions/runs/41241478289
Validation Failure:
1 out of 1 checks failed (flathub-hooks)
One or more validations failed.
{"diagnostics":[{"refstring":"app/io.github.maddecoder.Classic-RBDOOM-3-BFG/x86_64/stable","is_warning":false,"category":"flatpak_builder_lint","data":{"stdout":{"appstream":["E:io.github.maddecoder.Classic-RBDOOM-3-BFG.metainfo.xml:description-markup-attribute-invalid:29 Elements of description markup must not have any attributes set, with the exception of a language property on paragraphs and list items in MetaInfo files. Any other attribute is not permitted and will be removed when the metadata is read."],"errors":["appstream-failed-validation"],"info":["appstream-failed-validation: Metainfo file io.github.maddecoder.Classic-RBDOOM-3-BFG.metainfo.xml has failed validation. Please see the errors in appstream block"],"message":"See https://docs.flathub.org/linter for details and exceptions"},"stderr":""}}]}
cc @flathub/reviewers
This issue is being opened for tracking by Flathub admins and may indicate an infrastructure problem. Please do not close or modify this until an admin has responded.
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- Avg merge
- 15h 31m
- Merged PRs (30d)
- 3
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
Djangonauts
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
render-engine/render-engine-cli#71 ·
Maintainers usually reply within 1 day
-
Installation guide's prerequisites leave out ca-certificates, which a no-recommends system needsOpenbot-found documentation priority: P3
Difficulty 1/5 Under an hour Newbie friendliness 94/100
madenvel/KalinkaPlayer#544 ·
-
debt python-version
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
microsoft/vscode-flake8#614 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days