Package Details: whatpulse 5.8.2-1

Git Clone URL: https://aur.archlinux.org/whatpulse.git (read-only, click to copy)
Package Base: whatpulse
Description: Measures your keyboard, mouse and application usage, network traffic and uptime.
Upstream URL: http://www.whatpulse.org
Keywords: external statistics
Licenses: custom:whatpulse_tos
Submitter: jelly
Maintainer: ekkelett (ahmubashshir)
Last Packager: ahmubashshir
Votes: 26
Popularity: 0.017012
First Submitted: 2009-06-07 19:22 (UTC)
Last Updated: 2024-08-06 05:42 (UTC)

Latest Comments

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 Next › Last »

kokx commented on 2013-03-01 18:33 (UTC)

Doesn't compile anymore with the qt change to qt5. The dependency of qt should be changed to qt4. I created a new PKGBUILD: https://gist.github.com/kokx/5066717

maleadt commented on 2013-02-01 20:42 (UTC)

Updated to 2.0.4, seems to be a maintenance release only. Release notes at http://whatpulse.org/blog/106/

maleadt commented on 2013-01-23 21:48 (UTC)

Package updated with new checksum for 64bit version. Turned out only the README had changed, although it initially seemed like the binaries had changed as well (must have been an error of mine).

sh4wn commented on 2013-01-23 17:12 (UTC)

Yeah read about 2.0.2 too, but it still doesn't detect any network interfaces here.

maleadt commented on 2013-01-23 13:04 (UTC)

Hm, scratch that, 2.0.2 seems to be segfaulting on autopulse, a known issue. I suppose I will wait with updating until the update appears on the homepage. Concerning the differences in checksums for the 64bit client, I'll update the package as soon as I know more.

maleadt commented on 2013-01-23 12:59 (UTC)

I've posted a message on their forum; but meanwhile I discovered 2.0.2 has (silently) been released. Since it fixes network interface detection on Linux, a problem I have been running into on different computers, I'm updating the package.

maleadt commented on 2013-01-23 12:49 (UTC)

Strange. Version 2.0.1 has been released at 2012-12-31, yet the 64bit tarball has a timestamp of 2013-01-13. Having a closer look at the tarball, it seems that the binary within has changed (differend md5, quite a bit larger) yet its timestamp is still 2012-12-31...

sh4wn commented on 2013-01-23 12:39 (UTC)

I have a different md5sum for the 64bit version: 85770ecdf14bdbf1e6c40a6ecb449ff1

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 Next › Last »