| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Using an unset variable hides the true intent and
also requires an extra backslash `\$running_under_some_shell`
when used in heredoc.
Note that this could also lead to mistake when using
`\$` in a regular Perl program, as this would be true
and not false as it should be.
Stop recommending the use of an undefined variable for
the shell fallback. Use '0', with a comment
making clear the goal of 'if 0'.
|
|
|
|
|
|
|
|
|
| |
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".
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
GitHub issue tracker
The perlbug utility and perlbug@perl.org should no longer be used to submit bug reports or patches.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[DELTA]
2.089 3 November 2019
* bin/streamzip
Add zipstream to EXE_FILES
https://github.com/pmqs/IO-Compress/issues/5
7f5ed78e5652125c9ba78aab720e18d384d59c00
fb8cd6480af6303f58fd2e12d4999cd1830f0c5f
2.088 31 October 2019
* t/105oneshot-zip-only.t
Fix reset of CompSize
6034da95f1dc5a594edc0d26e6add8d86990ad56
* Add Support Details
ad66b6ec4cf175a70e53f74572eed5f403648f11
* Update site for Bzip2 to sourceware
77497aeb2a234889a2b2c4ac7ea2f620895b16a9
* Fix number of tests
bc4e234449a82fb00f66af752dfc4c96097b2a4d
* Add streamzip script to bin
76d2795d0587bafb0cc398e97142740acba82a42
* zipdetails
* Update zipdetails to version 1.11
8958cb3aa90745a4b3369479846846fdca6b4f76
* Zip64 extra field typo
f186380d701fe5257f9fc92d69160dc6382cfc24
* t/105oneshot-zip-only.t
test with deflated directory
16bfffcf5089af67cb7f68685cc61d06409cba73
* t/105oneshot-zip-only.t
Add test for encrypted Zip files
5ad813115aed000f88d7df28261b43c00ae56525
2c64e255feb5a1ee33d033f7eccb6feca12ebe97
* Documentation Updates
https://github.com/pmqs/IO-Compress/issues/2
e1fd0d4eda0a8496981cbd83ad06906f4ae586a5
* Mention xz, lzma etc
https://github.com/pmqs/IO-Compress/issues/4
126f7b9da97b572d0fb89a9bdcc190c5405c72b8
|
|
|
|
|
|
| |
These files should not be in the MANIFEST
adjust porting/manifest.t to ignore .github files
in addition to .gitignore files.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This updates the bug tracker URL from http://rt.perl.org
to https://rt.perl.org.
There is a place in the code, in corelist.pl, that is sensitive
to the URL of the bug tracker. This now understands both
versions of the bug tracker URL. Ideally, this will be
consolidated once the dust settles.
This patch also updates ExtUtils::CBuilder, Safe, threads
and threads::shared to point to the new bug tracker URL.
|
|
|
|
|
|
| |
This commit moves more URLs from http to https. This time it
affects some source code, that's why it is not bunched up
with the commits affecting pod/*
|
| |
|
| |
|
|
|
|
|
|
| |
This adds a prompt asking for confirmation if the perlbug report would
overwrite an existing file. My guess is that the normal answer will be
yes.
|
|
|
|
|
|
|
| |
RT 130032: Thanks to Houston Perl Mongers for contributing to this work at
our monthly meeting!
NPD
|
|
|
|
|
| |
Note that this isn't normally executed during build, so it wasn't spotted
earlier.
|
|
|
|
|
|
|
|
|
|
| |
These programs are the same, just behave differently depending on
under which name you call it.
This is a very old script, originally dating from the perl3 era.
It has been deprecated in favour of h2xs for a long time.
In Perl 5.26, these utilities will no longer be available.
|
|
|
|
|
|
|
|
|
|
| |
Switch from two-argument form. Filehandle cloning is still done with the two
argument form for backward compatibility.
Committer: Get all porting tests to pass. Increment some $VERSIONs.
Run: ./perl -Ilib regen/mk_invlists.pl; ./perl -Ilib regen/regcharclass.pl
For: RT #130122
|
|
|
|
|
| |
require calls now require ./ to be prepended to the file since . is no
longer guaranteed to be in @INC.
|
|
|
|
|
| |
'typedef enum x { ... } x' causes h2xs to enter a substitution loop while
trying to write the typemap file.
|
| |
|
|
|
|
|
|
|
| |
While currently Encode and Storable are know to attempt to load modules
not included in the core, updates to other modules may lead to those
also attempting to load new modules, so be safe and remove . for those
as well.
|
|
|
|
| |
This fixes tests on Win32.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
_send_message_mailsend() needs to build the message itself rather than
calling build_complete_message() like the other backends, but they can
still share the file reading code, and so can the 'display report' part.
|
|
|
|
|
| |
Passing whitespace in an option through test.pl runperl() doesn't seem
to work, so relax the check in test mode (-t) for noninteractive testing.
|
|
|
|
|
|
|
|
|
|
| |
This makes it possible to drive perlbug noninteractively
without having it go to an infinite loop on end of file.
The change has no effect in non-test mode, where the default answer is
the empty string.
This is groundworks for perlbug unit tests.
|
|
|
|
|
|
|
|
|
|
|
| |
This is groundworks for perlbug unit tests.
Not all of the interactive questions can be overridden on
the command line, so we will have to pipe in commands.
Adapt the test mode ("-t"), which used to just override the
recipient address, for this rather than inventing one more
new option.
|
|
|
|
| |
Mostly these are too long verbatim lines.
|
| |
|
| |
|
|
|
|
|
| |
It's a bit confusing that a core .PL script is copying a cpan/ script
to utils/, so document it.
|
|
|
|
|
|
|
|
|
| |
Previously they were treated as identifiers resulting in code
generated like C< &0xFFF >.
We also try to prevent compile-time warnings from large hex integers,
the user isn't responsible for the generated code, so we delay those
warnings to run-time.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[DELTA]
$Revision: 2.70 $ $Date: 2015/02/05 10:53:00 $
! Makefile.PL
add bin/encguess to EXE_FILES
2.69 2015/02/05 10:35:11
! bin/encguess
Refactored so that
* does not depend on non-core module (File::Slurp in particular)
* PODified document
* -s "encA encB" to -s encA,encB which is more shell-friendly
* and more
! MANIFEST
+ bin/encguess
Pulled: Added CLI wrapper for Encode::Guess
https://github.com/dankogai/p5-encode/pull/32
! Unicode/Unicode.pm
Pulled: Bump $VERSION in module changed since Encode-2.60
https://github.com/dankogai/p5-encode/pull/31
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Guessing the encoding of a report file prepared ahead of time is
really, well, too much guesswork, plus there are at least a couple
of mistakes in the implementation. And we weren't even trying to
guess for reports created on-the-fly in an editor, which is a bit
inconsistent.
So handle prepared reports the same way as on-the-fly reports and
attachments, which means all I/O is done using the :raw layer.
This is only "Unicode-aware" in the sense that we're aware there
are a lot of encodings out there and we're trying not to mangle
them in transit by accidental conversion. We're not doing any
explicit character set conversions and we shouldn't assert in the
MIME headers that we know what character set we're sending because
we don't.
|
|
|
|
| |
When cross-compiling we want to run miniperl etc on the compile host, not the test target
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Try to do input in whatever the locale wants and output raw in
hopes that will best survive mail transport.
Except when reading in a patch file, we'll also use raw for input
because there may be multiple encodings in the patch, and we'll
also use raw for input when reading in the report file that we've
written out raw.
We attempt to detect the locale encoding using the private and
undocumented _get_locale_encoding() function of the deprecated
encoding pragma module. But it's what the open pragma does and
we protect ourselves by checking that it's available and falling
back to an empty layer specification ("<:") if we can't load that
function. That should also give us something workable when there
is no dynamic loading, such as under miniperl.
|
|
|
|
|
|
|
|
|
|
|
| |
The VMS mail utility can't do attachments because it always adds
a blank line in front of any headers you add. So use the Send
From File utility, which has been documented and supported for
any release in the last decade and was latently present before
that.
It takes the whole message verbatim just like sendmail, but also
needs the envelope prepended.
|
|
|
|
|
|
|
|
|
|
|
| |
Log files and other text attachments should also be fine as long
as they aren't big enough to be rejected by RT.
Only text attachments are supported, as other kinds would involve
wrestling with myriad MIME types and possibly content transfer
encodings. This should be fine for binary patches, though, as
git format-patch encodes those in Base85, so the patch file itself
is still text.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Add rules to the Win32 Makefiles to call utils/Makefile.PL to generate
utils/Makefile, and rules to both them and the *nix Makefile to delete
the generated file as part of the cleanup targets.
VMS continues to do its own thing, rather than using utils/Makefile.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This shares all the existing deficiencies of utils/Makefile.SH, and
generates a byte-for-byte identical utils/Makefile, including boilerplate
that claims it was generated by utils/Makefile.SH
utils/Makefile remains as a file checked into the repository, and is not (yet)
deleted, because as-was only *nix platforms could run utils/Makefile.SH to
generate utils/Makefile. This messy state of affairs means that if you build
with static linking, the checked-out utils/Makefile is modified
('../miniperl' is replaced with '../perl')
The next commit will resolve just these bugs.
In turn, it seems that the pre-generated utils/Makefile is only used by
Win32, as VMS contains rules in descrip_mms.template to build the
utilities. Probably the next thing to unpick is the build on VMS, but it
seems better to reduce the size of the "problem" in both utils/Makefile.PL
and vms/descrip_mms.template by attempting to move the work from them to
the extension directories and ExtUtils::MakeMaker.
|
|
|
|
|
|
|
|
| |
Re-parsing patchlevel.h in Perl by perlbug.PL is error prone
and apparently unnecessary. The same information is available
to perlbug via Config::local_patches().
This fixes [perl #118433].
|
| |
|
|
|
|
| |
perl 5.5)
|