Package Details: rescuetime2

Git Clone URL: (read-only, click to copy)
Package Base: rescuetime2
Description: Application time-tracking for Linux. Stable version
Upstream URL:
Keywords: rescuetime rescuetime2
Licenses: proprietary
Conflicts: rescuetime
Submitter: ElXreno
Maintainer: ElXreno
Last Packager: ElXreno
Votes: 54
Popularity: 0.95
First Submitted: 2019-01-06 07:02
Last Updated: 2020-03-05 15:47

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »

chopps commented on 2017-05-04 12:34

The pkgver() is auto-bumping the version to and so the PKGBUILD doesn't match the .SRCINFO again and fails. :)

I think updating to pkgver= + pkgrel=1 (and .SRCINFO) should fix things.

wanderingfree commented on 2017-05-02 05:57

Switched to sha256sums, thanks @chopps.

I've noticed that yaourt is also experiencing the same issue (not pulling the latest update even when the pkgrel is updated.) I could solve this by updating the pkgver, but I'm reluctant to do so because then, until the next release, the version will not agree with the version on the release notes, and it might cause some confusion.

So, for now my recommendation is, when you're updating between releases, clear your yaourt / pacaur cache (or at least delete the cached rescuetime source files).

chopps commented on 2017-04-29 13:38

I think .SRCIFNO didn't get updated in any case it fails if you have the previous version in your .cache/pacaur cache, as pacaur is trying to re-use the old rpm and failing the md5 check. Also should probably switch to sha256sums.

wanderingfree commented on 2017-04-26 03:19

Updated md5sums. Thanks all.

t_vb commented on 2017-04-19 13:13

Had to replace MD5-sums in order to build.


wanderingfree commented on 2017-04-06 03:35

@poppingtonic I've already updated the package.

wanderingfree commented on 2017-04-05 10:12

Updated to . I'll update the changelog once the changelog on the site has been updated.

chopper commented on 2017-04-04 14:27

There is an update for linux.
Can you please update it?

jhenriquez commented on 2017-03-28 08:25

Do I need to manually start rescuetime every time? I guess it does need to be running locally. I already was able to activate the computer. But Shouldn't there be something like a systemctl service or anything that allows me to start this on the background?

Thanks in advance, sorry If I'm missing something silly :)

wanderingfree commented on 2017-03-20 04:57

@tomas.novoselic I'm still checking regularly for updates on the sources for rescuetime. However, I have also flagged xprintidle as out of date (latest version seems to be 0.2-10 on launchpad).

If there is no maintainer action within 3 days, I'll request to take over the package and update it myself.

For now, rescuetime is working fine on my system with the old version of xprintidle though.