Search Criteria
Package Details: nextcloud-talk-desktop-bin 1.1.7-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/nextcloud-talk-desktop-bin.git (read-only, click to copy) |
---|---|
Package Base: | nextcloud-talk-desktop-bin |
Description: | Nextcloud Talk Desktop client based on Nextcloud Talk web application bundling |
Upstream URL: | https://github.com/nextcloud/talk-desktop |
Licenses: | AGPL-3.0-only |
Provides: | nextcloud-talk-desktop |
Submitter: | matthiasqui |
Maintainer: | matthiasqui |
Last Packager: | matthiasqui |
Votes: | 6 |
Popularity: | 0.38 |
First Submitted: | 2024-02-10 17:07 (UTC) |
Last Updated: | 2025-04-18 22:10 (UTC) |
Latest Comments
1 2 Next › Last »
vawaver commented on 2025-04-11 04:58 (UTC)
v1.1.6 is available - be so kind and update.
vawaver commented on 2025-02-25 12:11 (UTC)
Can I ask you for the update to latest version v1.1.5 - Talk v21.0.0?
matthiasqui commented on 2025-01-21 23:16 (UTC)
@BlueCase Yeah sorry that was unintended, thanks
BlueCase commented on 2025-01-21 23:06 (UTC)
@matthiasqui In your last commit you removed in nextcloud-talk.desktop "Type=Application". By this the Desktop Starter will not longer be visible under Applications in GNOME.
matthiasqui commented on 2025-01-11 21:07 (UTC)
@BlackIkeEagle Thanks, I will include that in the next update.
BlackIkeEagle commented on 2025-01-08 16:04 (UTC)
Suggestion for the desktop file (The categories did not work properly under plasma-desktop) + taken the generic name and startupnotify from the flatpak desktop entry
matthiasqui commented on 2024-12-29 10:56 (UTC)
Thanks @pheerai, they changed it with the 1.0 release to not have the version number in the archive name and I did not realize this would cause problems with aur helpers. Should be fixed now!
pheerai commented on 2024-12-28 11:24 (UTC)
Would it make sense to download the zip-file to a location that contains the version number, instead of plain
Nextcloud.Talk-linux-x64.zip
? That could omit the caching issue, since package builders won't believe they already downloaded the file (which is still residing there from previous builds)fred118 commented on 2024-12-06 11:40 (UTC)
@matthiasqui @mrwsl same for me. Cleaning the cache worked. Thank you for the tips.
mrwsl commented on 2024-12-04 09:31 (UTC)
@matthiasqui Had the sha mismatch too, and can confirm that cleaning the cache did solve the problem.
1 2 Next › Last »