Package Details: go-mtpfs-git 20200111-1

Git Clone URL: https://aur.archlinux.org/go-mtpfs-git.git (read-only, click to copy)
Package Base: go-mtpfs-git
Description: Simple tool for viewing MTP devices as FUSE filesystems
Upstream URL: http://github.com/hanwen/go-mtpfs
Licenses: BSD
Submitter: wmarshall
Maintainer: valandil
Last Packager: valandil
Votes: 138
Popularity: 0.62
First Submitted: 2012-08-03 20:06
Last Updated: 2020-02-15 02:15

Dependencies (4)

Required by (1)

Sources (1)

Latest Comments

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

Firefishe commented on 2013-11-14 11:53

I'm using a Samsung SGH-I747 (Galaxy S3/AT&T/US). I've followed the wiki instructions for appending 15-android.rules (in /usr/lib/udev/rules.d/).

I'm a bit confused as to the syntax of that file, though. The line I created for the phone is:

# Galaxy S3 SGH-I747
ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", SYMLINK+="android_adb", OWNER="username"

Then I do this command: (I'm already in the directory so I use "." I've also tried it outside the directory, using normal syntax.)

$ go-mtpfs .
/usr/bin/fusermount: user has no write access to mountpoint /home/username/mountpoint
2013/11/14 05:23:34 mount failed: fusermount exited with code 256.

Here is a pastebin link showing the SAMSUNG portion of my 15-android.rules file:

http://pastie.org/8479806

Any help is appreciated. Thanks in advance. --Stephen

Firefishe commented on 2013-11-14 11:44

I'm using a Samsung SGH-I747 (Galaxy S3/AT&T/US). I've followed the wiki instructions for appending 15-android.rules (in /usr/lib/udev/rules.d/).

I'm a bit confused as to the syntax of that file, though. The line I created for the phone is:

# Galaxy S3 SGH-I747
ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", SYMLINK+="android_adb", OWNER="username"

$ go-mtpfs .
/usr/bin/fusermount: user has no write access to mountpoint /home/username/mountpoint
2013/11/14 05:23:34 mount failed: fusermount exited with code 256

I've double-checked my user's addition to the fuse usergroup, and all seems okay. I created a mountpoint directory in my own /home/username directory, and I get that error.

Any help is appreciated. Thanks --Stephen Brown

Firefishe commented on 2013-11-14 11:42

I'm using a Samsung SGH-I747 (Galaxy S3/AT&T/US). I've followed the wiki instructions for appending 15-android.rules (in /usr/lib/udev/rules.d/).

I'm a bit confused as to the syntax of that file, though. The line I created for the phone is:

# Galaxy S3 SGH-I747
ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", SYMLINK+="android_adb", OWNER="username"

$ go-mtpfs .
/usr/bin/fusermount: user has no write access to mountpoint /home/username/mountpoint
2013/11/14 05:23:34 mount failed: fusermount exited with code 256

Anonymous comment on 2013-08-14 16:23

# github.com/hanwen/go-mtpfs
src/github.com/hanwen/go-mtpfs/main.go:13: import /tmp/packerbuild-1000/go-mtpfs-git/go-mtpfs-git/src/pkg/linux_386/github.com/hanwen/go-fuse/fuse.a: object is [linux 386 go1.1.1 X:none] expected [linux 386 go1.1.2 X:none]
==> ERROR: A failure occurred in build().
Aborting...
The build failed.

Help??

wmarshall commented on 2013-07-10 20:51

Thanks for the correction ledti.

Incidentally, I noticed that when I changed to the pacman 4.1 format, with the new pkgver() function, I changed the format of the version string enough to confuse the AUR. It turns out that version 2013.07.08 counts as *older* than 20130326, so no one has gotten the last couple updates. I put the version back into 20130708 format, so updates should now work as expected.

ledti commented on 2013-07-01 09:20

'fuse' should be added to the depends array as go-mtpfs fails without it, since it requires the fusermount binary.

Thanks for the PKGBUILD. :)

wmarshall commented on 2013-05-14 15:04

tomxtobin, did you ever get this building? I'd be glad to help any way I can, but I'll be of limited use debugging go. I've never used the language.

wmarshall commented on 2013-05-14 15:03

I updated to the pacman 4.1 format of PKGBUILD, and I moved 'go' to a build-time dependency as pulb suggested.

Anonymous comment on 2013-02-15 20:20

The build fails for me right now:

src/github.com/hanwen/go-mtpfs/mtp/mtp.go:282: undefined: NullWriter

wmarshall commented on 2013-02-13 20:36

Thanks for the feedback pulb. This is my first exposure to go, so I wasn't sure if it was needed at runtime or not. I'm reluctant to change the depends, though, since this is a git package and the tool is under active development. You're going to need go for every update, and it would be a pain to (a) have to install it anew each time, (b) have go listed as unneeded by pacman -Qtd, or (c) mark it as explicitly installed and eventually forget what depends on it and why you installed it in the first place.

Anyone else have an opinion one way or the other? I'm happy to change it to whatever people think would be most useful.