Package Details: clockify-desktop 2.2.9-1

Git Clone URL: https://aur.archlinux.org/clockify-desktop.git (read-only, click to copy)
Package Base: clockify-desktop
Description: Truly free time tracker for teams, Desktop App
Upstream URL: https://clockify.me
Licenses: LicenseRef-custom
Submitter: elmo-space
Maintainer: jankoh
Last Packager: jankoh
Votes: 15
Popularity: 0.018219
First Submitted: 2019-01-14 10:32 (UTC)
Last Updated: 2024-12-14 08:40 (UTC)

Dependencies (25)

Required by (0)

Sources (1)

Latest Comments

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

jankoh commented on 2021-06-05 12:50 (UTC)

Hey there,

the package fails to build at the moment since upstream changed something in the package. I can provide an updated package, but a newly built one fails to run giving the error message:

A JavaScript error occurred in the main process Uncaught Exception: Error: /tmp/.org.chromium.Chromium.su4vxk: failed to map segment from shared object at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:160:31) at Object.Module._extensions..node (internal/modules/cjs/loader.js:722:18) at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:169:18) at Module.load (internal/modules/cjs/loader.js:602:32) at tryModuleLoad (internal/modules/cjs/loader.js:541:12) at Function.Module._load (internal/modules/cjs/loader.js:533:3) at Module.require (internal/modules/cjs/loader.js:640:17) at require (internal/modules/cjs/helpers.js:20:18) at Object.<anonymous> (/opt/Clockify/resources/app.asar/node_modules/active-windows/index.js:1:178) at Object.<anonymous> (/opt/Clockify/resources/app.asar/node_modules/active-windows/index.js:5:3)

I contacted upstream about the issue and waiting for response. As on now (2021-06-05) do not rebuild the package; it will fail.

rickslash commented on 2021-05-04 16:00 (UTC)

@jankoh, thanks for the update, worked no problem :)

jankoh commented on 2021-05-03 05:42 (UTC)

@rickslash,

please remove the existing deb before updating, so your building system downloads the latest version. It'll work after that. I'll provide an updated version correcting the need to do that.

rickslash commented on 2021-05-03 02:56 (UTC)

Thanks @jankoh

Latest update doesnt work:

Making package: clockify-desktop 2.0.1-1 (Sun 02 May 2021 21:54:47 CDT) ==> Retrieving sources... -> Found Clockify_Setup.deb ==> Validating source files with sha512sums... Clockify_Setup.deb ... FAILED ==> ERROR: One or more files did not pass the validity check! error downloading sources: clockify-desktop

jankoh commented on 2021-03-01 11:19 (UTC)

@rickslash "yay -S clockify-desktop" just installs the package "as is" from the aur. This works because the package is up-to-date. :-D

As upstream still uses their brain-dead release strategy, I now established a build pipeline running once a day using the current package from upstream, so I get informed by a failing pipeline, if anything changes in the deb-package. They sometimes release more than on version by day, so there still might be misses, but they should be fixed quite soon.

Best, Jan

rickslash commented on 2021-03-01 10:49 (UTC)

Installing from YaY solved the issue without extra work:

yay -S clockify-desktop

jost21 commented on 2021-01-13 18:14 (UTC)

In case this happens again in the future, it might be an option to edit the build file and enter SKIP for the checksum (https://www.linuxsecrets.com/archlinux-wiki/wiki.archlinux.org/index.php/PKGBUILD.html). This seems to be not too much of a security risk, since clockify doesn't provide a checksum to compare it to on their website anyway (at least I couldn't find it). Correct me, if I'm wrong :)

jankoh commented on 2021-01-13 07:15 (UTC)

Thanks, @DendyMb. Package updated.

DenysMb commented on 2021-01-13 03:04 (UTC) (edited on 2021-01-13 03:05 (UTC) by DenysMb)

The current version is 1.8.61-1 and the checksum is: fe4e85ae0006817b0fa5dbe55dd2f1e5291a5f1c85df0846ccb6aa26c855cfeed4ad3517e9d30dbe59ae794306121f81c200aa1cc685fbb081d0ad2f24e596fd

amaxcz commented on 2020-12-07 07:33 (UTC)

Please update package if not hard... thanks!

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