https://bugzilla.redhat.com/show_bug.cgi?id=1753543
Bug ID: 1753543
Summary: perl-Font-AFM for EL8
Product: Fedora EPEL
Version: epel8
Status: NEW
Component: perl-Font-AFM
Assignee: tcallawa(a)redhat.com
Reporter: xavier(a)bachelot.org
QA Contact: extras-qa(a)fedoraproject.org
CC: lxtnow(a)gmail.com, perl-devel(a)lists.fedoraproject.org,
rc040203(a)freenet.de, rob.myers(a)gtri.gatech.edu,
tcallawa(a)redhat.com, tremble(a)tremble.org.uk
Target Milestone: ---
Classification: Fedora
Hi,
Could you please branch and build perl-FontAFM for EPEL 8 ?
It is in the dependency chain of another package I'd like to maintain in EPEL
8.
Regards,
Xavier
--
You are receiving this mail because:
You are on the CC list for the bug.
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(a)redhat.com
Reporter: iamdexpl(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: berrange(a)redhat.com, ddick(a)cpan.org,
perl-devel(a)lists.fedoraproject.org
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.
https://bugzilla.redhat.com/show_bug.cgi?id=1694444
Bug ID: 1694444
Summary: Unescaped left brace in regex is deprecated here (and
will be fatal in Perl 5.32), passed through in regex;
marked by <-- HERE in m/ ( { <-- HERE } (?: / \* )? |
\* ) / at (eval 97) line 830.
Product: Fedora
Version: rawhide
Status: NEW
Component: amavisd-new
Assignee: juan.orti(a)miceliux.com
Reporter: dac.override(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: janfrode(a)tanso.net, juan.orti(a)miceliux.com,
perl-devel(a)lists.fedoraproject.org, steve(a)silug.org,
vanmeeuwen+fedora(a)kolabsys.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Unescaped left brace in regex is deprecated here (and will be fatal in Perl
5.32), passed through in regex; marked by <-- HERE in m/ ( { <-- HERE } (?: /
\* )? | \* ) / at (eval 97) line 830.
They fixed it here:
https://bz-attachments.freebsd.org/attachment.cgi?id=200278
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1691325
Bug ID: 1691325
Summary: Upgrade perl-Net-DNS-SEC to 1.12
Product: Fedora
Version: rawhide
Status: NEW
Component: perl-Net-DNS-SEC
Assignee: wjhns174(a)hardakers.net
Reporter: jplesnik(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: perl-devel(a)lists.fedoraproject.org,
pwouters(a)redhat.com, wjhns174(a)hardakers.net
Target Milestone: ---
Classification: Fedora
Latest Fedora delivers 1.11 version. Upstream released 1.12. When you have free
time, please upgrade it.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1690193
Bug ID: 1690193
Summary: perl-CPAN-2.26 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: perl-CPAN
Keywords: FutureFeature, Triaged
Assignee: ppisar(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: perl-devel(a)lists.fedoraproject.org, ppisar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Latest upstream release: 2.26
Current version/release in rawhide: 2.25-1.fc31
URL: http://search.cpan.org/dist/CPAN/
Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from anitya:
https://release-monitoring.org/project/2727/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1751896
Bug ID: 1751896
Summary: perl-Verilog-Perl-3.468 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: perl-Verilog-Perl
Keywords: FutureFeature, Triaged
Assignee: jplesnik(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: chitlesh(a)gmail.com, jplesnik(a)redhat.com,
perl-devel(a)lists.fedoraproject.org
Target Milestone: ---
Classification: Fedora
Latest upstream release: 3.468
Current version/release in rawhide: 3.466-3.fc31
URL: http://search.cpan.org/dist/Verilog-Perl/
Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from anitya:
https://release-monitoring.org/project/3494/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1710933
Bug ID: 1710933
Summary: Invalid DocumentLocator object passed to
Product: Fedora
Version: 30
Hardware: x86_64
OS: Linux
Status: NEW
Component: perl-XML-SAX
Assignee: jplesnik(a)redhat.com
Reporter: bug.report.tracker(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: caillon+fedoraproject(a)gmail.com, caolanm(a)redhat.com,
john.j5live(a)gmail.com, jplesnik(a)redhat.com,
kasal(a)ucw.cz, perl-devel(a)lists.fedoraproject.org,
rhughes(a)redhat.com, rstrode(a)redhat.com,
sandmann(a)redhat.com
Target Milestone: ---
Classification: Fedora
Created attachment 1569596
--> https://bugzilla.redhat.com/attachment.cgi?id=1569596&action=edit
perl XML::SAX::DocumentLocator test
Description of problem:
When parsing XLM data, set_document_locator is passed an empty hash instead of
DocumentLocator object.
Version-Release number of selected component (if applicable):
perl-XML-SAX-Base-1.09-7.fc30.noarch
perl-XML-SAX-1.00-4.fc30.noarch
How reproducible:
Always
Steps to Reproduce:
1. Run the attached test.
Actual results:
Test prints: $VAR2 = {};
Expected results:
A valid DocumentLocator object printed:
$VAR2 = bless( {
'ColumnNumber' => 0,
'Encoding' => undef,
'XMLVersion' => undef,
'LineNumber' => 1,
'SystemId' => undef,
'PublicId' => undef
}, 'XML::SAX::DocumentLocator' );
Additional info:
Test works on https://f.perl.bot/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1709199
Bug ID: 1709199
Summary: /usr/sbin/rt-setup-database segfaults
Product: Fedora
Version: 30
Status: NEW
Component: rt
Assignee: rc040203(a)freenet.de
Reporter: rc040203(a)freenet.de
QA Contact: extras-qa(a)fedoraproject.org
CC: perl-devel(a)lists.fedoraproject.org,
rc040203(a)freenet.de, tibbs(a)math.uh.edu
Target Milestone: ---
Classification: Fedora
Description of problem:
When setting up rt, /usr/sbin/rt-setup-database segfaults:
# /usr/sbin/rt-setup-database --action init --dba root --dba-password XXXXX
Working with:
Type: mysql
Host: localhost
Port:
Name: rt4
User: rt_user
DBA: root
Now creating a mysql database rt4 for RT.
Done.
Now populating database schema.
Done.
Now inserting database ACLs.
Done.
Now inserting RT core system objects.
Done.
Now inserting data.
Segmentation fault (core dumped)
Version-Release number of selected component (if applicable):
rt-4.4.4-1.fc30 (currently in updates-testing)
or
rt-4.4.3-3.fc30 (in release)
How reproducible:
Always.
Steps to Reproduce:
1. set up rt according to /usr/share/doc/rt/README.fedora
Actual results:
cf. above.
Expected results:
No segfault.
Additional info:
- Despite the segfault, rt's mysql db seems to be functional, afterwards,
AFAICT.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1742913
Bug ID: 1742913
Summary: biber-2.13 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: biber
Keywords: FutureFeature, Triaged
Assignee: cbm(a)m.fsf.org
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: cbm(a)m.fsf.org, jnovy(a)redhat.com, mefoster(a)gmail.com,
perl-devel(a)lists.fedoraproject.org
Target Milestone: ---
Classification: Fedora
Latest upstream release: 2.13
Current version/release in rawhide: 2.11-6.fc31
URL: http://biblatex-biber.sourceforge.net/
Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from anitya:
https://release-monitoring.org/project/6443/
--
You are receiving this mail because:
You are on the CC list for the bug.