{"action":"created","issue":{"url":"https://api.github.com/repos/ufo-kit/ufo-filters/issues/129","repository_url":"https://api.github.com/repos/ufo-kit/ufo-filters","labels_url":"https://api.github.com/repos/ufo-kit/ufo-filters/issues/129/labels{/name}","comments_url":"https://api.github.com/repos/ufo-kit/ufo-filters/issues/129/comments","events_url":"https://api.github.com/repos/ufo-kit/ufo-filters/issues/129/events","html_url":"https://github.com/ufo-kit/ufo-filters/issues/129","id":191447899,"number":129,"title":"Debian lintian warning and errors","user":{"login":"picca","id":2741482,"avatar_url":"https://avatars.githubusercontent.com/u/2741482?v=3","gravatar_id":"","url":"https://api.github.com/users/picca","html_url":"https://github.com/picca","followers_url":"https://api.github.com/users/picca/followers","following_url":"https://api.github.com/users/picca/following{/other_user}","gists_url":"https://api.github.com/users/picca/gists{/gist_id}","starred_url":"https://api.github.com/users/picca/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/picca/subscriptions","organizations_url":"https://api.github.com/users/picca/orgs","repos_url":"https://api.github.com/users/picca/repos","events_url":"https://api.github.com/users/picca/events{/privacy}","received_events_url":"https://api.github.com/users/picca/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2016-11-24T07:10:42Z","updated_at":"2016-11-24T09:48:13Z","closed_at":null,"body":"Hello, here I add all the lintian errors.\r\nsome a re packaging releavant and other are intersting.\r\n\r\nCheers\r\n\r\nFred\r\n```\r\n$ lintian -EviI ufo-filters_0.11.1+dfsg1-1_i386.changes\r\nN: Using profile debian/main.\r\nN: Setting up lab in /tmp/temp-lintian-lab-dGD75Ahe_d ...\r\nN: Unpacking packages in group ufo-filters/0.11.1+dfsg1-1\r\nN: ----\r\nN: Processing changes file ufo-filters (version 0.11.1+dfsg1-1, arch source all i386) ...\r\nN: ----\r\nN: Processing source package ufo-filters (version 0.11.1+dfsg1-1, arch source) ...\r\nI: ufo-filters source: vcs-field-uses-insecure-uri vcs-browser http://anonscm.debian.org/cgit/debian-pan/packages/ufo-filters.git\r\nN: \r\nN:    The Vcs-* field uses an unencrypted transport protocol for the URI. It\r\nN:    is recommended to use a secure transport such as HTTPS for anonymous\r\nN:    read-only access.\r\nN:    \r\nN:    Note that you can often just exchange e.g. git:// with https:// for\r\nN:    repositories. Though, in some cases (bzr's \"lp:\" or CVS's pserver) it\r\nN:    might not be possible to use an alternative url and still have a working\r\nN:    (anonymous read-only) repository.\r\nN:    \r\nN:    Severity: wishlist, Certainty: certain\r\nN:    \r\nN:    Check: fields, Type: binary, udeb, source\r\nN: \r\nW: ufo-filters source: timewarp-standards-version (2013-07-27 < 2016-04-06)\r\nN: \r\nN:    The source package refers to a Standards-Version that was released after\r\nN:    the date of the most recent debian/changelog entry. Perhaps you forgot\r\nN:    to update the timestamp in debian/changelog before building the package?\r\nN:    \r\nN:    Severity: normal, Certainty: certain\r\nN:    \r\nN:    Check: standards-version, Type: source\r\nN: \r\nW: ufo-filters source: debian-watch-file-should-mangle-version line 3\r\nN: \r\nN:    The version of this package contains dfsg, ds, or debian, which normally\r\nN:    indicates that the upstream source has been repackaged to comply with\r\nN:    the Debian Free Software Guidelines (or similar reason), but there is no\r\nN:    version mangling in the debian/watch file. Since the dfsg string is not\r\nN:    part of the upstream version, the debian/watch file should use the\r\nN:    dversionmangle option to remove the dfsg before version number\r\nN:    comparison.\r\nN:    \r\nN:    Refer to the uscan(1) manual page and https://wiki.debian.org/DEHS for\r\nN:    details.\r\nN:    \r\nN:    Severity: normal, Certainty: certain\r\nN:    \r\nN:    Check: watch-file, Type: source\r\nN: \r\nN: ----\r\nN: Processing binary package ufo-filters-data (version 0.11.1+dfsg1-1, arch all) ...\r\nI: ufo-filters-data: spelling-error-in-copyright GNU Lesser Public License GNU Lesser General Public License\r\nN: \r\nN:    Lintian found a spelling error in the copyright file. Lintian has a list\r\nN:    of common misspellings that it looks for. It does not have a dictionary\r\nN:    like a spelling checker does. If this is a spelling error in the\r\nN:    upstream license, in supporting email messages, or a case of Lintian\r\nN:    being confused by non-English text, add an override.\r\nN:    \r\nN:    Severity: minor, Certainty: possible\r\nN:    \r\nN:    Check: copyright-file, Type: binary\r\nN: \r\nN: ----\r\nN: Processing binary package ufo-filters-doc (version 0.11.1+dfsg1-1, arch all) ...\r\nI: ufo-filters-doc: spelling-error-in-copyright GNU Lesser Public License GNU Lesser General Public License\r\nI: ufo-filters-doc: possible-documentation-but-no-doc-base-registration\r\nN: \r\nN:    The package ships a .html or .pdf file under /usr/share/doc/, which are\r\nN:    usually documentation, but it does not register anything in doc-base.\r\nN:    (Files under an examples directory are excluded.)\r\nN:    \r\nN:    Refer to Debian Policy Manual section 9.10 (Registering Documents using\r\nN:    doc-base) for details.\r\nN:    \r\nN:    Severity: wishlist, Certainty: possible\r\nN:    \r\nN:    Check: menus, Type: binary\r\nN: \r\nN: ----\r\nN: Processing binary package ufo-filters (version 0.11.1+dfsg1-1, arch i386) ...\r\nI: ufo-filters: hardening-no-fortify-functions usr/lib/i386-linux-gnu/ufo/libufofilterread.so\r\nN: \r\nN:    This package provides an ELF binary that lacks the use of fortified libc\r\nN:    functions. Either there are no potentially unfortified functions called\r\nN:    by any routines, all unfortified calls have already been fully validated\r\nN:    at compile-time, or the package was not built with the default Debian\r\nN:    compiler flags defined by dpkg-buildflags. If built using\r\nN:    dpkg-buildflags directly, be sure to import CPPFLAGS.\r\nN:    \r\nN:    NB: Due to false-positives, Lintian ignores some unprotected functions\r\nN:    (e.g. memcpy).\r\nN:    \r\nN:    Refer to https://wiki.debian.org/Hardening and\r\nN:    https://bugs.debian.org/673112 for details.\r\nN:    \r\nN:    Severity: normal, Certainty: wild-guess\r\nN:    \r\nN:    Check: binaries, Type: binary, udeb\r\nN: \r\nX: ufo-filters: binary-file-built-without-LFS-support usr/lib/i386-linux-gnu/ufo/libufofilterread.so\r\nN: \r\nN:    The listed ELF binary appears to be (partially) built without \"Large\r\nN:    File Support\" (LFS). If so, it may not be able to handle large files or\r\nN:    files with large metadata values (ex: inode numbers) correctly.\r\nN:    \r\nN:    To support large files, code review might be needed to make sure that\r\nN:    those files are not slurped into memory or mmap(2)ed, and that correct\r\nN:    64-bit data types are used (ex: off_t instead of ssize_t), etc. Once\r\nN:    that has been done ensure _FILE_OFFSET_BITS is defined and set to 64\r\nN:    before the relevant files are included. This can be done by using the\r\nN:    AC_SYS_LARGEFILE macro with autoconf, or by appending the output of\r\nN:    getconf LFS_CFLAGS and getconf LFS_LDFLAGS to CFLAGS and LDFLAGS\r\nN:    respectively.\r\nN:    \r\nN:    Take into account that even if this tag is not emitted, that does not\r\nN:    mean the binary is LFS-safe (ie. no OOM conditions, file truncation or\r\nN:    overwrite will happen).\r\nN:    \r\nN:    Also note that enabling LFS on a shared library is not always safe as it\r\nN:    might break ABI in case some of the exported types change size, in those\r\nN:    cases a SOVERSION bump might be required.\r\nN:    \r\nN:    Severity: minor, Certainty: possible\r\nN:    \r\nN:    Check: binaries, Type: binary, udeb\r\nN:    \r\nN:    This tag is marked experimental, which means that the code that\r\nN:    generates it is not as well-tested as the rest of Lintian and might\r\nN:    still give surprising results. Feel free to ignore experimental tags\r\nN:    that do not seem to make sense, though of course bug reports are always\r\nN:    welcome.\r\nN: \r\nX: ufo-filters: binary-file-built-without-LFS-support usr/lib/i386-linux-gnu/ufo/libufofilterringwriter.so\r\nI: ufo-filters: hardening-no-fortify-functions usr/lib/i386-linux-gnu/ufo/libufofilterstdin.so\r\nX: ufo-filters: binary-file-built-without-LFS-support usr/lib/i386-linux-gnu/ufo/libufofilterwrite.so\r\nI: ufo-filters: hardening-no-bindnow usr/lib/i386-linux-gnu/ufo/libufofilteraverage.so\r\nN: \r\nN:    This package provides an ELF binary that lacks the \"bindnow\" linker\r\nN:    flag.\r\nN:    \r\nN:    This is needed (together with \"relro\") to make the \"Global Offset Table\"\r\nN:    (GOT) fully read-only. The bindnow feature trades startup time for\r\nN:    improved security. Please consider enabling this feature or consider\r\nN:    overriding the tag (possibly with a comment about why).\r\nN:    \r\nN:    If you use dpkg-buildflags, you may have to add hardening=+bindnow or\r\nN:    hardening=+all to DEB_BUILD_MAINT_OPTIONS.\r\nN:    \r\nN:    The relevant compiler flags are set in LDFLAGS.\r\nN:    \r\nN:    Refer to https://wiki.debian.org/Hardening for details.\r\nN:    \r\nN:    Severity: wishlist, Certainty: certain\r\nN:    \r\nN:    Check: binaries, Type: binary, udeb\r\nN: \r\nI: ufo-filters: hardening-no-bindnow usr/lib/i386-linux-gnu/ufo/libufofilterbackproject.so\r\nI: ufo-filters: hardening-no-bindnow usr/lib/i386-linux-gnu/ufo/libufofilterbin.so\r\nI: ufo-filters: hardening-no-bindnow ... use --no-tag-display-limit to see all (or pipe to a file/program)\r\nI: ufo-filters: spelling-error-in-binary usr/lib/i386-linux-gnu/ufo/libufofilterlaminobackproject.so paramter parameter\r\nN: \r\nN:    Lintian found a spelling error in the given binary. Lintian has a list\r\nN:    of common misspellings that it looks for. It does not have a dictionary\r\nN:    like a spelling checker does.\r\nN:    \r\nN:    If the string containing the spelling error is translated with the help\r\nN:    of gettext or a similar tool, please fix the error in the translations\r\nN:    as well as the English text to avoid making the translations fuzzy. With\r\nN:    gettext, for example, this means you should also fix the spelling\r\nN:    mistake in the corresponding msgids in the *.po files.\r\nN:    \r\nN:    You can often find the word in the source code by running:\r\nN:    \r\nN:     grep -rw <word> <source-tree>\r\nN:    \r\nN:    This tag may produce false positives for words that contain non-ASCII\r\nN:    characters due to limitations in strings.\r\nN:    \r\nN:    Severity: minor, Certainty: wild-guess\r\nN:    \r\nN:    Check: binaries, Type: binary, udeb\r\nN: \r\nI: ufo-filters: spelling-error-in-binary usr/lib/i386-linux-gnu/ufo/libufofilterremovecircle.so occured occurred\r\nI: ufo-filters: spelling-error-in-copyright GNU Lesser Public License GNU Lesser General Public License\r\nX: ufo-filters: shlib-calls-exit usr/lib/i386-linux-gnu/ufo/libufofilterdfisinc.so\r\nN: \r\nN:    The listed shared library calls the C library exit() or _exit()\r\nN:    functions.\r\nN:    \r\nN:    In the case of an error, the library should instead return an\r\nN:    appropriate error code to the calling program which can then determine\r\nN:    how to handle the error, including performing any required clean-up.\r\nN:    \r\nN:    In most cases, removing the call should be discussed with upstream,\r\nN:    particularly as it may produce an ABI change.\r\nN:    \r\nN:    Severity: wishlist, Certainty: possible\r\nN:    \r\nN:    Check: shared-libs, Type: binary, udeb\r\nN:    \r\nN:    This tag is marked experimental, which means that the code that\r\nN:    generates it is not as well-tested as the rest of Lintian and might\r\nN:    still give surprising results. Feel free to ignore experimental tags\r\nN:    that do not seem to make sense, though of course bug reports are always\r\nN:    welcome.\r\nN: \r\nN: ----\r\nN: Processing binary package ufo-filters-dbgsym (version 0.11.1+dfsg1-1, arch i386) ...\r\n```"},"comment":{"url":"https://api.github.com/repos/ufo-kit/ufo-filters/issues/comments/262733634","html_url":"https://github.com/ufo-kit/ufo-filters/issues/129#issuecomment-262733634","issue_url":"https://api.github.com/repos/ufo-kit/ufo-filters/issues/129","id":262733634,"user":{"login":"picca","id":2741482,"avatar_url":"https://avatars.githubusercontent.com/u/2741482?v=3","gravatar_id":"","url":"https://api.github.com/users/picca","html_url":"https://github.com/picca","followers_url":"https://api.github.com/users/picca/followers","following_url":"https://api.github.com/users/picca/following{/other_user}","gists_url":"https://api.github.com/users/picca/gists{/gist_id}","starred_url":"https://api.github.com/users/picca/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/picca/subscriptions","organizations_url":"https://api.github.com/users/picca/orgs","repos_url":"https://api.github.com/users/picca/repos","events_url":"https://api.github.com/users/picca/events{/privacy}","received_events_url":"https://api.github.com/users/picca/received_events","type":"User","site_admin":false},"created_at":"2016-11-24T09:48:13Z","updated_at":"2016-11-24T09:48:13Z","body":"I do not know yet :), I will try to find some time before next week to cehck what can be done.\n\nCan you see neverthless the BIG file flag problem ?"}}
{"actor":{"display_login":"picca"}}