Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

multiple bugs in perlbug #9975

Closed
p5pRT opened this issue Nov 20, 2009 · 7 comments
Closed

multiple bugs in perlbug #9975

p5pRT opened this issue Nov 20, 2009 · 7 comments

Comments

@p5pRT
Copy link

p5pRT commented Nov 20, 2009

Migrated from rt.perl.org#70690 (status was 'resolved')

Searchable as RT70690$

@p5pRT
Copy link
Author

p5pRT commented Nov 20, 2009

From wanradt@gmail.com

Created by wanradt@gmail.com

After filling bug report and trying to send it away, i got answer​:

  I am terribly sorry, but I cannot find sendmail, or a close
  equivalent, and the perl package Mail​::Send has not been
  installed, so I can't send your bug report. We apologize for the
  inconvenience.

  So you may attempt to find some way of sending your message, it
  has been left in the file `/tmp/QsEe2TfxL9'.

On some reason there was now such temp file mentioned above, too. I
looked for such file on many occasion.

And still, i had correctly installed Mail​::Send module on system
(/usr/share/perl5/Mail/Send.pm
), in @​INC, as you can check on details below.

So,
1. perlbug does not WARN users on start, that something more is
required to fill report
2. perlbug tries send report away without testing requirements and
without warnings
3. perlbug does not save report properly
4. perlbug does not use correctly modules on @​INC

Perl Info

Flags:
    category=core
    severity=low

Site configuration information for perl 5.10.0:

Configured by Debian Project at Mon Sep 21 08:42:41 UTC 2009.

Summary of my perl5 (revision 5 version 10 subversion 0) configuration:
  Platform:
    osname=linux, osvers=2.6.24-24-server, archname=i486-linux-gnu-thread-multi
    uname='linux palmer 2.6.24-24-server #1 smp tue aug 18 17:46:20
utc 2009 i686 gnulinux '
    config_args='-Dusethreads -Duselargefiles -Dccflags=-DDEBIAN
-Dcccdlflags=-fPIC -Darchname=i486-linux-gnu -Dprefix=/usr
-Dprivlib=/usr/share/perl/5.10 -Darchlib=/usr/lib/perl/5.10
-Dvendorprefix=/usr -Dvendorlib=/usr/share/perl5
-Dvendorarch=/usr/lib/perl5 -Dsiteprefix=/usr/local
-Dsitelib=/usr/local/share/perl/5.10.0
-Dsitearch=/usr/local/lib/perl/5.10.0 -Dman1dir=/usr/share/man/man1
-Dman3dir=/usr/share/man/man3 -Dsiteman1dir=/usr/local/man/man1
-Dsiteman3dir=/usr/local/man/man3 -Dman1ext=1 -Dman3ext=3perl
-Dpager=/usr/bin/sensible-pager -Uafs -Ud_csh -Ud_ualarm -Uusesfio
-Uusenm -DDEBUGGING=-g -Doptimize=-O2 -Duseshrplib
-Dlibperl=libperl.so.5.10.0 -Dd_dosuid -des'
    hint=recommended, useposix=true, d_sigaction=define
    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='cc', ccflags ='-D_REENTRANT -D_GNU_SOURCE -DDEBIAN
-fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64',
    optimize='-O2 -g',
    cppflags='-D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fno-strict-aliasing
-pipe -I/usr/local/include'
    ccversion='', gccversion='4.4.1', 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='cc', ldflags =' -L/usr/local/lib'
    libpth=/usr/local/lib /lib /usr/lib /usr/lib64
    libs=-lgdbm -lgdbm_compat -ldb -ldl -lm -lpthread -lc -lcrypt
    perllibs=-ldl -lm -lpthread -lc -lcrypt
    libc=/lib/libc-2.10.1.so, so=so, useshrplib=true, libperl=libperl.so.5.10.0
    gnulibc_version='2.10.1'
  Dynamic Linking:
    dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-Wl,-E'
    cccdlflags='-fPIC', lddlflags='-shared -O2 -g -L/usr/local/lib'

Locally applied patches:



@INC for perl 5.10.0:
    /etc/perl
    /usr/local/lib/perl/5.10.0
    /usr/local/share/perl/5.10.0
    /usr/lib/perl5
    /usr/share/perl5
    /usr/lib/perl/5.10
    /usr/share/perl/5.10
    /usr/local/lib/site_perl
    .


Environment for perl 5.10.0:
    HOME=/home/wanradt
    LANG=et_EE.UTF-8
    LANGUAGE=et_EE:et:en_GB:en
    LD_LIBRARY_PATH (unset)
    LOGDIR (unset)
    PATH=/home/wanradt/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
    PERL_BADLANG (unset)
    SHELL=/bin/bash

@p5pRT
Copy link
Author

p5pRT commented Nov 23, 2009

From @Abigail

On Fri, Nov 20, 2009 at 02​:24​:23PM -0800, WK wrote​:

# New Ticket Created by WK
# Please include the string​: [perl #70690]
# in the subject line of all future correspondence about this issue.
# <URL​: http​://rt.perl.org/rt3/Ticket/Display.html?id=70690 >

This is a bug report for perl from wanradt@​gmail.com,
generated with the help of perlbug 1.36 running under perl 5.10.0.

-----------------------------------------------------------------
[Please enter your report here]

After filling bug report and trying to send it away, i got answer​:

I am terribly sorry\, but I cannot find sendmail\, or a close
equivalent\, and the perl package Mail&#8203;::Send has not been
installed\, so I can't send your bug report\. We apologize for the
inconvenience\.

So you may attempt to find some way of sending your message\, it
has been left in the file \`/tmp/QsEe2TfxL9'\.

On some reason there was now such temp file mentioned above, too. I
looked for such file on many occasion.

And still, i had correctly installed Mail​::Send module on system
(/usr/share/perl5/Mail/Send.pm
), in @​INC, as you can check on details below.

So,
1. perlbug does not WARN users on start, that something more is
required to fill report
2. perlbug tries send report away without testing requirements and
without warnings
3. perlbug does not save report properly
4. perlbug does not use correctly modules on @​INC

To address one issue​: perlbug doesn't attempt to use Mail​::Send if
the platform is Linux or OpenBSD, citing​:

  # on linux certain "mail" implementations won't accept the subject
  # as "~s subject" and thus the Subject header will be corrupted
  # so don't use Mail​::Send to be safe

as the reason. I'll make a patch to fix the wording.

Abigail

@p5pRT
Copy link
Author

p5pRT commented Nov 23, 2009

The RT System itself - Status changed from 'new' to 'open'

@p5pRT
Copy link
Author

p5pRT commented Nov 23, 2009

From @Abigail

On Mon, Nov 23, 2009 at 06​:41​:56PM +0100, Abigail wrote​:

On Fri, Nov 20, 2009 at 02​:24​:23PM -0800, WK wrote​:

# New Ticket Created by WK
# Please include the string​: [perl #70690]
# in the subject line of all future correspondence about this issue.
# <URL​: http​://rt.perl.org/rt3/Ticket/Display.html?id=70690 >

This is a bug report for perl from wanradt@​gmail.com,
generated with the help of perlbug 1.36 running under perl 5.10.0.

-----------------------------------------------------------------
[Please enter your report here]

After filling bug report and trying to send it away, i got answer​:

I am terribly sorry\, but I cannot find sendmail\, or a close
equivalent\, and the perl package Mail&#8203;::Send has not been
installed\, so I can't send your bug report\. We apologize for the
inconvenience\.

So you may attempt to find some way of sending your message\, it
has been left in the file \`/tmp/QsEe2TfxL9'\.

On some reason there was now such temp file mentioned above, too. I
looked for such file on many occasion.

And still, i had correctly installed Mail​::Send module on system
(/usr/share/perl5/Mail/Send.pm
), in @​INC, as you can check on details below.

So,
1. perlbug does not WARN users on start, that something more is
required to fill report

That's because perlbug can be used without sending the message. Only
after the report is made is the user prompted what to do next - with
Send being one of the options.

2. perlbug tries send report away without testing requirements and
without warnings

No, actually. You get that warning when perlbug tests the requirements
(which, for Linux, means looking for /usr/lib/sendmail, /usr/sbin/sendmail
and /usr/ucblib/sendmail), and fails to find it.

3. perlbug does not save report properly

Well, it does, but the message can be a bit misleading. At the moment
the above message is displayed, the report *is* in '/tmp/QsEe2TfxL9'.
However, afterwards, perlbug prompts you for a filename to save the
report in, after which it removes the file in /tmp.

4. perlbug does not use correctly modules on @​INC

To address one issue​: perlbug doesn't attempt to use Mail​::Send if
the platform is Linux or OpenBSD, citing​:

\# on linux certain "mail" implementations won't accept the subject
\# as "~s subject" and thus the Subject header will be corrupted
\# so don't use Mail&#8203;::Send to be safe

as the reason. I'll make a patch to fix the wording.

That would be commit e90d614.

Abigail

@p5pRT
Copy link
Author

p5pRT commented May 2, 2012

From @jkeenan

On Mon Nov 23 10​:17​:06 2009, abigail@​abigail.be wrote​:

On Mon, Nov 23, 2009 at 06​:41​:56PM +0100, Abigail wrote​:

On Fri, Nov 20, 2009 at 02​:24​:23PM -0800, WK wrote​:

# New Ticket Created by WK
# Please include the string​: [perl #70690]
# in the subject line of all future correspondence about this issue.
# <URL​: http​://rt.perl.org/rt3/Ticket/Display.html?id=70690 >

This is a bug report for perl from wanradt@​gmail.com,
generated with the help of perlbug 1.36 running under perl 5.10.0.

-----------------------------------------------------------------
[Please enter your report here]

After filling bug report and trying to send it away, i got answer​:

I am terribly sorry\, but I cannot find sendmail\, or a close
equivalent\, and the perl package Mail&#8203;::Send has not been
installed\, so I can't send your bug report\. We apologize for the
inconvenience\.

So you may attempt to find some way of sending your message\, it
has been left in the file \`/tmp/QsEe2TfxL9'\.

On some reason there was now such temp file mentioned above, too. I
looked for such file on many occasion.

And still, i had correctly installed Mail​::Send module on system
(/usr/share/perl5/Mail/Send.pm
), in @​INC, as you can check on details below.

So,
1. perlbug does not WARN users on start, that something more is
required to fill report

That's because perlbug can be used without sending the message. Only
after the report is made is the user prompted what to do next - with
Send being one of the options.

2. perlbug tries send report away without testing requirements and
without warnings

No, actually. You get that warning when perlbug tests the requirements
(which, for Linux, means looking for /usr/lib/sendmail, /usr/sbin/sendmail
and /usr/ucblib/sendmail), and fails to find it.

3. perlbug does not save report properly

Well, it does, but the message can be a bit misleading. At the moment
the above message is displayed, the report *is* in '/tmp/QsEe2TfxL9'.
However, afterwards, perlbug prompts you for a filename to save the
report in, after which it removes the file in /tmp.

4. perlbug does not use correctly modules on @​INC

To address one issue​: perlbug doesn't attempt to use Mail​::Send if
the platform is Linux or OpenBSD, citing​:

\# on linux certain "mail" implementations won't accept the subject
\# as "~s subject" and thus the Subject header will be corrupted
\# so don't use Mail&#8203;::Send to be safe

as the reason. I'll make a patch to fix the wording.

That would be commit e90d614.

Abigail

WK, Abigail​: Have we sufficiently addressed all the issues in this ticket?

Thank you very much.
Jim Keenan

@p5pRT
Copy link
Author

p5pRT commented Jul 22, 2016

From @dcollinsn

Partially resolved and partially rejected per Abigail - error message was improved, otherwise working as intended.

--
Respectfully,
Dan Collins

@p5pRT
Copy link
Author

p5pRT commented Jul 22, 2016

@dcollinsn - Status changed from 'open' to 'resolved'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant