[Bug 1418399] New: _WARN:
Use of uninitialized value in subroutine entry at /usr/lib64/perl5/
vendor_perl/Encode/MIME/Header.pm line 198
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1418399
Bug ID: 1418399
Summary: _WARN: Use of uninitialized value in subroutine entry
at /usr/lib64/perl5/vendor_perl/Encode/MIME/Header.pm
line 198
Product: Fedora
Version: 25
Component: perl-Encode
Severity: high
Assignee: ppisar(a)redhat.com
Reporter: mysqlstudent(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: perl-devel(a)lists.fedoraproject.org, ppisar(a)redhat.com
Description of problem:
_WARN: Use of uninitialized value in subroutine entry at
/usr/lib64/perl5/vendor_perl/Encode/MIME/Header.pm line 198
Version-Release number of selected component (if applicable):
# rpm -qf /usr/lib64/perl5/vendor_perl/Encode/MIME/Header.pm
perl-Encode-2.88-5.fc25.x86_64
How reproducible:
It appears to be ongoing with amavisd-new-2.11.0-4.fc25.noarch
Steps to Reproduce:
1. Run amavisd-new with spamassassin
2.
3.
Actual results:
_WARN: Use of uninitialized value in subroutine entry at
/usr/lib64/perl5/vendor_perl/Encode/MIME/Header.pm line 198
Expected results:
No warning
Additional info:
All latest updates applied
perl-5.24.1-383.fc25.x86_64
amavisd-new-2.11.0-4.fc25.noarch
spamassassin-3.4.2-45.fc25.x86_64
spamassassin-iXhash2-2.05-9.fc24.noarch
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 4 months
[Bug 1436968] New: Numerous testsuite errors w/ DBD::MySQL 4.042
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1436968
Bug ID: 1436968
Summary: Numerous testsuite errors w/ DBD::MySQL 4.042
Product: Fedora
Version: 25
Component: rt
Severity: high
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
Description of problem:
The upgrade of perl-DBD-MySQL to 4.042 causes numerous testsuite errors in
rt-4.4.1's testsuite, similar to this:
...
# t/mail/charsets-outgoing-plaintext.t ................ 1/80 Wide
character in field 14 but mysql_enable_utf8 not set at
/usr/share/perl5/vendor_perl/DBIx/SearchBuilder/Handle.pm line 586.
# Failed test 'all mails have correct data'
# at t/mail/charsets-outgoing-plaintext.t line 78.
Wide character in field 1 but mysql_enable_utf8 not set at
/usr/share/perl5/vendor_perl/DBIx/SearchBuilder/Handle.pm line 586.
Wide character in field 8 but mysql_enable_utf8 not set at
/usr/share/perl5/vendor_perl/DBIx/SearchBuilder/Handle.pm line 586.
t/mail/charsets-outgoing-plaintext.t ................ 12/80 Wide
character in field 4 but mysql_enable_utf8 not set at
/usr/share/perl5/vendor_perl/DBIx/SearchBuilder/Handle.pm line 586.
# Failed test 'all mails have correct data'
# at t/mail/charsets-outgoing-plaintext.t line 130.
Wide character in field 8 but mysql_enable_utf8 not set at
/usr/share/perl5/vendor_perl/DBIx/SearchBuilder/Handle.pm line 586.
...
Version-Release number of selected component (if applicable):
rt-4.4.1-5.noarch
perl-DBD-MySQL-4.042-1.fc25.x86_64
How reproducible:
Always
Steps to Reproduce:
1. run rt's testsuite
Actual results:
These tests fail:
mail-charsets-outgoing-plaintext.t
mail-charsets-outgoing.t
mail-not-supported-charset.t
mail-precedence-outgoing.t
mail-rfc2231-attachment.t
mail-sendmail-plaintext.t
mail-sendmail.t
web-attachment_encoding.t
web-basic.t
web-html_template.t
web-query_builder.t
web-rest-non-ascii-subject.t
web-ticket-create-utf8.t
web-ticket_forward.t
web-ticket_txn_subject.t
Downgrading to perl-DBD-MySQL-4.041-1.fc25.x86_64.rpm immediately silences all
these testsuite errors.
Expected results:
No errors.
Additional info:
- I assume the cause to be the incompatibilities described under "WARNING" in
https://metacpan.org/pod/DBD::mysql#mysql_enable_utf8
- Reported upstream rt as
https://issues.bestpractical.com/Ticket/Display.html?id=32670
- I assume this issue to not only affect the testsuite, but it to affect rt's
runtime, too.
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 4 months
[Bug 1471436] New: Please link weblint(1) man page to
HTML::Lint(3pm)
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1471436
Bug ID: 1471436
Summary: Please link weblint(1) man page to HTML::Lint(3pm)
Product: Fedora
Version: 25
Component: perl-HTML-Lint
Severity: low
Assignee: rc040203(a)freenet.de
Reporter: ferdnyc(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: perl-devel(a)lists.fedoraproject.org,
rc040203(a)freenet.de
Description of problem:
There is currently no man page provided for the /usr/bin/weblint script, which
installs with perl-HTML-Lint. However, the HTML::Lint(3pm) man page does
contain some rudimentary documentation on weblint, and would be a "better than
nothing" result for `man weblint` than the current response, which is nothing.
Version-Release number of selected component (if applicable):
perl-HTML-Lint-2.26-1.fc25.noarch
How reproducible:
`man weblint`
Actual results:
"No manual entry for weblint"
Expected results:
Same as `man 3 HTML::Lint`
Additional info:
Man pages can be configured as references to other man pages in two ways.
1. A symlink can be created in /usr/share/man/$SECTION/ under a new name that
points to the existing documentation. However, since the link source would be
in a different section than the target, this would require a symlink through
../ and is not advisable.
2. The preferable method, in the case of cross-section references, is to
install a file /usr/share/man/man1/weblint.1.gz containing (before compression)
a single line of text:
.so man3/HTML::Lint.3pm
This will establish weblint(1) as an alias for the HTML::Lint(3pm) man page,
and it will be displayed when the user runs `man weblint`.
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 4 months
[Bug 1502214] New: abi-compliance-checker:
behavior changed within f26 release
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1502214
Bug ID: 1502214
Summary: abi-compliance-checker: behavior changed within f26
release
Product: Fedora
Version: 26
Component: abi-compliance-checker
Keywords: Regression
Assignee: hobbes1069(a)gmail.com
Reporter: nmavrogi(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: hobbes1069(a)gmail.com, orion(a)nwra.com,
perl-devel(a)lists.fedoraproject.org
Description of problem:
After updating my F26 CI systems, the gnutls CI fails with:
"ERROR: the version of the ABI dump is too old and unsupported anymore, please
regenerate it"
The CI works fine with the abi-compliance-checker included in the initial F26
builds (abi-compliance-checker-2.1-1.fc26.noarch).
The error is far from easy or trivial to address as the files after which the
ABI was checked do not exist.
Please follow the rules for stable releases in updating on a stable release:
https://fedoraproject.org/wiki/Updates_Policy#Stable_Releases
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 4 months
[Bug 1378895] New:
8-bpp TIFF images are broken in the resulting PDF document
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1378895
Bug ID: 1378895
Summary: 8-bpp TIFF images are broken in the resulting PDF
document
Product: Fedora
Version: 23
Component: perl-PDF-API2
Assignee: jplesnik(a)redhat.com
Reporter: ppisar(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: bjohnson(a)symetrix.com, jplesnik(a)redhat.com,
perl-devel(a)lists.fedoraproject.org
Blocks: 1369984
External Bug ID: CPAN 118047
Created attachment 1204154
--> https://bugzilla.redhat.com/attachment.cgi?id=1204154&action=edit
8-bpp TIFF image
This code creates an PDF with broken 8-bpp TIFF image:
#!/usr/bin/perl
use strict;
use warnings;
use PDF::API2;
my $pdf = PDF::API2->new(-file => 'out.pdf');
my $page = $pdf->page;
$page->mediabox(157, 196);
my $imgobj = $pdf->image_tiff('8.tiff');
my $gfx = $page->gfx;
$gfx->image($imgobj, 0, 0, 157, 196);
$pdf->save;
$pdf->end;
It works fine if the TIFF image has only 1 bit per pixel. I have
perl-PDF-API2-2.025-1.fc23.noarch, but it it's broken in all Fedoras.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1369984
[Bug 1369984] gscan2pdf v1.3.8 saves imported PDF pages as negative images
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 4 months
[Bug 1469031] New: Please update perl-Plack version
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1469031
Bug ID: 1469031
Summary: Please update perl-Plack version
Product: Fedora EPEL
Version: epel7
Component: perl-Plack
Assignee: rc040203(a)freenet.de
Reporter: clem.oudot(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: emmanuel(a)seyman.fr, extras-qa(a)fedoraproject.org,
jose.p.oliveira.oss(a)gmail.com, kwizart(a)gmail.com,
perl-devel(a)lists.fedoraproject.org, ppisar(a)redhat.com,
rc040203(a)freenet.de
Hi,
for LemonLDAP::NG I need a more recent version of perl-Plack.
We currently have perl-Plack-1.0030-3.el7.noarch, and I would need at least
1.0033.
Thanks a lot for your help.
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 4 months
[Bug 1335443] New: Net::SSLeay produces a warning on EOF
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1335443
Bug ID: 1335443
Summary: Net::SSLeay produces a warning on EOF
Product: Fedora
Version: 22
Component: perl-Net-SSLeay
Severity: low
Assignee: paul(a)city-fan.org
Reporter: lav(a)yars.free.net
QA Contact: extras-qa(a)fedoraproject.org
CC: jose.p.oliveira.oss(a)gmail.com, kasal(a)ucw.cz,
paul(a)city-fan.org, perl-devel(a)lists.fedoraproject.org
Created attachment 1156525
--> https://bugzilla.redhat.com/attachment.cgi?id=1156525&action=edit
proposed fix
Description of problem:
I repeatedly get this warning from Net::SSLeay:
Use of uninitialized value $got in string eq at blib/lib/Net/SSLeay.pm
(autosplit into blib/lib/auto/Net/SSLeay/ssl_read_all.al) line 549.
Version-Release number of selected component (if applicable):
perl-Net-SSLeay-1.68-1.fc22.x86_64
Expected results:
no warnings
Additional info:
a patch is attached.
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 5 months