Bug#530359: ussp-push: transition from libbluetooth2-dev to libbluetooth-dev and use of hci_remote_name

2009-06-20 Thread Hendrik Sattler
Am Freitag 19 Juni 2009 23:33:03 schrieb Filippo Giunchedi: On Sun, May 24, 2009 at 01:49:01PM +0200, Filippo Giunchedi wrote: On Sun, May 24, 2009 at 01:23:02PM +0200, Hendrik Sattler wrote: I will fix the build-depend but will not include the patch because either that function is still

Bug#530359: ussp-push: transition from libbluetooth2-dev to libbluetooth-dev and use of hci_remote_name

2009-06-20 Thread Filippo Giunchedi
On Sat, Jun 20, 2009 at 12:04:39PM +0200, Hendrik Sattler wrote: I'm not sure what you mean, libbluetooth-dev right now is 4.40 which has headers for libbluetooth3 so I don't see what needs to be changed. is there any update on this bug? Same as with obexfs, this is in the queue.

Bug#530359: ussp-push: transition from libbluetooth2-dev to libbluetooth-dev and use of hci_remote_name

2009-06-20 Thread Hendrik Sattler
Am Samstag 20 Juni 2009 12:48:40 schrieb Filippo Giunchedi: On Sat, Jun 20, 2009 at 12:04:39PM +0200, Hendrik Sattler wrote: I'm not sure what you mean, libbluetooth-dev right now is 4.40 which has headers for libbluetooth3 so I don't see what needs to be changed. is there any

Bug#530359: ussp-push: transition from libbluetooth2-dev to libbluetooth-dev and use of hci_remote_name

2009-06-20 Thread Filippo Giunchedi
On Sat, Jun 20, 2009 at 01:32:13PM +0200, Hendrik Sattler wrote: Am Samstag 20 Juni 2009 12:48:40 schrieb Filippo Giunchedi: On Sat, Jun 20, 2009 at 12:04:39PM +0200, Hendrik Sattler wrote: I'm not sure what you mean, libbluetooth-dev right now is 4.40 which has headers for

Bug#530359: ussp-push: transition from libbluetooth2-dev to libbluetooth-dev and use of hci_remote_name

2009-06-20 Thread Luk Claes
Hendrik Sattler wrote: Am Samstag 20 Juni 2009 12:48:40 schrieb Filippo Giunchedi: On Sat, Jun 20, 2009 at 12:04:39PM +0200, Hendrik Sattler wrote: I'm not sure what you mean, libbluetooth-dev right now is 4.40 which has headers for libbluetooth3 so I don't see what needs to be changed. is

Bug#530359: ussp-push: transition from libbluetooth2-dev to libbluetooth-dev and use of hci_remote_name

2009-06-20 Thread Hendrik Sattler
Am Samstag 20 Juni 2009 12:48:40 schrieb Filippo Giunchedi: On Sat, Jun 20, 2009 at 12:04:39PM +0200, Hendrik Sattler wrote: I'm not sure what you mean, libbluetooth-dev right now is 4.40 which has headers for libbluetooth3 so I don't see what needs to be changed. is there any

Bug#530359: ussp-push: transition from libbluetooth2-dev to libbluetooth-dev and use of hci_remote_name

2009-06-19 Thread Filippo Giunchedi
On Sun, May 24, 2009 at 01:49:01PM +0200, Filippo Giunchedi wrote: On Sun, May 24, 2009 at 01:23:02PM +0200, Hendrik Sattler wrote: I will fix the build-depend but will not include the patch because either that function is still available (and works) or the name of the -dev package

Bug#530359: ussp-push: transition from libbluetooth2-dev to libbluetooth-dev and use of hci_remote_name

2009-05-24 Thread Filippo Giunchedi
Package: ussp-push Version: 0.9-2 User: fili...@debian.org Usertags: bluez4-transition Hi, your package seems to build-depend on libbluetooth2-dev, however it has been deprecated in favour of versionless libbluetooth-dev, please update. Also, building the package I found that it makes uses of a

Bug#530359: ussp-push: transition from libbluetooth2-dev to libbluetooth-dev and use of hci_remote_name

2009-05-24 Thread Hendrik Sattler
Am Sonntag 24 Mai 2009 12:59:32 schrieb Filippo Giunchedi: Package: ussp-push Version: 0.9-2 User: fili...@debian.org Usertags: bluez4-transition Hi, your package seems to build-depend on libbluetooth2-dev, however it has been deprecated in favour of versionless libbluetooth-dev, please

Bug#530359: ussp-push: transition from libbluetooth2-dev to libbluetooth-dev and use of hci_remote_name

2009-05-24 Thread Filippo Giunchedi
On Sun, May 24, 2009 at 01:23:02PM +0200, Hendrik Sattler wrote: I will fix the build-depend but will not include the patch because either that function is still available (and works) or the name of the -dev package needs to change. I'm not sure what you mean, libbluetooth-dev right now is