[Bug 637077] New: PID file location miss match
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: PID file location miss match
https://bugzilla.redhat.com/show_bug.cgi?id=637077
Summary: PID file location miss match
Product: Fedora
Version: 13
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: amavisd-new
AssignedTo: steve(a)silug.org
ReportedBy: tomo(a)appletz.jp
QAContact: extras-qa(a)fedoraproject.org
CC: steve(a)silug.org, fedora-perl-devel-list(a)redhat.com,
kanarip(a)kanarip.com
Classification: Fedora
Description of problem:
'/usr/share/clamav/clamd-wrapper' considers the place of the PID file to be
'/var/run/clamd.${CLAMD_SERVICE}/clamd.pid' if it isn't specified.
However, because '/etc/clamd.d/amavisd.conf' specifies
'var/run/amavisd/clamd.pid', so
it is necessary to be specified in '/etc/sysconfig/clamd.amavisd'.
--- SOURCES/amavis-clamd.sysconfig~ 2006-01-26 17:11:54.000000000 -0500
+++ SOURCES/amavis-clamd.sysconfig 2010-09-24 07:51:42.605828909 -0400
@@ -1,3 +1,4 @@
CLAMD_CONFIGFILE=/etc/clamd.d/amavisd.conf
CLAMD_SOCKET=/var/spool/amavisd/clamd.sock
+CLAMD_PIDFILE=/var/run/amavisd/clamd.pid
CLAMD_OPTIONS=
--
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.
12 years, 9 months
[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
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.
12 years, 9 months
[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
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.
12 years, 9 months
[Bug 574195] New: AMAVISD_DB_HOME in amavisd-agent has wrong default
by Red Hat Bugzilla
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.
12 years, 9 months
[Bug 616626] New: python-pip pkg conflict with perl-pip
by Red Hat Bugzilla
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.
12 years, 9 months
[Bug 613872] New: Request for support in EPEL
by Red Hat Bugzilla
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.
12 years, 10 months
[Bug 646832] New: Net::Amazon::S3 is way out of date, please update
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: Net::Amazon::S3 is way out of date, please update
https://bugzilla.redhat.com/show_bug.cgi?id=646832
Summary: Net::Amazon::S3 is way out of date, please update
Product: Fedora
Version: 14
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: medium
Priority: low
Component: perl-Net-Amazon-S3
AssignedTo: rrati(a)redhat.com
ReportedBy: jik(a)kamens.brookline.ma.us
QAContact: extras-qa(a)fedoraproject.org
CC: fedora-perl-devel-list(a)redhat.com, rrati(a)redhat.com
Classification: Fedora
perl-Net-Amazon-S3 is currently version 0.43, which is very old. Current
version is 0.53. Please update.
--
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.
12 years, 10 months
[Bug 459954] New: Default clamd conf file is broken
by Red Hat Bugzilla
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.
12 years, 10 months
[Bug 571192] New: $ENV{"HTTP_TRANSFER_ENCODING"} may be undefined in SOAP::Transport::HTTP
by Red Hat Bugzilla
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.
12 years, 11 months
[Bug 628046] New: Needs to BR version.pm for EPEL build
by Red Hat Bugzilla
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.
12 years, 11 months