Re: [AUH] kmscube: upgrading to f632b23a528ed6b4e1fddd774db005c30ab65568 SUCCEEDED

Re: [AUH] kmscube: upgrading to f632b23a528ed6b4e1fddd774db005c30ab65568 SUCCEEDED

[Carlos Rafael Giani]

Hi,

FYI: I have updated kmscube to perform run-time checks that replace the 
existing build-time gbm_bo_map() check (which is what the patch in the 
kmscube folder is about), since upstream prefers run-time checks via 
weak functions. The commit is here: 
https://gitlab.freedesktop.org/dv1/kmscube/commit/99264af7f2b820f7464ff3036a49aff3dd7fd8cf

Unfortunately, I have no platform with a Mali GPU, so I cannot test-run 
these changes. I have asked the authors mentioned in the patch for help. 
If anybody else here can also test-run this on a Mali-enabled platform, 
it would be very helpful. Once I get an OK from test-runs, I'll update 
the recipes to use this instead of the existing patch.

On 17.08.19 19:49, auh@auh.yoctoproject.org wrote:
> Hello,
>
> You are receiving this email because you are the maintainer
> of *kmscube* recipe and this is to let you know that the automatic attempt
> to upgrade the recipe to *f632b23a528ed6b4e1fddd774db005c30ab65568* has Succeeded.
>
> Next steps:
>      - apply the patch: git am 0001-kmscube-upgrade-to-latest-revision.patch
>      - check the changes to upstream patches and summarize them in the commit message,
>      - compile an image that contains the package
>      - perform some basic sanity tests
>      - amend the patch and sign it off: git commit -s --reset-author --amend
>      - send it to the appropriate mailing list
>
> Alternatively, if you believe the recipe should not be upgraded at this time,
> you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
> automatic upgrades would no longer be attempted.
>
> Please review the attached files for further information and build/update failures.
> Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
>
> Regards,
> The Upgrade Helper