arpon (3.0-ng+dfsg1-1) unstable; urgency=low
* Maintain arpon in pkg-security (Closes: #866832).
* Imported Upstream version 3.0-ng.
- Repacked without doc which contains the linkedin logo and pre-compiled
PDFs without the source, violating the DFSG.
- Drop existing patches, as the new version is a rewrite.
- The libdumbnet library is now properly detected without using
lsb-release (Closes: #783536).
- The permissions of the log file are now 0640 and owned by root:root, the
file is no longer world readable (Closes: #614518).
- Stderr is properly redirected to /dev/null (Closes: #614027).
* Update README.Debian: Mention missing documentation due to repack.
* Update debian/copyright:
- Convert to machine readable format.
- Update for new version.
- Add Files-Excluded for automatic uscan repacking without the doc dir.
* Update debian/watch to deal with dfsg version suffix.
* Package using git-buildpackage:
- Add Vcs-{Git,Browser} to debian/control.
- Add debian/gbp.conf.
* Update to debhelper compatibility level 10, cleanup of debian/rules.
* Drop Build-Depends on lsb-release.
* Introduce a patch to fix gcc-7 compile errors.
* Introduce a patch to adjust the installed files and paths.
* Cleanup of control files:
- Remove dirs, no longer needed.
- Cleanup docs.
- Prefix control files with packagename where appropriate.
* Fix spelling errors in man page.
* Add patch to remove unwanted build options.
* Remove the pre-3.0 configuration file /etc/arpon.sarpi.
- Explain the change in debian/NEWS.
* Remove the /var/log/arpon folder in postrm (not just the contents).
* Simplify and adjust init script for the new version:
- Allow it to start multiple instances of arpon for different interfaces.
- Support the status option.
* Adjust logrotate configuration:
- Only keep 4 weekly rotations.
- Cleanup of unneeded options.
- Updated the postrotate script for usage with systemd.
* Provide a systemd service file.
* Update /etc/default/arpon for new version and init script / service file.
* Bump Standards-Version to 4.1.0.
* Compile with NDEBUG, otherwise the log is flooded with debug messages that
cannot be disabled.
-- Lukas Schwaighofer <email address hidden> Thu, 07 Sep 2017 20:26:55 +0200