lp:libmtp

Created by dobey and last modified
Get this branch:
bzr branch lp:libmtp

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
VCS imports
Project:
libmtp
Status:
Development

Import details

Import Status: Failed

This branch is an import of the HEAD branch of the Git repository at git://git.code.sf.net/p/libmtp/code.

The import has been suspended because it failed 5 or more times in succession.

Last successful import was .

Import started on pear and finished taking 15 seconds — see the log
Import started on pear and finished taking 15 seconds — see the log
Import started on pear and finished taking 15 seconds — see the log
Import started on pear and finished taking 15 seconds — see the log

Recent revisions

1882. By Marcus Meissner <email address hidden>

added lenovo p70-a
https://sourceforge.net/p/libmtp/support-requests/178/

1881. By Marcus Meissner <email address hidden>

Kyocera Torque Model E6715
https://sourceforge.net/p/libmtp/feature-requests/134/

1880. By Marcus Meissner <email address hidden>

hp slate 10 hd added
https://sourceforge.net/p/libmtp/bugs/1366/

1879. By Andres G. Aragoneses

README: mention another gvfs monitor besides the gphoto2 one

In some systems[1], the gvfs-gphoto2-volume-monitor is not
the only GVFS monitor that could be hogging the device.

[1] In particular in my Ubuntu 14.04.x LTS, this is the result
of a `ps aux | grep gvfs`:
knocte1+ 2150 0.0 0.0 196640 3204 ? Sl jun25 0:00 /usr/lib/gvfs/gvfsd
knocte1+ 2157 0.0 0.0 345660 3124 ? Sl jun25 0:00 /usr/lib/gvfs/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes
knocte1+ 2403 0.0 0.0 298964 5552 ? Sl jun25 0:00 /usr/lib/gvfs/gvfs-udisks2-volume-monitor
knocte1+ 2423 0.0 0.0 285964 3376 ? Sl jun25 0:00 /usr/lib/gvfs/gvfs-afc-volume-monitor
knocte1+ 2428 0.0 0.0 212440 3456 ? Sl jun25 0:00 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
knocte1+ 2433 0.0 0.0 204936 3492 ? Sl jun25 0:00 /usr/lib/gvfs/gvfs-mtp-volume-monitor
knocte1+ 2451 0.0 0.0 433144 3636 ? Sl jun25 0:00 /usr/lib/gvfs/gvfsd-trash --spawner :1.5 /org/gtk/gvfs/exec_spaw/1
knocte1+ 2469 0.0 0.0 124728 3036 ? Sl jun25 0:00 /usr/lib/gvfs/gvfsd-metadata
knocte1+ 2479 0.0 0.0 270376 3084 ? Sl jun25 0:00 /usr/lib/gvfs/gvfsd-burn --spawner :1.5 /org/gtk/gvfs/exec_spaw/3
knocte1+ 8648 0.0 0.0 296744 4760 ? Sl 15:11 0:00 /usr/lib/gvfs/gvfsd-http --spawner :1.5 /org/gtk/gvfs/exec_spaw/4

1878. By Andres G. Aragoneses

README: use killall instead of pkill

As discussed in the mailing list[1], pkill seems not
to be working in a very typical Linux setup.

[1] http://sourceforge.net/p/libmtp/mailman/libmtp-discuss/?viewmonth=201504&style=threaded&viewday=6

1877. By Andres G. Aragoneses

autogen.sh: call ./configure at the end

Most open source projects have the convention of
just running 3 commands to install in a system:
configuration, build, installation.

The first of these steps usually consists of running
./configure (if it's a tarball) *OR* autogen.sh (if
it's a git checkout) because autogen.sh normally
calls ./configure (if NOCONFIGURE is not set).

So then in general it is expected that calling
./autogen.sh --prefix=/foo in a git checkout
has the same effect as calling
./configure --prefix=/foo in a tarball, which
was not the case before this.

1876. By Marcus Meissner <email address hidden>

tomtom rider 40
https://sourceforge.net/p/libmtp/bugs/1362/

1875. By Marcus Meissner <email address hidden>

added verizon ellipsis 7
https://sourceforge.net/p/libmtp/bugs/1359/

1874. By Marcus Meissner <email address hidden>

added lenovo k3 note
https://sourceforge.net/p/libmtp/bugs/1360/

1873. By Marcus Meissner <email address hidden>

add huawei ascend p8
https://sourceforge.net/p/libmtp/bugs/1361/

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
This branch contains Public information 
Everyone can see this information.

Subscribers