The format of debian/changelog is very rigid as it is parsed by the
build tools to determine the version number and other information.
The version number must use ~ so that 1.3.0 is considered greater than
1.3.0~rc2 for upgrades, and there must be a Debian release number like
-1 because this is not a Debian-native package. Finally, the default
urgency is medium these days.
Signed-off-by: Anders Kaseorg <andersk@mit.edu>
Unaligned data on ARM architectures do not perform efficiently unaligned
memory access, and in the case of ARMv7 and iOS it completely breaks. The OCB
algorithm dereferences a uint64x2_t pointer, and is replaced by a
memcpy to avoid penalties when trying to align it.
More info https://brewx.qualcomm.com/bws/content/gi/common/appseng/en/knowledgebase/docs/kb95.html
This reverts commit f002e3bb30.
That commit appears to have created a race between ssh restoring
termios state and mosh-client initializing termios.
Probably fixes#844.
Also makes this bit of code more readable, but the overall handling of
Unicode characters in Actions and Transitions is messy, and may get
reworked later.
I was recommended to use mosh as "an in-place replacement for ssh" by
my friends, and take a while to figure out the message until I
realized I missed the line "The Mosh package should be installed on
both the client and server."
If this line often corresponds to missing server-side installation,
rather than other mysterious scenario, how about adding a hint?
These should output to stdout and exit with status 0. Passing
std-options to AM_INIT_AUTOMAKE causes ‘make installcheck’ (hence also
‘make distcheck’) to verify this.
Signed-off-by: Anders Kaseorg <andersk@mit.edu>
A character cell can only be either narrow or wide. It's more
convenient to represent that as an int containing 1 or 2, but slightly
more correct to represent it as a "boolean" single-bit integer.
The terminal framebuffer was not resetting the wrap state of a row
when a previously-wrapping line was overwritten by a non-wrapping
line. Restore previous, subtle behavior of line wrap. Fix wrap
verification bug now exposed by emulation-wrap-across-frames.test.
Also hoist some getters, mostly for clarity.
Fixes#820.
None of the previous tests even ran the mosh script unless tmux ≥ 1.8 is
installed. Thus ‘make check’ was “passing” on, e.g., RHEL 6 even though
its Perl is too old (5.10.1).
Signed-off-by: Anders Kaseorg <andersk@mit.edu>
This builds an OS X package and deploys it to a GitHub release when a
tag is pushed. It also generates a tarball reporting the build
environment and configuration. The build log is still separate.
This is not yet final, it deploys to cgull/mosh and not
mobile-shell/mosh.
It should not affect Linux or OS X CI builds (other than the change to
the Travis Xcode 7.1 image).
Included changes:
The Travis Xcode 7 image seems to have added tmux while we were gone,
breaking our Homebrew setup.
There seems to be no clean reliable way to determine whether a
Homebrew package is installed or needs updating. Reinstalling is less
efficient but seems to work reliably.
The OS X build is now split between four files:
.travis.yml contains Travis-specific CI/release build configuration.
macosx/brew.sh contains Homebrew-specific package manager installs and
reporting.
macosx/osx-xcode.sh contains Apple-specific OS/X and Xcode reporting.
macosx/build.sh does the actual package build.
On Perl < 5.14, we can use Socket::GetAddrInfo from CPAN to replace the
missing getaddrinfo functionality of Socket.
Socket::GetAddrInfo < 0.22 requires :newapi in the import list, but 0.22
forbids it and enables the new API by default.
Signed-off-by: Anders Kaseorg <andersk@mit.edu>
The root problem here is that writes to the frame buffer may alter it,
but leave it with the same contents as before, and the diff between
the two states is the empty string. With the dirty-rows,
smart-pointer changes to Framebuffer, it is easy to run into this
situation. This got Network::TransportSender confused about timeouts,
and mosh-server would spin.
The theoretically correct fix would be to have operator==() exactly
correspond to diff(otherstate).empty(). I have partly implemented
this (and may yet finish) but it's not trivial to get right.
This is a much simpler fix that simply attempts to correctly update
timers when two framebuffers are different and an empty diff is
generated.
John Hood