Closed eszlari closed 4 years ago
Started test build 11259
Build 11259 failed
How about this solution:
This is easier to edit from the Github UI.
Also I don't see why this is happening. Looks like the page should have been updated.
You have two top-level <releases>
tags.
Started test build 11263
I'm planing on submitting a patch like this upstream:
https://github.com/obsproject/obs-studio/commit/6b9da9b9127f066e782d0fe8be5cc703da570d1f
Then the release entry will always be up to date.
Build 11263 successful To test this build, install it from the testing repository:
flatpak install --user https://dl.flathub.org/build-repo/10733/org.darktable.Darktable.flatpakref
Started test build 11266
Build 11266 successful To test this build, install it from the testing repository:
flatpak install --user https://dl.flathub.org/build-repo/10735/org.darktable.Darktable.flatpakref
You have two top-level
<releases>
tags.
Oops. Seriously I missed that. Now the drastic appstream util validate
didn't catch that either.
Sorry this is too cryptic as a solution.
If you want to submit to upstream something that will update the appdata file automatically, feel free.
I have pushed a patch to fix this issue here.
https://flathub.org/apps/details/org.darktable.Darktable still shows 2.6.2