perl-devel September 2010

perl-devel@lists.fedoraproject.org

28 participants
622 discussions

[Bug 603502] New: [abrt] crash in perl-Padre-0.50-4.fc13: Process /usr/bin/perl was killed by signal 11 (SIGSEGV)
by Red Hat Bugzilla 27 Jun '11

27 Jun '11

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: [abrt] crash in perl-Padre-0.50-4.fc13: Process /usr/bin/perl was killed by signal 11 (SIGSEGV) https://bugzilla.redhat.com/show_bug.cgi?id=603502 Summary: [abrt] crash in perl-Padre-0.50-4.fc13: Process /usr/bin/perl was killed by signal 11 (SIGSEGV) Product: Fedora Version: 13 Platform: x86_64 OS/Version: Linux Status: NEW Status Whiteboard: abrt_hash:1c0f880ad9686d02efbd3096ee944822c284105a Severity: medium Priority: low Component: perl-Padre AssignedTo: mmaslano(a)redhat.com ReportedBy: it_rom(a)gmx.de QAContact: extras-qa(a)fedoraproject.org CC: fedora-perl-devel-list(a)redhat.com, mmaslano(a)redhat.com, ppisar(a)redhat.com, psabata(a)redhat.com Classification: Fedora abrt 1.1.1 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: /usr/bin/perl /usr/bin/padre component: perl-Padre executable: /usr/bin/perl global_uuid: 1c0f880ad9686d02efbd3096ee944822c284105a kernel: 2.6.33.5-112.fc13.x86_64 package: perl-Padre-0.50-4.fc13 rating: 3 reason: Process /usr/bin/perl was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard) How to reproduce ----- 1.closed padre through the gnome-terminal 2. 3. -- 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 4

[Bug 598989] New: [abrt] crash in perl-Padre-0.50-4.fc13: Process /usr/bin/perl was killed by signal 11 (SIGSEGV)
by Red Hat Bugzilla 27 Jun '11

27 Jun '11

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: [abrt] crash in perl-Padre-0.50-4.fc13: Process /usr/bin/perl was killed by signal 11 (SIGSEGV) https://bugzilla.redhat.com/show_bug.cgi?id=598989 Summary: [abrt] crash in perl-Padre-0.50-4.fc13: Process /usr/bin/perl was killed by signal 11 (SIGSEGV) Product: Fedora Version: 13 Platform: x86_64 OS/Version: Linux Status: NEW Status Whiteboard: abrt_hash:70e28391c1a250dd6698df00e84aff62011f8668 Severity: medium Priority: low Component: perl-Padre AssignedTo: mmaslano(a)redhat.com ReportedBy: rob+redhat(a)pangalactic.org QAContact: extras-qa(a)fedoraproject.org CC: fedora-perl-devel-list(a)redhat.com, mmaslano(a)redhat.com, ppisar(a)redhat.com Classification: Fedora abrt 1.1.0 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: /usr/bin/perl /usr/bin/padre comment: See "How to reproduce" for instructions. I verified this twice. Problem does not occur when run locally. component: perl-Padre crash_function: _gdk_x11_screen_process_owner_change executable: /usr/bin/perl global_uuid: 70e28391c1a250dd6698df00e84aff62011f8668 kernel: 2.6.33.4-95.fc13.x86_64 package: perl-Padre-0.50-4.fc13 rating: 4 reason: Process /usr/bin/perl was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard) How to reproduce ----- 1. Start Hummingbird Exceed 12.0.0.124 on a Windows XP system 2. SSH into a Fedora 13 system with X11 tunnelling enabled using PuTTY 3. Start padre, loading a perl5 source file (e.g. "padre dbi-test.pl") 4. Select a module name such as "DBI" and press F2 -- 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 8

[Bug 574195] New: AMAVISD_DB_HOME in amavisd-agent has wrong default
by Red Hat Bugzilla 27 Jun '11

27 Jun '11

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: AMAVISD_DB_HOME in amavisd-agent has wrong default https://bugzilla.redhat.com/show_bug.cgi?id=574195 Summary: AMAVISD_DB_HOME in amavisd-agent has wrong default Product: Fedora Version: 12 Platform: All OS/Version: Linux Status: NEW Severity: low Priority: low Component: amavisd-new AssignedTo: steve(a)silug.org ReportedBy: bugzilla_redhat(a)penguinpee.nl QAContact: extras-qa(a)fedoraproject.org CC: steve(a)silug.org, fedora-perl-devel-list(a)redhat.com Classification: Fedora Created an attachment (id=400564) --> (https://bugzilla.redhat.com/attachment.cgi?id=400564) Fix default location of amavisd database Description of problem: AMAVISD_DB_HOME in amavisd-agent defaults to '/var/amavis/db' whereas the package installs the database in '/var/spool/amavisd/db'. Thus, running amavisd-agent will not produce the desired output. Version-Release number of selected component (if applicable): amavisd-new-2.6.4-1.fc12.noarch How reproducible: Always. Steps to Reproduce: 1. run amavisd-agent 2. 3. Actual results: No snmp database /var/amavis/db/snmp.db; waiting... Expected results: Output of amavisd statistics Additional info: The attached patch will fix the problem. Setting AMAVISD_DB_HOME to the right location will circumvent this problem. -- 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 4

[Bug 616626] New: python-pip pkg conflict with perl-pip
by Red Hat Bugzilla 24 Jun '11

24 Jun '11

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: python-pip pkg conflict with perl-pip https://bugzilla.redhat.com/show_bug.cgi?id=616626 Summary: python-pip pkg conflict with perl-pip Product: Fedora Version: rawhide Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: low Component: perl-pip AssignedTo: mmaslano(a)redhat.com ReportedBy: astokes(a)redhat.com QAContact: extras-qa(a)fedoraproject.org CC: fedora-perl-devel-list(a)redhat.com, mmaslano(a)redhat.com, phalliday(a)excelsiorsystems.net Depends on: 616399 Classification: Fedora Target Release: --- Clone Of: 616399 +++ This bug was initially created as a clone of Bug #616399 +++ Description of problem: Attempting to do a wildcard install of both python and perl packages results a file conflict for both python-pip and perl-pip Version-Release number of selected component (if applicable): python-pip 0.6.3-1 & perl-pip 1.16-1 How reproducible: 100% Steps to Reproduce: 1. yum install python* perl* 2. 3. Actual results: Running Transaction Test Transaction Check Error: file /usr/bin/pip conflicts between attempted installs of python-pip-0.6.3-1.fc13.noarch and perl-pip-1.16-1.fc13.noarch Expected results: No conflicts Additional info: --- Additional comment from phalliday(a)excelsiorsystems.net on 2010-07-20 14:26:35 EDT --- Well, I think the Debian approach (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551926) should be done here. Both packages should have to rename their /usr/bin/pip. Something like /usr/bin/pip-perl and /usr/bin/pip-python. That way completion will work at least. -- 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 5

[Bug 613872] New: Request for support in EPEL
by Red Hat Bugzilla 21 Jun '11

21 Jun '11

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: Request for support in EPEL https://bugzilla.redhat.com/show_bug.cgi?id=613872 Summary: Request for support in EPEL Product: Fedora Version: 13 Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: low Component: perl-Chart AssignedTo: steve(a)silug.org ReportedBy: fulko.hew(a)gmail.com QAContact: extras-qa(a)fedoraproject.org CC: steve(a)silug.org, fedora-perl-devel-list(a)redhat.com Classification: Fedora I would like to see one of your Fedora packages 'perl-Chart' in Extra Packages for Enterprise Linux (EPEL) repository. Would your be interested/willing to maintain this package in EPEL? Thanks Fulko -- 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 9

[Bug 459954] New: Default clamd conf file is broken
by Red Hat Bugzilla 09 Jun '11

09 Jun '11

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: Default clamd conf file is broken https://bugzilla.redhat.com/show_bug.cgi?id=459954 Summary: Default clamd conf file is broken Product: Fedora EPEL Version: el5 Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: medium Component: amavisd-new AssignedTo: steve(a)silug.org ReportedBy: jlquinn(a)optonline.net QAContact: extras-qa(a)fedoraproject.org CC: fedora-perl-devel-list(a)redhat.com Estimated Hours: 0.0 Classification: Fedora Description of problem: /etc/clam.d/amavisd.conf has syntax errors that prevent Version-Release number of selected component (if applicable): amavisd-new-2.4.5-1.el5 How reproducible: [root@mail1 ~]# service clamd.amavisd start Starting clamd.amavisd: ERROR: Parse error at line 2: Option LogSyslog requires boolean argument. ERROR: Can't open/parse the config file /etc/clamd.d/amavisd.conf [FAILED] After fixing this option to be: LogSyslog yes then [root@mail1 amavisd-new-2.4.5]# service clamd.amavisd start Starting clamd.amavisd: ERROR: Parse error at line 14: Option FixStaleSocket requires boolean argument. ERROR: Can't open/parse the config file /etc/clamd.d/amavisd.conf [FAILED] Fixing this to be: FixStaleSocket yes allows clamd to start correctly. 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.

1 2

[Bug 571192] New: $ENV{"HTTP_TRANSFER_ENCODING"} may be undefined in SOAP::Transport::HTTP
by Red Hat Bugzilla 16 May '11

16 May '11

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: $ENV{"HTTP_TRANSFER_ENCODING"} may be undefined in SOAP::Transport::HTTP https://bugzilla.redhat.com/show_bug.cgi?id=571192 Summary: $ENV{"HTTP_TRANSFER_ENCODING"} may be undefined in SOAP::Transport::HTTP Product: Fedora Version: 12 Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: low Component: perl-SOAP-Lite AssignedTo: mmcgrath(a)redhat.com ReportedBy: uckelman(a)nomic.net QAContact: extras-qa(a)fedoraproject.org CC: fedora-perl-devel-list(a)redhat.com, mmcgrath(a)redhat.com Classification: Fedora Description of problem: I get the following error message when calling Bugzilla's xmlrpc.cgi, which uses SOAP::Transport::HTTP: [Sun Mar 07 07:17:07 2010] [error] [client 146.50.208.39] [Sun Mar 7 07:17:07 2010] xmlrpc.cgi: Use of uninitialized value $ENV{"HTTP_TRANSFER_ENCODING"} in pattern match (m//) at /usr/lib/perl5/vendor_perl/5.10.0/SOAP/Transport/HTTP.pm line 530. The offending line looks like this: my $chunked = ( $ENV{'HTTP_TRANSFER_ENCODING'} =~ /^chunked.*$/ ) || 0; Since the Transfer-Encoding header will often not be present, wouldn't it be better to first check whether the key we're asking for exists? my $chunked = (exists $ENV{'HTTP_TRANSFER_ENCODING'} && $ENV{'HTTP_TRANSFER_ENCODING'} =~ /^chunked.*$/ ) || 0; Version-Release number of selected component (if applicable): perl-SOAP-Lite-0.710.10-1.fc12.noarch How reproducible: Always. Steps to Reproduce: 1. Load the URL for Bugzilla's xmlrpc.cgi. Actual results: Call fails with the above error. Expected results: No error. -- 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 24

[Bug 628046] New: Needs to BR version.pm for EPEL build
by Red Hat Bugzilla 11 May '11

11 May '11

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: Needs to BR version.pm for EPEL build https://bugzilla.redhat.com/show_bug.cgi?id=628046 Summary: Needs to BR version.pm for EPEL build Product: Fedora Version: 13 Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: low Component: perl-SOAP-Lite AssignedTo: mmcgrath(a)redhat.com ReportedBy: bloch(a)verdurin.com QAContact: extras-qa(a)fedoraproject.org CC: fedora-perl-devel-list(a)redhat.com, mmcgrath(a)redhat.com Classification: Fedora Description of problem: I'm trying to make an EPEL5 build of perl-bioperl (ultimately so I can make an RPM of perl-Bio-SamTools). One of the bioperl requirements is perl-SOAP-Lite. In order to make the tests pass, I had to add the following to the .spec: BuildRequires: perl(version) Version-Release number of selected component (if applicable): perl-SOAP-Lite-0.710.10-1.fc13.noarch How reproducible: 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.

1 2

[Bug 620413] New: perl-Test-Memory-Cycle - Request for EL-6 branch
by Red Hat Bugzilla 30 Apr '11

30 Apr '11

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: perl-Test-Memory-Cycle - Request for EL-6 branch https://bugzilla.redhat.com/show_bug.cgi?id=620413 Summary: perl-Test-Memory-Cycle - Request for EL-6 branch Product: Fedora EPEL Version: el6 Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: low Component: perl-Test-Memory-Cycle AssignedTo: rob.myers(a)gtri.gatech.edu ReportedBy: paul(a)city-fan.org QAContact: extras-qa(a)fedoraproject.org CC: rob.myers(a)gtri.gatech.edu, fedora-perl-devel-list(a)redhat.com Classification: Fedora perl-Test-Memory-Cycle is included in EL-6 optional packages, but not on all architectures (e.g. it is missing from ppc64), which is a problem when building packages that depend on it in EPEL-6. Please could we have an EPEL EL-6 branch built using the RHEL-6 SRPM to provide it for the other arches. I (pghmcfc) am willing to (co)maintain. -- 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 10

[Bug 483772] New: SVK fails because it cannot find Time/Progress.pm
by Red Hat Bugzilla 28 Apr '11

28 Apr '11

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: SVK fails because it cannot find Time/Progress.pm https://bugzilla.redhat.com/show_bug.cgi?id=483772 Summary: SVK fails because it cannot find Time/Progress.pm Product: Fedora Version: 10 Platform: All OS/Version: Linux Status: NEW Severity: urgent Priority: low Component: perl-SVK AssignedTo: ianburrell(a)gmail.com ReportedBy: warlord(a)mit.edu QAContact: extras-qa(a)fedoraproject.org CC: ianburrell(a)gmail.com, fedora-perl-devel-list(a)redhat.com Classification: Fedora Description of problem: I just upgraded Fedora 10 yesterday and this morning I noticed that SVK isn't working anymore. When I try to sync I get: Can't locate Time/Progress.pm in @INC (@INC contains: /usr/lib/perl5/5.10.0/i386-linux-thread-multi /usr/lib/perl5/5.10.0 /usr/local/lib/perl5/site_perl/5.10.0/i386-linux-thread-multi /usr/local/lib/perl5/site_perl/5.10.0 /usr/lib/perl5/vendor_perl/5.10.0/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.10.0 /usr/lib/perl5/vendor_perl /usr/local/lib/perl5/site_perl .) at /usr/lib/perl5/vendor_perl/5.10.0/SVK/Notify.pm line 214. Version-Release number of selected component (if applicable): perl-SVK-2.2.1-1.fc10.noarch How reproducible: Seems to happen every time I try to use "svk sync". Some other svk operations seem to work okay. Steps to Reproduce: 1. yum update (as of 2009-02-03 10:20am US/EST) 2. svk sync <depotpath> 3. Actual results: See above Expected results: It should sync. Additional info: I cannot find Time/Progress.pm in a package.. And indeed the perl-SVK RPM doesn't depend on perl(Time/Progress.pm) for some odd reason... Probably because the "require Time/Progress.pm" is within a subroutine instead of global? But this bug makes SVK practically useless. -- 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 7

← Newer
1
2
3
4
5
6
7
...
63
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

perl-devel September 2010