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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use 23.04 craft cache version as pixman is not (yet) available in 23.07 #5874

Closed
wants to merge 1 commit into from

Conversation

m7913d
Copy link
Contributor

@m7913d m7913d commented Jul 9, 2023

KDE has recently switched the default craft cache version from 23.04 to 23.07 (see KDE/craft@a860e18). This new version does not include (yet?) the pixman libraries (see https://files.kde.org/craft/master/23.07/windows/cl/msvc2019/x86_64/RelWithDebInfo).

Advantage of using a specific version is that new PR will not start to fail due to an (unexpected) upstream change.

This PR fixes the failed "Windows Build and Test / Build" Github workflow.

KDE has recently switched the default craft cache version from 23.04 to 23.07 (see KDE/craft@a860e18). This new version does not include (yet?) the pixman libraries (see https://files.kde.org/craft/master/23.07/windows/cl/msvc2019/x86_64/RelWithDebInfo).

Advantage of using a specific version is that new PR will not start to fail due to an (unexpected) upstream change.

Signed-off-by: m7913d <[email protected]>
@nextcloud-desktop-bot
Copy link

AppImage file: nextcloud-PR-5874-ba2ac850e7a4b4ad867b0880678b0eade46fbfe5-x86_64.AppImage

To test this change/fix you can simply download above AppImage file and test it.

Please make sure to quit your existing Nextcloud app and backup your data.

@m7913d
Copy link
Contributor Author

m7913d commented Jul 11, 2023

The pixman library is now available in 23.07 too. Moreover, the pixman dependency is removed in commit nextcloud/desktop-client-blueprints@c9a496e.

Either we should close this commit or we may set the Packager/CacheVersion to 23.07. Advantage of explicitly setting the cache version is that future upstream changes will not make (unrelated) PR to fail randomly.

@mgallien
Copy link
Collaborator

@m7913d I am not a fan of setting the version. In the past we did hardcode some version requirements in Craft to workaround temporary build failures. Then later the build fail because we did not follow up changes in upstream.

as far as I can say, I would think that a cache refreshed via a scheduled action running maybe once a week and overriding existing cache only on success would isolate from temp failures without having to set versions in stone

as I have no time to work on this, I am not asking you to do it for me 😄

Copy link
Collaborator

@mgallien mgallien left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please rebase on top of master branch

@m7913d
Copy link
Contributor Author

m7913d commented Jul 12, 2023

Closing the PR as @mgallien prefers not setting a fixed version and 23.07 is now supported (see my previous comment).

@m7913d m7913d closed this Jul 12, 2023
@mgallien
Copy link
Collaborator

by the way, sorry
I forgot to say thank you @m7913d

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.

4 participants