Arch Linux User Repository

@yochananmarqos the tutanota-desktop-linux package was not uninstalled as part of the process. It wasn't touched at all. The makepkg process succeeded but once you go to install the package, it's unable to install because it's trying to overwrite some files that belong to tutanota-desktop-linux (like the launcher in /usr/bin, etc). It worked fine by doing "pacman -R tutanota-desktop-linux" and then installing the tutanota-desktop-bin package.

@ajgraves: I'm not sure what you're talking about. Installing this package will remove tutanota-desktop-linux and install this. That's what replaces does.

@arp12: There's no way to make package transition smooth in the AUR. Your expectations are unrealistic. Remember, you're responsible for managing the AUR packages you install.

Looks like you will need to uninstall the old package, then install this package, however you won't lose settings, cache, etc. Unless @yochananmarqos has another idea.

@arp12 we should be able to fix that by using a “replaces=“ line in the PKGBUILD. I can’t add that right now but should be able to in a couple of hours if it hasn’t been done already.

Edit: disregard, the replaces variable is already set.

Hmm I expected the migration to be smoother for users and not require manual actions. I'm getting this today which means user experience is broken and trust lost because of simple package rename:

:: Searching AUR for updates... -> Missing AUR Packages: tutanota-desktop-linux there is nothing to do

@yochananmarqos I can't believe I didn't check the file permissions... good grief!

I've gone ahead and created tutanota-desktop-bin and submitted the request to merge this package into it.

The reason why the AppRun was not executing was due to having the wrong permissions. It was 640 instead of 644.

@yochananmarqos would be glad to have the help. As you can tell, I've still got a lot to learn!

@arp12: I'd be happy to contribute.

@ajgraves:

I'll work on renaming the package as soon as I figure out the proper way to do so.

You would submit a new package called tutanota-desktop-bin, then submit a request to merge this one into it. See AUR Submission guidelines: Requests.

As for the depends, technically those aren't necessary anyways since all this is doing is running the AppImage.

That's true, I was making my own PKGBUILD attempting to run it unpacked when I was composing that.

As for not executing AppRun, I don't call that anywhere in any of the code used for the package. Not sure where you're seeing that commented out. Can you elaborate?

The commented out bits imply that's what would be happening. The only way to run it unpacked is with AppRun or using the system Electron to execute the app.asar, but neither work for some reason.

You can also add signature checking to the prepare() array, see How do I verify the signature of the desktop client?

    # Validate the signature against public key
    set -e
    openssl dgst -sha512 -verify tutao-pub.pem -signature linux-sig.bin "$pkgname-$pkgver.AppImage"
    set +e

The name is 'tutanota-desktop-linux' because it's the original name of the binary file Tutanota officially produces. I created this package because it didn't exist, but very quickly @ajgraves offered his support in managing it. He's the main contributor here.

If you @yochananmarqos would like to help fix the issues you highlighted, I would be happy to add you as a contributor.

I'm also happy to disown the package if someone with more time and experience would like to take it over for the greater good.