Re: How to unblock bugfix, pipeline failed with unrelated error in gtk

Den 2022-02-16 kl. 15:02, skrev Baldvin Kovacs via gtkmm-list:
> Hello,
>
> I'm trying to send a merge request of a bugfix 
> <https://gitlab.gnome.org/GNOME/gtkmm/-/merge_requests/66> in gtkmm, 
> but the build pipeline fails with an unrelated error 
> <https://gitlab.gnome.org/baldvin.kovacs/gtkmm/-/jobs/1828583> in (or 
> at least it seems so, the error is pasted to the bottom of this email).
>
> What's the usual way to go about this? Should I notify owners of Gtk? 
> By what channels? Or is it on me to track it down, get that fixed 
> first, before I can propose my Gtkmm fix to be considered?
>
> Thanks,
> Baldvin
>
> FAILED: subprojects/gtk/examples/application3/exampleapp3_resources.h
> /usr/bin/glib-compile-resources 
> ../subprojects/gtk/examples/application3/exampleapp.gresource.xml 
> --sourcedir ../subprojects/gtk/examples/application3/. --sourcedir 
> ../subprojects/gtk/examples/application3 --internal --generate 
> --target subprojects/gtk/examples/application3/exampleapp3_resources.h
> ../subprojects/gtk/examples/application3/exampleapp.gresource.xml: 
> Failed to close file descriptor for child process (Operation not 
> permitted).
>
The latest gtkmm commits require gtk4 >=4.6.0, but that's not available 
from the distro that the CI uses.

Dependency gtk4 found: NO found 4.4.1 but need: '>= 4.6.0'

Gtk is then built as a subproject of gtkmm. The latest patch on gtk's 
main branch is used. Today gtk folks have added patches that make their 
own CI pipeline fail. For the time being, just accept that the latest 
gtk patches don't work. The gtk folks will find out, and fix it themselves.

Hopefully that latest version of some distro will soon include gtk 
4.6.0. Then it won't be built as a subproject.

Kjell
||

_______________________________________________
gtkmm-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/gtkmm-list