CSV output: timestamp inaccuracy and Y-2038 problem

[Thomas Dreibholz]

bwm-ng has two issues with the unix timestamp written for CSV output:
* It uses (int)time(NULL) -> With 32-bit "int" type, it has the Y-2038 problem.
* Calling "bwm-ng -o csv -F x.csv" causes bwm-ng to write 2 measurements per second (i.e. every 0.5 seconds), but the time stamp granularity is 1 second => two measurements for the same time stamp.

Upstream bug report: https://github.com/vgropp/bwm-ng/issues/19
Upstream pull request with fix: https://github.com/vgropp/bwm-ng/pull/20

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bwm-ng 0.6.1-5
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Jun 24 14:34:54 2018
InstallationDate: Installed on 2018-04-13 (71 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
SourcePackage: bwm-ng
UpgradeStatus: No upgrade log present (probably fresh install)

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "bwm-ng-timestamp.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]