Bug#1079548: gtk4: upload of 4.16 to unstable blocked by riscv64 build

[Aurelien Jarno]

On 2024-09-12 11:53, Simon McVittie wrote:
> Control: unblock -1 by 1081275
> 
> On Sat, 24 Aug 2024 at 09:37:57 -0400, Jeremy Bícha wrote:
> > This is a tracker bug with known blockers for uploading the new gtk4
> > series 4.15.x/4.16.x to Unstable.
> > 
> > The new gtk4 series is required for libadwaita 1.6 which is required
> > by many GNOME 47 apps.
> 
> I believe we are now only waiting for GTK 4.16.0+ds-2 to be successfully
> built on a riscv64 buildd. (It works on a porterbox, but it would be safer
> to have a successful build on a buildd before going to unstable.)
> 
> Would it be possible for a riscv64 porter or a buildd operator to bump up
> the priority of gtk4/experimental (gtk4_4.16.0+ds-2) on riscv64, to get that
> built a bit sooner?

It seems it has been done. Unfortunately it failed to build from source,
but it is not riscv64 specific and can be reproduced easily on amd64.

As a first guess by looking at the packages difference, it seems to be
due to weston 14, and seems to be corroborated by the corresponding
autopkgtest:

https://ci.debian.net/packages/g/gtk4/testing/amd64/51575899/

Regards
Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien at aurel32.net                     http://aurel32.net