Package Details: aafm-git 20140930-1

Git Clone URL: (read-only, click to copy)
Package Base: aafm-git
Description: Android ADB File Manager.
Upstream URL:
Licenses: GPL3
Conflicts: aafm
Provides: aafm
Submitter: cyker
Maintainer: cyker
Last Packager: cyker
Votes: 75
Popularity: 0.030800
First Submitted: 2012-08-23 04:15
Last Updated: 2015-07-20 15:04

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

Firef0x commented on 2014-10-06 11:34

Hello, @cyker !

When I execute the following command in the terminal, it works fine:

$ sudo aafm

So it means that the latest version requires root privilege to run somehow, while the previous one (20120414-4) doesn't. This seems to make 'aafm.desktop' useless.

Is there any workaround to make 'aafm.desktop' work again???

Hope for your reply!

Yours sincerely,

cyker commented on 2014-10-03 20:05

@Firef0x aafm is written in python2. The PKGBUILD file also uses python2. python2 and python3 are different. The package builds fine on my machine and I don't know how you got a python3.4 error. The reason may be an incomplete dependency list but I'm not quite sure. If you are sure something is missing please kindly tell me. Thanks.

Firef0x commented on 2014-10-03 18:15

I've added the binary package to my own repository.
Pls visit and add my repository, then execute `sudo pacman -S aafm-git` to install the package.

The following is Simplified Chinese translation:
请访问 并添加我的仓库,然后执行 `sudo pacman -S aafm-git` 来安装本包。

Firef0x commented on 2014-10-03 18:13

Hello, @cyker !

Thx for your updating and maintaining!

First, I am just confused with the meaning of the pkgver '20120414', and glad to see that you give it the meaning "last commit date". AFAIK, project 'aafm' is very casual in its version, it doesn't even have an 'About' dialog to tell the version, and doesn't push the tag 'r5' for its 5th version.

What's more, I've packaged this package in OpenSUSE Build Service successfully. The new PKGBUILD is much more machine-friendly than the older one.

Furthermore, after I installed the latest version of aafm-git, I execute it from the terminal. However, it just outputs the following and exit unexpectly:


Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/aafm/", line 5, in <module>
import gtk
File "/usr/lib/python2.7/site-packages/gtk-2.0/gtk/", line 40, in <module>
from gtk import _gtk
File "/usr/lib/python3.4/site-packages/cairo/", line 2
SyntaxError: Non-ASCII character '\xc2' in file /usr/lib/python3.4/site-packages/cairo/ on line 3, but no encoding declared; see for details


Did you or anyone else have the same problem? Should I report this to the upstream?

Hope for your reply!

Yours sincerely,

cb474 commented on 2014-10-03 06:28

By the way, for aafm users, there were a whole bunch of new commits last week, in case people want to update.

cyker commented on 2014-10-03 04:03

Hi @Firef0x,

Thanks for the update notice. Now I've checked and included most of your changes and listed you as a contributor. What I don't really like is the pkgver. First, it doesn't make sense specifying the same value in two different ways. Second, the format, though recommended, doesn't seem to be easily understood by the users. If one's gonna use a -git version of a package, then showing the last change time makes more sense.

Let me know whether the new PKGBUILD works for you.

Firef0x commented on 2014-10-02 08:40

Hello, @cyker !

Thx for your submitting and maintaining! As the project 'aafm' runs again and the new commits come, I think it's time to open this topic -- Consider to refactor PKGBUILD.

You wrote this PKGBUILD 2 years ago, and used an old-style packaging method. Yes, it works, and works perfectly of course. But starting with pacman 4.1, the VCS sources should be specified in the source=() array and should be treated like any other source. What's more, the 'pkgver' autobump is now achieved via a dedicated pkgver() function. So I think it would be good to refactor the PKGBUILD to fit in the new-style method.

The following is what I think the new PKGBUILD should be:

It has a new pkgver() function, and moves the git cloning to the source=() array. It obeys the VCS PKGBUILD Guidelines, and could be auto-packaged by OpenSUSE Build Service.(in which the current one fails to be)

Is it worth a shot?? Hope for your reply!



cb474 commented on 2014-08-30 06:44

Okay. Thanks again.

cyker commented on 2014-08-30 03:51

@cb474 Use yaourt. It helps get the PKGBUILD and then makepkg on it.

cb474 commented on 2014-08-30 03:50


To ask a novice question, how do I do that? Would it accomplish the same thing to reinstall aafm with yaourt?