[Bug 1669119] New: perl-TeX-Encode-2.004-4.fc30 FTBFS:
t/Encode-LaTeX.t test fails: Unknown check argument: expected one of undef,
FB_DEFAULT, FB_CROAK, FB_QUIET or FB_WARN
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1669119
Bug ID: 1669119
Summary: perl-TeX-Encode-2.004-4.fc30 FTBFS: t/Encode-LaTeX.t
test fails: Unknown check argument: expected one of
undef, FB_DEFAULT, FB_CROAK, FB_QUIET or FB_WARN
Product: Fedora
Version: rawhide
Status: NEW
Component: perl-TeX-Encode
Assignee: tcallawa(a)redhat.com
Reporter: ppisar(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: perl-devel(a)lists.fedoraproject.org,
tcallawa(a)redhat.com
Target Milestone: ---
External Bug ID: Github athreef/TeX-Encode/issues/4
Classification: Fedora
perl-TeX-Encode-2.004-4.fc30 fails to build in F30 because a test fails:
t/02check.t ............ ok
BUILDSTDERR: Unknown check argument: expected one of undef, FB_DEFAULT,
FB_CROAK, FB_QUIET or FB_WARN at
/builddir/build/BUILD/TeX-Encode-2.004/blib/lib/TeX/Encode.pm line 52.
BUILDSTDERR: TeX::Encode::encode(TeX::Encode=HASH(0x1002012e070), "eacute =
'\x{e9}'", "") called at t/Encode-LaTeX.t line 19
BUILDSTDERR: # Looks like your test exited with 255 just after 1.
t/Encode-LaTeX.t .......
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 36/37 subtests
This is triggered by upgrading perl-Encode from 4:2.98 to 4:2.99.
--
You are receiving this mail because:
You are on the CC list for the bug.
5 years, 1 month
Retiring perl-perlmenu
by Emmanuel Seyman
[ perl-devel is in cc: ]
Hello, all.
I maintain perl-perlmenu in Fedora and I will be retiring it at the end
of the week unless someone offers to maintain it instead. For the record,
I would advise against this since upstream no longer exists and nothing
depends on the particular package.
Emmanuel
5 years, 1 month
[Bug 1670047] New: xtables.lock is not removed
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1670047
Bug ID: 1670047
Summary: xtables.lock is not removed
Product: Fedora
Version: 29
Hardware: x86_64
OS: Linux
Status: NEW
Component: perl-IPTables-libiptc
Severity: medium
Assignee: ppisar(a)redhat.com
Reporter: balwierz(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: perl-devel(a)lists.fedoraproject.org, ppisar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
IPTables-libiptc perl module does not deal with xtables lock file
(/run/xtables.lock) properly. Upon a call of IPTables::libiptc::init() a lock
file is created. But this lock file is not removed after commit(). It is
actually being recreated after each iptables_do_command() call.
As a result, any script using this module will get stuck on the second
invocation of iptables_do_command, as the lock file will be already created at
this time. It will wait forever for a release of this lock file which would
never happen.
Version-Release number of selected component (if applicable):
0.52-27.fc29
How reproducible:
Always
Steps to Reproduce:
1.a) Run the simple perl code:
use IPTables::libiptc;
my $filter = IPTables::libiptc::init('filter');
$filter->commit(); #an empty commit
2.a) ls /run/xtables.lock
1.b) If you add iptables_do_command() the script will never finish:
$| = 1;
use IPTables::libiptc;
my $filter = IPTables::libiptc::init('filter');
print "debug: after init\n";
$filter->iptables_do_command(['--flush', "OUTPUT"]);
print "debug: after the first flush\n";
$filter->iptables_do_command(['--flush', "OUTPUT"]); # a wait occurs here
print "debug: after the second flush\n";
$filter->commit();
Actual results:
a) Lock file persists after the script has finished.
b) Lock file prevents script from being finished. The messages printed:
debug: after init
debug: after the first flush
Another app is currently holding the xtables lock; still -9s 0us time ahead
to have a chance to grab the lock...
Another app is currently holding the xtables lock; still -19s 0us time ahead
to have a chance to grab the lock...
[...]
Expected results:
No self-locking behaviour.
xtables.lock removed after all objects called ->commit() or the script has
finished.
Additional info:
- From my inspection perl-IPTables-libiptc has the most recent patch against
iptables 1.6.1, which is older than 1.8.0 shipped with FC29.
- There was no such problem in FC26 which ships older iptables 1.6.x
- The same version is in rawhide, but I have not tested it
--
You are receiving this mail because:
You are on the CC list for the bug.
5 years, 1 month
[Bug 1666094] New: Provide perl-Fuse for EPEL7
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1666094
Bug ID: 1666094
Summary: Provide perl-Fuse for EPEL7
Product: Fedora
Version: rawhide
Hardware: All
OS: Linux
Status: NEW
Component: perl-Fuse
Severity: medium
Assignee: jplesnik(a)redhat.com
Reporter: orion(a)nwra.com
QA Contact: extras-qa(a)fedoraproject.org
CC: jplesnik(a)redhat.com,
perl-devel(a)lists.fedoraproject.org
Target Milestone: ---
Classification: Fedora
Description of problem:
It would be nice to have perl-Fuse for EPEL7. I was able to build it fine
after removing the version requirement for MakeMaker, and removing
"Recommends". Perhaps the Recommends on perl(threads) and
perl(threads::shared) should just be a Requires in EPEL?
I would be willing to maintain it there if you do not want to.
--
You are receiving this mail because:
You are on the CC list for the bug.
5 years, 1 month
[Bug 1668818] New: perl-File-BOM-0.15-9.fc30 FTBFS: t/01..bom.t with
Encode 2.99
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1668818
Bug ID: 1668818
Summary: perl-File-BOM-0.15-9.fc30 FTBFS: t/01..bom.t with
Encode 2.99
Product: Fedora
Version: rawhide
URL: https://apps.fedoraproject.org/koschei/build/5955535
Status: NEW
Component: perl-File-BOM
Assignee: jplesnik(a)redhat.com
Reporter: ppisar(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: jplesnik(a)redhat.com,
perl-devel(a)lists.fedoraproject.org, steve(a)silug.org
Target Milestone: ---
External Bug ID: CPAN 128334
Classification: Fedora
perl-File-BOM-0.15-9.fc30 fails to build in F30 because a test fails like this:
t/00..setup.t ....... ok
BUILDSTDERR: UTF-32BE:Partial character at
/builddir/build/BUILD/File-BOM-0.15/blib/lib/File/BOM.pm line 364, <FH> line 1.
BUILDSTDERR: # Looks like your test exited with 25 just after 8.
t/01..bom.t .........
Dubious, test returned 25 (wstat 6400, 0x1900)
Failed 107/115 subtests
t/02..perlio-via.t .. ok
t/03..exceptions.t .. ok
t/04..pod.t ......... ok
t/99..shutdown.t .... ok
Test Summary Report
-------------------
t/01..bom.t (Wstat: 6400 Tests: 8 Failed: 0)
Non-zero exit status: 25
Parse errors: Bad plan. You planned 115 tests but ran 8.
This is triggered by upgrading perl-Encode from 4:2.98 to 4:2.99 and caused by
a deficiency in the t/01..bom.t test.
--
You are receiving this mail because:
You are on the CC list for the bug.
5 years, 1 month