p5-Test-Differences: update to 0.7300.
0.73 2026-10-03
- Changes to tests only, to cope with changes to how line numbers
are reported in what will become perl 5.46 (thanks to Richard Leach)
p5-Moose: update to 2.4001.
Set HOMEPAGE.
2.4001 2026-10-01
[TESTS]
- adapted a test to changes in perl 5.45.4 regarding the line number
reported for particular errors (Richard Leach, #188)
p5-Future: update to 0.53.
0.53 2026-09-30
[CHANGES]
* Add documentation to point at the `Future::XS` distribution
* Defend unit tests against changes to perl's reporting of line
numbers in code involving multi-line anonymous subroutines
(Perl #24396)
p5-Exception-Class: update to 1.46.
1.46 2026-09-27
- If you use Exception::Class to create a class whose module file is already loaded, it no longer
overwrites the %INC entry for that module with the path to Exception/Class.pm. Typically, this
happens when you have a package that implements an exception with the same name as the package
itself. Implemented by Graham Knop (@haarg). PR #17.
- Similarly, if a package defines a $VERSION, this is no longer overwritten when the exception class
is defined with Exception::Class. Implemented by Graham Knop (@haarg). PR #18.
p5-DateTime-TimeZone: update to 2.71.
2.71 2026-09-30
- This release is based on version 2026d of the Olson database. This release includes contemporary
changes for Manitoba, CA.
py-nodeenv: update to 1.11.0
New Features
* feat(certifi): optionally use certifi certificates
* feat(nodeenv): accept npm-style semver ranges in --node
* feat(nodeenv): add --prefer-system to use system node when available
* feat(nodeenv): add --isolate-npm to keep npm config inside the
environment
* feat(nodeenv): install local packages from a requirements file
* feat(nodeenv): write the posix activate on Windows for git-bash
Fixed bugs
* fix: repair Windows CI (ZipFile.extractall filter, test_smoke layout)
* fix(nodeenv): replace leftover debug print with logger.debug
* fix(nodeenv): stop -p from reinstalling node that is already there
* fix(nodeenv): let -p target a virtualenv nodeenv isn't installed in
* fix(nodeenv): report the url and proxy instead of a traceback
[24 lines not shown]
etc/etc.evbarm/Makefile.inc: follow-on hash generation fix
Revs. 141 & 142 introduced a guard that tried to prevent checksum
consolidation from running in contexts where there's nothing to process
-- that is, images aren't created at all. However, it then also
prevented clean builds that do include images from consolidating their
checksums as intended, since the "exists" check that was added reflects
too early a file system state on clean builds ("gzimg" doesn't exist
yet). It also didn't address the fact that there can be targets that
do in fact create and populate a "gzimg" directory, yet don't actually
generate any images as presently construed/defined are relevant for
hash generation, as happens with the evbearmv4-el arch.
Another fix for PR install/59195. Tested with earmv5hf (no images, no
"gzimg" directory created), evbearmv4-el (no images, "gzimg" directory
is created), and aarch64 (images and "gzimg" directory are created),
with clean builds into new directory structures and subsequent update
builds tested for each arch.
Prefer using ${.PARSEDIR} over assuming that ${.CURDIR} is src/lib/libc.
Mostly this changes ${.CURDIR} refs into either ${.PARSEDIR}, ${LIBCDIR},
or ${NETBSDSRCDIR} refs.
Set LIBCDIR earlier to ensure it's available always.
This will be used to build a smaller libc (eg, with no assert strings.)
Tested builds on atari, x86-64, arm64, and vax.
Yet another printf format fix...
Use PRI[diuoxX]PTR for [u]intptr_t types rather than PRId64.
Pointers (and hence [u]intptr_t's) are not 64 bits in ILP32 systems.
I picked 'x', well, just because ...
And this time I verified it builds on i386!
Fix wacky printf usage - hopefully unbreak 32 bit builds
Rather than converting an int type to a (void *) and then
printing using %p (one presumes to obtain hex), use the PRIx64
(the value is int64_t) macro (just like previous output lines do)
instead. (Use the '#' printf flag as well, to get the 0x when
needed, and just 0 if the value is 0).
As it was, 32 bit builds would complain about converting between
a pointer and an integer of a different size - converting it to
intptr_t before void * would have fixed that, but would lose the
top 32 bits of the value on 32 bit systems.
kqueue/kernel/t_pipe: Fix newly failing test.
If the read side of a pipe has been closed, then for the write side:
- poll will set POLLOUT, not POLLNVAL (nor fail with EBADF), and
- select will report writable, not fail with EBADF,
because the write side is immediately writable and will fail with
EPIPE/SIGPIPE -- it won't block if you try to write.
So surely kqueue with EVFILT_WRITE should simply report immediately
writable too, not fail with EBADF. And that is what I caused to
happen by simplifying and clarifying the code and fixing various edge
cases. (The bad response that this test was added to check is a
kernel crash on null pointer dereference; that, fortunately, has not
regressed.)
PR kern/59056: poll POLLHUP bugs
