Search Criteria
Package Details: superproductivity-bin 13.0.4-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/superproductivity-bin.git (read-only, click to copy) |
---|---|
Package Base: | superproductivity-bin |
Description: | ToDo list and Time Tracking |
Upstream URL: | http://super-productivity.com/ |
Licenses: | MIT |
Conflicts: | superproductivity, superproductivity-git |
Provides: | superproductivity |
Submitter: | alosarjos |
Maintainer: | alosarjos (johannesjo) |
Last Packager: | johannesjo |
Votes: | 30 |
Popularity: | 2.86 |
First Submitted: | 2020-10-26 19:09 (UTC) |
Last Updated: | 2025-05-14 16:14 (UTC) |
Dependencies (2)
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-patched-filechooser-icon-viewAUR, gtk3-classicAUR, gtk3-classic-xfceAUR)
- nss (nss-hgAUR)
Latest Comments
1 2 3 Next › Last »
Dominiquini commented on 2025-05-13 19:57 (UTC)
@tixwho:
Change the source to:
source=("superproductivity-${pkgver}-amd64.deb::https://github.com/johannesjo/super-productivity/releases/download/v${pkgver}/superProductivity-amd64.deb")
tixwho commented on 2025-05-13 19:01 (UTC)
Hi, I realized that superproductivity was NEVER upadted recently until I remove all the AUR cache.After digging through it I found that the current PKGBUILD will actually skip the attempt to download latest .deb file despite changing the source given the existence of the .deb with the same name in the cache folder (which is actuall the old version .deb; It will then proceed to extract and package the old .deb into a new version .tar.zst -- As a result, the version number in pacman is being updated, while the actual version of binary (as seen in "settings") is never updated.And because md5 verification for .deb was skipped, pacman could not catch the problem as well.
Before my manual intervention, the version stayed at Nov 202, exactly the time of last PR. I am not very familiar with PKGBUILD, but I wonder is it possible to rename the downloaded .deb file to a name with version number so pacman does not silently package the new version with old .deb?
siliconmeadow commented on 2024-11-09 02:48 (UTC)
Thank you @alosarjos! @thea - you did the right thing. I suspect @alosarjos had a few urgent priorities, but you should find that the latest one will no longer have the 404 error.
alosarjos commented on 2024-11-08 17:23 (UTC)
Thanks @siliconmeadow, forgot about the filename of the artifact.
siliconmeadow commented on 2024-11-08 16:14 (UTC)
@alosarjos - until your PR is merged upstream, and a new release is created upstream, I think you'll need to update this repo one more time. I think this patch will work for you:
thea commented on 2024-11-08 10:43 (UTC) (edited on 2024-11-08 10:43 (UTC) by thea)
@tovo I tried to understand the AUR rules of submission [1] and did a comment as stated
I also wrote the maintainer an email. Is there a better way to do ? I used the package repo, but am unsure how to propose the changes.
tovo commented on 2024-11-08 10:33 (UTC)
Thanks @thea,
Did you made a submit request to integrate your corrections?
thea commented on 2024-11-08 07:41 (UTC)
As @manzu said 10.1.1-2 failed for me too.
I fixed the PKGBUILD with
manzu commented on 2024-11-08 03:44 (UTC)
Getting the following error.
Joey5403 commented on 2024-11-07 08:15 (UTC)
package path is change from /opt/superProductivity/ to /opt/Super Productivity/
will not create the softlink
1 2 3 Next › Last »