Package Details: clockify-desktop 2.0.2-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: custom
Submitter: elmo-space
Maintainer: jankoh
Last Packager: jankoh
Votes: 9
Popularity: 0.005075
First Submitted: 2019-01-14 10:32
Last Updated: 2021-05-08 11:33

Latest Comments

1 2 3 4 Next › Last »

jankoh commented on 2021-06-11 23:30

Hey @Nek.12

as written in the previous comment: The package is broken by upstream at the moment. They (accidentally?) released another version of 2.0.2 that is broken. I can update the package using the new checksums but that will break existing installations as the broken version will not start but throw the mentioned json error at startup. I'm in contact with upstream and have been told a new version will be released soon that will hopefully fix the issue. I can only recommend to stay patient while they fix the issue.

Nek.12 commented on 2021-06-10 18:53

==> ERROR: One or more files did not pass the validity check!
error downloading sources: clockify-desktop

Deleting the cache did not help

jankoh commented on 2021-06-05 12:50

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

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

jankoh commented on 2021-05-03 05:42

@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

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

@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

Installing from YaY solved the issue without extra work:

yay -S clockify-desktop

joshsteele21 commented on 2021-01-13 18:14

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

Thanks, @DendyMb. Package updated.