Created attachment 1611740 [details]
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):
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
Created attachment 1611743 [details]
A less-strict template
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 30 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Still reproducible on F31 against GdkX11-3.0 (at least).
Reproducible on F32 against, for example, libxfce4-2.0 as well.
FEDORA-2020-e4ca77273f has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-e4ca77273f
Thanks for the report .
Sorry I missed this bug report, but with new version of perl-Glib-Object-Introspection I found it.
Is it worth updating the fedora 32 ?
FEDORA-2020-e4ca77273f has been pushed to the Fedora 33 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-e4ca77273f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-e4ca77273f
See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
> Sorry I missed this bug report, but with new version of
> perl-Glib-Object-Introspection I found it.
> Is it worth updating the fedora 32 ?
I think it does not — F33 is gonna release tomorrow.
FEDORA-2020-e4ca77273f has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.