summaryrefslogtreecommitdiff
path: root/debian/libfuzzylite5.1v5.lintian-overrides
diff options
context:
space:
mode:
authorGianfranco Costamagna <locutusofborg@debian.org>2016-08-13 14:33:03 +0100
committerGianfranco Costamagna <locutusofborg@debian.org>2016-08-13 14:33:03 +0100
commitc8420407cab7cdb112fb8b9cec7eaaebb3af73fd (patch)
tree044408e3122ffeea7c356a05729976c5c943df48 /debian/libfuzzylite5.1v5.lintian-overrides
parent0e8c1c9d31d15034b1ff1062c9bf0bfcdc849dd9 (diff)
parent59fd708e8df2286bf221956d702e9c7c0e71bc5d (diff)
fuzzylite (5.1+dfsg-3.1) unstable; urgency=medium
* Non-maintainer upload, with maintainer permission [ Steve Langasek ] * Fix up symbols file for symbols that are not part of the ABI and are optimized away at -O3 (Closes: #819142). [ Gianfranco Costamagna ] * Fix build failure with gcc-6 with upstream help (Closes: #811880) * Update symbols. [dgit import unpatched fuzzylite 5.1+dfsg-3.1]
Diffstat (limited to 'debian/libfuzzylite5.1v5.lintian-overrides')
-rw-r--r--debian/libfuzzylite5.1v5.lintian-overrides10
1 files changed, 10 insertions, 0 deletions
diff --git a/debian/libfuzzylite5.1v5.lintian-overrides b/debian/libfuzzylite5.1v5.lintian-overrides
new file mode 100644
index 0000000..fdda54a
--- /dev/null
+++ b/debian/libfuzzylite5.1v5.lintian-overrides
@@ -0,0 +1,10 @@
+# In the words of the author of fuzzylite, Juan Rada-Vilela:
+#
+# The calls to exit() happen on static methods signalHandler and terminate, both
+# of which are optionally configured by the program, not the library. The library
+# will not use either of these methods unless a program explicitly asks these
+# methods to be used. These are just handy/example methods. I would expect
+# programs to provide their own handling of signals instead.
+#
+# See: https://github.com/fuzzylite/fuzzylite/issues/4
+libfuzzylite5.1v5 binary: shlib-calls-exit