Package Details: maestral-git 1.4.4-1

Git Clone URL: (read-only, click to copy)
Package Base: maestral-git
Description: A light-weight and open-source Dropbox client.
Upstream URL:
Keywords: dropbox maestral python
Licenses: MIT
Conflicts: maestral
Provides: maestral
Submitter: bbaserdem
Maintainer: bbaserdem
Last Packager: bbaserdem
Votes: 0
Popularity: 0.000000
First Submitted: 2019-07-30 18:15
Last Updated: 2021-05-21 19:05

Latest Comments

1 2 3 Next › Last »

bbaserdem commented on 2020-07-13 15:35

@Pietro_Pizzi that error has nothing to with the pkgbuild; its the python-dropbox package in community repo that needs to be updated when you see that error.

Independently; the package has been updated to reflect the recent requirement changes.

Pietro_Pizzi commented on 2020-05-29 11:30

LANG=en_DK.UTF-8; yay -S maestral-git ==> Error: Could not find all required packages: python-dropbox<=9.5.0 (Wanted by: maestral-git)

yay python-dropbox 1 community/python-dropbox 10.1.2-1 (1005.7 KiB 16.2 MiB) (Installed)

bbaserdem commented on 2020-04-06 09:48

Done! Feel free to make any changes.

My plan has been to make this package build split packages; maestral-cli-git and maestral-gui-git to reflect the changes in the repo. The base name should remain as it is. I see no point in having seperate pkgbuilds for two packages.

coxackie commented on 2020-03-29 16:55

@bbaserdem - please make me co-maintainer if you wish. We should change the name of this to maestral-cli-git, most probably, and update latest dependencies.

coxackie commented on 2020-03-16 08:35

That would be good, in fact. I think that python-atomicwrites is a new dependency for 0.6.2, and I do not think python-rubicon-objc is needed. Furthermore, you may want to use the service file from here. The advantage is that it informs if the daemon was not successfully launched.

bbaserdem commented on 2020-03-15 23:42

I'm trying to manage multi-package building; since the author split this package into two. (Maestral and maestral-gui)

bbaserdem commented on 2020-02-05 20:03

@coxackie, the repo was updated so I updated a lot of dependencies, and created new packages for the dependencies. Everything works as far as I am concerned.

I will probably abandon this package when a stable release rolls out and push a stable release package cause the development is too fast; I rather not be such hands on maintainer for this package.

coxackie commented on 2020-01-29 00:02

utterly awesome, @bbaserdem. I will test soon. Maybe it would be a good idea to switch to actual releases instead of git after the upcoming one. it will also save you some trouble in chasing dependencies all the time. It appears that the project is moving towards stability.

bbaserdem commented on 2020-01-28 20:18

I included some service files. I tested them and are working fine. However, the main branch (not the PKGBUILD) is outdated, and will not work; as stated here Until this bug is resolved, the main branch won't work. Good news is we are nearing a stable release!

If you want to install through pacman/aur helper right now; you can build this project and have it run without the Pyro5 cyclic import error by checking out the dev branch (in the PKGBUILD sources array, add '#branch=develop' at the end of the url.) I use aurutils, which lets you edit the PKGBUILD before building. This branch builds fine, but it will not work due to missing dependencies. The one that is needed to work is python-bugsnag, which is not packaged in arch. This, I won't package (since it is prob only needed for this specific branch and not master branches) so a solution right now is to install it from pypi (pip install --user bugsnag) which will make it so that the dev build runs.

There are two service files that I provided. One is for a single instance, the other one is for multiple instances running concurrently. If you have a single instance, enable and start the background daemon with 'systemctl --user enable --now maestral.service' . If you have multiple config files; run 'systemctl --user enable --now maestral-config@<NAME>.service' for each one you want running in the background. This way you have a daemon running in the background. You can interface with the daemon by running 'maestral status' or 'maestral gui' (optionally include --config-name <NAME>) I suggest putting an autostart file in .config/autostart/maestral-gui.desktop . I will provide an autostart file once I figure out how to auto-generate it.

I am not removing the python-systemd dependence; because it is needed during build to make maestral play nice with systemd. (Also it is a pain to get optdeps working in my clean chroot build script) The new dependencies you mentioned are in the develop branch only; and are there because the developer is logging a bunch of information. The changes probably won't make it in the main branch; if they do I will add the missing packages.

Also, @coxackie it is all adhoc info learnt along the way, and just doing file searches in github. It is fun to look into projects you are using; especially if you are planning on making your own software projects down the future.

coxackie commented on 2020-01-27 14:21

many thanks @bbaserdem. you certainly seem to be way more knowledgeable on this - what I find peculiar is when I installed maestral using pip last week (per the instructions in the github page), it does not (at least to my recollection) install python-systemd. I can check again later and let you know for sure.

Edit: while I was writing this, 40 minutes ago, the requirements.txt was changed in the dev branch. python-systemd is not there anymore - but there is a bunch of other additions. I still think a systemd unit would make sense, though.