Update guidelines/modules/ROOT/pages/AppData.adoc to reference new validation tool

alexanderwilms commented

2023-09-07 22:21:03 +00:00

First-time contributor

The appstreamcli belonging to the appstream project supercedes appstream-util, which belongs to the appsttream-glib project:

https://github.com/hughsie/appstream-glib/issues/471#issuecomment-1650635348
https://github.com/ximion/appstream

The appstreamcli belonging to the appstream project supercedes appstream-util, which belongs to the appsttream-glib project: https://github.com/hughsie/appstream-glib/issues/471#issuecomment-1650635348 https://github.com/ximion/appstream

decathorpe commented

2023-09-07 22:27:15 +00:00

Owner

This is a known issue: https://pagure.io/packaging-committee/issue/1053

Long story short: Both tools / libraries are still in use, so we would actually need to validate with both tools.

This is a known issue: https://pagure.io/packaging-committee/issue/1053 Long story short: Both tools / libraries are still in use, so we would actually need to validate with *both* tools.

alexanderwilms commented

2023-09-07 22:43:54 +00:00

Author

First-time contributor

rebased onto cac9c28de5

rebased onto cac9c28de5e0ec94284165a5decbd13561699d8f

alexanderwilms commented

2023-09-07 22:49:56 +00:00

Author

First-time contributor

1 new commit added

Require validation using both appstream-util and appstreamcli

**1 new commit added** * ``Require validation using both appstream-util and appstreamcli``

alexanderwilms commented

2023-09-07 22:53:39 +00:00

Author

First-time contributor

Ah, I had come across that issue some time ago.

Should I mention both tools? Maybe that'd ease the transition.

Or should I leave it be until there's a decision?

Ah, I had come across that issue some time ago. Should I mention both tools? Maybe that'd ease the transition. Or should I leave it be until there's a decision?

carlwgeorge added the

meeting

label

2026-05-01 19:37:35 +00:00

carlwgeorge commented

2026-05-01 19:41:24 +00:00

Owner

Heads up @alexanderwilms, it looks like your pull request broke during the migration to forge.fpo. If you create a new fork here, you should be able to push the commits from your old fork to there. Once that is done, I think you can click the edit button by the subject and set a new "pull from" branch. If it doesn't work, you can always just create a new pull request.

On the topic itself, I think maybe instead of requiring validation with both tools, we should require that validation is done but with either tool. Sometimes appdata passes with one and fails with the other, so each package should align with their upstream.

Heads up @alexanderwilms, it looks like your pull request broke during the migration to forge.fpo. If you create a new fork here, you should be able to push the commits from your old fork to there. Once that is done, I think you can click the edit button by the subject and set a new "pull from" branch. If it doesn't work, you can always just create a new pull request. On the topic itself, I think maybe instead of requiring validation with both tools, we should require that validation is done but with either tool. Sometimes appdata passes with one and fails with the other, so each package should align with their upstream.

ngompa commented

2026-05-01 19:56:09 +00:00

Owner

We cannot change the tool recommendation until our appstream repodata is composed with appstream-generator. Otherwise we're going to have broken repodata.

carlwgeorge commented

2026-05-01 21:17:07 +00:00

Owner

If that's the rationale for using one tool over the other, maybe that should be mentioned explicitly in the guidelines so future maintainers can know when/if the guideline can change.

This branch is already included in the target branch. There is nothing to merge.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin main:main

git switch main

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main

git merge --no-ff main

git switch main

git rebase main

git switch main

git merge --ff-only main

git switch main

git rebase main

git switch main

git merge --no-ff main

git switch main

git merge --squash main

git switch main

git merge --ff-only main

git switch main

git merge main

git push origin main

Rows
Columns

Update guidelines/modules/ROOT/pages/AppData.adoc to reference new validation tool #1299

Checkout

Merge