https://bugzilla.redhat.com/show_bug.cgi?id=994894
Bug ID: 994894
Summary: perl-Soot does not support ARM
Product: Fedora
Version: rawhide
Component: perl-SOOT
Assignee: ppisar(a)redhat.com
Reporter: ppisar(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: perl-devel(a)lists.fedoraproject.org, ppisar(a)redhat.com
Depends On: 991031
Blocks: 485251 (F-ExcludeArch-ARM)
perl-Soot requires root which does not support ARM (bug #991031). perl-Soot
will be disabled on ARM.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=CKPzevCLAa&a=cc_unsubscribe
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: FTBFS: big endian bug in self checks
https://bugzilla.redhat.com/show_bug.cgi?id=808197
Summary: FTBFS: big endian bug in self checks
Product: Fedora
Version: 17
Platform: powerpc
OS/Version: Linux
Status: NEW
Severity: high
Priority: medium
Component: perl-Socket-Netlink
AssignedTo: bochecha(a)fedoraproject.org
ReportedBy: karsten(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: fedora-perl-devel-list(a)redhat.com,
bochecha(a)fedoraproject.org
Classification: Fedora
Story Points: ---
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Description of problem:
perl-Socket-Netlink fails to build on PPC as two of the self checks fail, one
of them looks like a big endian bug as the result has a swapped bit:
t/12netlink-message-header.t ..... ok
# Failed test '$message->attrs after unpack'
# at t/13netlink-message-attrs.t line 98.
# Structures begin differing at:
# $got->{str} = ''
# $expected->{str} = 'FGH'
# Looks like you failed 1 test of 14.
t/13netlink-message-attrs.t ......
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/14 subtests
t/14netlink-message-error.t ...... ok
# Failed test '$message->pack'
# at t/20io-socket-netlink-generic.t line 55.
# at bytes 0-0xf (0-15)
# got: | 00 00 00 14 00 1e 00 00 00 00 00 00 00 00 00 00 |................|
# exp: | 00 00 00 14 00 00 00 1e 00 00 00 00 00 00 00 00 |................|
# Looks like you failed 1 test of 13.
Version-Release number of selected component (if applicable):
perl-Socket-Netlink-0.03-4.fc17
How reproducible:
always
Steps to Reproduce:
1. ppc-koji build --scratch f17 perl-Socket-Netlink-0.03-4.fc17.src.rpm
2.
3.
Actual results:
http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=469988
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: [PATCH] specfile accords to new packaging guidelines
https://bugzilla.redhat.com/show_bug.cgi?id=671445
Summary: [PATCH] specfile accords to new packaging guidelines
Product: Fedora
Version: rawhide
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: unspecified
Priority: unspecified
Component: cpanspec
AssignedTo: steve(a)silug.org
ReportedBy: mmaslano(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: steve(a)silug.org, fedora-perl-devel-list(a)redhat.com
Classification: Fedora
Created attachment 474630
--> https://bugzilla.redhat.com/attachment.cgi?id=474630
add epel option
This patch should remove things, which are not needed according to new
packaging guidelines and latest rpm eg. defining buildroot. The old
behaviour is available under --epel option.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: Please build pcsc-perl for EPEL6
https://bugzilla.redhat.com/show_bug.cgi?id=807793
Summary: Please build pcsc-perl for EPEL6
Product: Fedora
Version: rawhide
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: unspecified
Priority: unspecified
Component: pcsc-perl
AssignedTo: tmraz(a)redhat.com
ReportedBy: mjeanson(a)rlnx.com
QAContact: extras-qa(a)fedoraproject.org
CC: tmraz(a)redhat.com, fedora-perl-devel-list(a)redhat.com
Classification: Fedora
Story Points: ---
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Hi,
I was hoping that you could build pcsc-perl for EPEL6.
I just tried a scratch build of the fc17 version and it builds without
modification within EPEL6.
http://koji.fedoraproject.org/koji/taskinfo?taskID=3940535
Thanks,
Michael
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1078438
Bug ID: 1078438
Summary: Templated types are causing "Could not find a typemap
for C type"
Product: Red Hat Enterprise Linux 7
Version: 7.0
Component: perl-ExtUtils-ParseXS
Assignee: perl-maint-list(a)redhat.com
Reporter: mhroncok(a)redhat.com
QA Contact: qe-baseos-apps(a)redhat.com
CC: perl-devel(a)lists.fedoraproject.org, ppisar(a)redhat.com
Depends On: 1032181
Blocks: 1032056
+++ This bug was initially created as a clone of Bug #1032181 +++
Description of problem:
When using perl-ExtUtils-ParseXS to build XS stuff (I don't know the
terminology here, sorry), errors like this happens:
https://rt.cpan.org/Public/Bug/Display.html?id=86367
Version-Release number of selected component (if applicable):
perl-ExtUtils-ParseXS-3.18-291.fc20.noarch
How reproducible:
Happend when building slic3r-xs
Steps to Reproduce:
1. Get slic3r tarball from
https://github.com/alexrj/Slic3r/archive/1.0.0RC1.tar.gz
2. unpack && cd Slic3r-1.0.0RC1/xs/ # be usre to be in xs folder
3. perl Build.PL && ./Build
Actual results:
<snip>
Could not find a typemap for C type 'std::vector< double >'.
The following C types are mapped by the current typemap:
'AV *', <snip>, 'wchar_t *'
in /usr/bin/perl -MExtUtils::XSpp::Cmd -e xspp -- -t
"/home/churchyard/Stažené/Slic3r-1.0.0RC1/xs/xsp/typemap.xspt"
"/home/churchyard/Stažené/Slic3r-1.0.0RC1/xs/xsp/TriangleMesh.xsp", line 138
Expected results:
No errors, just warnings
Additional info:
This is fixed in upstream release 3.22 and also in development release 3.18_03.
Fix is in Bug #1032181.
See the error in this build.log:
http://copr-be.cloud.fedoraproject.org/results/churchyard/epel7-3dprint/epe…
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1032056
[Bug 1032056] Slic3r 1.0.0RC1 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1032181
[Bug 1032181] Templated types are causing "Could not find a typemap for C
type"
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=ujbL1yHik6&a=cc_unsubscribe
https://bugzilla.redhat.com/show_bug.cgi?id=1101265
Bug ID: 1101265
Summary: perl-libwww-perl: incorrect handling of SSL
certificate verification [fedora-all]
Product: Fedora
Version: 20
Component: perl-LWP-Protocol-https
Keywords: FutureFeature
Severity: high
Priority: high
Assignee: ppisar(a)redhat.com
Reporter: ppisar(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: jpazdziora(a)redhat.com, jplesnik(a)redhat.com,
mmaslano(a)redhat.com, mzazrivec(a)redhat.com,
perl-devel(a)lists.fedoraproject.org, ppisar(a)redhat.com,
psabata(a)redhat.com
+++ This bug was initially created as a clone of Bug #1094442 +++
[...]
--- Additional comment from Jan Pazdziora on 2014-05-26 10:55:43 GMT ---
(In reply to Petr Pisar from comment #9)
> Thank you for the report. However there are two mistakes:
>
> (1) The IO::Socket::SSL::new option is "SSL_verifycn_scheme", not
> "SSL_verifycn_schema". Thus you could not find it in the documentation.
Ahh, sorry about that
.
> (2) The 6.04-3 behavior was flawed. As you can read in the upstream bug
> report, the "SSL_verify_mode" option is about checking hostname. It's not
> intended to control certificate validation. The same applies to
> "PERL_LWP_SSL_VERIFY_HOSTNAME" environment variable. 6.04-4 has restored the
> behavior which presented before 6.04.
So what is the way for making HTTP requests to websites with self-signed
certificates from perl, if the user does not care about the CA chain
validation?
In other way, what is the way for making LWP behave the same way it used to
behave with pre-6 version?
--- Additional comment from Petr Pisar on 2014-05-26 11:20:51 GMT ---
There is no LWP environment variable or command line option to control that
currently.
It's possible to pass ssl_opts => {SSL_verify_mode =>
IO::Socket::SSL::SSL_VERIFY_NONE} to LWP::UserAgent::new if you write your own
LWP application.
This is also discussed in the upstream report.
The reason why the PERL_LWP_SSL_VERIFY_HOSTNAME seemed to work before is the
IO::Socket::SSL < 1.950 defaulted to SSL_VERIFY_NONE. This has not been true
since Fedora 20. Unfortunately Fedora 20 delivered the flawed
LWP::Protocol::https, so it was not visible.
I agree with you that there should be way how to disable the certificate
validation externally.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=vNjL2yMVw5&a=cc_unsubscribe
https://bugzilla.redhat.com/show_bug.cgi?id=1027305
Bug ID: 1027305
Summary: pTk/*.t files in debuginfo package differ in mode on
each architecture
Product: Fedora
Version: rawhide
Component: perl-Tk
Assignee: andreas.bierfert(a)lowlatency.de
Reporter: ppisar(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: andreas.bierfert(a)lowlatency.de,
perl-devel(a)lists.fedoraproject.org
Created attachment 820390
--> https://bugzilla.redhat.com/attachment.cgi?id=820390&action=edit
Fix
perl-Tk-debuginfo files not consistent in file mode across all architectures.
This caused by build script regenerating some files based on external
dependencies and features supported on each architecture. This even causes file
mode changes across time.
Attached patch fixes this issue. Please consider applying this patch.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=DZLMtyzYzx&a=cc_unsubscribe
https://bugzilla.redhat.com/show_bug.cgi?id=1003471
Bug ID: 1003471
Summary: Manual pages generated from POD have almost all
Unicode characters mangled to X
Product: Fedora
Version: rawhide
Component: perl-podlators
Assignee: ppisar(a)redhat.com
Reporter: ppisar(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: perl-devel(a)lists.fedoraproject.org, ppisar(a)redhat.com
$ cat test
=encoding utf8
=head1 Kroužkovci
Žížala
=cut
$ pod2man test |tail
.\"
.IX Title "TEST 1"
.TH TEST 1 "2013-09-02" "perl v5.18.1" "User Contributed Perl Documentation"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.nh
.SH "KrouXkovci"
.IX Header "KrouXkovci"
Xi\*'Xala
This is caused by upstream decision to have pod2man output compatible with all
ROFFs. That means to pass ASCII charachtes, escape ISO-8859-1 characters, and
to replace others with plain `X'
(<https://rt.cpan.org/Public/Bug/Display.html?id=68741>).
There is pod2man option --utf8 which disables any escaping and outputs UTF-8,
but this is not default behaviour. This makes all manual pages from built
packages to be mangled. See Debian bug report
<http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=480997>.
Question is what to do. Should we be faster than upstream and make UTF-8 output
default? Should defaults you locale encoding? (Fedora packages are built in C
locale.)
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=1dZWcp091d&a=cc_unsubscribe
https://bugzilla.redhat.com/show_bug.cgi?id=981243
Bug ID: 981243
Summary: SDLx::App->new() does not work on frame buffer console
Product: Fedora
Version: 18
Component: perl-SDL
Severity: unspecified
Priority: unspecified
Assignee: hdegoede(a)redhat.com
Reporter: ppisar(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: hdegoede(a)redhat.com,
perl-devel(a)lists.fedoraproject.org
Created attachment 768694
--> https://bugzilla.redhat.com/attachment.cgi?id=768694&action=edit
Reproducer
I'm not able to initialize SDL video on frame buffer console using high-level
SDLx::App->new(). But it works with low-level SDL::Video::set_video_mode().
Output from the reproducer:
# DISPLAY= perl test -width 1280 -height 1024 -depth 32
Testing plain SDL:
Plain SDL::Video::set_video_mode() is Ok.
Width is 1280
Testing plain SDL::App:
Couldn't set console screen info at /usr/lib64/perl5/vendor_perl/SDLx/App.pm
line 123.
SDLx::App::new('SDLx::App', '-width', 1280, '-height', 1024, '-depth',
32) called at test line 32
root@dhcp-0-146:/tmp # rpm -q perl-SDL
perl-SDL-2.540-2.fc18.x86_64
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=GviunhawfM&a=cc_unsubscribe
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=204093
Summary: perl -i resets file ACLs and EAs
Product: Fedora Core
Version: fc5
Platform: All
OS/Version: Linux
Status: NEW
Severity: normal
Priority: normal
Component: perl
AssignedTo: rnorwood(a)redhat.com
ReportedBy: josh(a)jbc.edu
QAContact: dkl(a)redhat.com
CC: fedora-perl-devel-list(a)redhat.com
Description of problem:
When perl's -i option is used to do an in-place edit of a file, it resets the
ACLs and extended attributes on that file.
Since perl -i can be a very helpful tool for scripting and system
administration, it would be nice if it preserved ACLs and EAs.
Version-Release number of selected component (if applicable):
perl-5.8.8-5
How reproducible:
always
Steps to Reproduce:
1. touch testfile
2. setfacl -m u:testuser:r testfile
3. setfattr -n user.test testfile
4. perl -pi -e 's/Something/SomethingElse/' testfile
5. getfacl testfile; getfattr testfile
Actual results:
Nothing.
Expected results:
ACLs and EAs set in steps 2 and 3 above.
Additional info:
--
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.