Search Criteria
Package Details: superproductivity-bin 14.1.0-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: | 31 |
Popularity: | 1.41 |
First Submitted: | 2020-10-26 19:09 (UTC) |
Last Updated: | 2025-07-12 15:53 (UTC) |
Dependencies (2)
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- nss (nss-hgAUR)
Latest Comments
1 2 3 Next › Last »
alosarjos commented on 2025-06-07 08:38 (UTC)
As said before @Nowaker, to have checksums, first I would need to have them provided by upstream. As the Integrity section of the PKGBUILD page says:
https://wiki.archlinux.org/title/PKGBUILD
So either we need to have checksums on the release section of the Github.
https://github.com/johannesjo/super-productivity/releases/tag/v13.0.10
I have helped johannesjo, and he is at this point owner of the package. I have submitted a pull request to the Github repository to try to have this fixed on upstream.
Just have some patience. IF you need the latest package right now, if you download the PKGBUILD and run makepkg -si you will get the latest package.
And please stop with marking it as outdated as clearly that's not the way to ask for PKGBUILD changes. I have already answered you multiple times and provided a solution upstream.
Nowaker commented on 2025-06-07 03:04 (UTC)
Please stop this nonsense. This package is maintained by you - alosarjos. Whether it's connected to GitHub Actions or anything else is irrelevant. The manifest currently in https://aur.archlinux.org/superproductivity-bin.git is out of date. Simply push the change yourself, or keep it flagged as out of date until such a moment when this PKGBUILD is finally updated. Don't play stupid. You have full push rights to this AUR repo - USE THEM!
alosarjos commented on 2025-06-06 10:18 (UTC)
As provided by PKGBUILD page on the Wiki:
The checksum type and values should always be those provided by upstream, such as in release announcements.
Since this package is updated from a GitHub Action, the correct and valid way to fix adding a checksum is from the App GitHub repository. Doing it manually here will be for nothing since next release will generate another PKGBUILD without the Checksum.
Please step with the Spam, the AUR package is kept updated by the app developer himself with help from Arch users.
alosarjos commented on 2025-06-06 05:48 (UTC)
App is maintained through GitHub Actions. @johannesjo is not an Arch User, and I helped him years ago preparing the release of the app through GitHub Actions the best we could, I already submitted days ago a patch applying @Dominiquini suggestions, but he must be busy. If you want to change anything on the PKGBUILD I suggest doing a pull request on the repo.
cg505 commented on 2025-05-30 23:10 (UTC)
I hit the same problem.
@johannesjo could you make this change? Ideally also remove the SKIP for md5sums and use an actual md5sum of the source file, which would have caught this issue.
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:
1 2 3 Next › Last »