| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
This fixes issue #15544. If the user has PATH, or similar variables
containing a list of directories separated by e.g. a colon character
these can easily become lines with more than 1000 characters in a perlbug
report, resulting in a test failure in lib/perlbug.t.
|
|
|
|
|
|
|
|
|
| |
Output filename now always defaults to "perlbug.rep".
Sends by email only if an address is specified with -a,
invoked as perlthanks or with -T, or the prompt is
chosen to send the report to perl5-porters.
Removed option -A as it no longer does anything.
Clarified output to refer to "report" instead of "message".
|
|
|
|
|
|
| |
On VMS, pipes often introduce extra newlines, so the test
infrastructure deduplicates them, which then makes it impossible
to check for more than one. So just check for one or more.
|
|
|
|
|
|
|
| |
RT 130032: Thanks to Houston Perl Mongers for contributing to this work at
our monthly meeting!
NPD
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Mail transport agents limit the length of message lines at SMTP time.
One observed limit is 1000 characters per line. Mail user agents typically
work around these limits by MIME-encoding the message. Since perlbug
doesn't do that, it needs to limit the length of its lines manually to
make sure bug reports get delivered.
The longest lines in perlbug reports normally come from Config::myconfig
output, particularly 'config_args', which has been observed to exceed
1000 characters on some configurations, causing report rejection. While
less likely, the list of local patches is another potential source of
overly long lines.
Use Text::Wrap (if available) to wrap the body of the report at an
arbitrarily chosen and hopefully safe limit of 900 characters. No
indentation or continuation line markers are added, though it would
be easy to add those if desired. Attachments and mail headers are not
wrapped.
Bug-Debian: https://bugs.debian.org/822463
|
|
Some of these tests have to mimic the interactive interface, which is
probably rather fragile. However, as long as -F overrides any actual
sending, no mail bombs will hopefully result.
|