Bug#918774: Simple method of verifying this bug

2019-01-09 Thread Alan W. Irwin
In fact, it turned out that the libLASi-1.1.0 version of MissingGlyphExample.cpp did not verify this bug. So I looked more carefully at the PLplot results, and the first problem of this kind occurred for Unicode U+2648 = ♈. So I tried that glyph in MissingGlyphExample.cpp using the following pat

Bug#797968: release debian-patched version to fix SSL errors?

2019-01-09 Thread Marcel Partap
Hey, as there has been no upstream elinks release since six years and none is in sight, how about shipping a version in debian with these TLS patches applied? Also, there have been 115 commits in git since last release, some of them mention ssl errors.. Missing SNI (or whatever causes this) is a

Bug#918774: liblasi0: response to missing system glyphs no longer works correctly

2019-01-09 Thread Alan W. Irwin
Package: liblasi0 Version: 1.1.0-2 Severity: important Dear Maintainer, Since one of my recent Debian Buster upgrades I have been getting the following run-time errors with libLASi when a missing system glyph is encountered: terminate called after throwing an instance of 'std::runtime_error' w