TickTick has a new version 8.0.0. Seems to be working with a simple version bump. My patch:
index 99dd285..219013c 100644
--- a/.SRCINFO
+++ b/.SRCINFO
@@ -1,6 +1,6 @@
pkgbase = ticktick
pkgdesc = Official desktop application for Linux
- pkgver = 6.0.40
+ pkgver = 8.0.0
pkgrel = 1
url = https://ticktick.com/download
install = ticktick.install
@@ -22,9 +22,9 @@ pkgbase = ticktick
source = LICENSE
sha256sums = 422ab230ea6a54ba9a44db25b1395d71bd52fc3add0cab13bbc95d86f769416e
sha256sums = 2d866fcb749c30d931fa96cc1578869b3fa9fc61a5c5f30e0316ddb00abb5814
- source_x86_64 = ticktick-6.0.40-amd64.deb::https://d2atcrkye2ik4e.cloudfront.net/download/linux/linux_deb_x64/ticktick-6.0.40-amd64.deb
- sha256sums_x86_64 = d1e06c0ffa8509a2bf22cbb85c956f7bef1306cb202c0b0208cd461cddb73c89
- source_aarch64 = ticktick-6.0.40-arm64.deb::https://d2atcrkye2ik4e.cloudfront.net/download/linux/linux_deb_arm64/ticktick-6.0.40-arm64.deb
- sha256sums_aarch64 = 5122a6c9d8b2798f0889b7be79b706726c28ed7244c3f1047ff398e0fb12ae5f
+ source_x86_64 = ticktick-8.0.0-amd64.deb::https://d2atcrkye2ik4e.cloudfront.net/download/linux/linux_deb_x64/ticktick-8.0.0-amd64.deb
+ sha256sums_x86_64 = b3c984eba4efdd3c8be2b32fa24e9c33954cea9cd6c4f922be24b7d0a59c375a
+ source_aarch64 = ticktick-8.0.0-arm64.deb::https://d2atcrkye2ik4e.cloudfront.net/download/linux/linux_deb_arm64/ticktick-8.0.0-arm64.deb
+ sha256sums_aarch64 = 2e07dae3e5591f55c800c66befe462c31675b26b3040e8ac3a19854a0da9c931
pkgname = ticktick
diff --git a/PKGBUILD b/PKGBUILD
index 8347341..fb1d696 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,7 +1,7 @@
# Maintainer: Agustin Cisneros <agustincc@tutanota.com>
pkgname=ticktick
-pkgver=6.0.40
+pkgver=8.0.0
pkgrel=1
pkgdesc='Official desktop application for Linux'
arch=('x86_64' 'aarch64')
@@ -16,8 +16,8 @@ source_x86_64=("${pkgname}-${pkgver}-amd64.deb::https://d2atcrkye2ik4e.cloudfron
source_aarch64=("${pkgname}-${pkgver}-arm64.deb::https://d2atcrkye2ik4e.cloudfront.net/download/linux/linux_deb_arm64/${pkgname}-${pkgver}-arm64.deb")
sha256sums=('422ab230ea6a54ba9a44db25b1395d71bd52fc3add0cab13bbc95d86f769416e'
'2d866fcb749c30d931fa96cc1578869b3fa9fc61a5c5f30e0316ddb00abb5814')
-sha256sums_x86_64=('d1e06c0ffa8509a2bf22cbb85c956f7bef1306cb202c0b0208cd461cddb73c89')
-sha256sums_aarch64=('5122a6c9d8b2798f0889b7be79b706726c28ed7244c3f1047ff398e0fb12ae5f')
+sha256sums_x86_64=('b3c984eba4efdd3c8be2b32fa24e9c33954cea9cd6c4f922be24b7d0a59c375a')
+sha256sums_aarch64=('2e07dae3e5591f55c800c66befe462c31675b26b3040e8ac3a19854a0da9c931')
package() {
tar -xf data.tar.xz -C "${pkgdir}"
Pinned Comments
Aerz commented on 2025-04-01 09:21 (UTC)
Breaking Change in 6.0.30-2: Config File Moved
With the latest update (6.0.30-2), the user flags configuration file has been relocated for better consistency. This aligns with common Arch Linux packaging practices and TickTick’s existing config directory structure.
Please, you should move your config file:
Thanks @OJFord for pointing this out.
Aerz commented on 2023-11-16 18:03 (UTC) (edited on 2025-04-01 09:31 (UTC) by Aerz)
Custom Flags Support for TickTick
I recently pushed an update to v2.0.0, introducing a helper script to launch TickTick with custom (Electron) flags. Previously, this wasn't possible, making it hard to enable Wayland support. Fortunately, TickTick now allows this.
How to configure it:
Create the flags file:
Add your Electron flags, one per line (comments are ignored):
Run TickTick