[Bug 229179] New: check_whitelist and check_spamd scripts missing.
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=229179
Summary: check_whitelist and check_spamd scripts missing.
Product: Fedora Core
Version: fc6
Platform: All
OS/Version: Linux
Status: NEW
Severity: low
Priority: normal
Component: spamassassin
AssignedTo: wtogami(a)redhat.com
ReportedBy: m.d.t.evans(a)qmul.ac.uk
CC: fedora-perl-devel-
list@redhat.com,felicity@kluge.net,jm(a)jmason.org,parkerm
@pobox.com,reg+redhat@sidney.com,wtogami(a)redhat.com
Description of problem:
The SA source contains 2 useful perl scripts, one to maintain the autowhitelist
database file and a nagios monitoring script. It would be helpful if you could
include them. I've attached a patch below (which you will may want to tweak a bit).
Version-Release number of selected component (if applicable):
3.1.8-1.fc6
------- Additional Comments From m.d.t.evans(a)qmul.ac.uk 2007-02-19 07:00 EST -------
Created an attachment (id=148315)
--> (https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=148315&action=view)
Patch file for spamassassin that adds check_whitelist and check_spamd scripts.
--
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.
14 years, 10 months
[Bug 221113] New: readline function in perl does not correctly set $!
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=221113
Summary: readline function in perl does not correctly set $!
Product: Fedora Core
Version: fc6
Platform: i386
OS/Version: Linux
Status: NEW
Severity: normal
Priority: normal
Component: perl
AssignedTo: rnorwood(a)redhat.com
ReportedBy: wpilorz(a)gmail.com
QAContact: dkl(a)redhat.com
CC: fedora-perl-devel-list(a)redhat.com
Description of problem:
perldoc -f readline
displays example code how do check for errors with readline:
for (;;) {
undef $!;
unless (defined( $line = <> )) {
die $! if $!;
last; # reached EOF
}
# ...
}
Unfortunately this method no longer works as described in current perl version.
I am including a short perl script readline_test.pl attempting to use that
method and bash script readline_test.bash calling that perl script 16 times;
input is either "1234" or "1234\n",
PERLIO environment variable is set to perlio or stdio,
(PERLIO=perlio is equivalent to PERLIO not set in FC6)
$/ is set to undef, not modified, \2, \1024.
$/ is set to a reference to value specified in environment variable CHUNKSIZE,
unless it is 0 ($/ not set in this case) or negative ($/ set to undef).
In correct perl implementation all 16 tests should run successfully (no die).
The results included show that PERLIO=stdio is better (4 tests fail for stdio, 6
tests fail for perlio)
Version-Release number of selected component (if applicable):
perl-5.8.8-10
How reproducible:
always
Steps to Reproduce:
1. save readline_test.pl and readline_test.bash files from attachemnts into
current directory
2. run the following command in the current directory
bash readline_test.bash
you could prefer to run
bash -vx readline_test.bash
to see exactly what is being run
Actual results:
$ bash readline_test.bash
__ running readline_test.pl for stdin=1234,CHUNKSIZE=-1,PERLIO=perlio...
INFO: $/ will be set to undef
Bad file descriptor at readline_test.pl line 30, <F> chunk 1.
__ running readline_test.pl for stdin=1234,CHUNKSIZE=-1,PERLIO=stdio...
INFO: $/ will be set to undef
Bad file descriptor at readline_test.pl line 30, <F> chunk 1.
__ running readline_test.pl for stdin=1234,CHUNKSIZE=0,PERLIO=perlio...
INFO: $/ will not be set
Bad file descriptor at readline_test.pl line 30, <F> line 1.
__ running readline_test.pl for stdin=1234,CHUNKSIZE=0,PERLIO=stdio...
INFO: $/ will not be set
Bad file descriptor at readline_test.pl line 30, <F> line 1.
__ running readline_test.pl for stdin=1234,CHUNKSIZE=2,PERLIO=perlio...
INFO: $/ will be set to 2
INFO: File /dev/stdin has been read, nbytes = 4
__ running readline_test.pl for stdin=1234,CHUNKSIZE=2,PERLIO=stdio...
INFO: $/ will be set to 2
INFO: File /dev/stdin has been read, nbytes = 4
__ running readline_test.pl for stdin=1234,CHUNKSIZE=1k,PERLIO=perlio...
INFO: $/ will be set to 1024
Bad file descriptor at readline_test.pl line 30, <F> chunk 1.
__ running readline_test.pl for stdin=1234,CHUNKSIZE=1k,PERLIO=stdio...
INFO: $/ will be set to 1024
INFO: File /dev/stdin has been read, nbytes = 4
__ running readline_test.pl for stdin=1234\n,CHUNKSIZE=-1,PERLIO=perlio...
INFO: $/ will be set to undef
Bad file descriptor at readline_test.pl line 30, <F> chunk 1.
__ running readline_test.pl for stdin=1234\n,CHUNKSIZE=-1,PERLIO=stdio...
INFO: $/ will be set to undef
Bad file descriptor at readline_test.pl line 30, <F> chunk 1.
__ running readline_test.pl for stdin=1234\n,CHUNKSIZE=0,PERLIO=perlio...
INFO: $/ will not be set
INFO: File /dev/stdin has been read, nbytes = 5
__ running readline_test.pl for stdin=1234\n,CHUNKSIZE=0,PERLIO=stdio...
INFO: $/ will not be set
Bad file descriptor at readline_test.pl line 30, <F> line 1.
__ running readline_test.pl for stdin=1234\n,CHUNKSIZE=2,PERLIO=perlio...
INFO: $/ will be set to 2
Bad file descriptor at readline_test.pl line 30, <F> chunk 3.
__ running readline_test.pl for stdin=1234\n,CHUNKSIZE=2,PERLIO=stdio...
INFO: $/ will be set to 2
INFO: File /dev/stdin has been read, nbytes = 5
__ running readline_test.pl for stdin=1234\n,CHUNKSIZE=1k,PERLIO=perlio...
INFO: $/ will be set to 1024
Bad file descriptor at readline_test.pl line 30, <F> chunk 1.
__ running readline_test.pl for stdin=1234\n,CHUNKSIZE=1k,PERLIO=stdio...
INFO: $/ will be set to 1024
INFO: File /dev/stdin has been read, nbytes = 5
Expected results:
each run of perl should complete without die and show number of bytes on input
(4 for first 8 tests, 5 for remaining tests)
Additional info:
if PERLIO=perlio is used and there is actual I/O error in data file, the
readline_test.pl dies with inappropriate error message
'Bad file descriptor' rather than 'Input/output error'
im most cases.
This can be easily shown with truncated ISO-9660 image file, loop mounted.
Should I also include test cases for this?
------- Additional Comments From wpilorz(a)gmail.com 2007-01-01 18:46 EST -------
Created an attachment (id=144615)
--> (https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=144615&action=view)
readline_test.pl test script
--
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.
14 years, 11 months
[Bug 248731] New: cpan2rpm doesn't work when first file in tarball isn't a directory
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=248731
Summary: cpan2rpm doesn't work when first file in tarball isn't a
directory
Product: Fedora
Version: devel
Platform: All
OS/Version: Linux
Status: NEW
Severity: low
Priority: low
Component: cpan2rpm
AssignedTo: ghenry(a)suretecsystems.com
ReportedBy: jik(a)kamens.brookline.ma.us
QAContact: extras-qa(a)fedoraproject.org
CC: fedora-perl-devel-list(a)redhat.com
Tried to run "cpan2rpm Tk". The first file in Tk-804.027.tar.gz is Tk-
804.027/COPYING, i.e., it isn't the root directory of the tarball, which is
what cpan2rpm is expecting. cpan2rpm fails with:
get_meta(): Not a directory at /usr/bin/cpan2rpm line 393.
I added a bit more info to that error message and it reports:
get_meta(): chdir(/tmp/ZhnL73u9em/Tk-804.027/COPYING): Not a directory
at /usr/bin/cpan2rpm line 393.
--
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.
15 years, 4 months
[Bug 245225] New: perl-GD build warning perl-GD-2.35-2.fc6.src.rpm
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=245225
Summary: perl-GD build warning perl-GD-2.35-2.fc6.src.rpm
Product: Fedora
Version: devel
Platform: All
OS/Version: Linux
Status: NEW
Severity: low
Priority: low
Component: perl-GD
AssignedTo: jpo(a)di.uminho.pt
ReportedBy: herrold(a)owlriver.com
QAContact: extras-qa(a)fedoraproject.org
CC: fedora-perl-devel-list(a)redhat.com
Description of problem:
perl-GD emits header related warnings during its build -- eitehr its
expectation, of that of gd-devel as to header placement are wrong, and the
warning should be addressed
Version-Release number of selected component (if applicable):
perl-GD-2.35-2.fc6.src.rpm
$ rpm -qf /usr/include/gd.h
gd-devel-2.0.33-9.3.fc6
How reproducible:
rpmbuild --rebuild perl-GD-2.35-2.fc6.src.rpm 2>&1 | grep Warning
Steps to Reproduce:
1.
2.
3.
Actual results:
(from my error and warning checker) Error: perl cruft found -|1|-
** WARNING: found gd.h header file in /usr/include/gd.h, but it is expected at
/usr/include/gd.h. This may cause compile errors! **
Expected results:
no warning to stderr, and no error as well [ a > /dev/null is inappropriate ;) ]
Additional info:
--
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.
15 years, 9 months
[Bug 235553] New: perl.ppc64 @INC problem, perl.ppc conflicts
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=235553
Summary: perl.ppc64 @INC problem, perl.ppc conflicts
Product: Fedora Core
Version: fc6
Platform: ppc64
OS/Version: Linux
Status: NEW
Severity: medium
Priority: medium
Component: perl
AssignedTo: rnorwood(a)redhat.com
ReportedBy: christopher.murtagh(a)gmail.com
QAContact: dkl(a)redhat.com
CC: dwmw2@redhat.com,fedora-perl-devel-list(a)redhat.com
Description of problem:
perl.ppc64's @INC doesn't include paths where most perl binary packages are,
perl-BerkeleyDB.ppc for example.
[root@mybox~]# locate BerkeleyDB.pm
/usr/lib/perl5/vendor_perl/5.8.8/ppc-linux-thread-multi/BerkeleyDB.pm
Version-Release number of selected component (if applicable):
current (from base)
How reproducible:
100%.
Steps to Reproduce:
1. Install perl.ppc, perl.ppc64, install perl-BerkelyDB.
2. Then perl -e 'use BerkeleyDB; exit;'
3. There is no step 3... heh, there is no step 3.
Actual results:
Can't locate BerkeleyDB.pm in @INC (@INC contains:
/usr/lib64/perl5/site_perl/5.8.8/ppc64-linux-thread-multi
/usr/lib64/perl5/site_perl/5.8.7/ppc64-linux-thread-multi
/usr/lib64/perl5/site_perl/5.8.6/ppc64-linux-thread-multi
/usr/lib64/perl5/site_perl/5.8.5/ppc64-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7
/usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5
/usr/lib/perl5/site_perl
/usr/lib64/perl5/vendor_perl/5.8.8/ppc64-linux-thread-multi
/usr/lib64/perl5/vendor_perl/5.8.7/ppc64-linux-thread-multi
/usr/lib64/perl5/vendor_perl/5.8.6/ppc64-linux-thread-multi
/usr/lib64/perl5/vendor_perl/5.8.5/ppc64-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl/5.8.7
/usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5
/usr/lib/perl5/vendor_perl /usr/lib64/perl5/5.8.8/ppc64-linux-thread-multi
/usr/lib/perl5/5.8.8) at /usr/sbin/postgrey line 14.
Expected results:
Successful compilation and exit without error.
Additional info:
The workaround was to yum erase perl.ppc64, fetch the perl.ppc rpm and rpm -i
--replacepkgs --replacefiles (because they both dump perl in /usr/bin/perl, so
removing the perl.ppc64 still left the 64 bit binary).
--
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.
15 years, 11 months
[Bug 198399] New: Package perl lacks IPv6 support
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=198399
Summary: Package perl lacks IPv6 support
Product: Fedora Core
Version: devel
Platform: All
OS/Version: Linux
Status: NEW
Severity: normal
Priority: normal
Component: perl
AssignedTo: jvdias(a)redhat.com
ReportedBy: pvrabec(a)redhat.com
QAContact: dkl(a)redhat.com
CC: fedora-perl-devel-list@redhat.com,mbacovsk(a)redhat.com
This bug was reported automaticaly in connection with IPv6 project.
Our aim is to support IPv6 in all Fedora Core packages so FC6 and RHEL5 will be ready for IPv6.
This package seems to lack IPv6 support as is illustrated in attached log.
Here follows part of scanning log (grep -r F_INET *)/up to 30 lines:
/perl-5.8.8/pp_sys.c:2369:#if defined (HAS_SOCKETPAIR) || (defined (HAS_SOCKET) && defined(SOCK_DGRAM) && defined(AF_INET) && defined(PF_INET))
/perl-5.8.8/pp_sys.c:2742: if (((struct sockaddr *)SvPVX_const(sv))->sa_family == AF_INET &&
/perl-5.8.8/vms/sockadapt.c:122: if (addr->sa_family == AF_INET &&
/perl-5.8.8/vms/sockadapt.h:115:#ifndef AF_INET
/perl-5.8.8/vms/sockadapt.h:116:# define AF_INET 2
/perl-5.8.8/util.c:4166:#if !defined(HAS_SOCKETPAIR) && defined(HAS_SOCKET) && defined(AF_INET) && defined(PF_INET) && defined(SOCK_DGRAM) && defined(HAS_SELECT)
/perl-5.8.8/util.c:4185: sockets[i] = PerlSock_socket(AF_INET, SOCK_DGRAM, PF_INET);
/perl-5.8.8/util.c:4189: addresses[i].sin_family = AF_INET;
/perl-5.8.8/util.c:4311:#if !defined(HAS_SOCKETPAIR) && defined(HAS_SOCKET) && defined(AF_INET) && defined(PF_INET)
/perl-5.8.8/util.c:4342: listener = PerlSock_socket(AF_INET, type, 0);
/perl-5.8.8/util.c:4346: listen_addr.sin_family = AF_INET;
/perl-5.8.8/util.c:4355: connector = PerlSock_socket(AF_INET, type, 0);
/perl-5.8.8/mpeix/mpeix.c:511: /* AF_INET socket */
/perl-5.8.8/mpeix/mpeix.c:713: if (address->sa_family == AF_INET
/perl-5.8.8/mpeix/mpeix.c:724: if (address->sa_family == AF_INET)
/perl-5.8.8/mpeix/mpeix.c:750: && address->sa_family == AF_INET
/perl-5.8.8/mpeix/mpeix.c:799: result = 30000; /* AF_INET sock max */
--
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.
15 years, 11 months
[Bug 237025] New: perl-Text-CSV_XS: EPEL branches?
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=237025
Summary: perl-Text-CSV_XS: EPEL branches?
Product: Fedora Extras
Version: fc6
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: medium
Component: perl-Text-CSV_XS
AssignedTo: jpo(a)di.uminho.pt
ReportedBy: cweyl(a)alumni.drew.edu
QAContact: extras-qa(a)fedoraproject.org
CC: fedora-perl-devel-list(a)redhat.com
It would be useful to me to have this package in EPEL... Any chance of EL-4,
EL-5 branches? :)
Review is bug 175898.
--
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.
15 years, 11 months
[Bug 242249] New: syntax error in perl5db.pl
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=242249
Summary: syntax error in perl5db.pl
Product: Fedora Core
Version: fc6
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: perl
AssignedTo: rnorwood(a)redhat.com
ReportedBy: ihok(a)hotmail.com
CC: fedora-perl-devel-list(a)redhat.com
Unmatched right curly bracket at (eval 48)[/usr/lib/perl5/5.8.8/perl5db.pl:628]
line 5, at end of line
syntax error at (eval 48)[/usr/lib/perl5/5.8.8/perl5db.pl:628] line 5, near ";
}"
Version-Release number of selected component (if applicable):
perl-5.8.8-10
--
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.
16 years
[Bug 228043] New: ??? 64bit sa-update.1 manpage timestamp differs from 32bit?
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=228043
Summary: ??? 64bit sa-update.1 manpage timestamp differs from
32bit?
Product: Fedora Core
Version: devel
Platform: All
OS/Version: Linux
Status: NEW
Severity: low
Priority: low
Component: spamassassin
AssignedTo: wtogami(a)redhat.com
ReportedBy: wtogami(a)redhat.com
CC: fedora-perl-devel-
list@redhat.com,felicity@kluge.net,jm(a)jmason.org,parkerm
@pobox.com,reg+redhat@sidney.com,wtogami(a)redhat.com
Odd minor problem... low priority.
/usr/share/man/man1/sa-update.1.gz differs by the following unidiff between the
32bit and 64bit architecture builds of spamassassin.
--- 32 2007-02-09 12:46:19.000000000 -0500
+++ 64 2007-02-09 12:46:10.000000000 -0500
@@ -129,7 +129,7 @@
.\" ========================================================================
.\"
.IX Title "SA-UPDATE 1"
-.TH SA-UPDATE 1 "2006-07-30" "perl v5.8.5" "User Contributed Perl Documentation"
+.TH SA-UPDATE 1 "2007-01-22" "perl v5.8.5" "User Contributed Perl Documentation"
.SH "NAME"
sa\-update \- automate SpamAssassin rule updates
.SH "SYNOPSIS"
This appears to be the only difference in version 3.1.7. Notice that the 32bit
version retained the original source timestamp, while the 64bit version somehow
decided to differ in this behavior by changing the timestamp to the build date.
The above example is 3.1.7 built on RHEL4, but this persists through perl-5.8.8
in FC7 too.
While this appears to create a multilib conflict, in practice this is not a real
problem because spamassassin is based on perl, and we don't ship both archs in a
multilib distribution.
This bug is merely to figure out *why* it is behaving in this strange way
betweeen 32bit and 64bit builds.
--
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.
16 years
[Bug 232481] New: EPEL branches: a couple of perl packages from fedora.us
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=232481
Summary: EPEL branches: a couple of perl packages from fedora.us
Product: Fedora Extras
Version: devel
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: medium
Component: perl-pmtools
AssignedTo: jpo(a)di.uminho.pt
ReportedBy: jpo(a)di.uminho.pt
QAContact: extras-qa(a)fedoraproject.org
CC: fedora-perl-devel-list(a)redhat.com
Branches: EPEL4 and EPEL5
Perl packages to branch:
* perl-pmtools
* perl-ExtUtils-CBuilder
* perl-ExtUtils-ParseXS
Note:
* Please create the EPEL branchs from the devel or FC-6
--
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.
16 years