Dear Debian folks,
Am Freitag, den 23.09.2011, 21:52 +0300 schrieb Damyan Ivanov:
> Package: libmtp-common
> Version: 1.1.0-4
> Severity: normal
>
> It is annoying to see warnings about mtp-probe not being found during boot or
> USB hotplug.
I am seeing that issue too on a system where I installed `gnome`.
$ aptitude why libmtp-common
i gnome Depends rhythmbox-plugins
i A rhythmbox-plugins Depends libmtp9 (>= 1.1.0)
i A libmtp9 Depends libmtp-common
Does libmtp9 need to depend on libmtp-common and need the files packaged
in it?
$ dpkg -L libmtp-common
/.
/usr
/usr/share
/usr/share/hal
/usr/share/hal/fdi
/usr/share/hal/fdi/information
/usr/share/hal/fdi/information/20thirdparty
/usr/share/hal/fdi/information/20thirdparty/20-libmtp9.fdi
/usr/share/doc
/usr/share/doc/libmtp-common
/usr/share/doc/libmtp-common/changelog.Debian.gz
/usr/share/doc/libmtp-common/copyright
/usr/share/doc/libmtp-common/changelog.gz
/usr/share/apport
/usr/share/apport/package-hooks
/usr/share/apport/package-hooks/source_libmtp.py
/lib
/lib/udev
/lib/udev/rules.d
/lib/udev/rules.d/69-libmtp.rules
I guess the libmtp is split in libmtp-common and libmtp-runtime because
of multiarch reasons?
So should libmtp9 just recommend libmtp-runtime and libmtp-runtime
depend on libmtp-common?
Additionally, on Linux HAL is deprecated and replaced by udev. HAL is
only needed for the *BSD* stuff, if I remember correctly.
> Maybe make the udev rules not try to run that program if it is not available?
That would indeed hide the problem and not confuse users.
I hope though a “proper” solution can be found.
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
