From bugzilla at redhat.com Tue Nov 1 03:48:47 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 31 Oct 2005 22:48:47 -0500 Subject: [Bug 172153] /etc/mail is not an ideal place for spamassasin config files In-Reply-To: Message-ID: <200511010348.jA13ml6S005886@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: /etc/mail is not an ideal place for spamassasin config files https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172153 rcoker at redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO_REPORTER |ASSIGNED ------- Additional Comments From rcoker at redhat.com 2005-10-31 22:48 EST ------- My guess is that it dates back to when Sendmail was the only viable option for a MTA. I would be surprised if the upstream authors don't change their location when it's suggested to them. mail.spamassassin.org is running Postfix... -- 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. From bugzilla at redhat.com Tue Nov 1 15:35:59 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 1 Nov 2005 10:35:59 -0500 Subject: [Bug 172153] /etc/mail is not an ideal place for spamassasin config files In-Reply-To: Message-ID: <200511011535.jA1FZxGF004281@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: /etc/mail is not an ideal place for spamassasin config files https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172153 ------- Additional Comments From wtogami at redhat.com 2005-11-01 10:35 EST ------- What are the implications of *not* changing this? It has been here for a long time and I'd really like to avoid moving it. (I still need to ask upstream what they would prefer.) -- 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. From bugzilla at redhat.com Tue Nov 1 19:58:25 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 1 Nov 2005 14:58:25 -0500 Subject: [Bug 172236] New: missing C standard headers Message-ID: 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=172236 Summary: missing C standard headers Product: Fedora Core Version: devel Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: normal Component: perl AssignedTo: jvdias at redhat.com ReportedBy: jvdias at redhat.com QAContact: dkl at redhat.com CC: fedora-perl-devel-list at redhat.com Description of problem: All perl versions on Linux / glibc / gcc systems fail to look for the C standard header files in the correct location, eg. : stddef.h syslimits.h stdarg.h float.h stdbool.h These are gcc built-in headers, and cpp searches for them in the gcc architecture specific include directory before the system include directory: /usr/lib/gcc/${arch}-${os}/${gcc-version}/include During the perl build, perl does not look for any headers in the gcc architecture specific include directory, but instead either fails to find the header at all, or finds versions of them used only by the kernel, eg. as shown by this excerpt from a log of a Rawhide perl build : --- + for i in asm/termios.h syscall.h syslimits.h syslog.h sys/ioctl.h sys/socket.h sys/time.h wait.h ... ... + /var/tmp/perl-5.8.7-0.5.fc5-root-jvdias//usr/bin/perl /var/tmp/perl-5.8.7-0.5.fc5-root-jvdias//usr/bin/h2ph -a -d /var/tmp/perl-5.8.7-0.5.fc5-root-jvdias/usr/lib/perl5/5.8.7/i386-linux-thread-multi syslimits.h Can't open syslimits.h: No such file or directory syslimits.h -> syslimits.ph --- ( empty syslimits.ph - no syslimits.ph shipped ) --- + /var/tmp/perl-5.8.7-0.5.fc5-root-jvdias//usr/bin/perl /var/tmp/perl-5.8.7-0.5.fc5-root-jvdias//usr/bin/h2ph -a -d /var/tmp/perl-5.8.7-0.5.fc5-root-jvdias/usr/lib/perl5/5.8.7/i386-linux-thread-multi asm/termios.h ... linux/stddef.h -> linux/stddef.ph --- No shipped, only , which is meant to be used only by the kernel. This results in many system headers that reference the C standard headers being unusable because the C standard headers are not found (eg. sys/resource.ph -> bits/resource.ph -> linux/types.ph -> stddef.ph -> stddef.ph not found, bug 170088 ). The perl build process should find the C standard headers in their correct location, as many system perl headers that are shipped by perl reference them. Version-Release number of selected component (if applicable): ALL How reproducible: 100% Steps to Reproduce: $ perl -e 'require "sys/resource.ph";' Actual results: Fails due to missing stddef.ph Expected results: No error 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. From bugzilla at redhat.com Tue Nov 1 20:35:07 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 1 Nov 2005 15:35:07 -0500 Subject: [Bug 71513] perl headers are incompletely built In-Reply-To: Message-ID: <200511012035.jA1KZ7H8032404@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: perl headers are incompletely built https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=71513 wtogami at redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |CLOSED Resolution| |DUPLICATE ------- Additional Comments From wtogami at redhat.com 2005-11-01 15:34 EST ------- Closing as duplicate against a more coherent explanation of this problem. *** This bug has been marked as a duplicate of 172236 *** -- 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. From bugzilla at redhat.com Tue Nov 1 20:35:18 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 1 Nov 2005 15:35:18 -0500 Subject: [Bug 172236] missing C standard headers In-Reply-To: Message-ID: <200511012035.jA1KZIWn032509@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: missing C standard headers https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172236 wtogami at redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |corey at cac.washington.edu ------- Additional Comments From wtogami at redhat.com 2005-11-01 15:35 EST ------- *** Bug 71513 has been marked as a duplicate of this bug. *** -- 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. From jvdias at redhat.com Tue Nov 1 23:14:33 2005 From: jvdias at redhat.com (Jason Vas Dias) Date: Tue, 1 Nov 2005 18:14:33 -0500 Subject: [PATCH] h2ph inc_dirs() fails to prepend gcc include search path, resulting in missing C standard headers on Linux Message-ID: <200511011814.34115.jvdias@redhat.com> To: perlbug at perl.org Subject: h2ph inc_dirs fails to prepend gcc include search path, resulting in missing C standard headers on Linux Reply-To: jvdias at redhat.com Message-Id: <5.8.7_3660_1130885631 at jvdias> This is a bug report for perl from jvdias at redhat.com, generated with the help of perlbug 1.35 running under perl v5.8.7. ----------------------------------------------------------------- [Please enter your report here] When building perl-5.8.7 on Linux, the standard C headers fail to be converted into perl headers, resulting in missing include dependencies. The C standard headers, such as : stddef.h syslimits.h stdarg.h float.h stdbool.h fail to be converted into perl headers (.ph files) during a build and install of perl-5.8.7 . Many system headers include these headers, so many system headers are made unusable with perl because of this problem. This is because h2ph's inc_dirs() does not find the string 'Reading specs from' in gcc -v's output, when the gcc version is >= 4. My gcc's -v option emits: $ gcc -v Using built-in specs. Target: i386-redhat-linux Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-libgcj-multifile --enable-languages=c,c++,objc,java,f95,ada --enable-java-awt=gtk --with-java-home=/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre --host=i386-redhat-linux Thread model: posix gcc version 4.0.1 20050727 (Red Hat 4.0.1-5) $ gcc 4 understands the '-print-search-dirs' option: $ gcc -print-search-dirs install: /usr/lib/gcc/i386-redhat-linux/4.0.1/ ... Here's a patch which corrects h2ph.PL's inc_dirs() to pick up gcc4's built-in header include path: --- --- perl-5.8.7/utils/h2ph.PL.bz172236 2005-04-04 17:47:17.000000000 -0400 +++ perl-5.8.7/utils/h2ph.PL 2005-11-01 17:42:36.000000000 -0500 @@ -734,9 +734,15 @@ # non-GCC?) C compilers, but gcc uses an additional include directory. sub inc_dirs { - my $from_gcc = `$Config{cc} -v 2>&1`; - $from_gcc =~ s:^Reading specs from (.*?)/specs\b.*:$1/include:s; - + my $from_gcc = `LC_ALL=C $Config{cc} -v 2>&1`; + if( !( $from_gcc =~ s:^Reading specs from (.*?)/specs\b.*:$1/include:s ) ) + { # gcc-4+ : + $from_gcc = `LC_ALL=C $Config{cc} -print-search-dirs 2>&1`; + if ( !($from_gcc =~ s/^install:\s*([^\s]+[^\s\/])([\s\/]*).*$/$1\/include/s) ) + { + $from_gcc = ''; + }; + }; length($from_gcc) ? ($from_gcc, $Config{usrinc}) : ($Config{usrinc}); } --- [Please do not change anything below this line] ----------------------------------------------------------------- --- Flags: category=core severity=low --- This perlbug was built using Perl v5.8.7 in the Red Hat build system. It is being executed now by Perl v5.8.7 - Tue Oct 25 19:39:19 EDT 2005. Site configuration information for perl v5.8.7: Configured by Red Hat, Inc. at Tue Oct 25 19:39:19 EDT 2005. Summary of my perl5 (revision 5 version 8 subversion 7) configuration: Platform: osname=linux, osvers=2.6.13-1.1624_fc5, archname=i386-linux-thread-multi uname='linux jvdias 2.6.13-1.1624_fc5 #1 mon oct 24 01:16:31 edt 2005 i686 i686 i386 gnulinux ' config_args='-des -Doptimize=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=pentium4 -fasynchronous-unwind-tables -Dversion=5.8.7 -Dmyhostname=localhost -Dperladmin=root at localhost -Dcc=gcc -Dcf_by=Red Hat, Inc. -Dinstallprefix=/usr -Dprefix=/usr -Darchname=i386-linux -Dvendorprefix=/usr -Dsiteprefix=/usr -Duseshrplib -Dusethreads -Duseithreads -Duselargefiles -Dd_dosuid -Dd_semctl_semun -Di_db -Ui_ndbm -Di_gdbm -Di_shadow -Di_syslog -Dman3ext=3pm -Duseperlio -Dinstallusrbinperl=n -Ubincompat5005 -Uversiononly -Dpager=/usr/bin/less -isr -Dd_gethostent_r_proto -Ud_endhostent_r_proto -Ud_sethostent_r_proto -Ud_endprotoent_r_proto -Ud_setprotoent_r_proto -Ud_endservent_r_proto -Ud_setservent_r_proto -Dinc_version_list=5.8.6 5.8.5 5.8.4 5.8.3 -Dscriptdir=/usr/bin' hint=recommended, useposix=true, d_sigaction=define usethreads=define use5005threads=undef useithreads=define usemultiplicity=define useperlio=define d_sfio=undef uselargefiles=define usesocks=undef use64bitint=undef use64bitall=undef uselongdouble=undef usemymalloc=n, bincompat5005=undef Compiler: cc='gcc', ccflags ='-D_REENTRANT -D_GNU_SOURCE -DDEBUGGING -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm', optimize='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=pentium4 -fasynchronous-unwind-tables', cppflags='-D_REENTRANT -D_GNU_SOURCE -DDEBUGGING -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/include/gdbm' ccversion='', gccversion='4.0.2 20051007 (Red Hat 4.0.2-3)', gccosandvers='' intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=1234 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12 ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8 alignbytes=4, prototype=define Linker and Libraries: ld='gcc', ldflags =' -L/usr/local/lib' libpth=/usr/local/lib /lib /usr/lib libs=-lresolv -lnsl -lgdbm -ldb -ldl -lm -lcrypt -lutil -lpthread -lc perllibs=-lresolv -lnsl -ldl -lm -lcrypt -lutil -lpthread -lc libc=/lib/libc-2.3.90.so, so=so, useshrplib=true, libperl=libperl.so gnulibc_version='2.3.90' Dynamic Linking: dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-Wl,-E -Wl,-rpath,/usr/lib/perl5/5.8.7/i386-linux-thread-multi/CORE' cccdlflags='-fPIC', lddlflags='-shared -L/usr/local/lib' Locally applied patches: --- @INC for perl v5.8.7: /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.3/i386-linux-thread-multi /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/5.8.4 /usr/lib/perl5/site_perl/5.8.3 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi /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/5.8.4 /usr/lib/perl5/vendor_perl/5.8.3 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.7/i386-linux-thread-multi /usr/lib/perl5/5.8.7 . --- Environment for perl v5.8.7: HOME=/home/boston/jvdias LANG=en_US.UTF-8 LANGUAGE (unset) LD_LIBRARY_PATH (unset) LOGDIR (unset) PATH=/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/usr/games:/home/boston/jvdias/bin PERL_BADLANG (unset) SHELL=/bin/bash From jvdias at redhat.com Tue Nov 1 23:21:25 2005 From: jvdias at redhat.com (Jason Vas Dias) Date: Tue, 1 Nov 2005 18:21:25 -0500 Subject: [PATCH] h2ph inc_dirs() fails to prepend gcc include search path, resulting in missing C standard headers on Linux Message-ID: <200511011821.26000.jvdias@redhat.com> To: perlbug at perl.org Subject: h2ph inc_dirs fails to prepend gcc include search path, resulting in missing C standard headers on Linux Reply-To: jvdias at redhat.com Message-Id: <5.8.7_3660_1130885631 at jvdias> This is a bug report for perl from jvdias at redhat.com, generated with the help of perlbug 1.35 running under perl v5.8.7. ----------------------------------------------------------------- [Please enter your report here] When building perl-5.8.7 on Linux, the standard C headers fail to be converted into perl headers, resulting in missing include dependencies. The C standard headers, such as : stddef.h syslimits.h stdarg.h float.h stdbool.h fail to be converted into perl headers (.ph files) during a build and install of perl-5.8.7 . Many system headers include these headers, so many system headers are made unusable with perl because of this problem. This is because h2ph's inc_dirs() does not find the string 'Reading specs from' in gcc -v's output, when the gcc version is >= 4. My gcc's -v option emits: $ gcc -v Using built-in specs. Target: i386-redhat-linux Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-libgcj-multifile --enable-languages=c,c++,objc,java,f95,ada --enable-java-awt=gtk --with-java-home=/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre --host=i386-redhat-linux Thread model: posix gcc version 4.0.1 20050727 (Red Hat 4.0.1-5) $ gcc 4 understands the '-print-search-dirs' option: $ gcc -print-search-dirs install: /usr/lib/gcc/i386-redhat-linux/4.0.1/ ... Here's a patch which corrects h2ph.PL's inc_dirs() to pick up gcc4's built-in header include path: --- --- perl-5.8.7/utils/h2ph.PL.bz172236 2005-04-04 17:47:17.000000000 -0400 +++ perl-5.8.7/utils/h2ph.PL 2005-11-01 17:42:36.000000000 -0500 @@ -734,9 +734,15 @@ # non-GCC?) C compilers, but gcc uses an additional include directory. sub inc_dirs { - my $from_gcc = `$Config{cc} -v 2>&1`; - $from_gcc =~ s:^Reading specs from (.*?)/specs\b.*:$1/include:s; - + my $from_gcc = `LC_ALL=C $Config{cc} -v 2>&1`; + if( !( $from_gcc =~ s:^Reading specs from (.*?)/specs\b.*:$1/include:s ) ) + { # gcc-4+ : + $from_gcc = `LC_ALL=C $Config{cc} -print-search-dirs 2>&1`; + if ( !($from_gcc =~ s/^install:\s*([^\s]+[^\s\/])([\s\/]*).*$/$1\/include/s) ) + { + $from_gcc = ''; + }; + }; length($from_gcc) ? ($from_gcc, $Config{usrinc}) : ($Config{usrinc}); } --- [Please do not change anything below this line] ----------------------------------------------------------------- --- Flags: category=core severity=low --- This perlbug was built using Perl v5.8.7 in the Red Hat build system. It is being executed now by Perl v5.8.7 - Tue Oct 25 19:39:19 EDT 2005. Site configuration information for perl v5.8.7: Configured by Red Hat, Inc. at Tue Oct 25 19:39:19 EDT 2005. Summary of my perl5 (revision 5 version 8 subversion 7) configuration: Platform: osname=linux, osvers=2.6.13-1.1624_fc5, archname=i386-linux-thread-multi uname='linux jvdias 2.6.13-1.1624_fc5 #1 mon oct 24 01:16:31 edt 2005 i686 i686 i386 gnulinux ' config_args='-des -Doptimize=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=pentium4 -fasynchronous-unwind-tables -Dversion=5.8.7 -Dmyhostname=localhost -Dperladmin=root at localhost -Dcc=gcc -Dcf_by=Red Hat, Inc. -Dinstallprefix=/usr -Dprefix=/usr -Darchname=i386-linux -Dvendorprefix=/usr -Dsiteprefix=/usr -Duseshrplib -Dusethreads -Duseithreads -Duselargefiles -Dd_dosuid -Dd_semctl_semun -Di_db -Ui_ndbm -Di_gdbm -Di_shadow -Di_syslog -Dman3ext=3pm -Duseperlio -Dinstallusrbinperl=n -Ubincompat5005 -Uversiononly -Dpager=/usr/bin/less -isr -Dd_gethostent_r_proto -Ud_endhostent_r_proto -Ud_sethostent_r_proto -Ud_endprotoent_r_proto -Ud_setprotoent_r_proto -Ud_endservent_r_proto -Ud_setservent_r_proto -Dinc_version_list=5.8.6 5.8.5 5.8.4 5.8.3 -Dscriptdir=/usr/bin' hint=recommended, useposix=true, d_sigaction=define usethreads=define use5005threads=undef useithreads=define usemultiplicity=define useperlio=define d_sfio=undef uselargefiles=define usesocks=undef use64bitint=undef use64bitall=undef uselongdouble=undef usemymalloc=n, bincompat5005=undef Compiler: cc='gcc', ccflags ='-D_REENTRANT -D_GNU_SOURCE -DDEBUGGING -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm', optimize='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=pentium4 -fasynchronous-unwind-tables', cppflags='-D_REENTRANT -D_GNU_SOURCE -DDEBUGGING -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/include/gdbm' ccversion='', gccversion='4.0.2 20051007 (Red Hat 4.0.2-3)', gccosandvers='' intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=1234 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12 ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8 alignbytes=4, prototype=define Linker and Libraries: ld='gcc', ldflags =' -L/usr/local/lib' libpth=/usr/local/lib /lib /usr/lib libs=-lresolv -lnsl -lgdbm -ldb -ldl -lm -lcrypt -lutil -lpthread -lc perllibs=-lresolv -lnsl -ldl -lm -lcrypt -lutil -lpthread -lc libc=/lib/libc-2.3.90.so, so=so, useshrplib=true, libperl=libperl.so gnulibc_version='2.3.90' Dynamic Linking: dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-Wl,-E -Wl,-rpath,/usr/lib/perl5/5.8.7/i386-linux-thread-multi/CORE' cccdlflags='-fPIC', lddlflags='-shared -L/usr/local/lib' Locally applied patches: --- @INC for perl v5.8.7: /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.3/i386-linux-thread-multi /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/5.8.4 /usr/lib/perl5/site_perl/5.8.3 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi /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/5.8.4 /usr/lib/perl5/vendor_perl/5.8.3 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.7/i386-linux-thread-multi /usr/lib/perl5/5.8.7 . --- Environment for perl v5.8.7: HOME=/home/boston/jvdias LANG=en_US.UTF-8 LANGUAGE (unset) LD_LIBRARY_PATH (unset) LOGDIR (unset) PATH=/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/usr/games:/home/boston/jvdias/bin PERL_BADLANG (unset) SHELL=/bin/bash From bugzilla at redhat.com Tue Nov 1 23:23:40 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 1 Nov 2005 18:23:40 -0500 Subject: [Bug 172236] missing C standard headers In-Reply-To: Message-ID: <200511012323.jA1NNeIn003342@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: missing C standard headers https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172236 jvdias at redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |MODIFIED ------- Additional Comments From jvdias at redhat.com 2005-11-01 18:23 EST ------- This bug is now fixed with perl-5.8.7-0.7.fc5+ (Rawhide) . Upstream perl bug 37582 has been raised on this issue, with the patch. http://rt.perl.org/rt3/Ticket/Display.html?id=37582 -- 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. From bugzilla at redhat.com Wed Nov 2 00:00:27 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 1 Nov 2005 19:00:27 -0500 Subject: [Bug 172153] /etc/mail is not an ideal place for spamassasin config files In-Reply-To: Message-ID: <200511020000.jA200RVO011275@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: /etc/mail is not an ideal place for spamassasin config files https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172153 ------- Additional Comments From jm at jmason.org 2005-11-01 19:00 EST ------- at this stage, we're (upstream) pretty stuck with /etc/mail, unless someone can present a compelling reason; having to check both /etc/mail/spamassassin and /etc/spamassassin feels a little kludgy. If you'd like, open an upstream bug and see what the other committers say... -- 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. From bugzilla at redhat.com Wed Nov 2 00:26:07 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 1 Nov 2005 19:26:07 -0500 Subject: [Bug 168373] perl is compiled without 64bit int on i386 In-Reply-To: Message-ID: <200511020026.jA20Q7Gb015974@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: perl is compiled without 64bit int on i386 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=168373 jvdias at redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |CLOSED Resolution| |WONTFIX ------- Additional Comments From jvdias at redhat.com 2005-11-01 19:25 EST ------- When you are running perl on a 64-bit machine, and have installed the 64-bit architecture version, ie. on x86_64, perl-*.x86_64.rpm, not perl-*i386.rpm, then you do get 64-bit integers by default: e.g. on an x86_64, with perl*.x86_64 $ rpm -q perl --qf '%{ARCH}\n' x86_64 $ perl -e 'print ( 1 <<32, "\n" );' 4294967296 The 64bitint feature is meant to provide support for 64bit integers on 32 bit platforms, and has been associated with severe problems in the past. Using 64-bit integer emulation on 32-bit platforms would incur a heavy performance penalty for ALL applications, even those that make no use of 33+bit integers. It is also made redundant by use of the 'use bigint' pragma, which you can specify on the command line with -Mbigint, or in the environment of for your perl scripts on 32-bit platforms with the environment variable setting PERL5OPT=-Mbigint e.g, on an i386 machine: $ rpm -q perl --qf '%{ARCH}\n' i386 $ perl -e 'print ( 1<<32, "\n");' 1 $ PERL5OPT=-Mbigint perl -e 'print ( 1<<32, "\n");' 4294967296 Since there are many workarounds, and we don't want to incur a performance penalty for all perl scripts, and there have been problems with -D64bitint, I don't think we should enable this feature unless absolutely required - sorry. -- 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. From bugzilla at redhat.com Wed Nov 2 01:29:34 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 1 Nov 2005 20:29:34 -0500 Subject: [Bug 166478] glibc or perl incorrect locale LC_CTYPE data In-Reply-To: Message-ID: <200511020129.jA21TYgN026551@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: glibc or perl incorrect locale LC_CTYPE data https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=166478 ------- Additional Comments From jvdias at redhat.com 2005-11-01 20:29 EST ------- One has to carefully analyse the perl man-pages to find out what is going on here. I don't particularly agree with the way the upstream perl maintainers have done this, but this is not a bug - it is the way perl is meant to behave. The point is that /\w/ matches any ASCII word char, and /\W/ matches any ASCII non-word char. To match a UTF-8 word character, you have to use \p{IsWord} . The \w wildcard is a synonym for the POSIX character class [:word:]. So this version of your program : --- #!/usr/bin/perl -w -C use strict; use utf8; use locale; use Encode qw(decode); my $str = decode('utf-8', "\xc3\x81\xc4\x8c"); # U+00C1 "A with acute", U+010C "C with caron" (encoded in UTF-8) print 'Is UTF-8:',utf8::is_utf8($str), ' is word:', $str =~ /^\w+$/,' is UTF-8 word:', $str =~ /^\p{IsWord}+$/, ' str:',$str, "\n"; -- 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. From bugzilla at redhat.com Wed Nov 2 02:10:46 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 1 Nov 2005 21:10:46 -0500 Subject: [Bug 172153] /etc/mail is not an ideal place for spamassasin config files In-Reply-To: Message-ID: <200511020210.jA22AkAJ000836@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: /etc/mail is not an ideal place for spamassasin config files https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172153 ------- Additional Comments From wtogami at redhat.com 2005-11-01 21:10 EST ------- Indeed checking both locations would be kludgy. I also worry a little about all the past documentation pointing at /etc/mail and confusion it would cause to have new documentation pointing at the different location. It is easier for the users to keep it consistent if it is technologically possible. -- 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. From bugzilla at redhat.com Wed Nov 2 02:15:10 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 1 Nov 2005 21:15:10 -0500 Subject: [Bug 172153] /etc/mail is not an ideal place for spamassasin config files In-Reply-To: Message-ID: <200511020215.jA22FAd5001461@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: /etc/mail is not an ideal place for spamassasin config files https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172153 ------- Additional Comments From felicity at kluge.net 2005-11-01 21:15 EST ------- Apparently neither of my two last responses got through, so here's a short version. SA already checks multiple locations for configs, including /etc/spamassassin. However, the installer and such do /etc/mail/ spamassassin by default. -- 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. From bugzilla at redhat.com Wed Nov 2 10:30:21 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 2 Nov 2005 05:30:21 -0500 Subject: [Bug 166478] glibc or perl incorrect locale LC_CTYPE data In-Reply-To: Message-ID: <200511021030.jA2AUL0W017480@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: glibc or perl incorrect locale LC_CTYPE data https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=166478 ------- Additional Comments From kas at informatics.muni.cz 2005-11-02 05:30 EST ------- Well, then tell me why the same Perl works on FreeBSD. Is it that Linux UTF-8 locales does not consider U+00C1 to be a character, while U+10C is a character? Your statement that "\w matches any ASCII word char" is not true. See perlre(1): [...] If "use locale" is in effect, the list of alpha- betic characters generated by "\w" is taken from the current locale. See perllocale. [...] So the question is why Perl (or libc) in FreeBSD does consider U+00C1 to be a character under the UTF-8 locale, while the same perl with glibc on Linux doesn't. -- 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. From bugzilla at redhat.com Wed Nov 2 16:45:39 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 2 Nov 2005 11:45:39 -0500 Subject: [Bug 166478] glibc or perl incorrect locale LC_CTYPE data In-Reply-To: Message-ID: <200511021645.jA2Gjd2b009918@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: glibc or perl incorrect locale LC_CTYPE data https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=166478 jvdias at redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |NOTABUG ------- Additional Comments From jvdias at redhat.com 2005-11-02 11:45 EST ------- Sorry I submitted my previous comment before finishing it - then my machine rebooted (that's another story). As I was saying in Comment #2 : This version of your program shows the issue: --- #!/usr/bin/perl -w -C use strict; use utf8; use locale; use Encode qw(decode); my $str = decode('utf-8', "\xc3\x81\xc4\x8c"); # U+00C1 "A with acute", U+010C "C with caron" (encoded in UTF-8) print 'Is UTF-8:',utf8::is_utf8($str), ' is word:', $str =~ /^\w+$/, ' is UTF-8 word: ', $str =~ /^\p{IsWord}+$/, ' str:',$str, "\n"; --- With the "en_US.UTF-8" locale in effect ( the default on Red Hat systems ) this prints: $ ./test.pl Is UTF-8:1 is word: is posix word: 1 is UTF-8 word: 1 str:?? The point is that \p{IsWord} or [[:word:]] matches UTF-8 word characters, while \w / \W do not. As the perlre man-page states: " The following equivalences to Unicode \p{} constructs and equivalent backslash character classes (if available), will hold: [:...:] \p{...} backslash ... word IsWord ... " ie. the [:word:] / \p{IsWord} classes are NOT equivalent to \w . As I said, I don't particularly agree with the way the upstream perl developers have done this, but this is intended behaviour. RE: your comment #3: > Your statement that "\w matches any ASCII word char" is not true. > See perlre(1): > [...] If "use locale" is in effect, the list of alphabetic characters > generated by "\w" is taken from the current locale. Yes, that's alphabetic characters, not unicode sequences. To match unicode sequences in the word class, you must use \p{IsWord} or [:word:] . > So the question is why Perl (or libc) in FreeBSD does consider U+00C1 to be a > character under the UTF-8 locale, while the same perl with glibc on Linux > doesn't. Possibly because the default locale for Red Hat systems is UTF-8 enabled ? -- 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. From bugzilla at redhat.com Wed Nov 2 18:43:18 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 2 Nov 2005 13:43:18 -0500 Subject: [Bug 172316] [PATCH] Perl dies when encoding certain UTF-8 strings to other encodings In-Reply-To: Message-ID: <200511021843.jA2IhIYQ010263@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: [PATCH] Perl dies when encoding certain UTF-8 strings to other encodings https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172316 jvdias at redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |MODIFIED CC| |fedora-perl-devel- | |list at redhat.com ------- Additional Comments From jvdias at redhat.com 2005-11-02 13:43 EST ------- This bug affects FC-4's Encode version 2.8, NOT FC-5 / Rawhide's Encode version 2.10 . It is fixed in perl-5.8.6-16 . -- 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. From bugzilla at redhat.com Wed Nov 2 18:44:40 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 2 Nov 2005 13:44:40 -0500 Subject: [Bug 171111] (libperl) could not run system-config-printer In-Reply-To: Message-ID: <200511021844.jA2IieGd010728@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: (libperl) could not run system-config-printer https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=171111 jvdias at redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- OtherBugsDependingO| |172317 nThis| | -- 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. From bugzilla at redhat.com Wed Nov 2 18:53:38 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 2 Nov 2005 13:53:38 -0500 Subject: [Bug 172317] (libperl) could not run system-config-printer In-Reply-To: Message-ID: <200511021853.jA2Irc6F012919@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: (libperl) could not run system-config-printer https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172317 jvdias at redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |MODIFIED ------- Additional Comments From jvdias at redhat.com 2005-11-02 13:53 EST ------- fixed with perl-5.8.0-90.2 in RHEL-3 . -- 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. From bugzilla at redhat.com Wed Nov 2 19:10:20 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 2 Nov 2005 14:10:20 -0500 Subject: [Bug 140597] [PATCH] "use vX.X.X" causes problems with perl.req In-Reply-To: Message-ID: <200511021910.jA2JAKxF016462@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: [PATCH] "use vX.X.X" causes problems with perl.req https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=140597 n3npq at mac.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |UPSTREAM ------- Additional Comments From n3npq at mac.com 2005-11-02 14:09 EST ------- Checked into rpm CVS, should be in rpm-4.4.3-0.32 when built. -- 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. From bugzilla at redhat.com Wed Nov 2 21:42:16 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 2 Nov 2005 16:42:16 -0500 Subject: [Bug 128879] Break perl-libxml-enno into component CPAN modules In-Reply-To: Message-ID: <200511022142.jA2LgGk2025474@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Break perl-libxml-enno into component CPAN modules https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=128879 ville.skytta at iki.fi changed: What |Removed |Added ---------------------------------------------------------------------------- BugsThisDependsOn| |172330 -- 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. From bugzilla at redhat.com Wed Nov 2 21:43:14 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 2 Nov 2005 16:43:14 -0500 Subject: [Bug 128879] Break perl-libxml-enno into component CPAN modules In-Reply-To: Message-ID: <200511022143.jA2LhEDg025878@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Break perl-libxml-enno into component CPAN modules https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=128879 ville.skytta at iki.fi changed: What |Removed |Added ---------------------------------------------------------------------------- BugsThisDependsOn| |172332 -- 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. From bugzilla at redhat.com Wed Nov 2 21:45:00 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 2 Nov 2005 16:45:00 -0500 Subject: [Bug 128879] Break perl-libxml-enno into component CPAN modules In-Reply-To: Message-ID: <200511022145.jA2Lj0oW026518@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Break perl-libxml-enno into component CPAN modules https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=128879 ville.skytta at iki.fi changed: What |Removed |Added ---------------------------------------------------------------------------- BugsThisDependsOn| |172331 -- 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. From bugzilla at redhat.com Wed Nov 2 21:55:32 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 2 Nov 2005 16:55:32 -0500 Subject: [Bug 172336] New: getgrnam() crashes with "Out of memory" if /etc/group contains long lines Message-ID: 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=172336 Summary: getgrnam() crashes with "Out of memory" if /etc/group contains long lines Product: Fedora Core Version: fc4 Platform: i386 URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=227621 OS/Version: Linux Status: NEW Severity: security Priority: normal Component: perl AssignedTo: jvdias at redhat.com ReportedBy: jvdias at redhat.com QAContact: dkl at redhat.com CC: fedora-perl-devel-list at redhat.com,prockai at redhat.com +++ This bug was initially created as a clone of Bug #163958 +++ >From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050720 Firefox/1.0.6 Description of problem: This bug has been fixed in Debian and in newest Perl. I'm just wondering does this concern RHEL 3 too, because we are rather close having "too much" users in one group and I would rather see this bug fixed before that we are going to have problems. * Fix test of reenterant function return values which was causing perl to malloc itself to death if ERANGE was encountered before ENOENT (such as a long line in /etc/group; closes: #227621). Version-Release number of selected component (if applicable): How reproducible: Didn't try Additional info: -- Additional comment from jvdias at redhat.com on 2005-11-02 16:23 EST -- This is PERL bug 37056, fixed with patch 25084 in bleadperl (5.9.x): ( http://rt.perl.org/rt3/Ticket/Display.html?id=37056 ) Subject: getgrent fails if a line in /etc/groups gets too long Date: Fri, 02 Sep 2005 15:53:08 +0200 To: perlbug at perl.org From: Michiel Blotwijk This is a bug report for perl from michiel at altiplano.be, generated with the help of perlbug 1.35 running under perl v5.8.5. ----------------------------------------------------------------- [Please enter your report here] The function getgrent throws an error if a line in /etc/groups gets too long (> 3000 characters). This error can be reproduced as follows: 1/ Manually add a large number of users to a group in /etc/group. It doesn't really matter if these are real users or not, as long as the line exceeds 3000 characters. 2/ perl -e 'use User::grent; while (my $gr = getgrent() ) { print $gr->name."\n"; }' This will return an "Out of memory!" message. This thread seems to be related: http://lists.debian.org/debian-security/2005/06/msg00041.html Originally reported at Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=227621 As said in the Debian bug report: From: "Steinar H. Gunderson" To: Peter Pal?ch Cc: control at bugs.debian.org, 227621 at bugs.debian.org, debian-security at lists.debian.org Subject: Re: perl: getgrnam() crashes with "Out of memory" if /etc/group contains long lines Date: Fri, 10 Jun 2005 15:03:02 +0200 It's about the same bug in perl as it was in glibc. reentr.pl line 698 reads: $call = qq[((PL_REENTRANT_RETINT = $call)$test ? $true : (((PL_REENTRANT_RETINT == ERANGE) || (errno == ERANGE)) ? ($seenm{$func}{$seenr{$func}})Perl_reentrant_retry("$func"$rv) : 0))]; The problem here is "errno == ERANGE". If, at any time, there's a line longer than the initial buffer, getgrent() (or any in the same family) will get ERANGE back (and errno will be set to ERANGE). However, this is never reset. Thus, when getgrent_r() hits EOF, it returns ENOENT, _but errno is still ERANGE_. Perl figures the buffer was too small, doubles it and tries again, but still gets ENOENT, of course (and errno is still ERANGE). This goes on forever and ever until you run out of memory (which happens quite fast). The solution is simply to remove "errno == ERANGE" AFAICS; getgrent_r() does not define what happens to errno, and the return message will always be ERANGE if the buffer is too small. I'm a bit tempted to tag this "security"; if a user can (say) change his or her own GECOS field to make it long enough, Perl programs using getpwent() will crash, for instance. I can't find any direct way to exploit it (chfn limits the length of the fields, for instance), but I'm still slightly concerned over the possibilities of a DoS; Cc-ing debian-security. /* Steinar */ I agree this bug has security implications . This problem affects all {get,set}* nss perl wrapper functions, not only getgrent . This problem affects all previous releases of PERL in all current Red Hat releases. The patch is very straightforward - replace all occurences of ((PL_REENTRANT_RETINT == ERANGE) || (errno == ERANGE)) with (PL_REENTRANT_RETINT == ERANGE) in reentr.inc and reentr.pl. This bug is now being fixed in these perl versions: Rawhide / FC-5 : perl-5.8.7-0.7.fc5 FC-4 : perl-5.8.6-16 RHEL-4 : perl-5.8.5-17.RHEL4 RHEL-3 : perl-5.8.0-90.2 -- 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. From bugzilla at redhat.com Wed Nov 2 21:55:57 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 2 Nov 2005 16:55:57 -0500 Subject: [Bug 163958] getgrnam() crashes with "Out of memory" if /etc/group contains long lines In-Reply-To: Message-ID: <200511022155.jA2Ltvoq029412@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: getgrnam() crashes with "Out of memory" if /etc/group contains long lines https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=163958 jvdias at redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- OtherBugsDependingO| |172336 nThis| | -- 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. From bugzilla at redhat.com Wed Nov 2 22:39:56 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 2 Nov 2005 17:39:56 -0500 Subject: [Bug 172336] getgrnam() crashes with "Out of memory" if /etc/group contains long lines In-Reply-To: Message-ID: <200511022239.jA2Mdu9v007062@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: getgrnam() crashes with "Out of memory" if /etc/group contains long lines https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172336 Bug 172336 depends on bug 163958, which changed state. Bug 163958 Summary: getgrnam() crashes with "Out of memory" if /etc/group contains long lines https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=163958 What |Old Value |New Value ---------------------------------------------------------------------------- Resolution| |CURRENTRELEASE Status|MODIFIED |CLOSED -- 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. From bugzilla at redhat.com Wed Nov 2 22:43:14 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 2 Nov 2005 17:43:14 -0500 Subject: [Bug 172336] getgrnam() crashes with "Out of memory" if /etc/group contains long lines In-Reply-To: Message-ID: <200511022243.jA2MhELZ007905@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: getgrnam() crashes with "Out of memory" if /etc/group contains long lines https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172336 jvdias at redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |MODIFIED ------- Additional Comments From jvdias at redhat.com 2005-11-02 17:42 EST ------- This problem is fixed in : FC-5 : perl-5.8.7-0.7.fc5 FC-4 : perl-5.8.6-16 -- 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. From bugzilla at redhat.com Thu Nov 3 00:08:23 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 2 Nov 2005 19:08:23 -0500 Subject: [Bug 161331] perl sys::syslog formatting bug In-Reply-To: Message-ID: <200511030008.jA308N7o026421@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: perl sys::syslog formatting bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=161331 jvdias at redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution| |NOTABUG ------- Additional Comments From jvdias at redhat.com 2005-11-02 19:08 EST ------- Yes, this happens in all currently shipped Red Hat perl versions . I'm not sure this is really a bug - the 'man Sys::Syslog' man-page states: " openlog $ident, $logopt, $facility ... syslog $priority, $format, @args ... If you didn?t use openlog() before using syslog(), syslog will try to guess the $ident by extracting the shortest prefix of $format that ends in a ":". " So what is happening is that since you specified no 'ident' for openlog, Syslog.pm tries to extract the ident from the message, and thinks it is ':'. The "ident" is then used to prefix the message, ie. is the message 'tag', followed by ": " . The 'tag' field is not optional, as shown by the prototype of the c openlog call: void openlog(const char *ident, int option, int facility); The string pointed to by ident is prepended to every message, and is typically set to the program name, and if the LOG_PID option is supplied, it will be suffixed with the process id in brackets, to form the usual syslog tag of 'program[pid]:' . There are several ways to workaround this situation : 1. Provide an "ident" to openlog - eg., in your example: $ perl -e 'use Sys::Syslog; openlog $0, "", ""; syslog "info", "::a"; closelog;' This would emit the syslog line: -e: ::a Usually $0 will be the name of the script, which is '-e' for perl command line expressions . 2. Use a proper printf format as the second argument to syslog: $ perl -e 'use Sys::Syslog; syslog "info", "%s", "::a";' logs the line: : ::a The openlog is optional, meaning that syslog will open a log socket for you. Unless Sys::Syslog were to arbitrarily disallow an 'ident' value of ':', (which could be an executable file name), it cannot fix this bug and still provide the feature of embedding the ident tag in the message. So this is not a bug - use one of the workarounds given above. -- 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. From bugzilla at redhat.com Thu Nov 3 06:25:29 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 3 Nov 2005 01:25:29 -0500 Subject: [Bug 147465] XML::XQL not taint-safe by default and warnings if $ENV{TERM} unset. In-Reply-To: Message-ID: <200511030625.jA36PTg8002411@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: XML::XQL not taint-safe by default and warnings if $ENV{TERM} unset. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=147465 ------- Additional Comments From ville.skytta at iki.fi 2005-11-03 01:25 EST ------- FYI, I've fixed these issues in the upcoming FE5 perl-XML-XQL package (bug 172332). -- 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. From bugzilla at redhat.com Thu Nov 3 16:05:01 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 3 Nov 2005 11:05:01 -0500 Subject: [Bug 167797] perl-DBD-Pg package doesn't Provide: perl(DBD::Pg) In-Reply-To: Message-ID: <200511031605.jA3G5116029038@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: perl-DBD-Pg package doesn't Provide: perl(DBD::Pg) https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=167797 laroche at redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution| |RAWHIDE ------- Additional Comments From laroche at redhat.com 2005-11-03 11:04 EST ------- I've added a Provides: for this, should show up tomorrow in the FC-development release. regards, Florian La Roche -- 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. From bugzilla at redhat.com Thu Nov 3 16:13:55 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 3 Nov 2005 11:13:55 -0500 Subject: [Bug 167797] perl-DBD-Pg package doesn't Provide: perl(DBD::Pg) In-Reply-To: Message-ID: <200511031613.jA3GDtCa031090@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: perl-DBD-Pg package doesn't Provide: perl(DBD::Pg) https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=167797 wtogami at redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Resolution|RAWHIDE | ------- Additional Comments From wtogami at redhat.com 2005-11-03 11:13 EST ------- Ville, to clarify should we add the patch or a virtual provides? -- 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. From bugzilla at redhat.com Thu Nov 3 16:15:43 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 3 Nov 2005 11:15:43 -0500 Subject: [Bug 167797] perl-DBD-Pg package doesn't Provide: perl(DBD::Pg) In-Reply-To: Message-ID: <200511031615.jA3GFhUA031581@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: perl-DBD-Pg package doesn't Provide: perl(DBD::Pg) https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=167797 wtogami at redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- OtherBugsDependingO| |171491 nThis| | -- 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. From bugzilla at redhat.com Thu Nov 3 16:17:16 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 3 Nov 2005 11:17:16 -0500 Subject: [Bug 128879] Break perl-libxml-enno into component CPAN modules In-Reply-To: Message-ID: <200511031617.jA3GHGwq031948@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Break perl-libxml-enno into component CPAN modules https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=128879 Bug 128879 depends on bug 172330, which changed state. Bug 172330 Summary: Review Request: perl-XML-RegExp https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172330 What |Old Value |New Value ---------------------------------------------------------------------------- Resolution| |NEXTRELEASE Status|NEW |CLOSED -- 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. From bugzilla at redhat.com Thu Nov 3 16:22:30 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 3 Nov 2005 11:22:30 -0500 Subject: [Bug 147957] DBD-Pg core dumps when doing a select from a variable length array In-Reply-To: Message-ID: <200511031622.jA3GMUx4000670@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: DBD-Pg core dumps when doing a select from a variable length array https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=147957 laroche at redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |RAWHIDE ------- Additional Comments From laroche at redhat.com 2005-11-03 11:22 EST ------- Ok, this should at least be fixed now in the FC-development tree. Thanks, Florian La Roche -- 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. From bugzilla at redhat.com Thu Nov 3 16:45:23 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 3 Nov 2005 11:45:23 -0500 Subject: [Bug 158733] perl(Inline) duplication In-Reply-To: Message-ID: <200511031645.jA3GjNLk006388@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: perl(Inline) duplication https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=158733 laroche at redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |CLOSED Resolution| |RAWHIDE ------- Additional Comments From laroche at redhat.com 2005-11-03 11:45 EST ------- This is fixed with the current packages in FC-development. Thanks, Florian La Roche -- 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. From bugzilla at redhat.com Thu Nov 3 17:03:00 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 3 Nov 2005 12:03:00 -0500 Subject: [Bug 167797] perl-DBD-Pg package doesn't Provide: perl(DBD::Pg) In-Reply-To: Message-ID: <200511031703.jA3H30QR010532@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: perl-DBD-Pg package doesn't Provide: perl(DBD::Pg) https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=167797 ------- Additional Comments From ville.skytta at iki.fi 2005-11-03 12:02 EST ------- As long as the package provides correct things, IMO the implementation is a matter of maintainer preference. I would have personally opted for the Provides too. (BTW, I don't see the change from comment 7 in CVS yet. ) -- 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. From bugzilla at redhat.com Thu Nov 3 19:04:44 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 3 Nov 2005 14:04:44 -0500 Subject: [Bug 172396] multi-threaded perl builds use localtime_r which does not call tzset In-Reply-To: Message-ID: <200511031904.jA3J4ijP005888@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: multi-threaded perl builds use localtime_r which does not call tzset https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172396 jvdias at redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|multi-threaded perl builds |multi-threaded perl builds |use localtime_r which does |use localtime_r which does |not call tzset |not call tzset Status|NEW |MODIFIED ------- Additional Comments From jvdias at redhat.com 2005-11-03 14:04 EST ------- This bug is fixed in perl-5.8.7-0.7.fc5 . -- 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. From bugzilla at redhat.com Sat Nov 5 09:42:18 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sat, 5 Nov 2005 04:42:18 -0500 Subject: [Bug 128879] Break perl-libxml-enno into component CPAN modules In-Reply-To: Message-ID: <200511050942.jA59gIh0002898@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Break perl-libxml-enno into component CPAN modules https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=128879 Bug 128879 depends on bug 172331, which changed state. Bug 172331 Summary: Review Request: perl-XML-DOM https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172331 What |Old Value |New Value ---------------------------------------------------------------------------- Resolution| |NEXTRELEASE Status|NEW |CLOSED -- 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. From mpeters at mac.com Sat Nov 5 22:21:26 2005 From: mpeters at mac.com (Michael A. Peters) Date: Sat, 05 Nov 2005 14:21:26 -0800 Subject: perl-File-BOM update Message-ID: <1131229286.2660.26.camel@locolhost.localdomain> I maintain this package in Extras. I am not going to abandon it, but it is the only perl package I maintain. If someone else who does a lot of perl wants to maintain it - feel free to take it. -=- That being said - I'm in the process of updating it to 0.11 (current in Extras is 0.9) 1) I'm inclined to only update it for devel branch because the changes file speaks of a change in behavior for open_bom. I haven't verified that it would impact anything if it was updated for FC3/FC4. 2) The build complains that Readonly is not available. This is a new requirement (0.9 does not need it). Would someone like to package that for Extras? A grep of the Extras owners.list did not turn up a maintainer. I will do it if necessary, but my preference would be for someone else to do it. I would definitely be willing to review the package. My apologies if it is already in core devel branch - I can't boot into rawhide until later tonight. Thanks, Michael From bugzilla at redhat.com Sun Nov 6 07:48:20 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 6 Nov 2005 02:48:20 -0500 Subject: [Bug 167797] perl-DBD-Pg package doesn't Provide: perl(DBD::Pg) In-Reply-To: Message-ID: <200511060748.jA67mKfF006880@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: perl-DBD-Pg package doesn't Provide: perl(DBD::Pg) https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=167797 rc040203 at freenet.de changed: What |Removed |Added ---------------------------------------------------------------------------- OtherBugsDependingO|170384 | nThis| | -- 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. From bugzilla at redhat.com Sun Nov 6 16:16:32 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 6 Nov 2005 11:16:32 -0500 Subject: [Bug 128879] Break perl-libxml-enno into component CPAN modules In-Reply-To: Message-ID: <200511061616.jA6GGWIb012443@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Break perl-libxml-enno into component CPAN modules https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=128879 Bug 128879 depends on bug 172332, which changed state. Bug 172332 Summary: Review Request: perl-XML-XQL https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172332 What |Old Value |New Value ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Resolution| |NEXTRELEASE Status|ASSIGNED |CLOSED -- 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. From bugzilla at redhat.com Sun Nov 6 16:28:34 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 6 Nov 2005 11:28:34 -0500 Subject: [Bug 152535] perl-RPM2 incomplete owned-files list In-Reply-To: Message-ID: <200511061628.jA6GSYOU013235@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: perl-RPM2 incomplete owned-files list https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=152535 ------- Additional Comments From n3npq at mac.com 2005-11-06 11:28 EST ------- This problem is fixed in http://wraptastic.org/pub/rpm-devel/rpm-perl-4.4.3-0.37 and later. -- 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. From bugzilla at redhat.com Mon Nov 7 17:34:57 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 7 Nov 2005 12:34:57 -0500 Subject: [Bug 172587] New: upstream patch #26011: "A surprising segfault" Message-ID: 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=172587 Summary: upstream patch #26011: "A surprising segfault" Product: Fedora Core Version: devel Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: normal Component: perl AssignedTo: jvdias at redhat.com ReportedBy: jvdias at redhat.com QAContact: dkl at redhat.com CC: fedora-perl-devel-list at redhat.com Description of problem: $ ./perl -e 'map print(reverse), ("")x68' Segmentation fault Version-Release number of selected component (if applicable): perl-5.8.7 How reproducible: 100% -- 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. From bugzilla at redhat.com Mon Nov 7 17:39:36 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 7 Nov 2005 12:39:36 -0500 Subject: [Bug 172587] upstream patch #26011: "A surprising segfault" In-Reply-To: Message-ID: <200511071739.jA7HdaJb025125@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: upstream patch #26011: "A surprising segfault" https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172587 ------- Additional Comments From jvdias at redhat.com 2005-11-07 12:39 EST ------- Issue fixed with upstream patches 26009 and 26011: Change 26011 by rgs at marais on 2005/11/05 10:10:09 Subject: Re: A surprising segfault From: SADAHIRO Tomoyuki Date: Nov 5, 2005 5:54 AM Message-Id: <20051105135053.27D7.BQW10602 at nifty.com> Affected files ... ... //depot/perl/pp.c#483 edit ... //depot/perl/pp_sort.c#47 edit ... //depot/perl/pp_sys.c#469 edit Differences ... ==== //depot/perl/pp.c#483 (text) ==== Index: perl/pp.c --- perl/pp.c#482~26004~ Fri Nov 4 13:39:44 2005 +++ perl/pp.c Sat Nov 5 02:10:09 2005 @@ -700,7 +700,7 @@ while (MARK < SP) do_chop(TARG, *++MARK); SP = ORIGMARK; - PUSHTARG; + XPUSHTARG; RETURN; } @@ -718,7 +718,7 @@ while (SP > MARK) count += do_chomp(POPs); - PUSHi(count); + XPUSHi(count); RETURN; } ==== //depot/perl/pp_sort.c#47 (text) ==== Index: perl/pp_sort.c --- perl/pp_sort.c#46~25953~ Wed Nov 2 04:49:54 2005 +++ perl/pp_sort.c Sat Nov 5 02:10:09 2005 @@ -1504,6 +1504,7 @@ if (gimme != G_ARRAY) { SP = MARK; + EXTEND(SP,1); RETPUSHUNDEF; } ==== //depot/perl/pp_sys.c#469 (text) ==== Index: perl/pp_sys.c --- perl/pp_sys.c#468~26000~ Fri Nov 4 12:20:56 2005 +++ perl/pp_sys.c Sat Nov 5 02:10:09 2005 @@ -430,12 +430,16 @@ SV *tmpsv; const char *tmps; STRLEN len; - if (SP - MARK != 1) { + if (SP - MARK > 1) { dTARGET; do_join(TARG, &PL_sv_no, MARK, SP); tmpsv = TARG; SP = MARK + 1; } + else if (SP == MARK) { + tmpsv = &PL_sv_no; + EXTEND(SP, 1); + } else { tmpsv = TOPs; } @@ -3402,7 +3406,7 @@ const I32 value = (I32)apply(PL_op->op_type, MARK, SP); SP = MARK; - PUSHi(value); + XPUSHi(value); RETURN; } @@ -3993,7 +3997,7 @@ if (errno != EAGAIN) { value = -1; SP = ORIGMARK; - PUSHi(value); + XPUSHi(value); if (did_pipes) { PerlLIO_close(pp[0]); PerlLIO_close(pp[1]); @@ -4042,7 +4046,7 @@ STATUS_NATIVE_CHILD_SET(-1); } } - PUSHi(STATUS_CURRENT); + XPUSHi(STATUS_CURRENT); RETURN; } if (did_pipes) { @@ -4088,7 +4092,7 @@ STATUS_NATIVE_CHILD_SET(value); do_execfree(); SP = ORIGMARK; - PUSHi(result ? value : STATUS_CURRENT); + XPUSHi(result ? value : STATUS_CURRENT); #endif /* !FORK or VMS */ RETURN; } @@ -4140,7 +4144,7 @@ } SP = ORIGMARK; - PUSHi(value); + XPUSHi(value); RETURN; } End of Patch. Change 26009 by davem at davem-splatty on 2005/11/05 01:57:23 pp_print didn't extend the stack before pushing its return value Affected files ... ... //depot/perl/pp_hot.c#424 edit Differences ... ==== //depot/perl/pp_hot.c#424 (text) ==== @@ -677,12 +677,12 @@ } } SP = ORIGMARK; - PUSHs(&PL_sv_yes); + XPUSHs(&PL_sv_yes); RETURN; just_say_no: SP = ORIGMARK; - PUSHs(&PL_sv_undef); + XPUSHs(&PL_sv_undef); RETURN; } -- 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. From bugzilla at redhat.com Mon Nov 7 17:41:08 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 7 Nov 2005 12:41:08 -0500 Subject: [Bug 172587] upstream patch #26011: "A surprising segfault" In-Reply-To: Message-ID: <200511071741.jA7Hf8TR025292@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: upstream patch #26011: "A surprising segfault" https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172587 jvdias at redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |MODIFIED ------- Additional Comments From jvdias at redhat.com 2005-11-07 12:41 EST ------- Patches applied in perl-5.8.7-0.7.fc5 . -- 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. From bugzilla at redhat.com Tue Nov 8 08:08:28 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 8 Nov 2005 03:08:28 -0500 Subject: [Bug 172677] Review Request: perl-Readonly In-Reply-To: Message-ID: <200511080808.jA888SGD024672@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: perl-Readonly https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172677 mpeters at mac.com changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Review Request: perl- |Review Request: perl- |Readonly |Readonly CC| |fedora-perl-devel- | |list at redhat.com OtherBugsDependingO| |172676 nThis| | ------- Additional Comments From mpeters at mac.com 2005-11-08 03:08 EST ------- This package has two source files. The perl-Readonly src could produce a noarch rpm, it does not *need* the binary Readonly::XS module - but it benefits from it performance wise - and thus should be made available. Readonly::XS is only of value if Readonly is installed. Rather than building them as separate packages with a noarch perl-Readonly package requiring the binary arch specific perl-Readonly-XS package, I figured it was cleaner to just package both in the same rpm. -- 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. From bugzilla at redhat.com Tue Nov 8 09:58:18 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 8 Nov 2005 04:58:18 -0500 Subject: [Bug 144536] (libperl) could not run system-config-printer In-Reply-To: Message-ID: <200511080958.jA89wIuH002399@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: (libperl) could not run system-config-printer https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=144536 msz at astrouw.edu.pl changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msz at astrouw.edu.pl ------- Additional Comments From msz at astrouw.edu.pl 2005-11-08 04:57 EST ------- Any chance that this bug will be fixed? Having an operating system *release* that can't configure an usb printer is somewhat annoying. Is there any simple workaround other than connecting the printer to the parallel port, configuring, reconnecting to the USB port and then manually changing the device in /etc/cupr/printers.conf ? Michal. -- 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. From bugzilla at redhat.com Tue Nov 8 15:17:03 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 8 Nov 2005 10:17:03 -0500 Subject: [Bug 172677] Review Request: perl-Readonly In-Reply-To: Message-ID: <200511081517.jA8FH364006167@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: perl-Readonly https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172677 ------- Additional Comments From mpeters at mac.com 2005-11-08 10:16 EST ------- Created an attachment (id=120815) --> (https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=120815&action=view) spec file I've attached the spec file as the server where it is hosted seems to be having some timeout issues for some people. -- 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. From bugzilla at redhat.com Tue Nov 8 16:28:05 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 8 Nov 2005 11:28:05 -0500 Subject: [Bug 144536] (libperl) could not run system-config-printer In-Reply-To: Message-ID: <200511081628.jA8GS5Xd016065@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: (libperl) could not run system-config-printer https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=144536 ------- Additional Comments From jvdias at redhat.com 2005-11-08 11:27 EST ------- I'm very sorry for the problems this has caused. I'll be issuing a PERL update for FC-3 by the end of this week. Until this new perl version fixes the core problem, you could fix it yourself as follows, by editing the /usr/share/printconf/conf/printconf_conf.py file, @ line 1459 - change: magic_perl = "perl -e 'ioctl(STDIN,0x84005001,$result);" to: magic_perl="perl -e '$result=chr(0)x1024;ioctl(STDIN,0x84005001,$result);" That will fix the problem with the printconf gui . -- 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. From bugzilla at redhat.com Tue Nov 8 22:19:32 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 8 Nov 2005 17:19:32 -0500 Subject: [Bug 172739] New: Deep recursion in CGI::Carp::warn Message-ID: 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=172739 Summary: Deep recursion in CGI::Carp::warn Product: Fedora Core Version: fc4 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: normal Component: perl AssignedTo: jvdias at redhat.com ReportedBy: jorris at redhat.com QAContact: dkl at redhat.com CC: fedora-perl-devel-list at redhat.com Description of problem: CGI::Carp::Warn experiences deep recursion when hit, followed by a segmentation fault. This can make developing any web applications using CGI::Carp::Warn difficult, as any trivial warning will cause pages of log output followed by a crash. See https://rt.perl.org/rt3/Ticket/Display.html?id=36521 for details and possible patches. Version-Release number of selected component (if applicable): perl-5.8.6-15 How reproducible: Always Steps to Reproduce: Execute script: #!/usr/bin/perl use CGI::Carp qw(fatalsToBrowser); use diagnostics; warn "foo"; Results: Deeply nested warning message followed by segfault. -- 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. From bugzilla at redhat.com Tue Nov 8 22:32:34 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 8 Nov 2005 17:32:34 -0500 Subject: [Bug 157071] Perl doesn't lovercase accented caracters in UTF-8 In-Reply-To: Message-ID: <200511082232.jA8MWY9k029815@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Perl doesn't lovercase accented caracters in UTF-8 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=157071 jvdias at redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |NOTABUG ------- Additional Comments From jvdias at redhat.com 2005-11-08 17:32 EST ------- Yes, I know the perl unicode implementation is far from user-friendly or intuitive - this is an upstream issue that is being addressed - but it does work (just) if used correctly . perl's lc / uc DO work for UTF-8, IF the UTF-8 is properly encoded, AND perl is running in wide-character mode , AND the characters have defined upper/lower case counterparts in your current locale. These examples should expose the issues - I suggest you also read the perlunicode and perllocale man-pages . $ perl -C -e 'use locale; use utf8; use Encode qw(decode); $s=decode(utf8,"\xc5\x99\xc4\x9b"); print uc $s,"\n";' ?? $ perl -C -e 'use locale; use utf8; use Encode qw(decode); $s=decode(utf8,"\xc5\x99\xc4\x9b"); print $s,"\n";' ?? $ perl -e 'use Encode qw(decode); $s=decode(utf8,"\xc5\x99\xc4\x9b"); print $s,"\n";' Wide character in print at -e line 1. ?? $ perl -C -e 'use Encode qw(decode); $s=decode(utf8,"\xc5\x99\xc4\x9b"); print $s,"\n";' ?? $ PERL_UNICODE=31 perl -e 'use Encode qw(decode); $s=decode(utf8,"\xc5\x99\xc4\x9b"); print uc $s,"\n";' ?? $ PERL_UNICODE=31 perl -e 'use Encode qw(decode); $s=decode(utf8,"??"); print lc $s,"\n";' ?? -- 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. From bugzilla at redhat.com Tue Nov 8 23:11:51 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 8 Nov 2005 18:11:51 -0500 Subject: [Bug 172739] Deep recursion in CGI::Carp::warn In-Reply-To: Message-ID: <200511082311.jA8NBpPT001918@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Deep recursion in CGI::Carp::warn https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172739 jvdias at redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- Version|fc4 |devel ------- Additional Comments From jvdias at redhat.com 2005-11-08 18:11 EST ------- Oh dear! Yes, this appears to be an issue with perl-5.8.6-* in FC-4, and with the latest perl-5.8.7 in FC-5/Rawhide. investigating ... -- 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. From bugzilla at redhat.com Tue Nov 8 23:43:58 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 8 Nov 2005 18:43:58 -0500 Subject: [Bug 172739] Deep recursion in CGI::Carp::warn In-Reply-To: Message-ID: <200511082343.jA8NhwsF005817@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Deep recursion in CGI::Carp::warn https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172739 ------- Additional Comments From jvdias at redhat.com 2005-11-08 18:43 EST ------- This only happens in FC-4 and FC-5 with the 'use diagnostics;' - without this, the command completes ok: $ perl -e 'use CGI::Carp; CGI::Carp::warn("foo");' [Tue Nov 8 18:25:03 2005] -e: foo at -e line 1. The 'use CGI::Carp; use diagnostics; CGI::Carp::warn("foo");' works fine with RHEL-3's perl-5.8.0-90.2 and RHEL-4's perl-5.8.5-17.RHEL4 . -- 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. From bugzilla at redhat.com Tue Nov 8 23:49:25 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 8 Nov 2005 18:49:25 -0500 Subject: [Bug 172739] Deep recursion in CGI::Carp::warn In-Reply-To: Message-ID: <200511082349.jA8NnPe1006356@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Deep recursion in CGI::Carp::warn https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172739 ------- Additional Comments From jvdias at redhat.com 2005-11-08 18:49 EST ------- This is upstream perl bug: '#36521: Deep recursion on subroutine "CGI::Carp::warn"' ( http://rt.perl.org/rt3/Ticket/Display.html?id=36521 ) The upstream patch #25160 has been applied to perl-5.8.6-16 (FC-4) and perl-5.8.7-0.7 (FC5) in CVS, and will be released to FC-4 updates and Rawhide shortly . -- 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. From bugzilla at redhat.com Wed Nov 9 02:03:37 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 8 Nov 2005 21:03:37 -0500 Subject: [Bug 145215] garbage after split() In-Reply-To: Message-ID: <200511090203.jA923bsU018237@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: garbage after split() https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145215 jvdias at redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |MODIFIED ------- Additional Comments From jvdias at redhat.com 2005-11-08 21:02 EST ------- We apologize for the long delay in processing this bug report. This bug is fixed with perl-5.8.0-90.2 , which should be in the next RHEL-3 update release. -- 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. From bugzilla at redhat.com Wed Nov 9 03:52:56 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 8 Nov 2005 22:52:56 -0500 Subject: [Bug 172153] /etc/mail is not an ideal place for spamassasin config files In-Reply-To: Message-ID: <200511090352.jA93quAm027621@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: /etc/mail is not an ideal place for spamassasin config files https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172153 ------- Additional Comments From wtogami at redhat.com 2005-11-08 22:52 EST ------- After thinking of this for a while more, I am inclined to leave it as is. This will help to limit difficulties in upgrading from one RH package version to another while keeping everything consistent in configuration. -- 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. From bugzilla at redhat.com Wed Nov 9 17:42:03 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 9 Nov 2005 12:42:03 -0500 Subject: [Bug 161785] spamassassin restart fails - functions bug? In-Reply-To: Message-ID: <200511091742.jA9Hg3WE005651@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: spamassassin restart fails - functions bug? https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=161785 ------- Additional Comments From wtogami at redhat.com 2005-11-09 12:41 EST ------- http://people.redhat.com/wtogami/temp/spamassassin/fc3/ http://people.redhat.com/wtogami/temp/spamassassin/fc4/ Please help me to test this package that will soon go to FC3 and FC4 updates. It is essentially an upstream 3.0.5 release candidate. -- 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. From bugzilla at redhat.com Wed Nov 9 17:42:44 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 9 Nov 2005 12:42:44 -0500 Subject: [Bug 169236] New version of SpamAssassin available (3.1.0) In-Reply-To: Message-ID: <200511091742.jA9HgiJX005755@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: New version of SpamAssassin available (3.1.0) https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169236 ------- Additional Comments From wtogami at redhat.com 2005-11-09 12:42 EST ------- http://people.redhat.com/wtogami/temp/spamassassin/fc3/ http://people.redhat.com/wtogami/temp/spamassassin/fc4/ Please help me to test this package that will soon go to FC3 and FC4 updates. It is essentially an upstream 3.0.5 release candidate. -- 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. From bugzilla at redhat.com Wed Nov 9 18:11:05 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 9 Nov 2005 13:11:05 -0500 Subject: [Bug 136009] MakeMaker::MM_Unix doesn't honor LD_RUN_PATH requirements In-Reply-To: Message-ID: <200511091811.jA9IB51q008902@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: MakeMaker::MM_Unix doesn't honor LD_RUN_PATH requirements https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136009 jvdias at redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |MODIFIED ------- Additional Comments From jvdias at redhat.com 2005-11-09 13:10 EST ------- This is now fixed - MM_Unix uses upstream method of preventing use of empty LD_RUN_PATH while allowing non-empty LD_RUN_PATH to be used. Patch applied in: perl-5.8.7-7 (FC5), perl-5.8.6-16 (FC4), perl-5.8.5-17 (RHEL4), perl-5.8.0-90 (RHEL-3). -- 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. From bugzilla at redhat.com Wed Nov 9 18:52:31 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 9 Nov 2005 13:52:31 -0500 Subject: [Bug 135975] Perl's 'study' function breaks regexp matching In-Reply-To: Message-ID: <200511091852.jA9IqVcQ013196@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Perl's 'study' function breaks regexp matching https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=135975 jvdias at redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |MODIFIED ------- Additional Comments From jvdias at redhat.com 2005-11-09 13:52 EST ------- This bug is similar to an upstream perl bug: '17757: s///g fails when using English & study in 5.8.0' ( http://rt.perl.org/rt3/Ticket/Display.html?id=17757 ) and is fixed by upstream patches 18553 ( replaced by 19210 ). The upstream patch for this issue has been applied and this bug is fixed in the next perl release for RHEL-3 : perl-5.8.0-90.2 . -- 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. From jvdias at redhat.com Wed Nov 9 20:21:33 2005 From: jvdias at redhat.com (Jason Vas Dias) Date: Wed, 9 Nov 2005 15:21:33 -0500 Subject: use of study() with utf8 enabled breaks regexps Message-ID: <200511091521.33973.jvdias@redhat.com> To: perlbug at perl.org Subject: use of study() with utf8 enabled breaks regexps Cc: fedora-perl-devel-list at redhat.com Reply-To: jvdias at redhat.com Message-Id: <5.8.7_481_1131565834 at jvdias> This is a bug report for perl from jvdias at redhat.com, generated with the help of perlbug 1.35 running under perl v5.8.7. ----------------------------------------------------------------- [Please enter your report here] Use of study() with utf8 support enabled breaks perl-5.8.7's regular expressions : OK without UTF: $ echo 'ABDCEFGHIJK' | perl -pe 'study; s/HIJK/1234/;' ABDCEFG1234 $ echo 'ABCDEFGHIJK' | perl -e '$_=<>; study; print /HIJK/,"\n";' 1 FAILS with UTF: $ echo 'ABDCEFGHIJK' | PERL_UNICODE=31 perl -pe 'study; s/HIJK/1234/;' ABDCEFGHIJK $ echo 'ABCDEFGHIJK' | PERL_UNICODE=31 perl -e '$_=<>; study; print /HIJK/,"\n";' (re did not match) Seems to be study() that is the culprit: $ echo 'ABDCEFGHIJK' | PERL_UNICODE=31 perl -pe 's/HIJK/1234/;' ABDCEFG1234 And it is because $_ gets utf8-ness from STDIN: $ echo 'ABDCEFGHIJK' | PERL_UNICODE=63 perl -e '$_=<>; study; print /HIJK/ ? "OK" : "FAIL","\n";' FAIL $ echo 'ABDCEFGHIJK' | perl -e '$_=<>; study; print /HIJK/ ? "OK" : "FAIL","\n";' OK $ echo 'ABDCEFGHIJK' | PERL_UNICODE=63 perl -e '$_=<>; print /HIJK/ ? "OK" : "FAIL","\n";' OK This was in the 'en_US.UTF-8' locale. If I make utf-8 support conditional on locale, the problem goes away for the C locale: $ echo 'ABDCEFGHIJK' | PERL_UNICODE=127 LC_ALL=C perl -e '$_=<>; study; print /HIJK/ ? "OK" : "FAIL","\n";' OK [Please do not change anything below this line] ----------------------------------------------------------------- --- Flags: category=core severity=medium --- This perlbug was built using Perl v5.8.7 in the Red Hat build system. It is being executed now by Perl v5.8.7 - Tue Nov 8 16:24:03 EST 2005. Site configuration information for perl v5.8.7: Configured by Red Hat, Inc. at Tue Nov 8 16:24:03 EST 2005. Summary of my perl5 (revision 5 version 8 subversion 7) configuration: Platform: osname=linux, osvers=2.6.14-1.1655_fc5, archname=i386-linux-thread-multi uname='linux jvdias 2.6.14-1.1655_fc5 #1 tue nov 8 06:55:58 est 2005 i686 i686 i386 gnulinux ' config_args='-des -Doptimize=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=pentium4 -fasynchronous-unwind-tables -Dversion=5.8.7 -Dmyhostname=localhost -Dperladmin=root at localhost -Dcc=gcc -Dcf_by=Red Hat, Inc. -Dinstallprefix=/usr -Dprefix=/usr -Darchname=i386-linux -Dvendorprefix=/usr -Dsiteprefix=/usr -Duseshrplib -Dusethreads -Duseithreads -Duselargefiles -Dd_dosuid -Dd_semctl_semun -Di_db -Ui_ndbm -Di_gdbm -Di_shadow -Di_syslog -Dman3ext=3pm -Duseperlio -Dinstallusrbinperl=n -Ubincompat5005 -Uversiononly -Dpager=/usr/bin/less -isr -Dd_gethostent_r_proto -Ud_endhostent_r_proto -Ud_sethostent_r_proto -Ud_endprotoent_r_proto -Ud_setprotoent_r_proto -Ud_endservent_r_proto -Ud_setservent_r_proto -Dinc_version_list=5.8.6 5.8.5 5.8.4 5.8.3 -Dscriptdir=/usr/bin' hint=recommended, useposix=true, d_sigaction=define usethreads=define use5005threads=undef useithreads=define usemultiplicity=define useperlio=define d_sfio=undef uselargefiles=define usesocks=undef use64bitint=undef use64bitall=undef uselongdouble=undef usemymalloc=n, bincompat5005=undef Compiler: cc='gcc', ccflags ='-D_REENTRANT -D_GNU_SOURCE -DDEBUGGING -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm', optimize='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=pentium4 -fasynchronous-unwind-tables', cppflags='-D_REENTRANT -D_GNU_SOURCE -DDEBUGGING -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/include/gdbm' ccversion='', gccversion='4.0.2 20051007 (Red Hat 4.0.2-3)', gccosandvers='' intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=1234 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12 ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8 alignbytes=4, prototype=define Linker and Libraries: ld='gcc', ldflags =' -L/usr/local/lib' libpth=/usr/local/lib /lib /usr/lib libs=-lresolv -lnsl -lgdbm -ldb -ldl -lm -lcrypt -lutil -lpthread -lc perllibs=-lresolv -lnsl -ldl -lm -lcrypt -lutil -lpthread -lc libc=/lib/libc-2.3.90.so, so=so, useshrplib=true, libperl=libperl.so gnulibc_version='2.3.90' Dynamic Linking: dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-Wl,-E -Wl,-rpath,/usr/lib/perl5/5.8.7/i386-linux-thread-multi/CORE' cccdlflags='-fPIC', lddlflags='-shared -L/usr/local/lib' Locally applied patches: --- @INC for perl v5.8.7: /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.3/i386-linux-thread-multi /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/5.8.4 /usr/lib/perl5/site_perl/5.8.3 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi /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/5.8.4 /usr/lib/perl5/vendor_perl/5.8.3 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.7/i386-linux-thread-multi /usr/lib/perl5/5.8.7 . --- Environment for perl v5.8.7: HOME=/home/boston/jvdias LANG=en_US.UTF-8 LANGUAGE (unset) LD_LIBRARY_PATH (unset) LOGDIR (unset) PATH=/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/usr/games:/home/boston/jvdias/bin PERL_BADLANG (unset) SHELL=/bin/bash From bugzilla at redhat.com Wed Nov 9 20:23:23 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 9 Nov 2005 15:23:23 -0500 Subject: [Bug 135975] Perl's 'study' function breaks regexp matching In-Reply-To: Message-ID: <200511092023.jA9KNNsW023255@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Perl's 'study' function breaks regexp matching https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=135975 ------- Additional Comments From jvdias at redhat.com 2005-11-09 15:23 EST ------- Actually, this is not quite fixed: it is the UTF-8 locale which enables UTF-8 support that makes study() break regexps. This is still a bug with the upstream perl-5.8.7 releases (perl bug 37646 raised). -- 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. From bugzilla at redhat.com Wed Nov 9 20:32:20 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 9 Nov 2005 15:32:20 -0500 Subject: [Bug 172792] New: use of study() with utf8 support enabled breaks regexps Message-ID: 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=172792 Summary: use of study() with utf8 support enabled breaks regexps Product: Fedora Core Version: devel Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: normal Component: perl AssignedTo: jvdias at redhat.com ReportedBy: jvdias at redhat.com QAContact: dkl at redhat.com CC: fedora-perl-devel-list at redhat.com Description of problem: Use of study() with utf8 support enabled breaks perl-5.8.7's regular expressions : OK without UTF: $ echo 'ABDCEFGHIJK' | perl -pe 'study; s/HIJK/1234/;' ABDCEFG1234 $ echo 'ABCDEFGHIJK' | perl -e '$_=<>; study; print /HIJK/,"\n";' 1 FAILS with UTF: $ echo 'ABDCEFGHIJK' | PERL_UNICODE=31 perl -pe 'study; s/HIJK/1234/;' ABDCEFGHIJK $ echo 'ABCDEFGHIJK' | PERL_UNICODE=31 perl -e '$_=<>; study; print /HIJK/,"\n";' (re did not match) Seems to be study() that is the culprit: $ echo 'ABDCEFGHIJK' | PERL_UNICODE=31 perl -pe 's/HIJK/1234/;' ABDCEFG1234 And it is because $_ gets utf8-ness from STDIN: $ echo 'ABDCEFGHIJK' | PERL_UNICODE=63 perl -e '$_=<>; study; print /HIJK/ ? "OK" : "FAIL","\n";' FAIL $ PERL_UNICODE=63 perl -e '$_="ABDCEFGHIJK"; study; print /HIJK/ ? "OK" : "FAIL","\n";' OK This was in the 'en_US.UTF-8' locale. If I make utf-8 support conditional on locale, the problem goes away for the C locale: $ echo 'ABDCEFGHIJK' | PERL_UNICODE=127 LC_ALL=C perl -e '$_=<>; study; print /HIJK/ ? "OK" : "FAIL","\n";' OK Version-Release number of selected component (if applicable): ALL perl versions How reproducible: 100% Additional Information: This is upstream perl bug 37646 ( http://rt.perl.org/rt3/index.html?q=37646 ) -- 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. From bugzilla at redhat.com Wed Nov 9 20:45:12 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 9 Nov 2005 15:45:12 -0500 Subject: [Bug 172792] use of study() with utf8 support enabled breaks regexps In-Reply-To: Message-ID: <200511092045.jA9KjCU1028939@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: use of study() with utf8 support enabled breaks regexps https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172792 jvdias at redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- OtherBugsDependingO| |135975 nThis| | -- 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. From bugzilla at redhat.com Wed Nov 9 20:45:06 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 9 Nov 2005 15:45:06 -0500 Subject: [Bug 135975] Perl's 'study' function breaks regexp matching In-Reply-To: Message-ID: <200511092045.jA9Kj5wP028759@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Perl's 'study' function breaks regexp matching https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=135975 jvdias at redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|MODIFIED |ASSIGNED BugsThisDependsOn| |172792 ------- Additional Comments From jvdias at redhat.com 2005-11-09 15:45 EST ------- While the fix partially fixed the problem, this bug is still a problem if UTF-8 support is enabled, which it is by default since the default locale is en_US.UTF-8. Workaround: run your perl scripts with 'LC_ALL=C' . -- 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. From bugzilla at redhat.com Wed Nov 9 21:40:12 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 9 Nov 2005 16:40:12 -0500 Subject: [Bug 128879] Break perl-libxml-enno into component CPAN modules In-Reply-To: Message-ID: <200511092140.jA9LeCjf010684@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Break perl-libxml-enno into component CPAN modules https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=128879 ville.skytta at iki.fi changed: What |Removed |Added ---------------------------------------------------------------------------- OtherBugsDependingO|170716 | nThis| | -- 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. From bugzilla at redhat.com Thu Nov 10 14:50:31 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 10 Nov 2005 09:50:31 -0500 Subject: [Bug 161785] spamassassin restart fails - functions bug? In-Reply-To: Message-ID: <200511101450.jAAEoVxj006644@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: spamassassin restart fails - functions bug? https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=161785 ------- Additional Comments From john.horne at plymouth.ac.uk 2005-11-10 09:50 EST ------- Re comment 8: I have installed onto one of our FC4 mailhubs spamassassin-3.0.4-2.fc4 from the fedora-updates repo. This seems to work fine; restarting spamassassin repeatedly using 'service spamassassin restart' worked every time. Previously this would have failed pretty much immediately. Many thanks. John. -- 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. From wtogami at redhat.com Thu Nov 10 16:12:23 2005 From: wtogami at redhat.com (Warren Togami) Date: Thu, 10 Nov 2005 11:12:23 -0500 Subject: Remove perl-RPM2 from FC Message-ID: <43737167.9010609@redhat.com> Can we remove perl-RPM2 from FC? AFAICT nothing depends on it and I haven't seen anyone actually rely on it. Any objections from the Fedora Perl Devel team? Warren Togami wtogami at redhat.com From bugzilla at redhat.com Thu Nov 10 17:57:02 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 10 Nov 2005 12:57:02 -0500 Subject: [Bug 172677] Review Request: perl-Readonly In-Reply-To: Message-ID: <200511101757.jAAHv2nb029172@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: perl-Readonly https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172677 ------- Additional Comments From rc040203 at freenet.de 2005-11-10 12:56 EST ------- I am still unable to access your site. Therefore only some comments on the spec file from the attachment: 1. FE's packaging policy recommends to ship one package per perl distribution, and I don't see many compelling reasons to make an exception in this case. I.e. I recommend to split this package into 2 packages: perl-Readonly and perl-Readonly-XS 2. Readonly wants to ship this file: /usr/lib/perl5/vendor_perl/5.8.6/benchmark.pl IMO, shipping a script of this name at this location should be avoided. I recommend to move it elsewhere (eg. %doc) or to remove it entirely. -- 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. From bugzilla at redhat.com Thu Nov 10 18:48:02 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 10 Nov 2005 13:48:02 -0500 Subject: [Bug 172677] Review Request: perl-Readonly In-Reply-To: Message-ID: <200511101848.jAAIm2i7001656@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: perl-Readonly https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172677 ------- Additional Comments From mpeters at mac.com 2005-11-10 13:47 EST ------- I'm going to contact my service provider and ask why access isn't working for some people. -=- With respect to splitting it - I can do that, but then perl-Readonly-XS will need to Require perl-Require because it is useless without perl-Readonly. However - perl-Readonly should also require perl-Readonly-XS because it gives perl-Readonly-XS a performance boost, and perl scripts that use perl-Readonly will not require perl-Readonly-XS by automatic dep resolution, so the only way to get perl-Readonly-XS pulled in with yum is to have perl-Readonly require it. Since the two modules will thus need to require each other, and are maintained by the same maintainer, and released in pair (new version of one means new version of other) - does it really make sense for them to be separate packages in this case? -- 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. From bugzilla at redhat.com Thu Nov 10 19:13:15 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 10 Nov 2005 14:13:15 -0500 Subject: [Bug 113304] perl should not export -D_FILE_OFFSET_BITS=64 In-Reply-To: Message-ID: <200511101913.jAAJDFGJ006945@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: perl should not export -D_FILE_OFFSET_BITS=64 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=113304 jvdias at redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution| |CURRENTRELEASE Fixed In Version| |ALL ------- Additional Comments From jvdias at redhat.com 2005-11-10 14:13 EST ------- I believe this is no longer a problem - all current kernels fully support largefiles, and perl largefile support can be turned on / off by the '%define largefiles 1' (default 1) in the .spec files for all current perl releases - if I'm wrong, please let me know and re-open this bug - thanks. -- 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. From ville.skytta at iki.fi Thu Nov 10 21:02:39 2005 From: ville.skytta at iki.fi (Ville =?ISO-8859-1?Q?Skytt=E4?=) Date: Thu, 10 Nov 2005 23:02:39 +0200 Subject: Remove perl-RPM2 from FC (and maybe perl-XML-Encoding, perl-Parse-Yapp?) In-Reply-To: <43737167.9010609@redhat.com> References: <43737167.9010609@redhat.com> Message-ID: <1131656559.21951.64.camel@localhost.localdomain> On Thu, 2005-11-10 at 11:12 -0500, Warren Togami wrote: > Can we remove perl-RPM2 from FC? AFAICT nothing depends on it and I > haven't seen anyone actually rely on it. > > Any objections from the Fedora Perl Devel team? None here. While at it, if you feel like pruning more perl-* packages from FC5, it seems to me that as a result of the perl-libxml-enno drop/split-and-move-to-extras (#128879), perl-XML-Encoding doesn't have any deps in Core nor Extras, and perl-Parse-Yapp is needed only in Extras. From bugzilla at redhat.com Fri Nov 11 22:16:23 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 11 Nov 2005 17:16:23 -0500 Subject: [Bug 172998] New: spamassassin 3.0.4 DOS vulnerability Message-ID: 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=172998 Summary: spamassassin 3.0.4 DOS vulnerability Product: Fedora Core Version: fc4 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: normal Component: spamassassin AssignedTo: wtogami at redhat.com ReportedBy: goemon at anime.net CC: fedora-perl-devel- list at redhat.com,felicity at kluge.net,jm at jmason.org,parkerm @pobox.com,reg+redhat at sidney.com,wtogami at redhat.com Description of problem: spamassassin 3.0.4 is vulnerable to DOS attacks. Version-Release number of selected component (if applicable): 3.0.4 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: http://secunia.com/advisories/17386/ http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4570 -- 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. From bugzilla at redhat.com Fri Nov 11 22:20:22 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 11 Nov 2005 17:20:22 -0500 Subject: [Bug 172998] spamassassin 3.0.4 DOS vulnerability In-Reply-To: Message-ID: <200511112220.jABMKM6l028710@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: spamassassin 3.0.4 DOS vulnerability https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172998 goemon at anime.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |ERRATA ------- Additional Comments From goemon at anime.net 2005-11-11 17:20 EST ------- bleh nm, i see this was just recently patched in FC. -- 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. From bugzilla at redhat.com Sat Nov 12 09:04:48 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sat, 12 Nov 2005 04:04:48 -0500 Subject: [Bug 172677] Review Request: perl-Readonly In-Reply-To: Message-ID: <200511120904.jAC94mQN006149@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: perl-Readonly https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172677 ------- Additional Comments From ville.skytta at iki.fi 2005-11-12 04:04 EST ------- I think the bundling makes sense in this case. I'd personally add "Provides: perl-Readonly-XS = %{version}". And the inclusion of benchmark.pl the way it's done now looks pretty suspicious indeed. If it can't be removed or moved to %doc, it needs to renamed to something less generic. -- 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. From bugzilla at redhat.com Sat Nov 12 09:14:34 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sat, 12 Nov 2005 04:14:34 -0500 Subject: [Bug 172677] Review Request: perl-Readonly In-Reply-To: Message-ID: <200511120914.jAC9EYG1006599@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: perl-Readonly https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172677 ------- Additional Comments From ville.skytta at iki.fi 2005-11-12 04:14 EST ------- (In reply to comment #5) > I'd personally add "Provides: perl-Readonly-XS = %{version}". Oops, s/%{version}/%{version}-%{release}/ -- 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. From bugzilla at redhat.com Sun Nov 13 04:51:22 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sat, 12 Nov 2005 23:51:22 -0500 Subject: [Bug 172677] Review Request: perl-Readonly In-Reply-To: Message-ID: <200511130451.jAD4pMRl009924@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: perl-Readonly https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172677 ------- Additional Comments From rc040203 at freenet.de 2005-11-12 23:51 EST ------- (In reply to comment #5) > I think the bundling makes sense in this case. I could not disagree more. * Readonly-XS and Readonly are independent, there is no dependency between both. Actually, Readonly-XS is a sort of overlay plugin to Readonly * Readonly is noarch/Readonly-XS is arch'ed. Probs will occur, should Readonly-XS not be buildable on one particular architecture. * Splitting both makes the *specs much simpler and less error-prone. => There is no technically need to merge these perl-dists into one, therefore there is no need to make an exception from the FE packaging rules. -- 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. From bugzilla at redhat.com Sun Nov 13 06:10:12 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 13 Nov 2005 01:10:12 -0500 Subject: [Bug 172677] Review Request: perl-Readonly In-Reply-To: Message-ID: <200511130610.jAD6ACt3013660@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: perl-Readonly https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172677 ------- Additional Comments From mpeters at mac.com 2005-11-13 01:09 EST ------- OK. I'll build them separately and submit a spec file for perl-Readonly-XS. I'll fix the benchmark.pl issue as well - I suspect it can be thrown into %doc but I'll verify first. -- 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. From bugzilla at redhat.com Sun Nov 13 06:56:26 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 13 Nov 2005 01:56:26 -0500 Subject: [Bug 172677] Review Request: perl-Readonly In-Reply-To: Message-ID: <200511130656.jAD6uQmi015971@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: perl-Readonly https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172677 ------- Additional Comments From mpeters at mac.com 2005-11-13 01:56 EST ------- New rpm and spec file: http://mpeters.us/fc_extras/perl-Readonly-1.03-2.src.rpm http://mpeters.us/fc_extras/perl-Readonly.spec I'll attach the spec file in case there are still issues with people not being able to access my site. -- 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. From bugzilla at redhat.com Sun Nov 13 06:58:09 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 13 Nov 2005 01:58:09 -0500 Subject: [Bug 172677] Review Request: perl-Readonly In-Reply-To: Message-ID: <200511130658.jAD6w9q3016060@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: perl-Readonly https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172677 mpeters at mac.com changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #120815|0 |1 is obsolete| | ------- Additional Comments From mpeters at mac.com 2005-11-13 01:58 EST ------- Created an attachment (id=120998) --> (https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=120998&action=view) Updated spec file -- 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. From bugzilla at redhat.com Sun Nov 13 07:06:12 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 13 Nov 2005 02:06:12 -0500 Subject: [Bug 173053] Review Request: perl-Readonly-XS In-Reply-To: Message-ID: <200511130706.jAD76CjX016428@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: perl-Readonly-XS https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=173053 mpeters at mac.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fedora-perl-devel- | |list at redhat.com ------- Additional Comments From mpeters at mac.com 2005-11-13 02:06 EST ------- This is a companion package to the package submitted in bug 172677 and is intended to be an explicit Requires of that package (so that yum will pull this in when perl-Readonly is requested) -- 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. From bugzilla at redhat.com Sun Nov 13 07:15:57 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 13 Nov 2005 02:15:57 -0500 Subject: [Bug 173053] Review Request: perl-Readonly-XS In-Reply-To: Message-ID: <200511130715.jAD7FveH016971@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: perl-Readonly-XS https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=173053 mpeters at mac.com changed: What |Removed |Added ---------------------------------------------------------------------------- OtherBugsDependingO| |172677 nThis| | ------- Additional Comments From mpeters at mac.com 2005-11-13 02:15 EST ------- I'm putting this in as blocking 172677 because if it fails to build on a supported arch and can't be fixed, 172677 will need to be changed so that it can ifnarch the broken arch before it can be built. -- 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. From bugzilla at redhat.com Sun Nov 13 07:16:03 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 13 Nov 2005 02:16:03 -0500 Subject: [Bug 172677] Review Request: perl-Readonly In-Reply-To: Message-ID: <200511130716.jAD7G3Nt016993@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: perl-Readonly https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172677 mpeters at mac.com changed: What |Removed |Added ---------------------------------------------------------------------------- BugsThisDependsOn| |173053 -- 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. From bugzilla at redhat.com Mon Nov 14 23:24:53 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 14 Nov 2005 18:24:53 -0500 Subject: [Bug 167354] Review Request: amavisd-new In-Reply-To: Message-ID: <200511142324.jAENOrZI026477@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: amavisd-new https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=167354 ------- Additional Comments From dennis at ausil.us 2005-11-14 18:24 EST ------- Starting amavisd: Problem in the Amavis::Unpackers code: Archive::Zip version 1.14 required--this is only version 1.12 at (eval 46) line 20. BEGIN failed--compilation aborted at (eval 46) line 20. Just as a start i havent done a full check on the package yet. -- 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. From bugzilla at redhat.com Wed Nov 16 19:20:37 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 16 Nov 2005 14:20:37 -0500 Subject: [Bug 128879] Break perl-libxml-enno into component CPAN modules In-Reply-To: Message-ID: <200511161920.jAGJKbkB006362@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Break perl-libxml-enno into component CPAN modules https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=128879 ------- Additional Comments From ville.skytta at iki.fi 2005-11-16 14:20 EST ------- Ouch, I see perl-XML-Encoding and perl-Parse-Yapp have been removed from Rawhide. The former should be ok, but the latter causes an unsatisfied dependency in perl-XML-XQL in Extras, see comment 9. Is someone planning to package perl-Parse-Yapp for Extras? -- 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. From bugzilla at redhat.com Thu Nov 17 08:16:15 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 17 Nov 2005 03:16:15 -0500 Subject: [Bug 167797] perl-DBD-Pg package doesn't Provide: perl(DBD::Pg) In-Reply-To: Message-ID: <200511170816.jAH8GFTd003154@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: perl-DBD-Pg package doesn't Provide: perl(DBD::Pg) https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=167797 ------- Additional Comments From paul at city-fan.org 2005-11-17 03:16 EST ------- Upstream reports that this is now fixed in CVS and "will appear correctly formatted in 1.44", so the manual Provides: should be removable when that version is released. http://rt.cpan.org/NoAuth/Bug.html?id=14509 -- 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. From bugzilla at redhat.com Fri Nov 18 03:25:28 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 17 Nov 2005 22:25:28 -0500 Subject: [Bug 173563] New: filelist cleanup: drop unnecessary files, eliminate duplicates Message-ID: 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=173563 Summary: filelist cleanup: drop unnecessary files, eliminate duplicates Product: Fedora Core Version: devel Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: normal Component: perl AssignedTo: jvdias at redhat.com ReportedBy: altblue at n0i.net QAContact: dkl at redhat.com CC: fedora-perl-devel-list at redhat.com Drop more cruft that comes with the usual installation (Attribute/Handlers/demo, CGI/eg, TODOs, READMEs, etc) and let DBM_Filter live (as we just want NDBM* out). (patch for 5.8.7-0.7.fc5 spec attached) -- 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. From bugzilla at redhat.com Fri Nov 18 03:27:27 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 17 Nov 2005 22:27:27 -0500 Subject: [Bug 173563] filelist cleanup: drop unnecessary files, eliminate duplicates In-Reply-To: Message-ID: <200511180327.jAI3RRaj014791@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: filelist cleanup: drop unnecessary files, eliminate duplicates https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=173563 ------- Additional Comments From altblue at n0i.net 2005-11-17 22:27 EST ------- Created an attachment (id=121216) --> (https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=121216&action=view) drop useless files, eliminate duplicates -- 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. From bugzilla at redhat.com Fri Nov 18 17:56:14 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 18 Nov 2005 12:56:14 -0500 Subject: [Bug 173563] filelist cleanup: drop unnecessary files, eliminate duplicates In-Reply-To: Message-ID: <200511181756.jAIHuExD013630@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: filelist cleanup: drop unnecessary files, eliminate duplicates https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=173563 jvdias at redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From jvdias at redhat.com 2005-11-18 12:56 EST ------- OK, I'll put in most of these changes with the next perl-5.8.7-0.8.fc5 release - I'm still working on more upstream backports and a fix for bug 172792 . I disagree that README files, changelogs, and examples are "useless" - I think they should stay in. -- 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. From bugzilla at redhat.com Fri Nov 18 19:50:36 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 18 Nov 2005 14:50:36 -0500 Subject: [Bug 173646] New: Selinux denials for spamd Message-ID: 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=173646 Summary: Selinux denials for spamd Product: Fedora Core Version: fc4 Platform: i686 OS/Version: Linux Status: NEW Severity: normal Priority: normal Component: spamassassin AssignedTo: wtogami at redhat.com ReportedBy: gc1111 at optonline.net CC: fedora-perl-devel- list at redhat.com,felicity at kluge.net,jm at jmason.org,parkerm @pobox.com,reg+redhat at sidney.com,wtogami at redhat.com >From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7 Description of problem: SeLinux denies access to spamd many times. Version-Release number of selected component (if applicable): spamassassin-3.0.4-2.fc4 How reproducible: Always Steps to Reproduce: 1. Use Selinux in enforcing/targeted mode 2. Set evolution to filter mail using spamassassin 3. Read mail 4. Look at audit logs Actual Results: Many denials as per Additional Information Expected Results: No Selinux denials Additional info: Extract from /var/log/audit/audit.log: type=AVC msg=audit(1132324042.516:8455): avc: denied { write } for pid=1862 comm="spamd" name="log" dev=tmpfs ino=4750 scontext=system_u:system_r:spamd_t tcontext=system_u:object_r:device_t tclass=sock_file type=SYSCALL msg=audit(1132324042.516:8455): arch=40000003 syscall=102 success=no exit=-13 a0=3 a1=bfb60480 a2=862bc0 a3=6e items=1 pid=1862 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 comm="spamd" exe="/usr/bin/perl" -- 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. From bugzilla at redhat.com Sat Nov 19 08:55:04 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sat, 19 Nov 2005 03:55:04 -0500 Subject: [Bug 173563] filelist cleanup: drop unnecessary files, eliminate duplicates In-Reply-To: Message-ID: <200511190855.jAJ8t4lC010648@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: filelist cleanup: drop unnecessary files, eliminate duplicates https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=173563 ------- Additional Comments From ville.skytta at iki.fi 2005-11-19 03:54 EST ------- It would be nicer to have the READMEs etc in the doc dir instead of being scattered somewhere below /usr/lib/perl5/x.x.x though. -- 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. From bugzilla at redhat.com Sat Nov 19 14:17:22 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sat, 19 Nov 2005 09:17:22 -0500 Subject: [Bug 173563] filelist cleanup: drop unnecessary files, eliminate duplicates In-Reply-To: Message-ID: <200511191417.jAJEHMiF003821@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: filelist cleanup: drop unnecessary files, eliminate duplicates https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=173563 ------- Additional Comments From altblue at n0i.net 2005-11-19 09:17 EST ------- Indeed, "useless" is not an appropriate word for the matter, but the issue is valid - those files should really disappear _from /usr/lib/*_ I think it's better to not have them at all rather than scattered wherever on the filesystem. As Ville said, if you want to keep them, move them in %docdir. Farther, if you do that, than place those demo files there too, they should be useful too :) OTOH, do you remember any redhat/fedora perl package that includes changelogs? They don't even include the license :| If you want to fix this, then add this line to the %files list: %doc Artistic AUTHORS Changes* Copying README And this to %install or something: # wanna have them, but compressed though ;-) %{__gzip} Changes* -- 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. From bugzilla at redhat.com Mon Nov 21 08:54:21 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 21 Nov 2005 03:54:21 -0500 Subject: [Bug 173793] New: CAN-2005-0448 perl File::Path.pm rmtree race condition Message-ID: 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=173793 Summary: CAN-2005-0448 perl File::Path.pm rmtree race condition Product: Fedora Core Version: fc4 Platform: All OS/Version: Linux Status: NEW Severity: security Priority: normal Component: perl AssignedTo: jvdias at redhat.com ReportedBy: mjc at redhat.com QAContact: dkl at redhat.com CC: fedora-perl-devel-list at redhat.com,wtogami at redhat.com +++ This bug was initially created as a clone of Bug #157695 +++ Race condition in the rmtree function in File::Path.pm in Perl before 5.8.4 allows local users to create arbitrary setuid binaries in the tree being deleted, a different vulnerability than CAN-2004-0452. http://marc.theaimsgroup.com/?l=bugtraq&m=111039131424834&w=2 attachment 114350 contains the ubuntu patch (it needs some cleaning up) -- Additional comment from wtogami at redhat.com on 2005-05-28 02:05 EST -- "Race condition in the rmtree function in File::Path.pm in Perl before 5.8.4 allows local users to create arbitrary setuid binaries" 5.8.4 means FC3 is unaffected because we have perl-5.8.5? Can someone confirm? -- Additional comment from bressers at redhat.com on 2005-05-28 08:41 EST -- Warren, I just took a look at the latest perl source, this issue has not been fixed by upstream. It's proving very hard to do right, which is probably why upstream hasn't done it yet. -- Additional comment from wtogami at redhat.com on 2005-05-31 06:40 EST -- https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=114350 Attachment to fix this security bug is from Ubuntu, but we require help cleaning it up and testing before issuing a FC3 update. Apparently this is a difficult problem to fix, and this is our second attempt doing so. =( -- Additional comment from prockai at redhat.com on 2005-06-15 14:01 EST -- Created an attachment (id=115494) --> (https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=115494&action=view) debian's 03_fix_file_path Why not just use the debian patch? (attached) -- Additional comment from prockai at redhat.com on 2005-06-16 04:22 EST -- Assigning to self. -- Additional comment from prockai at redhat.com on 2005-06-16 08:15 EST -- Patched in CVS. Testing requested - if anyone has an exploit or something like that, please try out. The testsuite passes exactly like before patching, but regression testing is welcome as well. -- Additional comment from prockai at redhat.com on 2005-07-28 09:07 EST -- Fixed in FC3 update perl-5.8.5-14.FC3 -- 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. From bugzilla at redhat.com Mon Nov 21 23:18:33 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 21 Nov 2005 18:18:33 -0500 Subject: [Bug 173793] CAN-2005-0448 perl File::Path.pm rmtree race condition In-Reply-To: Message-ID: <200511212318.jALNIXDU020686@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: CAN-2005-0448 perl File::Path.pm rmtree race condition https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=173793 jvdias at redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution| |NOTABUG ------- Additional Comments From jvdias at redhat.com 2005-11-21 18:18 EST ------- perl 5.8.6 in FC-4 and perl-5.8.7 in FC-5 should NOT be vulnerable to this exploit - if anyone has found to the contrary, please supply a test case (perl script that exploits the vulnerability). I think the CVE is correct in stating that this is only a problem with 5.8.3(-). The 5.8.7 rmtree differs from that of 5.8.6 ONLY in potentially adding more privileges when it does the chmod before the remove - it sets the permissions of each file to ($rp | 0x00), where $rp is the permissions of the path being removed, instead of FC-4's 0x00, and in adding better support for VMS . Debian has gone with its own implementation of Path::rmtree, which is incompatible with the upstream version and shows no sign of being accepted there, and still carries the same warnings about the fundamental insecurity of the whole algorithm used by Path::rmtree . Gentoo basically copies Debian's patch. Neither Trustix nor OWL patch the upstream 5.8.7/5.8.6 Path::rmtree code at all. I think we should minimise the differences between our perl distribution and the upstream version. Since neither trustix nor owl have seen fit to patch the 5.8.6 or 5.8.7 Path::rmtree, and since no exploits for the 5.8.6/5.8.7 rmtree have been reported, I think we should stick with the upstream version. -- 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. From pankaj.rwth at gmail.com Wed Nov 23 14:59:13 2005 From: pankaj.rwth at gmail.com (Pankaj Bhatia) Date: Wed, 23 Nov 2005 15:59:13 +0100 Subject: Question. Message-ID: <11e744e10511230659y5469d16qedb861fad4588818@mail.gmail.com> Hi, I am a beginner perl developer. I am writing a script for pasing all files in a directory with perticular suffix. I use File::Find but I want to avoid searching in subdirectories. I tried to use File::Find::prune in "wanted" function. bit it did not work. So I use a heck return unless ($File::Find::topdir eq $File::Find::dir); to avoid processing in sub directories. but this is an inefficient way. I want to limit search only to first directory level. Please let me know the efficient way to do it. and any comments/modification on the code would also be appriciated. Regards Pankaj sub wanted { ## dir tree Depth = 1 return unless ($File::Find::topdir eq $File::Find::dir); $fileext= ".cgd"; if ($_ =~ /$fileext$/) { # $_ contain file base name. # $ sign at end of pattern looks for # .lisa suffix $files[$Count] = "$File::Find::name"; $Count++; } } -------------- next part -------------- An HTML attachment was scrubbed... URL: From shockwave at clan-tf20.com Wed Nov 23 15:29:33 2005 From: shockwave at clan-tf20.com (Shockwave) Date: Wed, 23 Nov 2005 10:29:33 -0500 Subject: Question. References: <11e744e10511230659y5469d16qedb861fad4588818@mail.gmail.com> Message-ID: <008501c5f042$b682cb60$0a02a8c0@RCS.local> Hi, I'm not an expert Perl developer, but I may be able to help you. Here's the way I've done it in the past: ----------------begin code sample------------------ #!/usr/bin/perl -w use strict; my $input_dir = '/path/to/files/'; # directory to search my $fileext = '.lisa'; # file extension to find my $count = 0; # files found counter my %files = (); # hash for file list # open filehandle to read output from "ls" command open(INF,"ls $input_dir|") or &error_msg("Cannot get directory listing for \'$input_dir\'. Error: \'$!\'\n"); while() { chomp; # drop line terminator if ($_ =~ m/$fileext$/) # match files ending in specified file extension { $files{$count} = $_; # add entry to hash $count++; # increment file counter } close(INF); # drop filehandle exit(0); ----------------end code sample------------------ I hope this helps. Tom ----- Original Message ----- From: Pankaj Bhatia To: fedora-perl-devel-list at redhat.com Sent: Wednesday, November 23, 2005 9:59 AM Subject: Question. Hi, I am a beginner perl developer. I am writing a script for pasing all files in a directory with perticular suffix. I use File::Find but I want to avoid searching in subdirectories. I tried to use File::Find::prune in "wanted" function. bit it did not work. So I use a heck return unless ($File::Find::topdir eq $File::Find::dir); to avoid processing in sub directories. but this is an inefficient way. I want to limit search only to first directory level. Please let me know the efficient way to do it. and any comments/modification on the code would also be appriciated. Regards Pankaj sub wanted { ## dir tree Depth = 1 return unless ($File::Find::topdir eq $File::Find::dir); $fileext= ".cgd"; if ($_ =~ /$fileext$/) { # $_ contain file base name. # $ sign at end of pattern looks for # .lisa suffix $files[$Count] = "$File::Find::name"; $Count++; } } ------------------------------------------------------------------------------ -- Fedora-perl-devel-list mailing list Fedora-perl-devel-list at redhat.com https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From shockwave at clan-tf20.com Wed Nov 23 15:40:28 2005 From: shockwave at clan-tf20.com (Shockwave) Date: Wed, 23 Nov 2005 10:40:28 -0500 Subject: Question. References: <11e744e10511230659y5469d16qedb861fad4588818@mail.gmail.com> <008501c5f042$b682cb60$0a02a8c0@RCS.local> Message-ID: <00bf01c5f044$3f235650$0a02a8c0@RCS.local> One correction, you will want to replace this line: open(INF,"ls $input_dir|") or &error_msg("Cannot get directory listing for \'$input_dir\'. Error: \'$!\'\n"); with this: open(INF,"ls $input_dir|") or die("Cannot get directory listing for \'$input_dir\'. Error: \'$!\'\n"); I forgot to remove the call to a custom error handling routine I usually use. ;) Tom ----- Original Message ----- From: Shockwave To: Fedora perl development team Sent: Wednesday, November 23, 2005 10:29 AM Subject: Re: Question. Hi, I'm not an expert Perl developer, but I may be able to help you. Here's the way I've done it in the past: ----------------begin code sample------------------ #!/usr/bin/perl -w use strict; my $input_dir = '/path/to/files/'; # directory to search my $fileext = '.lisa'; # file extension to find my $count = 0; # files found counter my %files = (); # hash for file list # open filehandle to read output from "ls" command open(INF,"ls $input_dir|") or &error_msg("Cannot get directory listing for \'$input_dir\'. Error: \'$!\'\n"); while() { chomp; # drop line terminator if ($_ =~ m/$fileext$/) # match files ending in specified file extension { $files{$count} = $_; # add entry to hash $count++; # increment file counter } close(INF); # drop filehandle exit(0); ----------------end code sample------------------ I hope this helps. Tom ----- Original Message ----- From: Pankaj Bhatia To: fedora-perl-devel-list at redhat.com Sent: Wednesday, November 23, 2005 9:59 AM Subject: Question. Hi, I am a beginner perl developer. I am writing a script for pasing all files in a directory with perticular suffix. I use File::Find but I want to avoid searching in subdirectories. I tried to use File::Find::prune in "wanted" function. bit it did not work. So I use a heck return unless ($File::Find::topdir eq $File::Find::dir); to avoid processing in sub directories. but this is an inefficient way. I want to limit search only to first directory level. Please let me know the efficient way to do it. and any comments/modification on the code would also be appriciated. Regards Pankaj sub wanted { ## dir tree Depth = 1 return unless ($File::Find::topdir eq $File::Find::dir); $fileext= ".cgd"; if ($_ =~ /$fileext$/) { # $_ contain file base name. # $ sign at end of pattern looks for # .lisa suffix $files[$Count] = "$File::Find::name"; $Count++; } } ---------------------------------------------------------------------------- -- Fedora-perl-devel-list mailing list Fedora-perl-devel-list at redhat.com https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list ------------------------------------------------------------------------------ -- Fedora-perl-devel-list mailing list Fedora-perl-devel-list at redhat.com https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From bugzilla at redhat.com Mon Nov 28 16:58:39 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 28 Nov 2005 11:58:39 -0500 Subject: [Bug 174373] New: Perl program crashes on end if prepared statements are used Message-ID: 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=174373 Summary: Perl program crashes on end if prepared statements are used Product: Fedora Core Version: fc4 Platform: i386 OS/Version: Linux Status: NEW Severity: normal Priority: normal Component: perl-DBD-Pg AssignedTo: wtogami at redhat.com ReportedBy: pb at bieringer.de CC: fedora-perl-devel-list at redhat.com >From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-DE; rv:1.7.12) Gecko/20050919 Firefox/1.0.7 Description of problem: A specific (not so big) Perl program crashes crashes on a special scenario Version-Release number of selected component (if applicable): perl-DBD-Pg-1.41-2 perl-5.8.6-16.fc4 postgresql-8.0.4-2.FC4.1 How reproducible: Always Steps to Reproduce: 1. create a Perl program 2. use DBD::Pg 3. connect to database 4. create some prepare statements like my $statement = "SELECT * FROM table WHERE number = ?"; my $sth_test_select = $dbh->prepare($statement) || die $DBI::errstr; 5. use statements 6. disconnect from database 7. exit Actual Results: Crash: rt_sigprocmask(SIG_BLOCK, [PIPE], [], 8) = 0 send(3, "Q\0\0\0\rrollback\0", 14, 0) = 14 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 poll([{fd=3, events=POLLIN|POLLERR, revents=POLLIN}], 1, -1) = 1 recv(3, "C\0\0\0\rROLLBACK\0Z\0\0\0\5I", 16384, 0) = 20 rt_sigprocmask(SIG_BLOCK, [PIPE], [], 8) = 0 send(3, "X\0\0\0\4", 5, 0) = 5 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 close(3) = 0 stat64("/usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi/auto/DBI/DESTROY.al", 0x94ce0c8) = -1 ENOENT (No such file or directory) open("/usr/share/locale/locale.alias", O_RDONLY) = 3 fstat64(3, {st_mode=S_IFREG|0644, st_size=2528, ...}) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7d6c000 read(3, "# Locale name alias data base.\n#"..., 4096) = 2528 read(3, "", 4096) = 0 close(3) = 0 munmap(0xb7d6c000, 4096) = 0 open("/usr/share/locale/en_US.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en_US.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en_US/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi/auto/DBI/DESTROY.al", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi/auto/DBI/DESTROY.al", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/lib/perl5/site_perl/5.8.4/i386-linux-thread-multi/auto/DBI/DESTROY.al", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/lib/perl5/site_perl/5.8.3/i386-linux-thread-multi/auto/DBI/DESTROY.al", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/lib/perl5/site_perl/5.8.6/auto/DBI/DESTROY.al", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/lib/perl5/site_perl/5.8.5/auto/DBI/DESTROY.al", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/lib/perl5/site_perl/5.8.4/auto/DBI/DESTROY.al", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/lib/perl5/site_perl/5.8.3/auto/DBI/DESTROY.al", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/lib/perl5/site_perl/auto/DBI/DESTROY.al", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi/auto/DBI/DESTROY.al", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi/auto/DBI/DESTROY.al", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/lib/perl5/vendor_perl/5.8.4/i386-linux-thread-multi/auto/DBI/DESTROY.al", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi/auto/DBI/DESTROY.al", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/lib/perl5/vendor_perl/5.8.6/auto/DBI/DESTROY.al", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/lib/perl5/vendor_perl/5.8.5/auto/DBI/DESTROY.al", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/lib/perl5/vendor_perl/5.8.4/auto/DBI/DESTROY.al", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/lib/perl5/vendor_perl/5.8.3/auto/DBI/DESTROY.al", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/lib/perl5/vendor_perl/auto/DBI/DESTROY.al", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/lib/perl5/5.8.6/i386-linux-thread-multi/auto/DBI/DESTROY.al", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/lib/perl5/5.8.6/auto/DBI/DESTROY.al", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("./auto/DBI/DESTROY.al", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) exit_group(0) = ? Expected Results: If prepare variable would be undef'ed before exit (before oder after disconnect), the crash would no longer occur. 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. From bugzilla at redhat.com Mon Nov 28 17:00:30 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 28 Nov 2005 12:00:30 -0500 Subject: [Bug 174373] Perl program crashes on end if prepared statements are used In-Reply-To: Message-ID: <200511281700.jASH0Ud7001474@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Perl program crashes on end if prepared statements are used https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=174373 ------- Additional Comments From pb at bieringer.de 2005-11-28 12:00 EST ------- I forgot to mentionend, that if I connect to database with "pg_server_prepare => 0", also no crash occurs. So problem mut be related to the new feature of PostgreSQL 7.4/8.0. -- 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. From bugzilla at redhat.com Wed Nov 30 12:52:29 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 30 Nov 2005 07:52:29 -0500 Subject: [Bug 174579] New: spamd init script has no nls messages Message-ID: 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=174579 Summary: spamd init script has no nls messages Product: Fedora Core Version: fc4 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: normal Component: spamassassin AssignedTo: wtogami at redhat.com ReportedBy: che666 at gmail.com CC: fedora-perl-devel- list at redhat.com,felicity at kluge.net,jm at jmason.org,parkerm @pobox.com,reg+redhat at sidney.com,wtogami at redhat.com Description of problem: spamd init script has no nls messages. patch makes the init script suck a bit less ;) Version-Release number of selected component (if applicable): 3.0.3 How reproducible: always Steps to Reproduce: 1. start the service 2. 3. Actual results: get an english starting/stopping message Expected results: nls support Additional info: some credits would be sweet ------- Additional Comments From che666 at gmail.com 2005-11-30 07:52 EST ------- Created an attachment (id=121633) --> (https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=121633&action=view) newrpms-spamassassin-init-nls.patch -- 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. From bugzilla at redhat.com Wed Nov 30 21:44:03 2005 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 30 Nov 2005 16:44:03 -0500 Subject: [Bug 174579] spamd init script has no nls messages In-Reply-To: Message-ID: <200511302144.jAULi3qL010590@www.beta.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: spamd init script has no nls messages https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=174579 wtogami at redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- OtherBugsDependingO| |171491 nThis| | -- 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.