https://bugzilla.redhat.com/show_bug.cgi?id=1749132 Bug ID: 1749132 Summary: Too strict gir lib search pattern Product: Fedora Version: 30 Status: NEW Component: perl-Glib-Object-Introspection Assignee: berrange@xxxxxxxxxx Reporter: iamdexpl@xxxxxxxxx QA Contact: extras-qa@xxxxxxxxxxxxxxxxx CC: berrange@xxxxxxxxxx, ddick@xxxxxxxx, perl-devel@xxxxxxxxxxxxxxxxxxxxxxx Target Milestone: --- Classification: Fedora Created attachment 1611740 --> https://bugzilla.redhat.com/attachment.cgi?id=1611740&action=edit A less-strict template Description of problem: perli11ndoc script from perl-Glib-Object-Introspection can either display a window with a drop-down list of available GIRs or, if launched with a GIR name, find the corresponding file, parse it and dump to stdout. The latter mode has, among other things, a check whether the given argument can be a valid GIR name. However the pattern to check against is too strict. For example, it filters out GdkX11, libxfce4panel, libxfce4ui, libxfce4util and PangoFT2 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. install and of the following — pango-devel, xfce4-panel, libxfce4ui, gtk3-devel, libxfce4util 2. run perli11ndoc without arguments; ensure that the GIR matching the installed package is listed in a drop-down list 3. run perli11ndoc GdkX11 (or whatever name from that packages installed on step 1) Actual results: "Cannot recognize the library name" on stderr Expected results: contents of that GIR on stdout -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ perl-devel mailing list -- perl-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to perl-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@xxxxxxxxxxxxxxxxxxxxxxx
