checkbox-dev team mailing list archive

[Zygmunt Krynicki <zygmunt.krynicki@xxxxxxxxxxxxx>]

Thanks for reporting this issue.

We'll have a look at all the bluetooth related APIs and see what kind
of changes we can make quickly.
The goal of the package is to be a data source for "plainbox" and
"checkbox-ng" packages. Though I must admit we haven't been releasing
them to Debian quite that often recently.

I'd like to understand how to address this bug in Debian better.
1) Should we try to synchronize this package to the latest upstream
release (bringing in many additional fixes), I guess that may not be
allowed because of the freeze
2) Should we try to disable/remove that particular test?
3) Should we try something different? What?

In addition, what is the timeline for any potential fixes? Days / weeks?

Thanks
ZK

On Fri, Nov 28, 2014 at 2:57 PM, Laurent Bigonville <bigon@xxxxxxxxxx> wrote:
> Package: plainbox-provider-checkbox
> Version: 0.3-2
> Severity: important
>
> Hello,
>
> The obex_send executable seems to use (really) old obexd dbus API that
> are not provided by any packages in the archive anymore.
>
> I'm not sure what's the goal of this package, so this might (or not) be
> RC.
>
> 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
>
> --
> Mailing list: https://launchpad.net/~checkbox-dev
> Post to     : checkbox-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~checkbox-dev
> More help   : https://help.launchpad.net/ListHelp