On 2022-05-17 16:57:55 +0200, Axel Beckert wrote: > > Concerning this bug, it was reported upstream 3 months ago, and > > there is still no reaction there. > > You are aware, that at least for mosh the Debian package maintainer > and main upstream developer of Mosh is the same person? So actually > the forwarding of this bug report into the upstream bug tracker was an > upstream reaction itself.
I didn't know that. So I'm wondering why he hasn't done anything for 3 months. Also note that /usr/share/doc/mosh/README.md.gz says A note on compiler flags: Mosh is security-sensitive code. When making automated builds for a binary package, we recommend passing the option `--enable-compile-warnings=error` to `./configure`. On GNU/Linux with `g++` or `clang++`, the package should compile cleanly with `-Werror`. Please report a bug if it doesn't. I assume that this is the real reason for the current failure. But the -Wdeprecated-declarations warning (which is thus changed into an error) isn't related to security. BTW, warnings may also come from macros provided by libraries, if any. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
