Search Criteria
Package Details: tutanota-desktop-bin 227.240502.0-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/tutanota-desktop-bin.git (read-only, click to copy) |
---|---|
Package Base: | tutanota-desktop-bin |
Description: | Official Tutanota email client |
Upstream URL: | https://tuta.com |
Licenses: | GPL-3.0-or-later |
Conflicts: | tutanota-desktop, tutanota-desktop-linux |
Provides: | tutanota-desktop |
Submitter: | yochananmarqos |
Maintainer: | yochananmarqos (ajgraves) |
Last Packager: | yochananmarqos |
Votes: | 45 |
Popularity: | 1.09 |
First Submitted: | 2019-12-23 17:19 (UTC) |
Last Updated: | 2024-05-02 17:39 (UTC) |
Dependencies (5)
- alsa-lib
- gtk3 (gtk3-ubuntuAUR, gtk3-no_deadkeys_underlineAUR, gtk3-patched-filechooser-icon-viewAUR, gtk3-classic-xfceAUR, gtk3-classicAUR)
- libsecret
- nss (nss-hgAUR)
- openssl (openssl-gitAUR, openssl-staticAUR) (make)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 Next › Last »
kainonergon commented on 2020-02-05 10:13 (UTC)
@ajgraves, I've checked that
grep Update /opt/tutanota-desktop/resources/app-update.yml
indeed givespublishAutoUpdate: false
with package versions 3.66.7-2, 3.67.2-1, and 3.67.3-1.ajgraves commented on 2020-02-04 14:23 (UTC)
@kainonergon, can you try the command
grep Update /opt/tutanota-desktop/resources/app-update.yml
and see what the output is? It should saypublishAutoUpdate: false
but just want to confirm.ajgraves commented on 2020-02-04 13:38 (UTC)
I have published the update to 3.67.3.
When the checksum validation fails, that means there's a new version available from Tutanota. This condition usually won't last long, as we're typically quick to get the package updated.
@kainonergon, I'll dig into this some as I thought we had that fixed.
<deleted-account> commented on 2020-02-04 13:17 (UTC)
There is a new version: 3.67.3
carloshmm commented on 2020-02-04 12:53 (UTC)
I'm getting this error now:
kainonergon commented on 2020-02-04 05:12 (UTC) (edited on 2020-02-04 11:25 (UTC) by kainonergon)
Following message still pops up every time the application starts and an update is available: "Oh no! The update process has failed. We'll try again later." EDIT. This happens with 3.66.7-2 and 3.67.2-1
tycrek commented on 2020-02-03 18:39 (UTC)
@yochananmarqos: It is working now, thank you
yochananmarqos commented on 2020-02-03 18:20 (UTC)
@tycrek: Does it still happen with 3.67.2?
tycrek commented on 2020-02-03 18:14 (UTC)
Trying to update with
yay
, doingcleanBuild
, however the package will not pass the validity check. Specifically:ajgraves commented on 2020-01-15 16:09 (UTC)
I have updated to the latest version, and made a fix to the PKGBUILD to add a version to the linux-sig.bin file. This is necessary because some AUR helpers such as yay will not download a file remotely if it already exists locally. This is the same reason there is a version number appended to the AppImage since the file name never changes upstream.
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 Next › Last »