Because python won't even try to build it.
You only see nis_failed.so if there is an error building it, when
it wanted to build it, and that should be fixed accordingly.
In a nutshell, if the yp headers are installed, python will build
the nis module, otherwise it won't.
On netbsd systems at least, if you have the yp headers installed and
subsequently re-install over the top with MKYP=no you get into the state
where the headers are installed, but the functions are no longer in libc.
This is an error with *your* system - either rebuild with MKYP=yes OR
remove the yp headers from include/rpc and include/rpcsvc.
Follow on fix for PR pkg/53673.
release-3.3.1
Lots of decomplation bugs, especially in the 3.x series fixed. Don't worry though, many more remain.
* Add annotation return values in 3.6+
* Fix 3.6+ lambda parameter handling decompilation
* Fix 3.7+ chained comparision decompilation
* split out semantic-action customization into more separate files
* Add 3.8 try/else
* Fix 2.7 generator decompilation
* Fix some parser failures fixes in 3.4+ using test_pyenvlib
* Add more run tests
Highlights from erlang 21.2 to 21.3:
Kernel:
The standard logger handler, logger_std_h, now has a new internal
feature for log rotation. For full information see the documentation.
SSL:
The Reason part of the error return from the functions connect and
handshake has a better and documented format. This is a potential
incompatibility. See the documentation.
Refactoring of state handling has improved the TLS application data
throughput and reduced CPU overhead
Code optimizations has reduced CPU load for encryption/decryption,
especially for Erlang's distribution protocol over TLS
Now supports active N
Erl_interface:
Support for plugin of a user supplied socket implementation has been added.
OTP:
The HTML reference documentation now shows the OTP version where
modules and functions were first introduced. Versions of OTP older than R13B04 is not shown in the reference
documentation
NAME
perldelta - what is new for perl v5.28.2
DESCRIPTION
This document describes differences between the 5.28.1 release and the 5.28.2 release.
If you are upgrading from an earlier release such as 5.28.0, first read perl5281delta, which describes
differences between 5.28.0 and 5.28.1.
Incompatible Changes
Any set of digits in the Common script are legal in a script run of another script
There are several sets of digits in the Common script. "[0-9]" is the most familiar. But there are also
"[\x{FF10}-\x{FF19}]" (FULLWIDTH DIGIT ZERO - FULLWIDTH DIGIT NINE), and several sets for use in
mathematical notation, such as the MATHEMATICAL DOUBLE-STRUCK DIGITs. Any of these sets should be able to
appear in script runs of, say, Greek. But the previous design overlooked all but the ASCII digits "[0-9]",
so the design was flawed. This has been fixed, so is both a bug fix and an incompatibility.
All digits in a run still have to come from the same set of ten digits.
Modules and Pragmata
Updated Modules and Pragmata
o Module::CoreList has been upgraded from version 5.20181129_28 to 5.20190419.
o PerlIO::scalar has been upgraded from version 0.29 to 0.30.
o Storable has been upgraded from version 3.08 to 3.08_01.
Platform Support
Platform-Specific Notes
Windows
The Windows Server 2003 SP1 Platform SDK build, with its early x64 compiler and tools, was accidentally
broken in Perl 5.27.9. This has now been fixed.
Mac OS X
Perl's build and testing process on Mac OS X for "-Duseshrplib" builds is now compatible with Mac OS X
System Integrity Protection (SIP).
SIP prevents binaries in /bin (and a few other places) being passed the "DYLD_LIBRARY_PATH" environment
variable. For our purposes this prevents "DYLD_LIBRARY_PATH" from being passed to the shell, which
prevents that variable being passed to the testing or build process, so running "perl" couldn't find
libperl.dylib.
To work around that, the initial build of the perl executable expects to find libperl.dylib in the build
directory, and the library path is then adjusted during installation to point to the installed library.
Selected Bug Fixes
o If an in-place edit is still in progress during global destruction and the process exit code (as stored
in $?) is zero, perl will now treat the in-place edit as successful, replacing the input file with any
output produced.
This allows code like:
perl -i -ne 'print "Foo"; last'
to replace the input file, while code like:
perl -i -ne 'print "Foo"; die'
will not.
o A regression in Perl 5.28 caused the following code to fail
close(STDIN); open(CHILD, "|wc -l")'
because the child's stdin would be closed on exec. This has now been fixed.
o "pack "u", "invalid uuencoding"" now properly NUL terminates the zero-length SV produced.
o Failing to compile a format now aborts compilation. Like other errors in sub-parses this could leave
the parser in a strange state, possibly crashing perl if compilation continued.
o See "Any set of digits in the Common script are legal in a script run of another script".
Update ruby26{,-base} to 2.6.3. Here is release announce:
Ruby 2.6.3 Released
Posted by naruse on 17 Apr 2019
Ruby 2.6.3 has been released.
This release adds support for New Japanese Era “令和” (Reiwa). It updates
the Unicode version to 12.1 beta (#15195), and updates date library (#15742).
This release also includes some bug fixes. See details commit logs.
release-3.3.0
First cut at Python 3.8 (many bugs remain)
Reinstate -c | --compile (compile before disassembly) option
The usual smattering of bug and doc fixes
go1.12.2 (released 2019/04/05) includes fixes to the compiler, the go command,
the runtime, and the doc, net, net/http/httputil, and os packages. See the Go
1.12.2 milestone on our issue tracker for details.
go1.12.3 (released 2019/04/08) was accidentally released without its intended
fix. It is identical to go1.12.2, except for its version number. The intended
fix is in go1.12.4.
go1.12.4 (released 2019/04/11) fixes an issue where using the prebuilt binary
releases on older versions of GNU/Linux led to failures when linking programs
that used cgo. Only Linux users who hit this issue need to update.
go1.11.7 (released 2019/04/05) includes fixes to the runtime and the net
packages. See the Go 1.11.7 milestone on our issue tracker for details.
go1.11.8 (released 2019/04/08) was accidentally released without its intended
fix. It is identical to go1.11.7, except for its version number. The intended
fix is in go1.11.9.
go1.11.9 (released 2019/04/11) fixes an issue where using the prebuilt binary
releases on older versions of GNU/Linux led to failures when linking programs
that used cgo. Only Linux users who hit this issue need to update.
Changelog:
Changes from 4.2.1 to 5.0.0
---------------------------
1. Support for the POSIX standard %a and %A printf formats has been added.
2. The test infrastructure has been greatly improved, simplifying the
contents of test/Makefile.am and making it possible to generate
pc/Makefile.tst from test/Makefile.in.
3. The regex routines have been replaced with those from GNULIB, allowing
me to stop carrying forward decades of changes against the original
ones from GLIBC.
4. Infrastructure upgrades: Bison 3.3, Automake 1.16.1, Gettext 0.19.8.1,
makeinfo 6.5.
5. The undocumented configure option and code that enabled the use of
non-English "letters" in identifiers is now gone.
6. The `--with-whiny-user-strftime' configuration option is now gone.
7. The code now makes some stronger assumptions about a C99 environment.
8. PROCINFO["platform"] yields a string indicating the platform for
which gawk was compiled.
9. Writing to elements of SYMTAB that are not variable names now
causes a fatal error. THIS CHANGES BEHAVIOR.
10. Comment handling in the pretty-printer has been reworked almost completely
from scratch. As a result, comments in many corner cases that were
previously lost are now included in the formatted output.
11. Namespaces have been implemented! See the manual. One consequence of this
is that files included with -i, read with -f, and command line program
segments must all be self-contained syntactic units. E.g., you can no
longer do something like this:
gawk -e 'BEGIN {' -e 'print "hello" }'
12. Gawk now uses the locale settings for ignoring case in single byte
locales, instead of hardwiring in Latin-1.
13. A number of bugs, some of them quite significant, have been fixed.
See the ChangeLog for details.
openbsd requires mapping the stack with MAP_STACK. binaries not doing this
will not run. patch taken from openbsd ports, via sjmulder.
I modified it to use GOOS_openbsd, because other OSes are not provided
an implementation of sysMarkStack.
Bump PKGREVISION.
* vulnerabilities of rubygems are already fixed in 2.4.5nb1.
Ruby 2.4.6 Released 1 Apr 2019
Ruby 2.4.6 has been released.
This release includes about 20 bug fixes after the previous release, and also
includes several security fixes. Please check the topics below for details.
* Multiple vulnerabilities in RubyGems
See the commit log for details.
After this release, we will end the normal maintenance phase of Ruby 2.4, and
start the security maintenance phase of it. This means that after the release
of 2.4.6 we will never backport any bug fixes to 2.4 except security fixes.
The term of the security maintenance phase is scheduled for 1 year. By the
end of this term, official support of Ruby 2.4 will be over. Therefore, we
recommend that you start planning to upgrade to Ruby 2.6 or 2.5.
