perl-devel January 2014

perl-devel@lists.fedoraproject.org

42 participants
1440 discussions

[Bug 783468] New: missing dependancy on perl-Email-Simple-Creator
by Red Hat Bugzilla 06 Apr '17

06 Apr '17

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: missing dependancy on perl-Email-Simple-Creator https://bugzilla.redhat.com/show_bug.cgi?id=783468 Summary: missing dependancy on perl-Email-Simple-Creator Product: Fedora EPEL Version: el5 Platform: Unspecified OS/Version: Unspecified Status: NEW Severity: unspecified Priority: unspecified Component: perl-Email-MIME-Creator AssignedTo: tcallawa(a)redhat.com ReportedBy: carl.johnstone(a)onthebeach.co.uk QAContact: extras-qa(a)fedoraproject.org CC: tcallawa(a)redhat.com, fedora-perl-devel-list(a)redhat.com Classification: Fedora Story Points: --- Type: --- Regression: --- Mount Type: --- Documentation: --- Description of problem: The perl-Email-MIME-Creator package has a missing dependency on Email::Simple::Creator / perl-Email-Simple-Creator Version-Release number of selected component (if applicable): perl-Email-MIME-Creator.noarch 0:1.453-2.el5 -- 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.

2 1

[Bug 706721] New: Missing Requires: perl(Clone)
by Red Hat Bugzilla 06 Apr '17

06 Apr '17

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: Missing Requires: perl(Clone) https://bugzilla.redhat.com/show_bug.cgi?id=706721 Summary: Missing Requires: perl(Clone) Product: Fedora EPEL Version: el5 Platform: Unspecified OS/Version: Unspecified Status: NEW Severity: unspecified Priority: unspecified Component: perl-Hash-Merge AssignedTo: tcallawa(a)redhat.com ReportedBy: redhat-bugzilla(a)camperquake.de QAContact: extras-qa(a)fedoraproject.org CC: tcallawa(a)redhat.com, iarnell(a)gmail.com, fedora-perl-devel-list(a)redhat.com Classification: Fedora Story Points: --- Description of problem: perl-Hash-Merge requires perl(Clone), but the spec does not reflect this. Version-Release number of selected component (if applicable): perl-Hash-Merge-0.11-2.el5 How reproducible: Look at /usr/lib/perl5/vendor_perl/5.8.8/Hash/Merge.pm, line 231 Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: -- 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.

2 1

[Bug 703101] New: [PATCH] DateTime should be rebuilt on tzdata updates
by Red Hat Bugzilla 06 Apr '17

06 Apr '17

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: [PATCH] DateTime should be rebuilt on tzdata updates https://bugzilla.redhat.com/show_bug.cgi?id=703101 Summary: [PATCH] DateTime should be rebuilt on tzdata updates Product: Fedora EPEL Version: el5 Platform: Unspecified OS/Version: Unspecified Status: NEW Severity: unspecified Priority: unspecified Component: perl-DateTime AssignedTo: tremble(a)tremble.org.uk ReportedBy: lkundrak(a)v3.sk QAContact: extras-qa(a)fedoraproject.org CC: fedora-perl-devel-list(a)redhat.com, tremble(a)tremble.org.uk Classification: Fedora Story Points: --- Description of problem: tzdata package updates and new time zones are added from time to time (such as Asia/Kolkata). As DateTime contains files generated from it, it should be rebuilt on each such update. The patch attached adds an explicit dependency on specific version of tzdata, so that it would disallow updates in case of tzdata rebuild w/o DateTime rebuilt, so that it would no go unnoticed. Additional info: At the very least, even if the patch is rejected, please trigger a DateTime rebuild. Maybe coordinate with tzdata maintainer on future updates. -- 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.

2 4

[Bug 757089] New: cpanspec error: Dest dir longer than base dir is not supported
by Red Hat Bugzilla 04 Apr '17

04 Apr '17

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: cpanspec error: Dest dir longer than base dir is not supported https://bugzilla.redhat.com/show_bug.cgi?id=757089 Summary: cpanspec error: Dest dir longer than base dir is not supported Product: Fedora Version: 16 Platform: Unspecified OS/Version: Unspecified Status: NEW Severity: unspecified Priority: unspecified Component: cpanspec AssignedTo: steve(a)silug.org ReportedBy: kas(a)fi.muni.cz QAContact: extras-qa(a)fedoraproject.org CC: steve(a)silug.org, fedora-perl-devel-list(a)redhat.com Classification: Fedora Story Points: --- Type: --- Description of problem: I am trying to build some CPAN modules as RPMs (namely Env::C and IO::Socket::Multicast), but the build fails with the following error: [...] extracting debug info from /root/rpmbuild/BUILDROOT/perl-Env-C-0.08-1.fc16.x86_64/usr/lib64/perl5/vendor_perl/auto/Env/C/C.so Dest dir longer than base dir is not supported error: Bad exit status from /var/tmp/rpm-tmp.LI9AHv (%install) I am not sure why the length of both paths should matter at all, but the cause of the problem is that cpanspec sets up too long buildroot. Taking the generated spec file, shortening the buildroot path, and rebuilding the package using the modified spec file works for me Before: BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n) After: BuildRoot: %{_tmppath}/%{name} Version-Release number of selected component (if applicable): cpanspec-1.78-9.fc16.noarch How reproducible: 100 % Steps to Reproduce: 1. cpanspec --build Env::C Actual results: build fails with the above error message Expected results: perl-Env-C binary and source RPMs should be built -- 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.

2 10

[Bug 347901] New: Port perl-IO-Socket-SSL to use NSS library for cryptography
by Red Hat Bugzilla 05 Jan '17

05 Jan '17

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/show_bug.cgi?id=347901 Summary: Port perl-IO-Socket-SSL to use NSS library for cryptography Product: Fedora Version: devel Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: medium Component: perl-IO-Socket-SSL AssignedTo: wtogami(a)redhat.com ReportedBy: pvrabec(a)redhat.com QAContact: extras-qa(a)fedoraproject.org CC: fedora-perl-devel- list@redhat.com,jpo@di.uminho.pt,tmraz@redhat.com perl-IO-Socket-SSL should be ported to use NSS library for cryptography. See the tracking bug for details and links on how it could be done. -- 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, or are watching someone who is.

1 2

[Bug 874942] New: Net-DNS: system configuration is used instead of user's
by Red Hat Bugzilla 20 Dec '16

20 Dec '16

https://bugzilla.redhat.com/show_bug.cgi?id=874942 Bug ID: 874942 QA Contact: extras-qa(a)fedoraproject.org Severity: high External Bug URL: http://rt.cpan.org/Public/ Version: rawhide Priority: unspecified CC: mmaslano(a)redhat.com, perl-devel(a)lists.fedoraproject.org, psabata(a)redhat.com Assignee: mmaslano(a)redhat.com Summary: Net-DNS: system configuration is used instead of user's Regression: --- Story Points: --- Classification: Fedora OS: Unspecified Reporter: mmaslano(a)redhat.com Type: Bug Documentation: --- Hardware: Unspecified Mount Type: --- Status: NEW Component: perl-Net-DNS Product: Fedora External Bug ID: CPAN 67602 If I define my own configuration file, system files are used, which could be security issue. Example: My configuration file is defined as: my $res = Net::DNS::Resolver->new(config_file => '/my/dns.conf'); These files are read even if I defined my own file: /etc/resolv.conf $HOME/.resolv.conf ./.resolv.conf Last 2 files shouldn't be read by default since it's possible security issue - user can drop .resolv.conf pointing to malicious dns server. This issue was found during testing spamassassin with selinux. For details see: https://bugzilla.redhat.com/sh ow_bug.cgi?id=628866#c2 I'm reporting this error back into our bugzilla because of last comment in rt: I think the level of this PR should be elevated to 'security'. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 831716] New: Moving legacy code out of perl-JSON-RPC breaks Bugzilla
by Red Hat Bugzilla 13 Dec '16

13 Dec '16

https://bugzilla.redhat.com/show_bug.cgi?id=831716 Bug ID: 831716 QA Contact: extras-qa(a)fedoraproject.org Severity: high Version: 17 Priority: unspecified CC: emmanuel.seyman(a)club-internet.fr, perl-devel(a)lists.fedoraproject.org Assignee: emmanuel.seyman(a)club-internet.fr Summary: Moving legacy code out of perl-JSON-RPC breaks Bugzilla Regression: --- Story Points: --- Classification: Fedora OS: Linux Reporter: lpsolit(a)netscape.net Type: Bug Documentation: --- Hardware: All Mount Type: --- Status: NEW Component: perl-JSON-RPC Product: Fedora Bugzilla still uses legacy code from JSON::RPC and despite the perl-JSON-RPC package is installed, which makes checksetup.pl happy, the JSON-RPC feature of Bugzilla fails because it cannot find the legacy code. This also prevents Apache from starting when mod_perl is enabled: httpd[1938]: Can't locate JSON/RPC/Legacy/Server/CGI.pm in @INC So the legacy code is still required by Bugzilla, and checksetup.pl and Bugzilla re confused by this package split. -- You are receiving this mail because: You are on the CC list for the bug.

1 26

[Bug 1054061] New: Segfault in Perl_gv_fetchpvn_flags when trying to initialize back_perl openldap backend
by Red Hat Bugzilla 02 Dec '16

02 Dec '16

https://bugzilla.redhat.com/show_bug.cgi?id=1054061 Bug ID: 1054061 Summary: Segfault in Perl_gv_fetchpvn_flags when trying to initialize back_perl openldap backend Product: Red Hat Enterprise Linux 7 Version: 7.0 Component: perl Assignee: perl-maint-list(a)redhat.com Reporter: jsynacek(a)redhat.com QA Contact: qe-baseos-apps(a)redhat.com CC: cweyl(a)alumni.drew.edu, hyc(a)symas.com, iarnell(a)gmail.com, jplesnik(a)redhat.com, kasal(a)ucw.cz, lkundrak(a)v3.sk, mmaslano(a)redhat.com, perl-devel(a)lists.fedoraproject.org, ppisar(a)redhat.com, psabata(a)redhat.com, rc040203(a)freenet.de, tcallawa(a)redhat.com Depends On: 967719 Group: devel External Bug ID: OpenLDAP ITS 7573 +++ This bug was initially created as a clone of Bug #967719 +++ Description of problem: When trying to initialize back_perl, a segfault occurs deep in perl itself. Version-Release number of selected component (if applicable): perl-5.16.3-264.fc19.x86_64 openldap-2.4.35-4.fc19.x86_64 How reproducible: Almost always. Steps to Reproduce: 1. Install fresh F19 2. If you try the reproducer here, all goes well 3. yum install perl-A* (I have no idea why I needed to do this to get it to segfault) 4. Try reproducer 5. Observe the segfault 6. From now on, reproducer works *without* producing any segfaults. I had to reboot the machine to be able to reproduce the issue again. Note on how to use the reproducer: 1. Unpack 2. Run go.sh (warning: it will wipe your /var/lib/ldap/* and your /etc/openldap/*, so don't run if you use openldap in production) This will run slapd in debug mode, so you will need another console to run the rest. 3. Run try.sh 4. If you want to repeat, go to 2. You can modify go.sh to run slapd through a debugger. However, you will probably need to set LD_PRELOAD=/usr/lib64/perl5/CORE/libperl.so to be able to run try.sh. Actual results: Perl segfaults. Expected results: The back_perl gets initialized without any problems. Additional info: This also happens on my production F18, but it happens always. It looks like it might have something to do with Bug 960048. --- Additional comment from Jan Synacek on 2013-05-28 08:53:11 CEST --- Note that in the frame #3, the my_perl variable changes from a (probably valid) pointer to 0x0. --- Additional comment from Petr Pisar on 2013-07-03 14:38:09 CEST --- What's expected output on the client site? I have patched perl so that it links all XS modules to libperl.so explicitly in my private F20 machine, and I do not get any segfaults. Instead I just get an error message from the second command: $ sh try.sh SASL/EXTERNAL authentication started SASL username: gidNumber=500+uidNumber=500,cn=peercred,cn=external,cn=auth SASL SSF: 0 adding new entry "cn=module,cn=config" ldap_add: Insufficient access (50) SASL/EXTERNAL authentication started SASL username: gidNumber=500+uidNumber=500,cn=peercred,cn=external,cn=auth SASL SSF: 0 adding new entry "olcDatabase=perl,cn=config" ldap_add: Invalid syntax (21) additional info: objectClass: value #1 invalid per syntax I guess this is how to should work. If this is the real fix, than this issue will be fixed in F20. --- Additional comment from Jan Synacek on 2013-07-03 14:57:38 CEST --- All LDAP operations should succeed without any errors. You don't have sufficient access rights to modify the LDAP database. Running the script as root should do it. You should see something like this: # ./try.sh SASL/EXTERNAL authentication started SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth SASL SSF: 0 adding new entry "cn=module,cn=config" SASL/EXTERNAL authentication started SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth SASL SSF: 0 adding new entry "olcDatabase=perl,cn=config" ldap_result: Can't contact LDAP server (-1) The last line indicates the termination (you can see that slapd segfaulted in the console where you ran go.sh). Expected output would look like the one above minus the 'ldap_result: ...' line. Plus there may be one additional 'adding new entry' line. --- Additional comment from Petr Pisar on 2013-07-03 16:07:01 CEST --- I run it as a non-root. I get much better results as a root: # ./try.sh SASL/EXTERNAL authentication started SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth SASL SSF: 0 adding new entry "cn=module,cn=config" SASL/EXTERNAL authentication started SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth SASL SSF: 0 adding new entry "olcDatabase=perl,cn=config" adding new entry "dc=perl-example,dc=com" However the server sometimes segfaults as you reported. --- Additional comment from Jan Synacek on 2013-07-04 07:54:23 CEST --- (In reply to Petr Pisar from comment #4) > I run it as a non-root. I get much better results as a root: Yes, that's how the output is supposed to look. > However the server sometimes segfaults as you reported. Ok, it's strange that it segfaults only sometimes. Does this mean that you can reproduce it even with all the perl modules linked to libperl.so explicitly? --- Additional comment from Petr Pisar on 2013-07-04 09:07:56 CEST --- I recompiled only modules in perl binary package and openldap for the test. Not yet all modules that exist. I also reverted the RTLD_GLOBAL patch and checked slapd does not crashes on linkage error. So the test does not use any not-yet-rebuild modules. I conclude this issue is independent on the linking bug #960048. But we will see more after rebuilding everything. --- Additional comment from Fedora Admin XMLRPC Client on 2013-08-12 13:50:07 CEST --- This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. --- Additional comment from Howard Chu on 2013-10-13 02:20:16 CEST --- Please also followup to OpenLDAP ITS#7573 with any conclusions you reach, thanks. --- Additional comment from Jan Synacek on 2013-10-16 08:13:38 CEST --- This problem still occurs in F20. Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=967719 [Bug 967719] Segfault in Perl_gv_fetchpvn_flags when trying to initialize back_perl openldap backend -- 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=RTtoq7IB5n&a=cc_unsubscribe

1 9

[Bug 994894] New: perl-Soot does not support ARM
by Red Hat Bugzilla 24 Nov '16

24 Nov '16

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

1 9

[Bug 808197] New: FTBFS: big endian bug in self checks
by Red Hat Bugzilla 09 Nov '16

09 Nov '16

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.

1 6

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

perl-devel January 2014