Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update cmake-3.28.1.tar.gz to 3.28.2 #171

Merged
merged 5 commits into from Feb 2, 2024
Merged

Update cmake-3.28.1.tar.gz to 3.28.2 #171

merged 5 commits into from Feb 2, 2024

Conversation

flathubbot
Copy link
Contributor

馃 This pull request was automatically generated by flathub-infra/flatpak-external-data-checker. Please open an issue if you have any questions or complaints. 馃

@flathubbot
Copy link
Contributor Author

Started test build 96636

@flathubbot
Copy link
Contributor Author

Build 96636 failed

@bbhtt
Copy link

bbhtt commented Jan 30, 2024

Looks like the icon was always wrong?

image

image

@travier
Copy link
Member

travier commented Jan 30, 2024

{
    "errors": [
        "appstream-missing-developer-name",
        "desktop-file-icon-key-wrong-value"
    ],
    "warnings": [
        "appstream-summary-too-long",
        "appstream-screenshot-missing-caption",
        "finish-args-contains-both-x11-and-wayland"
    ]
}

@flathubbot
Copy link
Contributor Author

Started test build 96721

@flathubbot
Copy link
Contributor Author

Build 96721 failed

@flathubbot
Copy link
Contributor Author

Started test build 96731

@flathubbot
Copy link
Contributor Author

Build 96731 failed

@travier
Copy link
Member

travier commented Jan 30, 2024

{
    "errors": [
        "desktop-file-icon-key-wrong-value",
        "appstream-failed-validation"
    ],
    "warnings": [
        "appstream-summary-too-long",
        "appstream-screenshot-missing-caption"
    ],
    "appstream": [
        "style-invalid         : <caption> is too long [Main KDevelop window with the code view, terminal integration at the bottom, project files on the left];longest allowed is 100 chars"
    ]
}

One down, one new :/

@bbhtt
Copy link

bbhtt commented Jan 30, 2024

One down, one new :/

You have to fix the desktop file too btw: desktop-file-icon-key-wrong-value Feel free to ping me if you need any help on this or any other apps.

@travier
Copy link
Member

travier commented Jan 30, 2024

I don't understand exactly what I need to fix. Help or pointers appreciated if you know where to look.

@flathubbot
Copy link
Contributor Author

Started test build 96741

@bbhtt
Copy link

bbhtt commented Jan 30, 2024

I don't understand exactly what I need to fix. Help or pointers appreciated if you know where to look.

The icon name in the desktop file is not a value flatpak exports, #171 (comment)

It should be a value flatpak exports like Icon=$FLATPAK_ID or combinations mentioned here https://docs.flathub.org/docs/for-app-authors/linter#desktop-file-icon-key-wrong-value

Flatpak won't export an icon that doesn't match the pattern described. So kdevelop won't be exported by flatpak as a result, the desktop file shows up without any icon on shell/overview/launchers etc.

@bbhtt
Copy link

bbhtt commented Jan 30, 2024

Only the main desktop file ie. $FLATPAK_ID.desktop is checked so I guess it is this one https://github.com/KDE/kdevelop/blob/9d98eb9ed94b838ccbccc073ad4224c15e56e707/app/org.kde.kdevelop.desktop#L5

You can use something like desktop-file-edit --set-key="Icon" --set-value="${FLATPAK_ID}" "${FLATPAK_DEST}/share/applications/${FLATPAK_ID}.desktop" in a post-install command/or a patch or patch it upstream whichever is preferred.

@bbhtt
Copy link

bbhtt commented Jan 30, 2024

Actually looks like the icons are also named wrong, so no icons are being exported too. You have to add a rename-icon: kdevelop too in the top.

@travier
Copy link
Member

travier commented Jan 30, 2024

Hum, doesn't this mean that we have to rename the icon as well? Maybe with https://docs.flatpak.org/en/latest/manifests.html#file-renaming ?

@bbhtt
Copy link

bbhtt commented Jan 30, 2024

Hum, doesn't this mean that we have to rename the icon as well? Maybe with https://docs.flatpak.org/en/latest/manifests.html#file-renaming ?

Yep just said that

@travier
Copy link
Member

travier commented Jan 30, 2024

Oh indeed, my bad. Thanks

@flathubbot
Copy link
Contributor Author

Started test build 96744

@flathubbot
Copy link
Contributor Author

Build 96741 was cancelled

@travier
Copy link
Member

travier commented Jan 30, 2024

error: /srv/buildbot/worker/build-x86_64/build/builddir/export/share/icons/hicolor/1024x1024/apps/org.kde.kdevelop.png is not a valid icon: Image too large (1024x1024). Max. size 512x512

@flathubbot
Copy link
Contributor Author

Build 96744 was cancelled

@flathubbot
Copy link
Contributor Author

Started test build 96747

@flathubbot
Copy link
Contributor Author

Build 96747 successful
To test this build, install it from the testing repository:

flatpak install --user https://dl.flathub.org/build-repo/79506/org.kde.kdevelop.flatpakref

@travier
Copy link
Member

travier commented Jan 30, 2024

馃帀 Thanks @bbhtt !

@bbhtt
Copy link

bbhtt commented Jan 31, 2024

Thanks, it now correctly appears with the icon:

image

@travier
Copy link
Member

travier commented Jan 31, 2024

Let's hold until we have an agreement about the developer name discussion and then I'll merge all the updates.

@travier
Copy link
Member

travier commented Feb 2, 2024

bot, build

@flathubbot
Copy link
Contributor Author

Queued test build for org.kde.kdevelop.

@flathubbot
Copy link
Contributor Author

Started test build 97427

@flathubbot
Copy link
Contributor Author

Build 97427 successful
To test this build, install it from the testing repository:

flatpak install --user https://dl.flathub.org/build-repo/80203/org.kde.kdevelop.flatpakref

@travier travier merged commit b8a12b1 into master Feb 2, 2024
1 check passed
@travier travier deleted the update-9c295c7 branch February 2, 2024 19:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants