[FFe] Sync Mosh 1.3.0 instead of release candidate
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mosh (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
Zesty currently has Mosh 1.3.0~rc2-1 (release candidate 2), synced from Debian sid.
Mosh upstream released the final version 1.3.0 yesterday, March 25. It is now in Debian sid and built successfully on all Debian architectures.
Could you please sync the final 1.3.0 release from Debian?
Debdiff attached. There are no changes in the upstream ChangeLog. There are almost no changes to the Mosh source code, other than (1) updating the version number to 1.3.0, and (2) working around a regression in OpenBSD's "pledge". This latter code is guarded by a HAVE_PLEDGE macro and does not affect builds on Linux. The other changes relate to improving the test suite for locale-related code when running in an sbuild chroot (e.g., on the Debian buildds).
We (upstream and Debian maintainer) would be grateful if the Ubuntu 17.04 release could include the final release of Mosh 1.3.0, instead of the release candidate. It would reduce our support burden and increase uniformity across platforms. Thank you for your consideration.
This bug was fixed in the package mosh - 1.3.0-1
Sponsored for Keith Winstein (keithw)
---------------
mosh (1.3.0-1) unstable; urgency=medium
* Version 1.3.0 released to unstable.
-- Keith Winstein <email address hidden> Sat, 25 Mar 2017 12:55:31 -0700
mosh (1.3.0~rc3-1) experimental; urgency=medium
* Workaround for Debian bug #817236 on buildds
-- Keith Winstein <email address hidden> Fri, 03 Mar 2017 02:21:02 -0800