[mosh-devel] Please test mosh 1.2 release candidate

[Nick Mason]

That did the trick, thanks!


On 24/04/2012, at 12:59 , Keith Winstein wrote:

> Thanks, Nick, for your timely report.
> 
> We've tracked this down to a bug in the Red Hat package
> (https://bugzilla.redhat.com/show_bug.cgi?id=815587).
> 
> We have reverted the change that depended on this header file for now,
> so your problem should be fixed in:
> 
> https://github.com/downloads/keithw/mosh/mosh-1.1.97.tar.gz
> 
> We'd be grateful if you could confirm that's the case.
> 
> Best regards,
> Keith
> 
> On Mon, Apr 23, 2012 at 8:56 PM, Nick Mason <nmason at atlassian.com> wrote:
>> Attached!
>> 
>> 
>> 
>> 
>> 
>> On 24/04/2012, at 10:47 , Keith Winstein wrote:
>> 
>>> Thanks for testing. Yes, we are targeting CentOS 5. Can you please
>>> send me the "config.log" output?
>>> 
>>> On Mon, Apr 23, 2012 at 8:37 PM, Nick Mason <nmason at atlassian.com> wrote:
>>>> Hi Keith,
>>>> 
>>>> Were you targeting CentOS 5 with this release? The build from source still doesn't work. :) It gets up to building in "network" then falls over:
>>>> 
>>>> 
>>>> make[3]: Entering directory `/home/nmasonmosh-1.1.95/src/network'
>>>>  CXX    network.o
>>>>  CXX    networktransport.o
>>>>  CXX    transportfragment.o
>>>> transportfragment.cc:20:44: error: google/protobuf/io/gzip_stream.h: No such file or directory
>>>> transportfragment.cc: In member function ‘TransportBuffers::Instruction Network::FragmentAssembly::get_assembly()’:
>>>> transportfragment.cc:130: error: ‘GzipInputStream’ was not declared in this scope
>>>> transportfragment.cc:130: error: expected `;' before ‘gzip_stream’
>>>> transportfragment.cc:131: error: ‘gzip_stream’ was not declared in this scope
>>>> transportfragment.cc: In member function ‘std::vector<Network::Fragment, std::allocator<Network::Fragment> > Network::Fragmenter::make_fragments(const TransportBuffers::Instruction&, int)’:
>>>> transportfragment.cc:175: error: ‘GzipOutputStream’ has not been declared
>>>> transportfragment.cc:175: error: expected `;' before ‘gzip_options’
>>>> transportfragment.cc:176: error: ‘gzip_options’ was not declared in this scope
>>>> transportfragment.cc:176: error: ‘GzipOutputStream’ has not been declared
>>>> transportfragment.cc:177: error: ‘GzipOutputStream’ was not declared in this scope
>>>> transportfragment.cc:177: error: expected `;' before ‘gzip_stream’
>>>> transportfragment.cc:178: error: ‘gzip_stream’ was not declared in this scope
>>>> make[3]: *** [transportfragment.o] Error 1
>>>> make[3]: Leaving directory `/home/nmasonmosh-1.1.95/src/network'
>>>> make[2]: *** [all-recursive] Error 1
>>>> make[2]: Leaving directory `/home/nmasonmosh-1.1.95/src'
>>>> make[1]: *** [all-recursive] Error 1
>>>> make[1]: Leaving directory `/home/nmasonmosh-1.1.95'
>>>> make: *** [all] Error 2
>>>> 
>>>> 
>>>> The protobuf, protobuf-devel, and protobuf-compiler packages are all installed (v2.3.0, according to yum).
>>>> 
>>>> Cheers,
>>>> Nick
>>>> 
>>>> 
>>>> 
>>>> On 23/04/2012, at 14:05 , Keith Winstein wrote:
>>>> 
>>>>> Hello all,
>>>>> 
>>>>> Thanks for all your hard work on mosh! We have a release candidate for
>>>>> mosh 1.2:
>>>>> 
>>>>> https://github.com/downloads/keithw/mosh/mosh-1.1.95.tar.gz
>>>>> 
>>>>> This is the first "post-deluge" release, and adds many improvements based
>>>>> on our experience with mosh in the real world, including:
>>>>> 
>>>>> * Helpful error messages for a variety of common problems
>>>>> 
>>>>> * Locale passing in mosh (so less likely to get UTF-8-related errors)
>>>>> 
>>>>> * Eliminates Boost and skalibs as dependencies
>>>>> 
>>>>> * Fixes to build on FreeBSD, Cygwin, RHEL 5, OS X 10.5 on PPC
>>>>> 
>>>>> * Improved responsiveness
>>>>> 
>>>>> * Bugfixes and improvements re: terminal emulation and startup
>>>>> 
>>>>> * Uses binary "hardening" compilation flags by default
>>>>> 
>>>>> ===
>>>>> 
>>>>> Please test the release candidate on your systems (and package managers)
>>>>> and let us know of any problems. I'm particularly concerned that our
>>>>> binary hardening flags may conflict with those on some distributions -- we
>>>>> already had to override this on Ubuntu and I have heard reports that it
>>>>> may also be a problem on Arch Linux.
>>>>> 
>>>>> If all goes well, we should have mosh 1.2 by the end of the week.
>>>>> 
>>>>> Thanks all,
>>>>> Keith
>>>>> 
>>>>> for the mosh developers
>>>>> _______________________________________________
>>>>> mosh-devel mailing list
>>>>> mosh-devel at mit.edu
>>>>> http://mailman.mit.edu/mailman/listinfo/mosh-devel
>>>> 
>> 
>>