[Bug 529172] New: Fedora::Bugzilla - get_flag() doesn't work for all flags
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: Fedora::Bugzilla - get_flag() doesn't work for all flags
https://bugzilla.redhat.com/show_bug.cgi?id=529172
Summary: Fedora::Bugzilla - get_flag() doesn't work for all
flags
Product: Fedora
Version: 11
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: perl-Fedora-Bugzilla
AssignedTo: cweyl(a)alumni.drew.edu
ReportedBy: jpirko(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: cweyl(a)alumni.drew.edu,
fedora-perl-devel-list(a)redhat.com, mmaslano(a)redhat.com
Classification: Fedora
Target Release: ---
Created an attachment (id=364891)
--> (https://bugzilla.redhat.com/attachment.cgi?id=364891)
test script
Description of problem:
I have trouble with get_flag() method of Fedora::Bugzilla::Bug. It works for me
for all flags except of "rhel-5.5.0" (and probably others). When I walk thru
the flags manually, the flag is there.
Version-Release number of selected component (if applicable):
0.10-1 - I tried 0.13 from CPAN and problem is still there.
How reproducible:
always
Steps to Reproduce:
run attached script
Actual results:
has pm_ack
+
has rhel-5.5.0
can't get rhel-5.5.0 flag
devel_ack, +
qa_ack, +
pm_ack, +
rhel-5.5.0, +
Expected results:
has pm_ack
+
has rhel-5.5.0
+
devel_ack, +
qa_ack, +
pm_ack, +
rhel-5.5.0, +
--
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.
11 years, 8 months
[Bug 247253] New: Conflicting Provides
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 report.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=247253
Summary: Conflicting Provides
Product: Fedora
Version: f7
Platform: All
OS/Version: Linux
Status: NEW
Severity: low
Priority: low
Component: perl-Time-Piece-MySQL
AssignedTo: chris(a)chrisgrau.com
ReportedBy: bugs.michael(a)gmx.net
QAContact: extras-qa(a)fedoraproject.org
CC: fedora-perl-devel-list(a)redhat.com
perl-Time-Piece provides perl(Time::Piece) EQ 0 1.09
perl-Time-Piece-MySQL provides perl(Time::Piece)
required by: perl-Email-Date - 1.102-2.fc7.noarch
required by: perl-Time-Piece-MySQL - 0.05-3.fc6.noarch
required by: perl-Time-Piece-MySQL - 0.05-3.fc6.noarch
required by: perl-Email-Date - 1.102-2.fc7.noarch
Indeed. perl-Time-Piece-MySQL does not include a Time::Piece
module and therefore must not provide perl(Time::Piece).
Luck has it that a second dependency on Time::Seconds
pulls in perl-Time-Piece. Else it would break.
[...]
Further reference, similar cases:
https://www.redhat.com/archives/fedora-perl-devel-list/2007-July/msg00011...
--
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.
12 years, 7 months
[Bug 450412] New: please build in EL-5
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 report.
https://bugzilla.redhat.com/show_bug.cgi?id=450412
Summary: please build in EL-5
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: low
Priority: low
Component: perl-JSON
AssignedTo: cweyl(a)alumni.drew.edu
ReportedBy: jonstanley(a)gmail.com
QAContact: extras-qa(a)fedoraproject.org
CC: bpeck@redhat.com,dmalcolm(a)redhat.com,fedora-perl-devel-
list@redhat.com,jlaska@redhat.com,poelstra(a)redhat.com
If you could branch this module for EL-5, it's required for Testopia, which is
currently under review.
I'd be happy to be co-maintainer for EPEL if you'd like, it builds fine as is in F9.
--
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.
12 years, 8 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, 10 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, 10 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, 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, 11 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 483772] New: SVK fails because it cannot find Time/Progress.pm
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: 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.
13 years