Package Details: timekpr-next 0.5.10-1

Git Clone URL: https://aur.archlinux.org/timekpr-next.git (read-only, click to copy)
Package Base: timekpr-next
Description: Control the computer usage of users. You can limit daily usage based on a timed access duration and configure periods of day when they can log in.
Upstream URL: https://launchpad.net/timekpr-next
Keywords: limit time timekpr track
Licenses: GPL
Conflicts: timekpr, timekpr-beta, timekpr-next-beta, timekpr-next-git, timekpr-revived-bzr
Provides: timekpr
Submitter: SanskritFritz
Maintainer: SanskritFritz (Mjasnik)
Last Packager: Mjasnik
Votes: 9
Popularity: 0.000004
First Submitted: 2019-09-09 20:01 (UTC)
Last Updated: 2026-08-17 06:58 (UTC)

Dependencies (12)

Required by (0)

Sources (1)

Latest Comments

1 2 Next › Last »

Mjasnik commented on 2026-08-20 09:59 (UTC) (edited on 2026-08-20 16:06 (UTC) by Mjasnik)

I am not quite sure what do you mean by "download fails". Package can be installed as usual.

I know that there were AUR issues some days back, that was why I was not able to update the package to the latest version, but it should be fine now.

kuestenpepe commented on 2026-08-16 10:13 (UTC)

Download fails. I guess the old version became unavailable with the version bump earlier this month.

GonerGenesis commented on 2025-12-23 10:43 (UTC)

error: failed to download sources for 'timekpr-next-0.5.9-1'

wampire commented on 2025-12-22 17:24 (UTC)

Hey! The checksum seems to be wrong!

SanskritFritz commented on 2021-03-15 14:51 (UTC)

Ennoia you probable have a former downloaded timekpr-next-0.5.1.tar.gz there. It has changed over the last few days.

Ennoia commented on 2021-03-15 14:32 (UTC)

Hi it seems you don't have the right checksum for the source code.

SanskritFritz commented on 2021-03-15 09:49 (UTC)

Thanks, updated the package.

Mjasnik commented on 2021-03-15 09:14 (UTC)

Hi, upstream here. The release should be ok, I even double checked the files and the changes are there as well as the changelog. There was a re-release of the same file, that's why md5sum in PKGBUILD was not according to the file itself, the correct md5sum is 290fd2e172b2189fa65858e59189c1c4.

SanskritFritz commented on 2021-03-13 09:26 (UTC)

Yes, upstream mistakenly updated the release with an unreleased change in the changelog file. I reported the problem upstream. You may use the new checksum in the meanwhile, only the changelog has been changed (so far).

zwei commented on 2021-03-13 03:45 (UTC) (edited on 2021-03-13 03:46 (UTC) by zwei)

I was getting some checksum verification errors with the AUR helper I was using. I think the current definition for md5sums in the PKGBUILD is incorrect based on what's listed on the md5 link for the 0.5.1 tar. Updated the PKGBUILD locally and it installed happily.