[Bug 807072] New: Currency quotes stopped working
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: Currency quotes stopped working
https://bugzilla.redhat.com/show_bug.cgi?id=807072
Summary: Currency quotes stopped working
Product: Fedora
Version: 16
Platform: Unspecified
OS/Version: Linux
Status: NEW
Severity: low
Priority: unspecified
Component: perl-Finance-Quote
AssignedTo: notting(a)redhat.com
ReportedBy: centaur(a)netmagic.net
QAContact: extras-qa(a)fedoraproject.org
CC: notting(a)redhat.com, fedora-perl-devel-list(a)redhat.com
Classification: Fedora
Story Points: ---
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Description of problem:
Earlier this year currency quotes stopped working due to a change in Yahoo's
site.
Version-Release number of selected component (if applicable):
perl-Finance-Quote-1.17-7.fc16.noarch
How reproducible:
Always
Steps to Reproduce:
1. Start GnuCash
2. Go to Tools->Price Editor
3. Press the Get Quotes button
Actual results:
No currency quotes will be retrieved.
Expected results:
Currency quotes used to work.
Additional info:
This issue is documented and patches have been developed to correct it. See:
http://gnucash.1415818.n4.nabble.com/Unable-to-receive-quote-for-CURRENCY...
--
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, 6 months
[Bug 680217] New: CVE-2011-0009 RT3: Insecure hashing algorithm used for storage of user passwords [epel-6]
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: CVE-2011-0009 RT3: Insecure hashing algorithm used for storage of user passwords [epel-6]
https://bugzilla.redhat.com/show_bug.cgi?id=680217
Summary: CVE-2011-0009 RT3: Insecure hashing algorithm used for
storage of user passwords [epel-6]
Product: Fedora EPEL
Version: el6
Platform: All
OS/Version: Linux
Status: NEW
Keywords: Security, SecurityTracking
Severity: low
Priority: low
Component: rt3
AssignedTo: xavier(a)bachelot.org
ReportedBy: vdanen(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: xavier(a)bachelot.org,
fedora-perl-devel-list(a)redhat.com, mmahut(a)redhat.com,
tremble(a)tremble.org.uk
Blocks: 672250
Classification: Fedora
epel-6 tracking bug for rt3: see blocks bug list for full details of the
security issue(s).
This bug is never intended to be made public, please put any public notes
in the 'blocks' bugs.
[bug automatically created by: add-tracking-bugs]
--
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, 6 months
[Bug 838551] New: syscall() truncates return value to 32 bits
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=838551
Bug ID: 838551
QA Contact: extras-qa(a)fedoraproject.org
Severity: high
URL: https://rt.perl.org/rt3/Public/Bug/Display.html?id=113
980
Version: 16
Priority: unspecified
CC: cweyl(a)alumni.drew.edu, 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
Assignee: mmaslano(a)redhat.com
Summary: syscall() truncates return value to 32 bits
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: ppisar(a)redhat.com
Type: Bug
Documentation: ---
Hardware: x86_64
Mount Type: ---
Status: ASSIGNED
Component: perl
Product: Fedora
There is problem when calling generic syscall() function on 64-bit
architectures. The return value is clamped to 32 bits.
Can be reproduced with mmap or mremap syscalls:
> #!/usr/bin/perl -w
> use strict;
>
> sub find_vdso()
> {
> open my $maps, '<', '/proc/self/maps' or die;
> /^(.*?)-.*\[vdso\]$/ and return hex $1 for <$maps>;
> }
>
> my $vdso_addr = find_vdso || die 'not 64-bit linux?';
>
> my $ret = syscall 25, # __NR_mremap
> $vdso_addr, # old_addr
> 1, # old_len
> 1, # new_len
> 0, # flags
> 0; # new_addr (unused)
>
> $ret == $vdso_addr or die "FAILED\n";
Fixed in upstream commit:
commit f9344c91a4ca48288bba30dc94a2d712d0659670
Author: Oleg Nesterov <oleg(a)redhat.com>
Date: Wed Jul 4 08:21:15 2012 -0700
[perl #113980] pp_syscall: "I32 retval" truncates the returned value
I noticed today that syscall(9, ...) (mmap) doesn't work for me.
The problem is obvious, pp_syscall() uses I32 for retval and the
"long" address doesn't fit into "int".
The one-liner below should fix the problem.
--
You are receiving this mail because:
You are on the CC list for the bug.
11 years, 7 months
[Bug 834226] New: `do' does not clean $@ on success sometimes
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=834226
Bug ID: 834226
QA Contact: extras-qa(a)fedoraproject.org
Severity: high
URL: https://rt.perl.org/rt3/Public/Bug/Display.html?id=113
730
Version: 16
Priority: unspecified
CC: cweyl(a)alumni.drew.edu, 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
Assignee: mmaslano(a)redhat.com
Summary: `do' does not clean $@ on success sometimes
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: ppisar(a)redhat.com
Type: Bug
Documentation: ---
Hardware: Unspecified
Mount Type: ---
Status: ASSIGNED
Component: perl
Product: Fedora
The `eval' and `do' functions should clear $@ variable on success. However this
does not happen always:
eval { die "shouldn't see this\n" };
do 'no such file';
warn $@ if $@;
This has been fixed in upstream commit:
commit a3ff80c12c16886edf9acdd3d172798e50defdb3
Author: Eric Brine <ikegami(a)adaelis.com>
Date: Mon Jun 18 14:56:32 2012 -0400
RT#113730 - $@ should be cleared on "do" IO error.
Tested with perl-5.14.2-198.fc16.x86_64. All Fedoras are affected probably.
--
You are receiving this mail because:
You are on the CC list for the bug.
11 years, 7 months
[Bug 826872] New: Trying to use the Pod::Man "parse_file" function in Perl results in errors
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=826872
Bug ID: 826872
QA Contact: extras-qa(a)fedoraproject.org
Severity: medium
Clone Of: 819042
Version: 16
Priority: unspecified
CC: cweyl(a)alumni.drew.edu, 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
Assignee: mmaslano(a)redhat.com
Summary: Trying to use the Pod::Man "parse_file" function in
Perl results in errors
Regression: ---
Story Points: ---
Classification: Fedora
OS: Linux
Reporter: ppisar(a)redhat.com
Type: Bug
Documentation: ---
Hardware: All
Mount Type: ---
Status: ASSIGNED
Component: perl
Product: Fedora
+++ This bug was initially created as a clone of Bug #819042 +++
If I try to use the Pod::Man "parse_file" function, I get failures. Even the
simplest invocation, directly from the man page, gives uninitialized value and
strict refs errors.
[...]
The documentation (man Pod::Man) says:
SYNOPSIS
use Pod::Man;
my $parser = Pod::Man->new (release => $VERSION, section => 8);
# Read POD from STDIN and write to STDOUT.
$parser->parse_file (\*STDIN);
...
The standard Pod::Simple method parse_file() takes one argument naming
the POD file to read from. By default, the output is sent to "STDOUT",
but this can be changed with the output_fd() method.
[...]
$ perl -we 'use strict; use Pod::Man; my $p = Pod::Man->new();
$p->parse_file($ARGV[0]);' /usr/share/perl5/Pod/Man.pm
Use of uninitialized value in ref-to-glob cast at /usr/share/perl5/Pod/Man.pm
line 722.
Can't use string ("") as a symbol ref while "strict refs" in use at
/usr/share/perl5/Pod/Man.pm line 722.
[...]
--- Additional comment from ppisar(a)redhat.com on 2012-05-31 07:40:08 GMT ---
Pod::Man developer decided do the fix in podlators-2.4.1
(http://cpansearch.perl.org/src/RRA/podlators-2.4.1/ChangeLog).
-----
perl-5.14.2-197.fc16.x86_64 in Fedora 16 affected. We should patch the perl or
provide podlators-2.4.1 as dual-lived package.
--
You are receiving this mail because:
You are on the CC list for the bug.
11 years, 7 months
[Bug 754689] New: CGI::Session emits deprecation warning when running under 'use warnings'
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: CGI::Session emits deprecation warning when running under 'use warnings'
https://bugzilla.redhat.com/show_bug.cgi?id=754689
Summary: CGI::Session emits deprecation warning when running
under 'use warnings'
Product: Fedora
Version: 16
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: unspecified
Priority: unspecified
Component: perl-CGI-Session
AssignedTo: andreas(a)bawue.net
ReportedBy: simon.andrews(a)bbsrc.ac.uk
QAContact: extras-qa(a)fedoraproject.org
CC: andreas(a)bawue.net, fedora-perl-devel-list(a)redhat.com
Classification: Fedora
Story Points: ---
Type: ---
Description of problem:
The F16 version of CGI session issues a deprecation warning when run under the
version of perl shipped with F16
Version-Release number of selected component (if applicable):
perl-CGI-Session-4.35-9.fc16.noarch
perl-5.14.2-190.fc16.i686
How reproducible:
Always
Steps to Reproduce:
1. perl -MCGI::Session -Mwarnings -e 'exit'
Actual results:
Use of qw(...) as parentheses is deprecated at
/usr/share/perl5/vendor_perl/CGI/Session.pm line 882.
Expected results:
No warning.
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.
11 years, 7 months