Bug#771290: [Pkg-bluetooth-maintainers] Bug#771290: bluez-obexd package improperly Provides obexd-client, obexd-server

2014-11-30 Thread Nobuhiro Iwamatsu 
Hi!

Thanks for your report.

2014-11-28 23:55 GMT+09:00 Laurent Bigonville bi...@debian.org:
 On Fri, 28 Nov 2014 11:20:31 +0100 Laurent Bigonville
 bi...@debian.org wrote:

 bluez-obexd packages provides obexd-client, obexd-server as they are
 NOT providing the same dbus interfaces.

 Argh, broken English...

 bluez-obexd should not provides obexd-client, obexd-server as they
 are NOT exporting the same dbus interfaces.

Oh, you are right!


 [...]

 I'm not exactly sure for the Conflicts, the .service file are
 providing the same dbus interface name so I guess the conflicts
 should stay (?).

 From what I saw, if a service is already started, dbus will not try to
 start an other one providing the same name (make sense), so IMHO the
 Conflitcs must stay.

I see.

OK, I will fix this. And GNOME and KDE already shift to bluez5. I will
request removing obexd
source package from unstable.

Best regards,
  Nobuhiro

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#771290: bluez-obexd package improperly Provides obexd-client, obexd-server

2014-11-28 Thread Laurent Bigonville 
Package: bluez-obexd
Version: 5.23-1
Severity: serious

Hello,

bluez-obexd packages provides obexd-client, obexd-server as they are
NOT providing the same dbus interfaces.

obexd-client and obexd-server are porviding interfaces like
org.bluez.obex.Transfer or org.bluez.obex.Client

OTHO, bluez-obexd is providing org.bluez.obex.Transfer1 and
org.bluez.obex.Client1 (yes this is confusing).

The provide should at least be remove (and the Replaces too I guess as
they doesn't seems to provide the same file on disk).

I'm not exactly sure for the Conflicts, the .service file are providing
the same dbus interface name so I guess the conflicts should stay (?).

Cheers,

Laurent Bigonville

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#771290: bluez-obexd package improperly Provides obexd-client, obexd-server

2014-11-28 Thread Laurent Bigonville 
On Fri, 28 Nov 2014 11:20:31 +0100 Laurent Bigonville
bi...@debian.org wrote:

 bluez-obexd packages provides obexd-client, obexd-server as they are
 NOT providing the same dbus interfaces.

Argh, broken English...

bluez-obexd should not provides obexd-client, obexd-server as they
are NOT exporting the same dbus interfaces.

[...]
 
 I'm not exactly sure for the Conflicts, the .service file are
 providing the same dbus interface name so I guess the conflicts
 should stay (?).

From what I saw, if a service is already started, dbus will not try to
start an other one providing the same name (make sense), so IMHO the
Conflitcs must stay.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org