According to the changelog, it seems not to be a bug fixing only release: * [tg] Shut up a bogus gcc warning during configuration process * [tg] Spell AT&T consistently in the source code * [tg] Tweak mksh(1) manual page, from wbx@ and «lewellyn:#ksh» * [tg] dot.mkshrc: fix $@ vs. $* mix-up * [tg] dot.mkshrc: add DJB cdb hash function * [tg] Sync with oksh: fix Vi editing mode word erase handling, again * [tg] Skip whitespace between POSIX style shell function name and its definition parenthesēs during detection if an alias of the same name already exists to be more robust (Debian Closes: #535970) * [tg] Build system improvements for ACK and nwcc, both on Debian sid * [tg] Fix spelling error in changelog discovered by Lintian * [tg] Aligh “set -o nounset” / “set -u” behaviour with future POSIX standard, as discussed with GNU bash maintainers, David Korn from AT&T ksh93, and The Open Group; prompted by use in Debian; Closes: #539538 * [tg] add an unsupported way to make printf(1) a builtin * [tg] Build system and regression test code and comment improvements: better and more comments matching reality better; more reliability w.r.t. passed CPPFLAGS; more of the MKSH_SMALL changes may be overridden, all of them are now enumerated on the webpage; fixed some breakage; portability * [tg] MKSH_NOPWNAM and MKSH_SMALL will now both disable the ~fac/ (homedir) expansion code wholly if defined, not just getpwnam(3) calls * [tg] shells without job control no longer define the standard “stop” and “suspend” aliases (they are pointless anyway); regression tests know * [tg] use system RCS ID macros on MirBSD if decent enough * [tg] shut up bogus gcc 4.5/trunk warnings caused by over-optimisation * [tg] restore ANSI C compilability broken in R38 (speed up, even) * [tg] use memcpy(3) ipv strlcpy(3) if possible and safe and secure
Do you confirm? If it's the case, motu-release should be subscribed, for a FFe. Thanks, Fabrice -- Please merge mksh 39.1-3 (universe) from Debian testing (main) https://bugs.launchpad.net/bugs/446132 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs -- universe-bugs mailing list universe-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/universe-bugs