Description of problem: perl-Gtk3 is failing to rebuild from source in rawhide and Fedora 30 because of broken GIR data for GdkPixdata's gdk_pixbuf_new_from_inline API: GLib-GIO-Message: 11:57:56.999: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications. Gtk3::Gdk::Pixbuf::new_from_inline: passed too few parameters (expected 4, got 3) at t/overrides.t line 762. # Looks like your test exited with 255 just after 162. t/overrides.t .................. This was reported upstream by Debian: https://gitlab.gnome.org/GNOME/gdk-pixbuf/issues/92 Please pull the patches mentioned in that ticket into Fedora 29 and Fedora 30 ASAP, so I can resolve the FTBFS for perl-Gtk3 Version-Release number of selected component (if applicable): gdk-pixbuf2-2.38.0-4.fc29.x86_64 How reproducible: Always Steps to Reproduce: 1. Try to build perl-Gtk3 2. 3. Actual results: Test suite fails with GLib-GIO-Message: 11:57:56.999: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications. Gtk3::Gdk::Pixbuf::new_from_inline: passed too few parameters (expected 4, got 3) at t/overrides.t line 762. # Looks like your test exited with 255 just after 162. t/overrides.t .................. Expected results: Tests succeed. Additional info:
Thanks, backported as https://src.fedoraproject.org/rpms/gdk-pixbuf2/c/c3941b7a6cd1e281f2f5ff220d9a6e65ea568e42?branch=master
gdk-pixbuf2-2.38.0-6.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-7c134bf772
gdk-pixbuf2-2.38.0-6.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-7c134bf772
gdk-pixbuf2-2.38.0-6.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.